Win10XPE Project

Win10 Pro x64 English:

19041.508 100% OK
19041.572 and 19042.608 Blue screen of death and reboot.

I checked the commit about IME_Common.bat, I know why IMEs can not work with your WIN10XPE.

Thanks Slore, I'll watch and follow you 

In 10.0.19041.508, after C:\ to X:\ mixups, I found the anomaly for the Full Software Hive

The SideBySide version of amd64_microsoft.windows.common-controls does not match the WinRE WinSxS folder:

In Full Software registry (19041.488):

Code: [Select]

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\Tmp_Software\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_microsoft.windows.common-controls_6595b64144ccf1df_none_62fe57338acfab7a\5.82]
@="5.82.19041.488"
"5.82.19041.488"=hex:01

[HKEY_LOCAL_MACHINE\Tmp_Software\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_microsoft.windows.common-controls_6595b64144ccf1df_none_62fe57338acfab7a\6.0]
@="6.0.19041.488"
"6.0.19041.488"=hex:01

In \Windows\WinSxS folder (19041.1):

Code: [Select]

amd64_microsoft.windows.common-controls_6595b64144ccf1df_5.82.19041.1_none_4b395a7b3c8e63ab
amd64_microsoft.windows.common-controls_6595b64144ccf1df_6.0.19041.1_none_b555e41d4684ddec

Here is the fix, for now in Additions, "Add or Edit converted PE registry":

Code: [Select]

[Registry]
// Fix 10.0.19541.508 Full Software Registry (@="6.0.19041.488" vs WinSxS\amd64_microsoft.windows.common-controls_*_6.0.19041.1_none_*)
RegWrite,HKLM,0x3,Tmp_Software\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_microsoft.windows.common-controls_6595b64144ccf1df_none_62fe57338acfab7a\5.82,5.82.19041.1,01
RegWrite,HKLM,0x1,Tmp_Software\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_microsoft.windows.common-controls_6595b64144ccf1df_none_62fe57338acfab7a\5.82,,5.82.19041.1
RegWrite,HKLM,0x3,Tmp_Software\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_microsoft.windows.common-controls_6595b64144ccf1df_none_62fe57338acfab7a\6.0,6.0.19041.1,01
RegWrite,HKLM,0x1,Tmp_Software\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_microsoft.windows.common-controls_6595b64144ccf1df_none_62fe57338acfab7a\6.0,,6.0.19041.1

I haven't tested yet 19041.572 or 19041.610 To know how they are for these 2 anomalies with the Default and the Full Software ?

Win10 Pro x64 English:

19041.508 100% OK
19041.572 and 19042.608 Blue screen of death and reboot.

~Same result here with Win10 Pro x64 French

Techbench ISO 10.0.19041.508 100% OK

With Media Creation Tool 10.0.19041.572, everything seems to be loaded and I get the startup sound but the screen stays black.
As it is originally install.esd (not supported), not sure if I'm looking any further.

When I uncheck that option, boot success! but, I can't input korean.
Maybe you don't need that option(default = off), but It is must for korean input(japanese, chinese,.... maybe).

I have completed Ime_Common.Script, following Slore's instructions 

If,%SourceBuild%,Bigger,18300,RegCopyKey,HKLM,Tmp_Software\Microsoft\FuzzyDS
+If,%SourceBuild%,Bigger,18300,RegCopyKey,HKLM,Tmp_Software\Microsoft\Input

 Ime_Common.Script (4.89 kB - downloaded 6 times.)
It would be nice to know if it works with the Default Sofware hive.

It's not working.

Thanks for the test and the feedback
It's a shame it doesn't work with the default Software hive.
Maybe it will come one day by a Korean friend

"Use Full Win10 Software hive" build option is the problem in Win10XPE_2020-10-29 with 20H2.

If I can get confirmation, I think it is fixed now with the right version in the Full Sofware registry for SideBySide, amd64_microsoft.windows.common-controls*

Projects\Win10XPE\Features\  Config.Script (27.55 kB - downloaded 14 times.)

Let me remember how to fast convert install.esd to install.wim in order to use any official MS ISO and not be dependent only on TechBend.

In a command prompt as admin run this to get an image number (Home, Pro, Education, etc):
DISM /Get-WimInfo /WimFile:E:\sources\install.esd

Then to export from install.esd to install.wim the chosen image, for example, the number 6, run :
dism /export-image /SourceImageFile:E:\sources\install.esd /SourceIndex:6 /DestinationImageFile:E:\install.wim /Compress:max /CheckIntegrity

