KB5017308 Windows 10 19042.2006, 19043.2006, 19044.2006 Win Update

Doing all five updates now.

.Net also installed.

It seems that maintanance is still broken...
KB5016616 Windows 10 19042.1889, 19043.1889, 19044.1889
KB5015807 Windows 10 19042.1826, 19043.1826, 19044.1826
https://answers.microsoft.com/en-us/...4-6591c5bef298

Needing help. KB5017308 and last months both worked perfectly on my insider old Dell D630, but totally messed up my desk top computer. It loaded fine, looked good but then went into a gray screen, taking "forever" to load to partial desk. It was not usable and never really finished opening. I had to use an install CD to repair and remove the update to get the computer running again. It works perfectly on Version 21H2 (OS Build 19044.1889) but ruins my computer on .2006 and the one before. Thanks for ideas.

Updated last night. No problems.

install.wim won't fit FAT32 thumb drive

Greetings,
Downloaded the ISO from UUP Dump, but the install.wim was apparently too large for the FAT32 thumb drive when tried to copy over. Never had this problem before. Has anyone encountered this?
Thanks for kind assistance. Attached is file properties reported by windows.

goopy said:

install.wim won't fit FAT32 thumb drive

Greetings,
Downloaded the ISO from UUP Dump, but the install.wim was apparently too large for the FAT32 thumb drive when tried to copy over. Never had this problem before. Has anyone encountered this?
Thanks for kind assistance. Attached is file properties reported by windows.

@goopy,
That is pretty common with a build that has so many updates even if you just get a single edition.
When you download from uup-dump you can specify install.esd compression instead on install.wim and that should fit and be below the 4GiB size limit.


You can also convert the install.wim to install.esd with the DISM command or split it into two .svm files

Convert install.wim to install.esd:
dism /export-image /SourceImageFile:"D:\Temp\install.wim" /SourceIndex:1 /DestinationImageFile:"D:\Temp\install.esd" /Compress:recovery /CheckIntegrity

Note that the SourceIndex number can change depending on the original file that could have a single edition or multiple editions, the index number will point to the one you want.

Split install.wim to install.swm and install2.svm:
Dism /Split-Image /ImageFile:"D:\Temp\install.wim" /SWMFile:"D:\Temp\install.swm" /FileSize:4000

Try3 said:

Yes, it's very common & has been for several Versions now.
- It has affected ISOs for new Versions not just UUP-Dumps that incorporate CUs into them.

I now use this method:
Create a Fat32 InstallUSB from a Windows ISO file - my post #537 - TenForumsTutorials

This method also exists:
Create bootable USB installer if install.wim is greater than 4GB - TenForumsTutorials



Denis

Or you can use an ISO editor to replace the big install.wim with the converted install.esd or the install.svm plus install2.svm.
Then you can just create the FAT32 install media from the modified ISO. ��

Juans said:

It seems that maintanance is still broken...

I hope you were not expecting otherwise... this is Microsoft we're talking about.

Just don't hold your breath. :P