definitely, but still asking as if released & posted but somehow I missed/overlooked that. So, am taking this answer as a 'NO'?
I can't get the cmd to work. I mount the iso first, the image is mounted in drive I. Then I issue the command: dism.exe /image:"I:\sources\install.wim" /Get-CurrentEdition. What did I do wrong?
First you need to mount the install.wim and next you need to aim the command at the mount folder, not the wim itself. ps, for being able to mount an install.wim from a mounted ISO you need to use this switch too: Code: /ReadOnly
It does work. Here are the steps if anyone is interested in: Code: DISM.exe /Mount-Image /ImageFile:I:\sources\install.wim /Index:3 /MountDir:D:\TEMP /ReadOnly Code: DISM.exe /Image:D:\TEMP /Get-CurrentEdition Image Version: 10.0.19043.928 Current edition is: Current Edition : Enterprise
Quoting myself to confirm that I've tested the final ISO and the issue persists. After installing Win10 32-bit, only first boot works. After a restart it just hangs at loading logo and won't start anymore. i7-8700K / Gigabyte Z370 Gaming 3 / 16GB RAM
In my opinion, it's a similar issue like Windows 10 Build 17763. (You can't run Windows 10 Build 17763 on the pure 32-bit PC because the ntoskrnl requires some instructions which is only on PC with 64-bit support.)
It's been a while since I have been on here. What version/release do the experts advise to download for 64x (dutch option) pro version. That is just close to retail and can be updated normally and activated with kmspico. What I currently have: Windows 10 pro-N 1909 NL thanks again.
The point is that there is a right time and a wrong time to apply an Enablement Package (EP). MSFT has provided a mixed answer to this question. It would be nice to know the build number for the earliest crossover build to which the 19043 EP could be applied and still activate all the features embedded in the build.