This article describes issues that occur when you run the Set-PSDebug cmdlet or Windows PowerShell scripts in Windows 8, Windows RT, or Windows Server 2012. A hotfix is available to resolve this issue. Check out the list of issues that are fixed in this hotfix.
Issues that are fixed in this hotfix
Issue 1
When you run Windows PowerShell scripts by using Task Scheduler tool, the scripts fail occasionally.
Issue 2
Consider the following scenario:
-
You have a computer that is running Windows 8, Windows RT, or Windows Server 2012.
-
You add the Set-PSDebug cmdlet at the top of a Windows PowerShell script to trace the script lines.
In this scenario, the debug trace only shows for the line right after the Set-PSDebug cmdlet. If you use the Windows PowerShell command-line interface to run the script, the debug trace is correct after the script runs for the first time.
Resolution
To resolve this issue, install update rollup 2984005. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
2984005 September 2014 update rollup for Windows RT, Windows 8, and Windows Server 2012
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
More Information
For more information about the Set-PSDebug cmdlet, go to the following Microsoft website:
General information about the Set-PSDebug cmdletFor more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates
