The back button worked for me.
Windows update policy aside (I'm seeing reports that you can disable driver updates even in home edition, or something, I don't care).
Isn't this NVidia's fault for releasing a crap driver?
And haven't they released about 378 crap drivers in the past? This may be a conservative number... I can't even remember how many separate home and work systems that have been screwed up by NVidia drivers in the past, but it seems to happen on every system I have ever used with NVidia chipsets. One of my last systems had the same NVidia driver sitting in WU for at least 2 years, no update... the same driver that wouldn't even allow Windows to finish booting. (Standard Dell workstation config.)
Microsoft should probably make it much easier to disable particular driver updates, if for no other reason than to distance themselves from this kind of issue. But more so, NVidia needs to make it much easier to not break your computer by installing an update.
I'm just going to focus on the following, well, because it's late and I'm sleepy. And some of your other points are good (yet I don't agree with all of them). But this one seems to be filled with misconceptions.
Modern Applications - The Windows store is a commercial failure and the majority of its offerings are terrible substitutes for classic third-party applications (ex. VLC Player, Chrome) or SaaS offerings (ex. Google Music or Netflix). Microsoft - accept the fact that you missed the boat on an app store, providing subscription services and building a viable mobile operating system. I STILL can't uninstall the majority of this bloatware - why Microsoft, why?
Universal Windows Platform apps (aka Windows 10 "universal apps") offer major improvements over previous iterations. They provide adaptive layout, making it much easier to have your app respond to the size of its window (like many modern websites) and to various input mechanisms. There are a host of XAML improvements, much improved focus on the desktop paradigm, improvements to interacting with system services, and so on.
Besides, there will now be legit Win32 desktop apps on the app store (via Project Centennial).
The Windows Store is no longer about putting mobile apps on the desktop. It's about putting desktop apps on the desktop, mobile apps on mobile devices, Xbox apps on the Xbox, HoloLens apps on HoloLens, IoT apps on IoT... and the developer can decide which platform(s) to target, and whether to build all platforms with the same executable binary or with separate binaries.
This store concept should look quite different from what you were used to in Windows 8. At least, once Windows 10 apps start appearing and taking over.
Here's the main article, or at least one of them: http://www.windowscentral.com/microsoft-cityman-and-talkman-flagship-full-details
The power button between volume keys is strange... not sure how I'd like that. All physical buttons need to be located, sized, and spaced in such a way that you don't need to see them in order to use them.
@wastingtimewithforums: You missed my point. My point is whether 10 will be managed differently such that the problematic updates won't cause the same kind of issues that make people turn them off. In other words, they may use more rigorous testing and the insider preview program to catch problems before they go out. More is at stake now with the forced update policy.
And I still haven't seen anything that indicates whether non-Windows updates will go through the same process, in-line with Windows updates. I'm hoping not.
I wasn't aware they were doing WaaS with those releases. When did that happen?
the idea of one OS to rule them all was already tried by Ubuntu and never took off. Why do they think they can succeed where Ubuntu failed?
I believe this is the first time that anyone has ever used Ubuntu's level of success in a market to establish whether that market has potential.
@cheong: "What if" questions are fine, but like I've said in other threads, you can't judge Windows 10's policy by faults in previous versions. Windows 10 may be managed differently because the policy is different.
Or maybe not. If/when this actually happens, throw as much feedback to Microsoft and make them answer for it.
But speculation is worthless.