Uh Oh, Windows 10 Update KB3176934 just broke PowerShell

Released earlier this week, a Windows 10 update by Microsoft has broken a couple of features in recently open-sourced PowerShell tool, for some users. The Windows Client KB3176934 update disables Desired State Configuration (DSC) and implicit remoting functionality of the PowerShell. This unintentional goof up comes within a week of Microsoft open-sourcing PowerShell and releasing its cross-platform binary builds for the users.


Microsoft has been trying to have the admin and developers use PowerShell, the company’s own task automation and configuration management framework. The tool has existed since 2006 when Microsoft released its first version for Windows XP SCP2.

Windows 10 Update KB3176934 breaks PowerShell

Desired State Configuration (DSC) is a management platform that enables deploying and managing configuration data for software services and managing the environment in which these services run. It provides a set of Windows PowerShell language extensions, new Windows PowerShell cmdlets, and resources that can be used to configure software environments.

Implicit remoting is a PowerShell feature where PowerShell commands work on a remote session instead of locally.

Microsoft reasons out the missing .MOF file in the build package as responsible for breaking the DSC and implicit remoting. With this update, All DSC operations will result in an “Invalid Property” error. While importing a remote session will no longer be useful.

Uninstall the update to fix the issue

On MSDS blog, Microsoft following actions to fix the issue,

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.

Meanwhile, Microsoft has confirmed that the next Windows update coming on 8/30/2016 will carry fix for this issue.

Ankit Gupta is a writer by profession and has more than 7 years of global writing experience on technology and other areas. He follows technological developments and likes to write about Windows & IT security. He has a deep liking for wild life and has written a book on Top Tiger Parks of India.

Leave a Reply

Your email address will not be published. Required fields are marked *

9 + 3 =