Latest Windows 10 Update Breaks PowerShell (infoworld.com)

whoever57 writes: According to a report via InfoWorld, the latest Windows 10 update [KB 3176934] breaks Desired State Configuration (DSC) functionality in PowerShell. Some things that were broken in the prior update, such as support of many webcams and a freeze issue, don't appear to have been fixed in this update. Windows PowerShell Blog reported last night: "Due to a missing .MOF file in the build package, the update breaks DSC. All DSC operations will result in an 'Invalid Property' error. If you are using DSC from or on any Windows client, take the following steps: Uninstall the update if already installed [...]; 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' [...] A fix for this issue will be included in the next Windows update which is due out 8/30/2016."

Comments

LOLOL

[Anonymous Coward]

And that's why my Win 10 installation process goes:

1) Install
2) Run updates once, make sure everything's ok
3) Disable updates, Cortana, scheduled maintenance, and antimalware from the registry, and disable Windows Search and Superfetch from Services
4) Never worry about an update breaking my system or the never effing ending HDD grinding or SSD wearing

Re:The MS Merry Go Round.

[hairyfeet]

Ain't no suspecting required, just look up Barancles Nerdgasm's "I was fired" video on YouTube. He was part of the testing team and talks about how pretty much all the QA and testing teams for Windows were fired and makes it clear the vibe at Redmond was pretty much Insider for alpha testing, Home and Pro is the beta, Enterprise is the actual product...which is of course the only version you have to rent instead of buy.

This is why I'm telling my customers to stay far away from Win 10 and if they get a new PC with that POS OS? I point them to Win 8 OEM which you can get quite cheaply (and once upgraded to 8.1 with Classic Shell is just Win 7 with some speed tweaks) because even with the new OEM systems it doesn't take more than one or two patches before I'm getting calls that shit is broken.

Now I've had every version of windows since 3.1, including the shitastic WinME and the bloated irritating Vista...Win10 IMHO is the worst product they have EVER came out with bar none. WinME? You could hack in some files from Win98 SE and make it a decent if not good OS. Vista? You could use NLite to chop out the crap and make an okay, not as good as XP X64 but an okay OS for daily use. And of course Win 8/8.1 you could just slap on Classic Shell and take out the crapstore and telemetry crap and its a good solid performer...Win 10? IMHO its not even beta quality, with every update just as much shit gets broke as gets fixed and frankly until Win 10 I had even forgotten what a BSOD looked like simply because how well previous versions past XP handled major errors. Its just not a good OS folks, its buggy, has baked in spyware and ads, it doesn't even look nice, its just a bad product.

Hopefully by the time 8.1 (if not 7) is reaching EOL they will have given Nutella his walking papers, if they haven't? Well I don't think there will be a Windows business to worry about really, it'll just be legacy installs while everyone is on Google or Apple OSes. Ballmer tried to kill the company being a faux Apple, Nutella is trying to finish the job by being a faux Google.