Windows 10

[Rroff]

Windows 8 was pretty decent underneath the hood - properly setup it boots faster than 10 and a lot of the underlying kernel is fast and responsive, lack of the start menu (though I managed to re-enable a good bit of it via registry/shell hacking) was a downside but it also is pretty ugly and file explorer is a mess like 10 (aside from the advanced file copy dialogue).

I'd take 8 over 10 any day which is a bit of a turn around as I slammed 8 for the removal of the [traditional] start menu and ugly UI/Metro stuff. At least it never interferes with what I'm doing and is always ready to do whatever you want.

Windows 7 is lacking a lot of quality of life features these days but I can at least rely on it - properly setup it never gets busy in the background unexpectedly, never tries to take executive actions with a lack of real life context awareness, etc. - for instance sometimes Windows 10 has even decided to launch CPU heavy maintenance tasks or even launched into updates and show the old "Do not turn off your PC" screen when I'm on battery and wanting to save it and/or don't have enough charge left to finish updates and not in a place where I can easily plug into the mains.

 

[LoadsaMoney]

KB5001649 gona again, replaced by a massive bug fix patch - KB5000842

 

[Deleted member 77746]

KB5001649 gona again, replaced by a massive bug fix patch - KB5000842

 

[Ur round next]

This update keeps failing on installing for some reason

 

[Mel_P]

Ok for me on 4 devices.

 

[Neil79]

Got a new SSD and a completely new OS install on one system now all up to date, then the main system tomorrow

 

[Neil79]

Well I'm pretty miffed, the latest 20h0(?) experience keeps on destroying itself on the main system, works on the other older one! BSOD after BSOD! Every time it connects to the internet to download the latest chipset/motherboard drivers, or I do it manually the computer gives me a BSOD and restarts, then corrupts itself. Windows 1909 works perfectly well, so whatever they've done isn't compatible with my board. I'm staying on 1909 now.. Tired and grumpy

https://www.overclockers.co.uk/forums/threads/system-hosed-need-help-asap.18925504/

 

[Mel_P]

I have devices from a 2009 Asus Eee, 2010 intel desktop, 2014 Lenovo yoga laptop, 2015 intel desktop and 2020 MSi amd 3600 desktop and all are on the latest windows. You do seem to be unfortunate! Mel.

 

[Neil79]

I have devices from a 2009 Asus see, 2010 intel desktop, 2014 Lenovo yoga laptop, 2015 intel desktop and 2020 MSi amd 3600 desktop and all are on the latest windows. You do seem to be unfortunate! Mel.

For sure! I don't understand it, as it works perfectly well on the other system... Every time it tries to install 20H2 instant BSOD, on a full install it works fine up until it installs anything. I believe it's something related to the MSI Gaming 5 board

 

[Neil79]

Reading reports with it failing with certain Z97 boards via the Intel Management Engine Interface driver

https://forums.evga.com/Z97-Classified-and-Win-10-20H2-update-m3146566.aspx

https://borncity.com/win/2021/02/21...-update-fails-due-to-intel-management-engine/

https://forums.lenovo.com/t5/ThinkP...auses-Vantage-BSoD/m-p/5035062?page=1#5126562

https://www.tenforums.com/bsod-cras...ult-when-updating-20h2-electric-boogaloo.html

As expected really!

The EVGA and MSI forum for the Z97 MB indicates a problem with the Intel Management firmware causing the update to fail.

 

[Mel_P]

I have an ASUS Z97-K board, i5 CPU / 16GB memory system. It has the Intel Management Engine dated October 2020 installed. Updates to and runs quite happily on 20H2. So not a generic problem?

Mel

 

[Neil79]

I've just flashed to the latest BIOS, so lets see what happens now!

 

[Rroff]

I'm staying on 1909 now..

Problem is Windows 10 has a habit of thinking it knows better in this respect and likely going to cause a headache sooner or later unless they actually fix it or you go to the trouble of actually disabling Windows update which isn't straight forward even with the use of programs designed to do that. Even using the MS tool to block specific updates won't guarantee a result

It is a horrendous OS, developed by people with their head firmly up their behinds, if you actually need to rely on it.

 

[Neil79]

It is a horrendous OS, developed by people with their head firmly up their behinds, if you actually need to rely on it.

Exactly, even worse for people with no knowledge of computer operating systems! - Why can't Windows 10 just go hold on a min, this file didn't update it's causing a BSOD, so lets put that back for now and do the rest

 

[Rroff]

Problem is - even if it detects a problem like that and it is clever enough to do so - it will still periodically re-try assumedly in the hope that the situation has changed with little to no user control of that.

It is daft - an OS with lack of real world contextual awareness should never take executive actions out of the user's control. An OS's purpose is to enable the user.

I really wish it was a simple as just dumping 10 for another OS as I'd be well gone by now - it is an OS developed by dumb ***** with no care as to the quality of life experience for the actual users.

 

[Neil79]

I'm stuck because I can't find Windows 10 May 2020 Update (version 20H1) anywhere! It's the only update that works prior to the balls up 20H2

 

[Neil79]

IT WORKED!!!!!!

Hours upon hours of trying to fix these damn BSOD's, and a very sleepless night where I could've lost everything ( *** YOU MICROSOFT ). It turns out the reason why it's BSOD'ing is because Windows 20H2 updates the Intel Management Engine interface automatically which doesn't support certain Z97 chipset motherboard Bios's. The MSI and some EVGA boards. The only way to fix it, is to flash to the latest BIOS and then re do the update! Basically the Interface is talking to the wrong code of the system hence BSOD every time when Windows thinks it knows best! I would never have known this if I hadn't typed the name of my motherboard and this update version!

 

[LoadsaMoney]

Good to hear you sorted it

 

[ChrisD.]

IT WORKED!!!!!!

Hours upon hours of trying to fix these damn BSOD's, and a very sleepless night where I could've lost everything ( *** YOU MICROSOFT ). It turns out the reason why it's BSOD'ing is because Windows 20H2 updates the Intel Management Engine interface automatically which doesn't support certain Z97 chipset motherboard Bios's. The MSI and some EVGA boards. The only way to fix it, is to flash to the latest BIOS and then re do the update! Basically the Interface is talking to the wrong code of the system hence BSOD every time when Windows thinks it knows best! I would never have known this if I hadn't typed the name of my motherboard and this update version!

Such a simple thing to have been tested by Microsoft and also write code to do a BIOS check.

 

[Rroff]

Such a simple thing to have been tested by Microsoft and also write code to do a BIOS check.

To be fair there are a million and one things like this which could trip up updates - sure many of them individually are simple to test but that is a lot of testing collectively.

(It doesn't help MS have massive reduced down their internal testing and only listen to what they want to hear from external testers/"insiders").

Which is why you don't use an updates approach like they are using in Windows 10 it is just idiotic.

Security updates need to be quicker and easier to apply and entirely separated. Hardware updates should never be pushed through automatically but notified if there are critical security, performance or compatibility issues, feature updates should be left to the end user's leisure. Anything else is utterly pants on head.