Windows 10: 2004 and 20H2 updates causing BSOD

Whenever I try to update to the newest version of Windows 10 from 1909 starting with 2004, now same issue with 20H2, my computer crashes and gives a Blue screen with an SYSTEM_SERVICE_EXCEPTION. I have looked at the error logs and they give a code of 0x0000003b. The error always occurs while the update is running, usually around Installing: 80% or so.


Following advice I've found, I have updated every driver on my PC and ran Memory Diagnostics and Driver Verifier, neither of which find any errors thought I haven't run a super intense Driver Verifier session, so that may be needed. The issue still occurs whenever I try to update. I have attempted to use Windows Update Assistant with the same result, and even used another computer to create a 20H2 ISO USB and run the setup from the USB with the same result. Any idea why this could be happening?

:)

 

Straight to Windows 10 Update, Version 20H2

I've never downloaded the version 2004, since people said that it's bugged. And I only use my phone as the main source of data connection. Now then there's another new update, version 20H2.

My question is, does update 20H2 covered up the version 2004? Like the update 20H2 already had the 2004 In it?

If it does how much GB will I consume downloading the update?

I've heard that update 2004 size is 4GB, Is the update 20H2 file size is another 4GB? or just 1GB?

Please do tell me the total file size.. Cause I really, really have a limited internet connection.

 

1909 to 2004 upgrade

The 20H2 iso is available for download (see News section), so that naturally 'includes' 2004. This is a step preceding 20H2 becoming available by Windows Update in place of 2004; presently you'd be offered 2004 by WU then the 20H2 enablement package. All downloads are available following the relevant article in the News section.

It's an evolving scenario following the pattern of 1903/1909.

 

Seeking Advice Skipping 2004, Jumping to 20H2

Even if you are keen on getting 20H2, I would advise going for 2004. The reason is that the update from 2004 to 20H2 is a minor one, a small 85KB enablement package that turns on the dormant 20H2 features that are already in 2004. This enablement package installs quickly, like a cumulative update.

If you upgrade to 2004 then let Windows Update install the 20H2 enablement package, it can easily be unistalled in Control Panel's Installed Updates and revert you to 2004. If you upgrade directly to 20H2 the enablement package cannot be uninstalled.