Windows 10: Different kinds of Powershell?

I've recently used Powershell, but there appear to be several different versions of this utility. Some of them work--some of them merely report not being able to find something or call up something else. For instance, when I call up Powershell from an elevated command prompt, Powershell does not let me use a script to retrieve the chkdsk log. However, when I click the search button and bring up Windows Powershell (x86), Powershell appears in a dark-blue window and does work when I paste the same command. And it seems these versions of Powershell are located in different places.



So what are the differences between these apparent different versions of Powershell?


:)

 

getting all kinds of different BSOD

What is your computer make and model? If not a branded computer what is your motherboard make and model?



Please download and run Driver View and upload a copy of the report it produces to your OneDrive. To get a report on all drivers select Edit, Select All followed by File, Save Selected Items. Text file format please, HTML files are less easy
to work with.

DriverView: Loaded Windows Drivers List



Please provide a copy of your System Information file. To access your System Information file select the keyboard shortcut
Win+R, type msinfo32 and press the ENTER
key. Select File, Export and give the file a name noting where it is located.
Files in the txt file format are preferred. Do not place the cursor within the body of the report before exporting the file. The system creates a new System Information file each time system information
is accessed. You need to allow a minute or two for the file to be fully populated before exporting a copy. Please upload the file to your OneDrive, share with everyone and post a link here.



For help with OneDrive see paragraph 9.3:

gerrys template

 

getting all kinds of different BSOD

I have been have BSOD issues lately and cant figure out the problem I did a driver verifier test to get mini dumps but I don't know how to read them. can someone help. I have my minidumps here

https://www.dropbox.com/s/cbhb03czuzn1ji7/dmp.rar?dl=0

 

The reason you can at the moment not run your scripts when running PowerShell (PS) from Command Prompt (CP) is most probably the execution policy set by the system; by default it is restricted. You need to launch the PS in CP with the ExecutionPolicy switch telling what kind of policy you want to be used, for instance Unrestricted. As I have changed the policy earlier, for this screenshot below I deliberately set it first to Restricted to show you an example:

• #1 = Checking the current execution policy, noticing it's Restricted. Exiting PS
• #2 = Launching the PS again, this time setting the policy to Unrestricted
• #3 = Checking the current execution policy again, now it is Unrestricted.

The ISE (Integrated Script Editor) version of the PS is just PS on steroids *Wink. You can for example open multiple tabs and do some other stuff not possible in the traditional PS (click the screenshot to enlarge):




The x86 versions of PS and PS ISE are what the name says, 32 bit versions made available on 64 bit Windows. Basically they are useless for you, I have difficulties to think even a single scenario where you would need a 32 bit PS instead of a 64 bit in modern Windows.

By the way, as you are interested in PowerShell, did you know that with it you can install most of your software, install all applications with one command, silently in the background without any user interaction, without any "Click Next", "Click Install", "Click this", "Would you also like to install that" and without any unwanted content being installed? Check the tutorial: PowerShell OneGet - Install Apps from Command Line - Windows 10 Forums

 

Thank you, Kari, for this explanation. I've set the execution policy to unrestricted (I confirmed that after the initial command wouldn't work), but I can't get this command--get-winevent -FilterHashTable @{logname="Application"; id="1001"}| ?{$_.providername –match "wininit"} | fl timecreated, message | out-file Desktop\CHKDSKResults.txt--to work when I bring up PS from an elevated CP, even with the policy is set to unrestricted. It does work, however, in Powershell ISE (x86) and Powershell x86. Any idea why? Thanks again.

 

This is very simple. When you run Powershell in an administrative prompt, your "current directory" defaults to C:\Windows\System32

When you run it from an icon, it's not running in administrative mode, and the default "current directory" is your user profile..

There is no "Desktop" directory under C:\Windows\System32, which is what the error is telling you. You're telling it to output to a file that cannot exist because the directory does not exist. There is, however, a desktop directory in your user profile.

If you look closely at the error, it tells you exactly what the problem is. "DirectoryNotFoundException"

 

Thank you, Mystere. So is it then possible to change the directory so that PS works in my administrative prompt? Or do I change the command to reflect the current directory?

 

Just edit your command by changing the path where the file will be written. At the end of the command line you have now path as Desktop\CHKDSKResults.txt.

Change it as you wish, for instance C:\Users\YourUserProfileName\Desktop\CHKDSKResults.txt would write the file to your desktop.

 

Thanks, Kari. Works perfectly! *Cool

 

You are welcome *Smile