And so it begins:
Windows Update in W10 pushes faulty nVidia drivers out which are unstoppable/unhidable and already brick PCs.
The flaw revolves around Nvidia graphics cards with users taking to Nvidia's forums to report Windows Update is automatically installing new drivers which break multimonitor setups, SLI (dual card) configurations and can even stop PCs booting entirely which pushes Windows 10 into its emergency recovery mode.
"Please pull these off Windows update!!!" writes Nvidia forum poster slycoder. "It makes my second monitor not work and lots of flickering! Please. I roll back and Windows Update reinstalls them :/"
"I second this," agrees ZabaZu. "For multi screen users, that driver is flat out broken and it is beyond annoying that windows auto updates to it."
Now that's bad and I absolutely knew this stuff would happen. It was bound to happen. It was 100% certain.Given Windows 10 updates cannot be stopped the most obvious solution is to uninstall third party driver management and hand it all over to Windows Update to avoid clashes. This potentially simplifies matters by providing an all-in-one update service, but it does mean taking away control from specialist companies over their own products.
A second approach is something many readers mentioned in comments on my previous post when Microsoft confirmed Windows 10 updates were unstoppable: hack it.
Initially this might work, but in April senior Microsoft product marketing manager Helen Harmetz said during a Windows 10 webinar that users who forcibly stopped any Windows 10 updates would eventually have their security updates cut off. Microsoft has yet to confirm this brutal enforcement policy in official documentation, but if this is the path it chooses that would ultimately make any form of update hack pointless.
Wait wait.. what?
Are they completey out of their mind ?!?!?!?!?!!!
Does that mean if I stop Windows Update by disabling its service for a while or use the gpedit.msc solution, Microsoft might punish me by stopping all Windows updates in the future? Microsoft is aware that paying customers are not their inmates?
Sick! No really, * THIS. Hardcore Stallmanism was sane compared to NuMicrosoft. This takes it way too far. This is not funny anymore.
You got it wrong: On Windows 7 this is fixable, on Windows 10 it's not fixable. At least not without some crazy workarounds or completely killing Windows Update.
What's there to speculate? I've seen Windows 10 myself - you cannot hide/reject updates there, Office ones included. That's no speculation.
If I would get a similar buggy patch in Office or Windows on W10 instead of W7, I would be FUBARed. And I know this kind of things will happen, because I doubt Microsoft's programmers will be blessed by the programming god between now (when they pushed another faulty Office update out) and the time W10 arrives (in a week).
And yet another example why Windows 10's updater is a disaster in the making.
I've had again crashes with IMAP and Outlook 2010. Microsoft knows this issue but doesn't list all updates which may do this:
So anyway, it crashes again, and this time KB3054976 is the perpetrator (released this patch day, and not on the above list). When I have it on, I get a crash, when I uninstall it the crashes are gone. It's reproducable.
Now of course, after I uninstall it, it appears again on Windows Update. So I have to hide it. On Windows 10 this is not possible anymore. At best you can disable WU completely through gpedit.msc (and only on pro you have the built-in tools to do this), which is a very sub-optimal soluton to say the least.
So again, tell me, how is Windows 10 an improvement in this area? Once you get such a situation (not exactly uncommon!) you're completey FUBARed on Windows 10: You either live with crashes (in this case on every Outlook start-up!) or you have to deactivate Windows Update completely! So much for the improved security the forcing and crippling of WU W10 brings.
Well OK, I can think of another "solution" in such case on W10: You save the working files and kludge up some batch file that copies them over the faulty ones Windows Update shoves up on every reboot. What a bizarre result of Microsoft "simplifying things".
Even with group-policy you won't regain the same functionality of W7 Home Basic in any version of W10, like the ability to deselect any single update or hiding them. Nor do you get the the list back which shows the found updates together with the description of them on the right pane.
The loss of all this is inexcusable. Just two months ago I had a situation with WU which was easily fixable in W7 but would be quite the pest on W10. I am pretty sure I am not alone who had such issues with updates. Losing almost all control over them is a recipe for disaster.
And any excuses for Windows 10 regarding this and bringing up the different "rings" and what not reminds me very much of the loss of start menu in W8 and bringing up keyboard shortcuts and third party tools. We all know how this ended up.
W10 makes something that worked just fine in prior versions into a far more complicated and dictatorial affair. There's no good reason why the working and proven update-regime had to transformed into this mess.
REVERSE? They are making it worse in W10.
And this newest stunt has nothing do with security. There was no problem at all with the older WU-regime. Most people had it on auto already, there's no rational need to tighten-up the screws and no need to bring the hacker-bogeyman in this discussion.
No, this is a way to get cheap R&D. MS reps are almost saying it out loud by describing how home users won't be able to control updates anymore and are automatically on fast-track, while the business users can at least postpone them. It's a cheap way to test updates on the population that won't fight back so that they can safely be released on the truly "important" customers. It also helps (MS) that MS can force any updates that way with no easy way to opt-out.
I have no problem with automatic updates, but I have a problem with them if you can't turn them off or select which updates to install. There are more than enough cases where this is needed (long-running tasks, tasks that require continous standby, trouble-shooting, testing) and removing these options is despicable, especially given that WU worked just fine in the previous versions. There's no good justification for this move (cheap R&D for MS isn't a good one).
wastingtimewithforums, package management is a legit reason on why Linux is better. One of my biggest pet peeves about Windows is how many apps essentially roll their own package management, and you have multiple "software updaters" running and bothering you. It's f*cking annoying. Apple and Adobe are especially bad, but it's not the point. It's not the right way of doing software lifecycle management. It's completely idiotic actually.
I am not against package management. I am saying that all this stuff tuxers threw around back in the day didn't matter a thing when it came to displace Windows.
Entrenchment of win32, familiarity with Windows and the huge investments into the ecosystem was the barrier that the freetards weren't able to tear down with their gimmicks (and package-managers are gimmicks in the grand scheme of things compared to the things Windows had)
Metrotards are doing the same mistakes the Linuxers did. WinRT and "metro" are gnome and yast.
No one important is going to ditch Windows (win32, w95-like GUI etc.) for this, because the cost is just too high doing it. And the fart-app addicted will stay on their smart phones or will just continue to use the web offerings of Angry Birds.
It's funny that Microsoft itself became the carbon-copy of the tards of the past though. It's not the new APIs that are the hillarious thing (MS has a bazillion of them anyway) but Microsoft's repeated declarations that everything until metro/modern/winrt/ua/uwp/wtf is legacy and dead and what not is the funniest thing I've seen in IT for ages. It beats Stallman's foot fetish by a wide margin.
I am religiously anti-tard.
Maybe Linux would have been successful at displacing Windows if the community weren't so batshit insane back in the day.
The "Linux-community" (not neccessarily open source as a whole) was almost a hate-movement at certain times and full of loons. Google and others were able to tame them finally though and productive things started to happen (Android).
But anyway, that's ancient history now. Metrotards are far more insane today than the freetards - some of the guys on Neowin during the W8-buzz could have filled up the legendary "COLA" Linux newsgroup with ease with their loon.