Updated the 20H1/2 Updates Overview with the RP DU for sources + CU: https://forums.mydigitallife.net/th...-20h1-2-vb_release.80763/page-16#post-1571109
@Enthousiast i need some help. i got 2 esd 19042.572.201009-1947.20h2_release_svc_refresh_CLIENTBUSINESS_VOL_x64FRE_pt-pt.esd 19042.572.201009-1947.20h2_release_svc_refresh_CLIENTBUSINESS_VOL_x86FRE_pt-pt.esd how can i create one ISO with for 32 or 64 bits PCs and selecting 32 with goes for all x86 editions or selecting x64 goes for x64 editions? because i tried and both 32 or 64 on boot have x86 and x64 editions.. like if i selected 32 bits on UEFI it show goes for x86 editions only, and not x86 and x64.. did u get it? decrypt.cmd is simple to use, but i'm confused when i use multi_arch_iso.cmd to create the AIO iso.. and btw is it possible to create 1 ISO for work on 32 and 64 bits platforms without choosing them on UEFI?
@Enthousiast installed it now switched to 20H2 but same error with kb xxxx311 errorcode 0x800f0984 methode windows update online maybe du to msgm toolkit or media creation tool i m building new windows from uupdownload
Download and extract ESD>ISO to a simple folder, put both ESD files in that folder and run decrypt.cmd Or put the x86 ISO and the x64 ISO next to the multi-arch_iso.cmd and run the cmd. You won't be able to install x86 on UEFI, needs very specific hardware to do it.
@Mr.X Replaced the dutch screen with an english one: https://forums.mydigitallife.net/th...20h1-2-vb_release.80763/page-261#post-1625372
Code: CONX CHostIsNewerChecker invoked. CONX pGetHostCSDBuildNumber: 'HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\CSDBuildNumber' does not exist. Assume 0 CONX Host OS version: 10.0.19042.0 (0.0) Platform 0x2, SuiteMask 0x300, ProdType 0x1 CONX Target OS version: 10.0.19041.508 CONX ConX::Compatibility::CSystemAbstraction::HostIsNewer: Host is newer than target. CONX CHostIsNewerChecker: checked HostIsNewer, found HardBlock. changing wim version to 19042 will not help it read the version from setupcompat.dll itself
Hi, so another question about 20H2 language pack compatibility. Someone already said the 20H1/2004 language packs are compatible with 20H2. But what about FOD packs? And what about WinPE language packs to add multilanguage to winre.wim and boot.wim? I really hope I can reuse what I already have on 20H2. Thanks.
It's called an in-place upgrade because apps, programs, files, and data are allowed to remain in-place with their configuration settings remaining intact, while the operating system (OS) files are replaced. An in-place-repair replaces potentially corrupt OS files with the same version of the OS files. An in-place-upgrade replaces the OS files with a newer version of the OS files. The advantage of an in-place install is that you don't have to reinstall programs like MS Office. They remain installed and are generally unaffected by the in-place install.
All are the same you just need to add-re-add Latest Cumulative Update afterward WinPE probably won't need that
Regarding the in-place install issue... If you are running 19042.572 and you want to perform an in-place repair, run regedit.exe and take ownership of the EditionVersion key. Then change the version and build subkeys to 19041.508. Reboot, mount the MCT ISO (19042.508) or ESD converted ISO (19042.572) to a drive letter, and run the Setup.exe from the ISO as administrator. I've successfully performed this in-place install with both ISOs. [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\EditionVersion] <---Take ownership of this key "EditionBuildBranch"="vb_release" "EditionBuildLab"="19041.vb_release.191206-1406" "EditionBuildLabEx"="19041.1.amd64fre.vb_release.191206-1406" "EditionBuildNumber"=dword:00004a62 <---Modify this key to the 4a61 value. "EditionBuildQfe"=dword:0000023c <---Modify this key to the 1fc value.