A few updates as people have mentioned: • Though Powershell ISE comes pre-installed, it is no longer in active feature development. Instead it's officially recommended to use Visual Studio Code with the Powershell Extension • Turns out the .NET "Core" name was simply dropped, and it's now just called .NET (though from my understanding, it is still a subset of the overall ".NET Framework")
It's no longer a subset. The reason the Core moniker was dropped was exactly to stop conveying this idea which was true during the Core development days. The .Net Framework is no longer being developed, and the last long-release version (.Net Framework 4.8) is only receiving maintenance patches. .Net is now the sole framework development trunk. It started at version 5, exactly to promote the idea of continuity. It's a tragicomedy the overly complicated way many companies these days handle their product development versioning schema.
@@kreont1 If we gonna go to the future we cant stick to 1981 software we need new software for the future not a 40 year old terminal we cant stick to CMD forever.
I am glad this video was made because when my PC starts I run a PS Script that sets up what I will be doing at least for the first few hours of my morning. I also have another Script I enable when I know ahead of time that say I'll be gaming all day so it stops a LOT of unnecessary processing that would normally run in the background from applications like Adobe, Autodesk, Microsoft Notepad, etc.. I'll definitely take a look at the changes and see if I can optimize some of it or it it's just as efficient without let it continue to do the thing with the funny characters I type on the picture box I sit in front of for 18 hours a day ...lmao. Cheers! Stay Healthy and Stay Sane!
I just cannot believe that this is the same guy that told me to charge me phone with aluminium foil, this is no man's sky level come back but for a youtuber
I'm glad you made this video! I was using the new Terminal app in Windows and then I was getting the prompt to "update to the latest Powershell". So I was very confused for a hot minute there.
Ah, that explains a lot... I was having trouble settling up something that said I should use Powershell 7, as I ignored that, assuming that I had the latest version. Because that's how Windows 10 normally works.
@@dekrain I'd assume that means you use it to run build scripts for various .net projects. But does it provide anything over and above bash or any other Linux based shell?
@@anon_y_mousse and by .NET stuff I meant working with .NET objects, reflection, etc. Powershell doesn't by default have rich completion for different programs (but maybe that can be changed?) and can be a bit slow at times, but it could be a good candidate for text processing, batch processing, and other things.
@@dekrain So using it to make tiny glue programs then to automate various tasks? Like using dialog with bash? And yeah, rich completion is pretty cool. I often forget how to spell various long switches with wget and rich completion is a godsend.
There are fewer differences between pwsh (PowerShell 7) on Windows and Linux than there are between pwsh and PowerShell, a lot of the Windows exclusive stuff, mainly WMI objects has been stripped
Yeah I think you're roughly 2-3 years late at this point. There's been some cool stuff covered. Pretty sure he did a joke video in the middle of it also as a throwback.
To be honest, I hate the confusing mess they've made with this. My work laptop with ISE has a bunch of scripts open in its session that I need to move, a separate Powershell 7 install that isn't even fully compatible with all of my existing modules, and VS Code which is incredibly sluggish compared to the aforementioned. Better yet, we use folder redirection in our DDP GPO, so for every command, IntelliSense, or every little trigger, I have to wait for it to scan UNC shares because I cannot remove the default Documents PSModulePath (workaround for me is running a script to manually set the path for every launch and even periodically). We've been waiting years to even get the option of removing PSModulePath out of the Documents folder.
How do I get the old gui directory indicator? For me it just says PS C:\Users without the fancy graphics. Back when it didn't open in windows terminal it still had it but now it's gone
Maybe I'm being picky but it's a bit of a stretch to say 'replaced by'. They were both in development simultaneously and they stopped development for ISE. It is still being included and they don't intend on removing it.
I have the PowerShellPreview, Being honest i just install it because it was purple :v and with the nerdfont the winfetch and the oh my posh looks really nice....
Yep, today I just noticed that apparently installing Powershell 7 updated .Net to 7 (??). In any case, the newer version of .Net removed some method from a system class and that broke an important component underlying much of my code base. So, I'm just trying to work here. That kind of thing is indeed undesirable.
@ThioJoe I love your videos, they are all so informative and useful. I would like to make one suggestion though. If you are talking about some software that could be/needs to be downloaded it would be helpful to put the links to where to download the software in your video description box. That being said, where can I download Powershell core or any of the other versions? Additionally could you do a video about how to set up the Powershell window so that it doesn't just look like the command prompt? For example, the blue background, plus any sorts of side panels that might give any sort of line numbering or formatting types of things. When I open my Powershell it looks just like the command prompt with black background and white text.
Hi ThioJoe I watch a video on PIA VPN you did, in which you recommended it and for that reason alone I began using it. My question is why did you recommend it. When I turn it on and use it I can not stream some services like Netflix or Amazon Prime. For that reason alone I would not recommend it. Another reason is that I have notified PIA of my problem and it has not been fix, only getting the response that it is my fault.
I installed Powershell 7. Is there a way to tell if a program will require administrator privileges and escalation or not? For example, some programs executables and msi files require administrator priviles to run and others do not. For example Google Chrome's msi can install Chrome without administrator privileges. Is there a way to evaluate whether Chrome can be installed on a computer by analyzing the msi file for example?
Maybe a developer would be better to answer this but I think that's a bit more complicated than a first glance at the file. I'm pretty sure it can be compiled as a user based install and only target user-accessible folders like AppData. I'm thinking that once it wants to target root:\Program Files*, it's going to need admin regardless.
Question... can PowerShell be completely removed from Windows 10? (All versions) Or does Windows utilize PowerShell for background tasks? (ie: Updates)
my approach to understand powershell is, it's like bash, works on linux like bash works on windows, has a executable file .ps1 like bash has a executable file .sh. And I know nothing about both, somebody cmiiw
Sir you talk about windows 10 and 11 power shell But windows server 19 and 22 use diff version? Means server has some features such as active directory Creates multiple user gives permission . So server use diff version of power shell ?
I don't think it's about the scripts.. It's probably rather about the cmdlets, which are written in C#. A dotnet core (or 5.0 or newer) dll file can't be used with dotnet Framework or the other way around.
@@bazoo513 I'm no expert, but I assume PS 7 has most cmdlets from WPS, so most script can be run on one or the other. It's just if the PS environment doesn't have the cmdlet you run into problems. I think the cmdlets can be thought of as programs you can run from the cli or scripts, but that are part of, or plugins of PS. Isn't _ls_ on Linux an actual program? Or is it part of bash?
@@phizc bash (and other shells) do have some simple built-in commands (which usually also have program equivalents, so that they can be used from other programs without the overhead of starting shell process), but most lines of your script will probably invoke "ordinary" programs. It's just that great care is excercised to avoid upgrades breaking old scripts. As the result, there are now several interchangeable syntaxes for, say, command substitution and such. I hope that this retention of the old version of PS if just for the peace of mind of corporate users, not actual neccesity.
A few updates as people have mentioned:
• Though Powershell ISE comes pre-installed, it is no longer in active feature development. Instead it's officially recommended to use Visual Studio Code with the Powershell Extension
• Turns out the .NET "Core" name was simply dropped, and it's now just called .NET (though from my understanding, it is still a subset of the overall ".NET Framework")
It's no longer a subset. The reason the Core moniker was dropped was exactly to stop conveying this idea which was true during the Core development days. The .Net Framework is no longer being developed, and the last long-release version (.Net Framework 4.8) is only receiving maintenance patches. .Net is now the sole framework development trunk. It started at version 5, exactly to promote the idea of continuity. It's a tragicomedy the overly complicated way many companies these days handle their product development versioning schema.
Oh, you need to install PowerShell manually on xp
PS = power shit. CMD or terminal is king.
Please make a video
About Microsoft Excel full tutorial in one video
And please use excel with fully dark theme
@@kreont1 If we gonna go to the future we cant stick to 1981 software we need new software for the future not a 40 year old terminal we cant stick to CMD forever.
If your company’s IT ADMIN needs to be taught Infrastructure after XP, I think it’s time to upgrade the entire IT Department 😂
🤣
No kidding. Lol.
I think that if the company is using windows they really need to upgrade to linux… ngl
@@lexicled That is a hard truth that many need to learn.
And they have to install powershell manually back when they set up in 2008 (at least it was included in windows 7).
Never expected PowerShell lore to be this deep tbh.
Dotnet core is now just called dotnet , I suspect that's the reason for powershell core got changed to powershell
Makes sense
I am glad this video was made because when my PC starts I run a PS Script that sets up what I will be doing at least for the first few hours of my morning. I also have another Script I enable when I know ahead of time that say I'll be gaming all day so it stops a LOT of unnecessary processing that would normally run in the background from applications like Adobe, Autodesk, Microsoft Notepad, etc.. I'll definitely take a look at the changes and see if I can optimize some of it or it it's just as efficient without let it continue to do the thing with the funny characters I type on the picture box I sit in front of for 18 hours a day ...lmao. Cheers! Stay Healthy and Stay Sane!
"Is it possible to learn this power?"
You playing all day ??? Does it expensive???
@@fixer1140 yeap but for what
I normally use it in the same way I used Command Prompt, but also use the ISE to make a script that can automate some of those tasks.
I was randomly searching about this today because of that message on the terminal! Glad you made a video about this to talk about this as well!
2 days ago, this mess was struggling in my head
now you've uploaded this, what a time
I just cannot believe that this is the same guy that told me to charge me phone with aluminium foil, this is no man's sky level come back but for a youtuber
You are amazing I am amazed how much effort you put into the little things in every video I appreciate your effort mate! 👍👍👍👍
awesome video again! explaining windows in detail for everyone, one-by-one :)
I'm glad you made this video! I was using the new Terminal app in Windows and then I was getting the prompt to "update to the latest Powershell". So I was very confused for a hot minute there.
I was just wondered about PowerShell a few days back. And here you are... What a coincidence
Ah, that explains a lot... I was having trouble settling up something that said I should use Powershell 7, as I ignored that, assuming that I had the latest version. Because that's how Windows 10 normally works.
Quick points... .NET Core is a superset to .NET Framework as Core contains Framework as well as Core. Also "winget install powershell". Great video!
It's neither. Dotnet framework has things that are missing from dotnet core and vice versa.
What about normal Powershell vs Powershell for Visual Studio Community 2022?
I like the prompts you set in those consoles. How can we set the same?
Ah yes PowerShell and PowerShell Core! I switched to PowerShell core, because it's overall better than the old legacy version.
Awesome video. Windows power shell is the most useful tool ever for me lol .
I love to know if anyone uses PowerShell on Linux and what their experiences with it are like.
I've used it on Linux a bit, but mostly for stuff related to .NET itself, rather than everyday tasks. But it has some nice things to it
@@dekrain I'd assume that means you use it to run build scripts for various .net projects. But does it provide anything over and above bash or any other Linux based shell?
@@anon_y_mousse and by .NET stuff I meant working with .NET objects, reflection, etc. Powershell doesn't by default have rich completion for different programs (but maybe that can be changed?) and can be a bit slow at times, but it could be a good candidate for text processing, batch processing, and other things.
@@dekrain So using it to make tiny glue programs then to automate various tasks? Like using dialog with bash? And yeah, rich completion is pretty cool. I often forget how to spell various long switches with wget and rich completion is a godsend.
There are fewer differences between pwsh (PowerShell 7) on Windows and Linux than there are between pwsh and PowerShell, a lot of the Windows exclusive stuff, mainly WMI objects has been stripped
Today I had a problem with Windows PS VS PS. Turns out the WPS generates files using UTF-16 and PS uses UTF-8.
What!? I could have sworn it was always UTF-8. Well, you never know. lol
Exactly what I was looking for!
Does thio make serious videos now? I swear I remember some of his older videos being about how to downlaod more RAM
Yes. I believe he even made an apology video for his old videos
Yeah I think you're roughly 2-3 years late at this point. There's been some cool stuff covered. Pretty sure he did a joke video in the middle of it also as a throwback.
Outstanding!
Great video. How is Windows Powershell updated then as I see updates in WSUS for 7 but not the inbuilt version? Is this part of the .net updates?
@ThioJoe how did you put that cool background in your PowerShell?
but how do you make powershell echo (print) stuff on the same line
i wanna rewrite my batch program in powershell
any help?
Write-Host "text" -NoNewline
Note, I'm no expert. This is just what I found out by googling.
@@phizc cool thanks
Thanks for the info on Powershell.
Nice material!
To be honest, I hate the confusing mess they've made with this. My work laptop with ISE has a bunch of scripts open in its session that I need to move, a separate Powershell 7 install that isn't even fully compatible with all of my existing modules, and VS Code which is incredibly sluggish compared to the aforementioned.
Better yet, we use folder redirection in our DDP GPO, so for every command, IntelliSense, or every little trigger, I have to wait for it to scan UNC shares because I cannot remove the default Documents PSModulePath (workaround for me is running a script to manually set the path for every launch and even periodically). We've been waiting years to even get the option of removing PSModulePath out of the Documents folder.
How do I get the old gui directory indicator? For me it just says PS C:\Users without the fancy graphics. Back when it didn't open in windows terminal it still had it but now it's gone
The ISE is replaced by Visual Code Studio…
Maybe I'm being picky but it's a bit of a stretch to say 'replaced by'. They were both in development simultaneously and they stopped development for ISE. It is still being included and they don't intend on removing it.
Thanks for your sharing
The Powershell ISE is replaced with the Powershell extension on Visual Studio Core after version 6 I think
Informativ video! Thanks :D
I have the PowerShellPreview, Being honest i just install it because it was purple :v and with the nerdfont the winfetch and the oh my posh looks really nice....
I literally went to install PowerShell 7 today just because Windows PowerShell does not support running multiple commands in one line with &&
Looking at the weather where you live. You're getting toasted
I don't have the upgrade option displayed. Is there another way to do the upgrade ?
how did you get that blueprint-ish background on your powershell
I'd love to know as well
I learnt something! Thank you.
Wheres the video that talk about cmd and powershell ?
Great Video! 👍
Sweet video. Installed PowerShell 7. Can you share your animated wallpaper? Peace
Is that why the powershell on Arch GNU/Linux So different than what I used to use with Windows
Yeah
I know its unrelated but I would really like if you would make a video on Bitwarden Password Manager
Got it, thanks.
what is Laravel Filament and how to use it?
Can you cover power toys if anything changes from 2 years ago?
amazing video!
Yep, today I just noticed that apparently installing Powershell 7 updated .Net to 7 (??). In any case, the newer version of .Net removed some method from a system class and that broke an important component underlying much of my code base. So, I'm just trying to work here. That kind of thing is indeed undesirable.
Can you run multiple versions on 1 system
TNice tutorials man did a really good job of explaining ever tNice tutorialng ever one else don't really go into detail
how do i get the return line to look like yours?
@ThioJoe I love your videos, they are all so informative and useful. I would like to make one suggestion though. If you are talking about some software that could be/needs to be downloaded it would be helpful to put the links to where to download the software in your video description box. That being said, where can I download Powershell core or any of the other versions? Additionally could you do a video about how to set up the Powershell window so that it doesn't just look like the command prompt? For example, the blue background, plus any sorts of side panels that might give any sort of line numbering or formatting types of things. When I open my Powershell it looks just like the command prompt with black background and white text.
Nice clearly explained :)
Call me silly, but I think with the Microsoft naming scheme, the next version of windows will just be "Windows".
Hi ThioJoe I watch a video on PIA VPN you did, in which you recommended it and for that reason alone I began using it. My question is why did you recommend it. When I turn it on and use it I can not stream some services like Netflix or Amazon Prime. For that reason alone I would not recommend it. Another reason is that I have notified PIA of my problem and it has not been fix, only getting the response that it is my fault.
That explains a lot
Can Android os has its cmd prompt.?
But user did not get ?
Thanks tNice tutorials helps alot man!!
Any recorded gui for power shell.
Thanks!
Right On, TJ~
Good video.
3:22 XP, God forbid 😂
Back when our computers were ours!
True horror
@@ThioJoe Trueeeee
Todd Howard - "It just works."
@@ScorpionCar still use it?
what is the best cloud type
with 22H2 is labeled as Terminal
@Albert Escanes on windows 11 version 22H2 when right click on start will be Terminal instead Windows Powershell
Use visual studio code as a core ise
The Powershell ISE is, as far as I know, discontinued (without any replacement)
Visual Studio Code with a PowerShell add-in is the replacement.
@@Lofote oh yes ofc, I never really thought of it like that but obviously that's it. 😅
Thank you very much 💪🏼👍🏼
just what I wanted.
I installed Powershell 7. Is there a way to tell if a program will require administrator privileges and escalation or not? For example, some programs executables and msi files require administrator priviles to run and others do not. For example Google Chrome's msi can install Chrome without administrator privileges.
Is there a way to evaluate whether Chrome can be installed on a computer by analyzing the msi file for example?
Maybe a developer would be better to answer this but I think that's a bit more complicated than a first glance at the file. I'm pretty sure it can be compiled as a user based install and only target user-accessible folders like AppData. I'm thinking that once it wants to target root:\Program Files*, it's going to need admin regardless.
I uninstalled 'Powershell 2.0" from Add and Remove Programs. 🙄🙄
Question... can PowerShell be completely removed from Windows 10? (All versions)
Or does Windows utilize PowerShell for background tasks? (ie: Updates)
Have you don a ' what is power shell ' please ? as I don't know !....cheers.
took me 8 mins into the vid to realize its a little hot outside according to your desktop
When the new PS cannot replace the older "included' PS w/o breaking things, then It's Internet Explorer in the making all over again.
It's just Great!
bruh my school blocked every command interface except powershell ise XD
I don’t understand why more sysadmins don’t learn PowerShell. It’s like intentionally keeping one arm handcuffed behind your back.
Lol! Thankfully I don't have touch screen! I can just use my mouse to Push the Like button :")
my approach to understand powershell is, it's like bash, works on linux like bash works on windows, has a executable file .ps1 like bash has a executable file .sh. And I know nothing about both, somebody cmiiw
A Shell that gives you power
Not that Microsoft has made PowerShell the least bit confusing or has been anything but totally consistent with it. 😉
at least its not as confusing as USB naming scheme
I can confirm powershell core doesn't run everything windows powershell does
Companies spending money on tech training… you should go into comedy! Lol
I prefer a graphical shell over a command line shell.
ATT does the same the same thing every so often. Rather annoying. Thank ThioJoe
i still like command prompt classic.
Windows PS vs PS Core. Which one is worse?
Sir you talk about windows 10 and 11 power shell
But windows server 19 and 22 use diff version?
Means server has some features such as active directory
Creates multiple user gives permission . So server use diff version of power shell ?
10:56 Hey, I just need a new Monitor 🥲
wow theres a newer version of powershell? how cool... procedes to use git bash
PowerShell is RA-C-IST, how do you think WeakShell feels
You owe me a monitor.👍
fora youu too
So, Powershell is not expected to be upwards compatible, even by Microsoft? Sad. I _never_ heard of new version of bash breaking old scripts...
I don't think it's about the scripts.. It's probably rather about the cmdlets, which are written in C#. A dotnet core (or 5.0 or newer) dll file can't be used with dotnet Framework or the other way around.
@@phizc Well, scripts consist of cmdlets, don't they?
@@bazoo513 I'm no expert, but I assume PS 7 has most cmdlets from WPS, so most script can be run on one or the other. It's just if the PS environment doesn't have the cmdlet you run into problems.
I think the cmdlets can be thought of as programs you can run from the cli or scripts, but that are part of, or plugins of PS.
Isn't _ls_ on Linux an actual program? Or is it part of bash?
@@phizc bash (and other shells) do have some simple built-in commands (which usually also have program equivalents, so that they can be used from other programs without the overhead of starting shell process), but most lines of your script will probably invoke "ordinary" programs.
It's just that great care is excercised to avoid upgrades breaking old scripts. As the result, there are now several interchangeable syntaxes for, say, command substitution and such.
I hope that this retention of the old version of PS if just for the peace of mind of corporate users, not actual neccesity.
Your great