Windows 10: Update to 2004 before 20H2?

I updated from 1909 to 20H2 and had all sorts of issues, to include my system locking up after about an hour, and that happened several times. I was able to roll back, but have since read that I should have updated from 1909 to 2004 first. How can I find the update to 2004 to try loading that?

:)

 

1909 was just automatically updated to 2004, instead of 20H2

Feature update to 2004 slipped by me even though the (optional) update to 20H2 was already listed in settings/windows update. Why didn't WU simply download the 20H2 fixes with 2004? I can't believe my system has suddenly been classified as incompatible, not if 2004 is good to install. Will the enablement package be offered next tuesday? I have checked for updates manually and it doesn't find it.

 

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.

 

windows 10 2004 update and now 20H2 error 0xC1900101

No I have more or less given up. The suggestions given by the "experts" on here have all proven to be hopeless. I have even tried to clean install windows 10 via the media creation tool and the computer would not boot from the usb though it does from the usb recovery media created. As soon as I have the funds then this computer will be consigned to the scrapheap. Even Lenovo have been useless and it seems support from Microsoft for 1909 will be ending soon with no update from them as to why the upgrade from 1909 to 2004 and 20H2 will not happen with this computer. Have had suggestions it could be the processor from others elsewhere.