[German]This week Microsoft released update KB3176934 to move Windows 10 Anniversary Update to Build 14393.82. Unfortunately this patch breaks the DSC function and remoting in PowerShell.
I’ve blogged about update KB3176934 for Windows 10 Anniversary Update at Updates KB3176934,KB3176935 and KB3176936 for Windows 10 Anniversary Update. This update fixes some issues, also in PowerShell – and most important, the Hyper-V bug mentioned in my blog post Windows 10 V1607: Hyper-V/Bitlocker/DeviceGuard as upgrade stopper.
But update KB3176934 breaks the PowerShell. Microsoft has added the two items to its KB article
Known issues in this update
After you apply this update and then start a remote Windows PowerShell session, the functionality to import a module (implicit remoting) no longer works. For more information, see the following Windows PowerShell Blog article:
After you apply this update, PowerShell Desired State Configuration no longer works. Users will receive an “Invalid Property” error message when they run any DSC operation. For more information, see the following Windows PowerShell Blog article:
Both links are pointing to this PowerShell blog article, where a Microsoft developer explains the the issue [DSC-PowerShell-Operationen (DSC = “Desired State Configuration“) and remote operation are broken]. Microsoft recommends to uninstall update KB3176934 using the command prompt:
wusa /uninstall /kb:3176934
or block the update in WSUS. After uninstalling, administrators needs to block further installs of this update via group policies (Microsoft addresses this issue only for business users, not for users running Windows 10 Home Anniversary Update). Details may be found in this PowerShell blog article. Microsoft also promised a fix until August 30, 2016.
Cookies helps to fund this blog: Cookie settings