The Gang Who Can't Code Straight!

Microsoft is at it again with W10. As Ars Technica reports:

As if that weren't bad enough, Microsoft has pushed out a bad update that breaks important PowerShell functionality. The update, KB3176934, is the latest cumulative update for the Anniversary Update and was released on August 23. It breaks two key PowerShell features: Desired State Configuration (DSC), which is used to deploy configurations to systems, and implicit remoting, a feature that makes it easier to use PowerShell commands that are installed on remote systems. The reason that these things have broken is remarkable. The Cumulative Update doesn't include all the files it needed to. One missing file breaks DSC; a second missing file breaks implicit remoting. A revised package that includes these missing files will be released on August 30; although Microsoft recognizes that the problem exists, it isn't apparently important enough to rush out a fix, so it'll have to wait for the next Tuesday.

Yep, a bad and broken update causing billions of dollars of down time!

Microsoft notes:

Known issues in this update
Issue 1

After you apply this update and then start a remote Windows PowerShell session, the functionality to import a module (implicit remoting) no longer works. 

Issue 2

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. 

 And then follow this to Microsoft:

On August 23, Windows update KB3176934 released for Windows Client. Due to a missing .MOF file in the build package, the update breaks DSC. All DSC operations will result in an “Invalid Property” error. In addition, due to a missing binary in the build package the update breaks PowerShell implicit remoting. Implicit remoting is a PowerShell feature where PowerShell commands work on a remote session instead of locally. Specifically, importing a remote session no longer works.

 One has to ask if there are any adults in Seattle. Perhaps it is some form of massive substance excess. The solution starts with a new CEO who has the customer in mind! Where is the Board, that is the problem. There will be massive class action suits sooner or later!