Microsoft published an article giving consumers ‘five reasons why you should install the Windows 10 Anniversary Update‘ on its website before the rollout began in August. I had some opinions too. However, since then it’s given Windows 10 users at least three reasons to be wary of updates. There was the mystery freezing issues and broken USB-connected webcams.
The latest came on Tuesday, when Microsoft rolled-out a cumulative patch for the Anniversary Update that broke PowerShell, its command line shell and scripting language. The notes accompanying the release suggest Microsoft knew the changes would stop several PowerShell features from working.
You’d be forgiven for thinking Microsoft is actively trying to stop people using Windows 10 Anniversary Edition.
KB 3176934, released on Tuesday as an automatic update, addresses a good number of bugs and other oddities in the operating system, including:
Improved reliability of Network Controller, DNS server, gateways, Storage Spaces Direct, Group Managed Service Accounts, remote procedure calls (RPC), PowerShell, Internet Explorer 11, printer pairing and interoperability, the Windows kernel, Media Core, Windows Store, Connected Standby, Cluster Health service, the Hypervisor debugger and platform, and Active Directory.
Improved performance of Storage Spaces Direct with many nodes or disks, scrolling lists on Xbox One, DHCP address acquisition, Active Directory queries, and Cluster Health service.
It doesn’t, however, fix up webcams blinded by video streaming changes made by Redmond – nor does it prevent computers freezing entirely.
Instead, it just made matters worse by breaking Microsoft’s scripting and automation platform PowerShell. Specifically, it borked PowerShell’s Desired State Configuration (DSC), which is useful for managing and controlling networks of PCs and systems in an automated way.
“Due to a missing .MOF file in the build package, the update breaks DSC. All DSC operations will result in an ‘Invalid Property’ error,” an advisory from the PowerShell team reads.
Of course, if you haven’t yet installed the Anniversary Update on your PC, you’re not experiencing any of the problems listed above. The simple fix for the PowerShell issues is to uninstall KB3176934, which you can do with the following PowerShell command:
wusa /uninstall /kb:3176934
If you want to stick it out, Microsoft is promising that the issue will be fixed in the next update to Windows 10, which is slated to arrive on August 30.