"Use Full Win10 Software hive" build option is the problem in Win10XPE_2020-10-29 with 20H2.

If I can get confirmation, I think it is fixed now with the right version in the Full Sofware registry for SideBySide, amd64_microsoft.windows.common-controls*

Projects\Win10XPE\Features\ (Attachment Link)

x86: Boot failed.
x64: Boot success, Korean input works.

P.S.
By the way, I cannot download the attachment again(I'm already logged in, but asked to log in again and again). Since you edited, I wanted to make sure it's the same file I tested(Config.Script = 28,209 bytes).

Cool
I only did it for x64, I'm going to do it for x86 now, it's probably the same thing: x86_microsoft.windows.common-controls* version.

Config.Script has not changed, I've had this before too and I think the cache needs to be cleaned to fix it.
In Chrome, more tools and delete navigation data.

And registry fix for Full Software and both architectures x86/x64 and Wow64.

 Config.Script (29.2 kB - downloaded 18 times.)

And registry fix for Full Software and both architectures x86/x64 and Wow64.

(Attachment Link)

Thanks ChrisR! 

x86 also works.

Let me remember how to fast convert install.esd to install.wim in order to use any official MS ISO and not be dependent only on TechBend.

In a command prompt as admin run this to get an image number (Home, Pro, Education, etc):
DISM /Get-WimInfo /WimFile:E:\sources\install.esd

Then to export from install.esd to install.wim the chosen image, for example, the number 6, run :
dism /export-image /SourceImageFile:E:\sources\install.esd /SourceIndex:6 /DestinationImageFile:E:\install.wim /Compress:max /CheckIntegrity

thanks for the recap 

Great thanks for the tests and feedback 
The mismatch in Win10 20H2 between SxS versions from Winre.wim and Install.wim is fixed now in the Full Software registry.
I'm going to update..

ps: Let me know, if you or any other Korean guy finds something for the Korean IME input with the Default Software registry
It would be nice for the project.
Also, the Default Software registry is more consistent and appropriate than the full hive with Many Many things included that are not used!

Let me remember how to fast convert install.esd to install.wim in order to use any official MS ISO and not be dependent only on TechBend.

In a command prompt as admin run this to get an image number (Home, Pro, Education, etc):
DISM /Get-WimInfo /WimFile:E:\sources\install.esd

Then to export from install.esd to install.wim the chosen image, for example, the number 6, run :
dism /export-image /SourceImageFile:E:\sources\install.esd /SourceIndex:6 /DestinationImageFile:E:\install.wim /Compress:max /CheckIntegrity

thanks for the recap 

Exactly as I had done 

After conversion to install.wim and deletion of install.esd
We can add the ISO's creation (oscdimg is downloaded and include in Projects\Tools\x64\Oscdimg folder):

Code: [Select]

Oscdimg.exe -bootdata:2#p0,e,b"E:\boot\etfsboot.com"#pEF,e,b"E:\efi\microsoft\boot\efisys.bin" -o -h -m -u2 -udfver102 -l"ISOLabel" "E:\" "XXX\ISOFileName.iso"

Great thanks for the tests and feedback 
The mismatch in Win10 20H2 between SxS versions from Winre.wim and Install.wim is fixed now in the Full Software registry.
I'm going to update..

ps: Let me know, if you or any other Korean guy finds something for the Korean IME input with the Default Software registry
It would be nice for the project.
Also, the Default Software registry is more consistent and appropriate than the full hive with Many Many things included that are not used!

In fact, the Korean script needs to be updated because the Korean language input have problem with some programs like notepad in the latest Windows 10 versions. I sent flower3 an update request message, but he is not active, so it is difficult to expect.

And registry fix for Full Software and both architectures x86/x64 and Wow64.

(Attachment Link)

just 4 info: tried a build with that latest script version and still black screen using 20H2 french.

regards.

Hi a66b
Which version of Windows 10 do you use ?
I use the French version also from TechBench "Windows 10 version 2009 - 20H2 (build 19042.XXX)" or version 10.0.19041.508
And I don't have a problem with both architectures, here
Have you tried with the default package, untouched, extracted to a new folder with an AV exclusion

Win10XPE_2020-11-01 update

Support for Windows 10 2009 - 20H2, continuation..
Fix the mismatch in Win10 20H2 between SideBySide versions from Winre.wim and Install.wim for the "Full Software hive" option

WinXShell: Updated to v4.4