Microsoft Said To Fix PowerShell Problems with Latest Window 10 Update

Microsoft is now giving an all-clear signal, of sorts, with regard to PowerShell issues caused by a late August Windows 10 update release.

The problems arose after Microsoft released an update to Windows 10 version 1607 on Aug. 23. That update, known as "KB3176934," broke PowerShell's Desired State Configuration feature and its "implicit remoting" capabilities. Microsoft had failed to include some needed files in the Aug. 23 update, which caused the problems.

Back then, Microsoft indicated that a fix would be arriving on Aug. 30. Instead, the fix showed up in a new Aug. 31 update to Windows 10 version 1607, known as "KB3176938."

However, it took prodding from veteran Microsoft reporter Mary Jo Foley for Microsoft to simply explain that PowerShell is now considered to be fixed with the release of KB3176938. Microsoft does have a support article for this update, but it just lists "PowerShell" as one key change, without further elaboration.

Microsoft actually released three updates in August to buttress its original Aug. 2 release of Windows 10 version 1607, which is known as the "anniversary update" release. The anniversary update is notable for delivering various feature additions to the operating system. For details on those past updates, see Microsoft's history page here.

Foley was just assured that the PowerShell Desired State Configuration issue was fixed. Apparently, the PowerShell implicit remoting problem also is fixed. Microsoft's Aug. 23 PowerShell blog post was updated recently and it includes a terse comment at the end from the PowerShell Team claiming that the PowerShell issues were resolved.

KB3176938 just delivers some "quality improvements" to Windows 10 version 1607. The update contains "no new operating system features," according to Microsoft's bare bones support article.

On the Azure PowerShell front, Microsoft announced late last month that some changes introduced in Azure PowerShell version 1.4 were "breaking changes," which also affected later versions of the scripting tool. To fix the problems, an Azure PowerShell version 1.7 hotfix was released.

About the Author

Kurt Mackie is senior news producer for 1105 Media's Converge360 group.


comments powered by Disqus

Subscribe on YouTube