I there a way to force Windows to use PS 7 instead of the old 5?

garlin said:

IFEO is a Window debugging function for devs

Click to expand...

garlin said:

Post #5 was the reg files...

Click to expand...

LesFerch said:

Not correct. Most PowerShell scripts will get interpreted by whatever version of PowerShell is the default for running PS1 files. Of course, if the script is run by another process, that process can specify powershell.exe or pwsh.exe but it doesn't have to.

Edit: There isn't a default interpreter for PS1 files. You cannot double-click PS1 files. You have to right-click and "Run with PowerShell" or open a PowerShell window and run the script. However, you could set an Image File Execution option (as noted by @garlin) so that "Run with PowerShell" runs pwsh.exe instead of powershell.exe, but that would not be a good idea.

Since PowerShell.exe existed long before pwsh.exe, changing the default (via IFEO) is guaranteed to be a problem at some point. It could only work correctly if pwsh.exe were 100% backwards compatible with powershell.exe. It definitely is not.

Click to expand...

1. Open Settings: Press the Windows key + I to open the Settings app, or click the Start button and select Settings.
   
   
2. Go to Default Apps: Click on Apps in the left-hand panel, then select Default apps.
   
   
3. Search for the File Extension: In the search bar under "Set defaults for applications," type the file extension you want to change (ps1,ps1xml,psc1,psd,psd1,psm1,psc,") and press Enter.
   
   
4. Change the Default App: Click on the current default app listed for that file type. (if not listed browse for it
   
   
5. Select Your App: In the "Choose an app" window, select the program you want to use as the default for that extension. If the app isn't listed, you may need to install it or search the Microsoft Store.
   
   
6. Set as Default: Click Set default to confirm the new association.
7. so now you set the new PowerShell 7to be the default one ta da

AlterNate37 said:

Hi,

because of other issues which I'm addressing in another thread I've realized that in my System there is Windows Powershell 5.1, and PowerShell (Core?) 7.5.
When I installed PS7 I've used Chris Titus Utility to make it be the default PS, but it doesn't seem to have worked.
When I evoke PS from Win+X by clicking on "Windows PowerShell (Admin)" (or also the non admin) what opens is the older PS, which has a lighter blue icon.
The new PS is triggered by default only in Terminal.

I was told that trying to forcibly uninstall PS5 can mess up the system. I was told that eventually I can try renaming the exe of PS5 so it can't be triggered anymore, but I wonder if that means that nothing would be triggered or that the system would automatically look for PS7.

I wish to reach two things:
1. that every and each single time where the system or some program needs to run PS, they'll evoke PS7 and not PS5. Or at least that they do whenever possible.
2. that all entries about PS in Win+X are about PS7 and not PS5, or at least that both of them are present (if it's not possible to have only PS7).

How do I achieve that?

I've tried removing PS5 in the environment variables, and pushing up PS7. No idea if I did it properly, but it doesn't seem to be having any effect.

Thanx

Click to expand...

garlin said:

While you can do this, it breaks the security norm for PS that it doesn't have a default file type handler. And you're forced to explicitly call a script instead of simply clicking on a .ps1 file in Explorer.

It's a personal choice, but be warned it's less secure as PS was deliberately designed not to be clickable or run without invoking powershell.exe or pwsh.exe by name.

Click to expand...

How to remove powershell ads and update checks in the Windows Terminal?

When I start the Windows Terminal, I get the following: How do I get rid of the copyright & version notifications, the help URL and the update check? I just want to get to the command line. My

stackoverflow.com