New
#21
I just downloaded the current 2004 ISO, it`s 3.94 GB now, so not too much of a difference.
Take a quick look at my post #15. Windows 10 1909 fails to update to 2004
The size difference is due to the full blown ISO contains all versions..... Home, Pro,Education. All of them. Here is the breakdown of that 5.1GB ISO you have, same one I have.
Code:O:\>DISM /get-wiminfo /wimfile:"O:\sources\install.wim" Deployment Image Servicing and Management tool Version: 10.0.19041.329 Details for image : O:\sources\install.wim Index : 1 Name : Windows 10 Home Description : Windows 10 Home Size : 14,212,376,596 bytes Index : 2 Name : Windows 10 Home N Description : Windows 10 Home N Size : 13,441,677,475 bytes Index : 3 Name : Windows 10 Home Single Language Description : Windows 10 Home Single Language Size : 14,211,972,277 bytes Index : 4 Name : Windows 10 Education Description : Windows 10 Education Size : 14,450,251,000 bytes Index : 5 Name : Windows 10 Education N Description : Windows 10 Education N Size : 13,693,633,242 bytes Index : 6 Name : Windows 10 Pro Description : Windows 10 Pro Size : 14,450,428,963 bytes Index : 7 Name : Windows 10 Pro N Description : Windows 10 Pro N Size : 13,691,468,430 bytes Index : 8 Name : Windows 10 Pro Education Description : Windows 10 Pro Education Size : 14,450,189,418 bytes Index : 9 Name : Windows 10 Pro Education N Description : Windows 10 Pro Education N Size : 13,693,570,760 bytes Index : 10 Name : Windows 10 Pro for Workstations Description : Windows 10 Pro for Workstations Size : 14,450,220,209 bytes Index : 11 Name : Windows 10 Pro N for Workstations Description : Windows 10 Pro N for Workstations Size : 13,693,602,001 bytes The operation completed successfully. O:\>
@zbook, thanks again, but this is a deceased horse. No amount of flogging will revive it (in my stable). If this was an important issue, I would have pursued it, but won't because I have many other software changes to deal with.
Also, this script was available in .exe format, and the logs were uploaded two days ago. They are attached to post #6 in this thread. At this point I prefer MS to resolve the issue.
The log in post #6 appears to be the result from running the DM log collector.
When there are Windows upgrade failures Microsoft provides free support.
There are three tiers.
The 3rd tier frequently uses the script that I provided.