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."
A fix for this issue will be included in the next Windows update which is due out 8/30/2016
I dread to think what that update will break.
I guess BASH was put in just in time, eh?
Obviously all the Windows admins are in a panic trying to organise stop-gap backup solutions to get them through the week...
What a complete disaster.
Lost its powa!
I'm afraid that like other shells it got BASHed to bits.
Bash still works perfectly fine, so all real IT guys and teams will be fine.
stuff
Mark my words: The day will come when an update from Microsoft will nuke the Windows installation beyond repair. ISPs will suddenly see a massive drop in traffic. Downloads and streaming will suddenly be super fast for everybody else. Spam, Ransomware, DDoS Bots and Trojans will vanish from the planet for 24 to 48 hours until people reinstall Windows on their machines and will access infected sites, get infected again... and the whole thing will start all over again :-)
All those moments will be lost in time, like tears in rain... time... to... die...
How to fix your PC: http://www.ubuntu.com/download/desktop
Considering Microsoft said nine years ago they were dropping PowerShell, why is this a surprise? Peter Neupert, head of Microsoft's healthcare division at the time, and Brad Silverberg, head of Windows 95 and several other projects including MSIE and Office, told us then to not use PowerShell. They said it would grow in popularity then be dropped because it didn't fit their .NET philosophy. We avoided it for that reason.
to Windows 7. It's great over here.
This is the latest demonstration of why the all-or-nothing forced updates coming in October are a terrible idea.
Windows code is such a mess, don't try to modify it. Just take Windows 7 code (the CD with the code must be in the same drawer as in 2009, 2nd from top), recompile it, and put a Windows 10 sticker on it.
Slashdot, fix the reply notifications... You won't get away with it...
Nothing of value was lost.
Score:-1 Flamebait
I was going to come here and post a comment about how installing WSUS for mere power users has turned out to be a great idea yet again (I've done it for myself and the time spent manually approving updates is well worth it) but first I have to scroll past the stupid comments:
I guess BASH was put in just in time, eh?
What a complete disaster.
Bash still works perfectly fine, so all real IT guys and teams will be fine.
Mark my words: The day will come when an update from Microsoft will nuke the Windows installation beyond repair. ISPs will suddenly see a massive drop in traffic. Downloads and streaming will suddenly be super fast for everybody else. Spam, Ransomware, DDoS Bots and Trojans will vanish from the planet for 24 to 48 hours until people reinstall Windows on their machines and will access infected sites, get infected again... and the whole thing will start all over again :-)
How to fix your PC: http://www.ubuntu.com/download/desktop
This is why I hate going to Slashdot. Not the factually incorrect articles, not the summaries needing proofreading, not the occasional "advertising". It's the asshole users.
Captcha: respects (ha!)
An anime had a plot like that (.hack? Accel World?) where basically everyone started using a particular OS after the previous prevalent OS was hit by a virus (Pluto Moon?) that crashed like every computer system worldwide.
Microsoft's new Win10 with updates and die attitude seems like it will result in that exact global catastrophe occuring.
Anyone that attempts to sue Microsoft is a hero, IMO. Their business model is basically to piss off users and waste peoples' time.
--- We need more Ron Paul!
Patch QA was moved in phases to I believe Shanghai starting a few years ago to reduce costs.
Which meant all the old-timers who knew their shit in Redmond got let go. You reap what you sow...
Captcha is abortion...
Lately the quality of the updates reminds me of Windows ME. I was affected by this mess just recently, now dealing with broken PS.
Windows ain't done until Powershell won't run!
#DeleteChrome
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
Yesterday my Windows 10 machine installed updates that caused the BIOS RAID setting for my boot drive to be disabled. "Error loading operating system" GG
Okay, before you all bash Microsoft, honestly, does anyone actually use this? PowerShell DSC is a horribly over-complicated thing with such limited power - I wouldn't be surprised if this didn't get picked up in QA because this feature is so ... pointless, that nobody sane actually uses this on Windows 10.
Hence why it took SO LONG to be found out after the anniversary update came out. Doesn't this mean that NONE of the people using Windows Insider builds encountered this issue? Means none of them are using this.
Frankly, it's an advert for sliming Windows down and, over time, getting rid of the dozens of ways of doing something and reducing it down to just one, sane, one.
SOME People might use it as a means to deploy configure windows server instances as part of their deploy an image type software... although honestly, docker containers will probably obsolete this approach. But... that's all SERVER deployments, not W10.
Microsoft QA will no doubt include this into their automated tests though to make sure it doesn't happen again.
True, it's not good... but... this particular case doesn't seem to me to be a showstopper.
I read where MS "opensourced" PowerShell and are gonna provide it for Linux.. Geez.. Keep that MS garbage off my computer.. I dumped Windows about 6 years ago for 100% Linux, and it will be a sub-zero day in hell before ANYthing MS writes goes on ANY machine *I* control..... (shudders)
THANK YOU, Edward Snowden!! Americans owe you a debt of gratitude (whether they know it or not..)
But then, on a Mac I guess everything Just Works, including Microsoft products... :-)
I think Microsoft constantly breaking Windows is a sort of technological freudian slip. Even they are tired of Windows.
"There is more worth loving than we have strength to love." - Brian Jay Stanley
Microsoft software has been a bug-ridden mess in every iteration since Windows XP and Office 2003, which were the last relatively stable versions your company ever released. Had you spent the intervening years ensuring Windows and Office had fewer and fewer bugs, were secure, and adhered to open standards instead of closed proprietary stuff, you would be much loved and cleanly earning money now.
Instead, you ignored the bugs, ignored the security, ignored the standards, and instead went down the primrose path of telemetry and subscription models, copying others instead of blazing your own positive path.
And now the chickens are coming home to roost. Why does your company always embrace the wrong things? Just a simple re-focus on avoiding buggy software would have brought you so much good will.
But modern Microsoft software is a buggy mess, and has been for 15 years or so. Why, oh why, do smart people act so foolishly?
None of the Windows Insiders getting the Fast Ring updates use PowerShell? Bring back the laid-off test lab monkeys that actually did more with the pre-release builds than look for shit to blog about.
Maybe this will accelerate Bash integration. I tried to play with the Powershell years ago... YUK! Lets take a shell and make it Object Oriented... Huh? Why? it's a F*ing command prompt. Why oh why make it so complicated?
Windows is dead.
Microsoft is dying.
Face it.
Time to move on.
Before it is too late for you...
MS wans to go back to the bad old days where their products were really crappy, but their revenue was king. So, since Win8, they have tried to fix the damage they did by releasing the actually reasonably good Win7, first by breaking the GUI and now by regularly breaking other things. Of course, this cargo-cult approach will not bring their revenue back, but it will remind everybody what MS really stands for quality-wise: Cheapest possible.
Most ACs are not even worth the keystrokes to insult them. Be generically insulted by this and ignored otherwise.
I have a Dell with a SSD and have experienced taskbar freezes, sound issues, and a general slow down. Done all updates, Bios, drivers, SFC scan. Just have to deal with the wonderful forced updates. What good is regressing back to previous version when you will just get Anniversary update forced upon you again?
What a awful mess Microsoft. How you will sell this to enterprise is beyond me?
Even though PowerShell is broken I found that BASH works fine (thanks Microsoft), even though I've only been using it a short while I'm already considering not going back.to.fucking,powershell.
As reported at The Register, the latest update will cause a BSOD if you plug a Kindle in.
I'm glad I blocked GWX and all MS's attempt to force this shit on me, especially with their "we'll update what we want, when we want" approach since it appears that MS do the absolute bare minimum thesedays in testing their software.
I'm also pissed that MS are fucking around with updates on Win7, accept a big cumulative update or none at all.
Fuck it, I'm done with Windows
All the pseudo "experts" on here, do you even read when you install styff or do you simply press next next like a trained monkey? Funny when i configured my win10 pro install no settings got rolled back during updates. Its called reading and paying attention you cheap bastards. Btw i have 4 linux boxes running side by side with win 10 and talking to eachother
For MS office compatibility with itself the problems most often happen between mac version and the windows version, I have seen several issues both with embedded media and font kerning, the latter messing up presentations that rely on things that "just fit" on one line. This is not so major but it is real and a real time waster, you need to check your presentation on the same OS as you present it. You will also get issues if you have organisation specific fonts installed somewhere.
As an added point of info their are a few gotchas with macros, especially between 32 bit and 64/Arm (vba6 compiled is 32 bit only) but I haven't used those so I don't know about the likely consequences.
see:
https://msdn.microsoft.com/en-us/library/office/jj229903.aspx
https://msdn.microsoft.com/en-us/library/office/ee691831(v=office.14).aspx
Connecting the Amazon e-reader to a fully up-to-date W10 machine via USB triggers an immediate Blue Screen of Death, according to complaints on Microsoft's support forum. All the trouble started when people downloaded and installed the Anniversary Update, which arrived at the turn of the month. That's the same upgrade that has knackered millions of webcams and caused some systems to freeze up.
The crash kicks off in the storage partition driver partmgr.sys, with a bugcheck code 0x7E (SYSTEM_THREAD_EXCEPTION_NOT_HANDLED) and cause code 0xC0000005 (STATUS_ACCESS_VIOLATION) – in other words, a kernel-level thread in the driver touched memory it shouldn't have, and blew away the environment. It sounds like Windows is trying to mount the filesystem on the Kindle as a removable storage device and getting completely confused.
During the 1511 update they also left an inconsistent MOF among the MOFs. MS better automate their moffing process soon before the users get royally moffed.
I understand that sometimes bad things come with updates. Old bugs get back in, compatibility breaks, new bugs are introduced. It happens to every software package sooner or later.
But if Microsoft wants to make updates fully automatic and even put them outside of the user's control, then they need to perform due diligence to minimize the risk of problems. Screwing up your build process in new, exciting, and trivial ways is not cutting it.
---
According to the latest ruleset, this post should be modded as Vorpal Flamebait +5.
It's "Windows Powers Hell".
I don't know what a powershell is, but when I updated my machine to Windows 10, many things stopped working. When I downgraded back to windows 8, my touchscreen stopped working, and several of the keys on my keyboard. It is just a computer now, so I let the neighborhood kids use what's left of my "was perfectly fine before I upgraded" computer. Really makes me sad as a consumer. And I don't know what's with the name tag, but I'M LA CHAUNTE AUGUST, not Anonymous coward.