Latest Windows 10 update breaks PowerShell DSC and implicit remoting, but a fix is coming
While mandatory updates mean Windows systems are kept safe from threats, the downside is if a bad update makes it through testing it gets pushed out to everyone.
This is a problem we’ve seen several times already with Windows 10, and the latest update, KB3176934, is another perfect example of this.
SEE ALSO: Windows 10 Anniversary Update crashing when Amazon Kindles are connected
As part of a cumulative update rolled out to users two days ago, KB3176934 is missing a .MOF file in the build and as a result has broken PowerShell DSC (Desired State Configuration). Try running a DSC operation and you’ll receive an "Invalid Property" error.
Due to a missing binary, KB3176934 also breaks PowerShell implicit remoting.
Microsoft has confirmed the problem, and is working on a fix which it says will be included in the next Windows update due out at the end of August.
In the meantime, there’s a workaround available.
If you are using DSC from or on any Windows client, take the following steps:
- Uninstall the update if already installed.
- From an 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.
Photo Credit: tommaso79/Shutterstock