If you thought that, with the recent announcement Microsoft will be moving to a single security update once a month for Windows 7/8, the company had somehow found a way to improve its patches, you’d have thought wrong.
A Cumulative Update that rolled out earlier this week has broken PowerShell. Microsoft admits the mistake in a blog post, saying…
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.
Oops.
Microsoft assures customers that a fix is coming. But, don’t lose sleep waiting for it. The blog post leaves us with…
A fix for this issue will be included in the next Windows update which is due out 8/30/2016.
Which is the way of things these days. Due to the one big update policy, Microsoft can’t deliver a fix for this one silly issue – no matter how critical it might be to your operations. You’ll need to wait until for another mega download.
Interested in joining your voice to the throngs of customers concerned with Microsoft patch quality? Check out the Birds of a Feather session, entitled ‘Microsoft set to change Windows patching in a disastrous way’ – discuss! at IT/Dev Connections 2016:
