Inplace upgrade is not working for 20H2 atm, uninstall the 20H2 EP to downgrade to 19041.508 and you can do an inplace upgrade.
w10ui updates integration for 1607 LTSB x64 is fixed ! good job edit: x86 boot now in vmware (no more vmware cpu fault) and 1st copy with normal restart. edit2: but can't pass oobe with x86
I've tried every possible fix but I'm unable to install latest 19042.538 CU (I'm with 19042.508). DISM /Online /Cleanup-Image /ScanHealth doesn't report any error at all. Same using SFC /scannow (no integrity errors at all). But installing 19042.538 CU gives me 0x800f0988 error, while if I unpack cab and do a different installation the reported error is 0x800f0984. Few days ago I've used the DISM /Online /Cleanup-Image /StartComponentCleanup command and after the same syntax command with the /ResetBase option. I don't know if this could be the reason. I'd like to try latest CU but I could do a secure erase and a clean install using the UUP Dump ISO 19042.538. Any help would be very appreciated.
Setup no longer restart and return to the beginning? i simply excluded adding LCU to boot.wim it seems there is an issue or certain combination cause the problem BTW, do you use the sources dynamic updates kb4039556 / kb4532820?
Look at Post #10614 Enthousiast said Inplace upgrade is not working for 20H2 atm, uninstall the 20H2 EP to downgrade to 19041.508 and you can do an inplace upgrade.
How do you create an additional index in the wim file though? I followed the microsoft link that you posted and I successfully upgraded the windows 10 edition from Pro to Enterprise but I still see just 1 index in the wim file. How do I make the wim image to have 2 indexes (1 for pro and 1 for enterprise) ?
Generic example: Code: Dism /mount-wim /wimfile:install.wim /index:1 /mountdir:c:\mount dism /Image:C:\Mount /Set-Edition:Enterprise /Channel:Volume dism /Unmount-Image /MountDir:C:\Mount /commit /append Next you have to set the flag for index 2 after appending the new sku. Code: imagex.exe /flags "Enterprise" /info "install.wim" 2 "Windows 10 Enterprise" "Windows 10 Enterprise" On windows 10 you need to have any ADK for 10 installed to be able to use imagex, or provide imagex manually.
I think I'll stay with 19042.508 as it's working fine. Furthermore the 538 CU is missing on UUPdump and even on the Microsoft Insider Preview channel.
yes, you can use w10 8.7 test from @abbodi1406 no, it isn't compatible with ltsb 2016 x86 & x64 w10ui 8.7 test is ok for x64 ltsb 2016 from @abbodi1406 post https://forums.mydigitallife.net/threads/windows-10-hotfix-repository.57050/page-531#post-1618720
all versions but it's just a test version, no yet released, it was done to confirm skipping updating boot.wim fix ltsb2016 incompatibilty