You might already have noticed the Night Light bugs but the update has also broken PowerShell for a few users. This update replaced the Command Prompt with the PowerShell. In doing so, it broke a few things. When you open PowerShell it shows gibberish instead of legible text. Here’s how to fix broken PowerShell in Windows 10. Even though Microsoft significantly improved the shell interface of PowerShell in Windows 10, I still prefer PowerShell ISE for most command-line tasks. For some reason, Microsoft hid this nifty Integrated Development Environment (IDE) even better in Windows 10. If you type “PowerShell” in the. Of late, Windows 10 users who have been facing some problems, may have read a lot of time, run this or that command in PowerShell to fix this or that problem. While most of us are familiar with.

-->

If you are using Windows 10 Anniversary Update, or Windows Server 2016, you should already have Windows PowerShell 5.1. That's because this application comes preinstalled with those operating systems.

To determine which version of Microsoft PowerShelll you are using, do the following on your Windows 7 or Windows Server 2008 R2 or Windows Server 2012 computer:

Click Start, click All Programs, click Accessories, click Windows PowerShell, and then click Windows PowerShell.
In the PowerShell console, type the following command and then press ENTER:
Information similar to the following should then be displayed in the console window:
If the returned Version number is 5.1, then you are running Windows PowerShell 5.1. If the returned Version number is not 5.1, then you'll need to install Windows PowerShell 5.1. You can download Windows Management Framework 5.1, which includes Windows PowerShell 5.1, from the Microsoft Download Center.

After you've verified that Windows PowerShell 5.1 is installed, you must make sure that PowerShell has been configured for running remote scripts. To do that, start PowerShell as an administrator. On Windows 7, Windows Server 2008 R2, Windows Server 2012, or Windows Server 2012 R2 do the following:

Click Start, click All Programs, click Accessories, click Windows PowerShell, right-click Windows PowerShell, and then click Run as administrator.
If the User Account Control dialog box appears, click Yes to verify that you want to run PowerShell under administrator credentials.

If you are running Windows 8, complete this procedure instead:

Access the Charms bar, click Search, and then right-click Windows PowerShell. You can quickly access the Charms bar on any Windows 8 computer (touch screen or non-touch screen) by holding down the Windows key and pressing C.
In the toolbar at the bottom of the screen, click Run as administrator.
If the User Account Control dialog box appears, click Yes to verify that you want to run PowerShell under administrator credentials.

After PowerShell is running, you must change the execution policy to allow the running of remote scripts. In the PowerShell console, type the following command and then press ENTER:

Windows Powershell Admin Windows 10

Note

When you run the preceding command, you might receive the following error message:> Set-ExecutionPolicy : Access to the registry key'HKEY_LOCAL_MACHINESOFTWAREMicrosoftPowerShell1ShellIdsMicrsoft.PowerShell' is denied. This error message typically occurs if you are not running PowerShell under administrator credentials. Close your session of PowerShell, and start a new session as an administrator.

To verify that the execution policy has been configured correctly, type the following at the PowerShell prompt and then press ENTER:

If you get back the following value, then everything has been configured correctly:

RemoteSigned

If you are not currently running Windows PowerShell 5.1, you'll also need to download and install Windows Management Framework 5.1 from the Microsoft Download Center. This is an installation package that includes Windows PowerShell 5.1 and Windows Remote Management (WinRM) 3.0. This installation package might be required if you, for example, are running Windows 7 SP1 and have not yet updated to Windows PowerShell 5.1. If you are running Windows Server 2016, or Windows 10 Anniversary Update, there should be no need to install Windows PowerShell 5.1. Windows PowerShell 5.1 comes preinstalled on those operating systems.

Before installing Windows Management Framework 5.1:

Make sure you have downloaded the correct version of the installation package. If you are running the 64-bit version of Windows 7 SP1, download the file Win7AndW2K8R2-KB3191566-x64.ZIP. If you are running the 32-bit version of Windows 7, download the file Win7-KB3191566-x86.ZIP.
If you are running Windows 7 on your computer, make sure that you have installed Windows 7 Service Pack 1.

If you aren't sure which version of Windows you are running, or you aren't sure if you've installed Windows 7 Service Pack 1, click Start, right-click Computer, and then click Properties. This information will be reported in the System dialog box.

To install Windows Management Framework 5.1, complete the procedure in Install and Configure WMF 5.1.

After the computer has rebooted, verify that Windows PowerShell can start and that the application can be run under administrative credentials. To do this:

Click Start, click All Programs, click Accessories, click Windows PowerShell, right-click Windows PowerShell and then click Run as administrator.
If the User Account Control dialog box appears, click Yes to verify that you want to run PowerShell under administrator credentials.

When the PowerShell console appears, you should then verify that the WinRM service is running and has been configured correctly. To verify that the service is running, type the following command at the PowerShell prompt and then press ENTER:

Information about the WinRM service will then be displayed on screen:

If the service Status does not equal 'Running', start the WinRM service by typing the following command and then pressing ENTER:

Windows Powershell For Windows 10 Recovery

After the service has started, run the following command to make sure that WinRM is using Basic authentication:

Information similar to the following will be displayed onscreen:

If basic authentication has been set to true, then you're ready to use PowerShell to connect to Skype for Business Online.

Tip

New to Office 365?

Discover free video courses for Office 365 admins and IT pros, brought to you by LinkedIn Learning.

Windows Powershell Admin Windows 10

Windows Powershell For Windows 10 Recovery

Download Windows Powershell For Windows 10

Related topics