Last week, Microsoft re-released Windows 10 Build 14393.82, but it appears that they missed one small but important file. The update package doesn’t include a single .MOF package, which results in a broken Desired State Configuration in PowerShell.
“On August 23, Windows update KB3176934 released for Windows Client,” Says the PowerShell Team. “Due to a missing .MOF file in the build package, the update breaks DSC. All DSC operations will result in an ‘Invalid Property’ error.”
It also breaks the implicit remoting feature, which allows users to work on a session away from their usual desktop or notebook. When trying to run the command, a “Could not load type ‘System.Management.Automation.SecuritySupport” error is given.
The build released to the Insider ring four days before the public, so it’s surprising that Microsoft didn’t notice. Microsoft has a “fix” for this, but it’s not going to be one users are happy with. The company simply tells users to uninstall the update:
- “If you are using DSC from or on any Windows client, take the following steps:
Uninstall the update if already installed. From elevated PowerShell prompt type
wusa /uninstall /kb:3176934
- If using WSUS, do not approve the update. Otherwise, Use Group Policy to set the ‘Configure Automatic Updates’ to ‘2 – Notify for download and notify for install’ as described in this Microsoft Support article.”
Not the First Time
Of course, this isn’t the first time in recent history that builds have shipped with bugs. The Windows 10 Anniversary Update broke millions of webcams around the world.
The issues started because the Anniversary update handles the webcam encoding process slightly differently. Microsoft has promised a fix for the issue, but it won’t be coming until at least September.
Fortunately, the fix for PowerShell will be coming a little sooner. The next Windows update on August 30th should contain the correct packages.
Until then, you can read Microsoft’s official blog post on the matter, which goes into more detail.