The latest Microsoft cumulative patch for the Anniversary update had unexpected consequences for PowerShell, the command line shell and scripting language. Notes accompanying the release suggest that this was not unexpected for Microsoft, as the company appears to have known of the implications for PowerShell features when pushing the update. The Windows 10 upgrade has brought a few issues to users, such as frozen screens and broken USB-connected webcams. These two issues have not yet been solved in the KB3176934 (OS Build 14393.82) –for Windows 10 version 1607, also known as the Anniversary Update. However this PowerShell break proves to be the most relevant and recent issues to emerge.
Microsoft explains that the update breaks PowerShell due to a missing MOF file in the build package, and therefore breaks PowerShell Desired State Configuration, a feature used by IT admins to manage enterprise environments.
“All DSC operations will result in an ‘Invalid Property’ error,” Microsoft said. “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.” www.zdnet.com
Microsoft open sourced PowerShell and brought it to Mac OS and Linux distributions just a week ago.
Microsoft expects the PowerShell issues to be resolved with the next update release, today August 30th.
If you would like to educate yourself in more detail about the material presented in this blog post please visit : www.zdnet.com