MS spent a very long time testing this one, but it’s out now.
Windows Terminal / Linux On Windows 2 or bust!
I had to suspend updates because of 1903, it tried at least 10 times to update and failed every time.
Huh. This is a Windows issue? I wondered. Every so often I lose wifi from a transceiver across the room, and resetting the connection fixes it.
I upgraded to 1903, now my windows settings UWP app is broken and just crashes when I click on “apps”. UWP is such a miserable piece of shit.
That list is specific to the brand-spanking-new 1903 release, but I suppose it might be an issue carried over from prior releases.
Also:
In other words, wait :-)
Semi-annual channel is twice per year, in other words this update as soon as it’s offered in windows update.
Yes, but it also means stop smacking the “Update Now” button :-)
No, it means they shouldn’t offer an update to endusers until they think it’ll work.
MS has a serious quality control problem. I’m a sample size of one, but I’ve personally had a previous update completely trash my OS, and this one broke the settings app. They delayed it by a month for extra QA and it’s still shitty.
You’ll be glad to hear that some of drivers that come with 1903 (including nvidia) now are DCH drivers, rejoice, now you get to visit the Windows Store to download the control panel and the drivers will be a UWP wrapper around the Win32 driver (in some cases).
Win10 works flawlessly aside from the UWP shit. Never had a problem elsewhere.
Edit: Looks like it’s a known bug from over a month ago and they just went ahead and released 1903 to endusers anyway.
Luckily the Windows 7 style uninstall in control panel hasn’t been removed yet, and that still works fine.
Kyrios
4128
For what it’s worth, I’ve had more crashes/blue screens with Win10 (3 years at home, 6 months at work) than in the rest of my Windows experience combined (back to the late 90s). Anecdotally, it seems like a lot of minor things that would have popped the occasional non-fatal error in previous versions cause Win10 to have fatal memory management issues? Not really sure, I can usually find some cause if I tinker around enough, but I didn’t start doing anything different with 10 than in prior versions, and they never got remotely this fussy. For a long time I thought it was my fault with my home-built PC that upgraded from 8, but I’ve had the same issues with clean installs on a fresh built PC at home and an off-the-shelf ThinkPad at work.
(It also seems a bit dumber about multiple monitors and monitor switching than 7 and 8 were, common stuff like recognizing the correct monitors every time when I go in/out of dock, but that could easily be a driver issue, especially because somehow I go between 5 external monitors and home and work and none of them are the same resolution.)
Win10 doesn’t crash on its own, the kernel is stable. You have a hardware or driver issue somewhere.
Win10 has a lot of UI inconsistencies, and tons of forced telemetry that they don’t allow you to disable, and UWP is a godawful piece of shit. But the core OS is still fine.
Solved my 1903 problem finally. Dug around until I found the error code. Turned out it had something to do with Windows Search. Turn that off, and the install went smoothly.
Kyrios
4131
Oh, there are definitely issues, and I can usually track them down. Drivers more often than not, as you’d guess. But it (again anecdotally) seems like what would have previously been a driver conflict that led to a device not working 100% is now a driver conflict that leads to a memory management BSOD. That’s not Win10’s fault or crashing on its own - after all, something was wrong! - but it still hasn’t been my favorite thing ever. Maybe I just had great luck with all of the previous versions, who knows?
rei
4132
I can’t find where this is myself yet.
rei
4133
1903 broke my MS Snip & Sketch even after resetting, uninstalling and reinstalling. Just runs and closes. Back to Snipping Tool and/or Snagit.
