Win10XPE Project

Win10XPE_2020-10-29 update is not working for me.
I build 20H2 2009 with it in win7.

Hi

sorry to hear you're having probs - not sure what to suggest, can only confirm that in my case building on a win7pro system using 20H2  - UK int from Techbench as source, I've built at least 6 times today without a problem.

Thanks but,
Win10XPE_2020-10-29 update is not working for me.

I build 20H2 2009 with it in win7.
Build was successful, but boot failed with it.
when I boot with it "files loadinig..." message and progess bar is not displayed but after seconds windows logo is displayed, after then
"Welcome, the Configuration is in Progress..." message is not displayed, just screen is black and system is stopped or automatically rebooted. x86/x64 both.

so, I edited pecmd.ini "KILL explorer.exe" and "SHEL %WinDir%\explorer.exe" lines with
old "FIND $%USERNAME%=SYSTEM,SHEL %WinDir%\explorer.exe" code, but it's the same. It doesn't help.

Regards.

Your report of the booting process is consistent with the known issue of C rather then X in the registry...
extract project release to a clean win10xpe directory and verify tools/regfind.exe was not blocked by AV software (although it is a MS file from 2013)

With 20H2 - MSEdge (chromium Based) is now the Default Internet Browser - although install.wim contains older version 84 and not the newest

got same issue with 20H2, booted then stuck .

previous version got an issue too

so i reverted back to 1809 iso, works perfectly.

(my system is Win10 1909)

I build 20H2 2009 with it in win7.
Build was successful, but boot failed with it.

I took out my old Windows 7 x64 home PC for a test rather than doing it in a VM.

I built from the last package Win10XPE_2020-10-29 downloaded  and extracted it into a new folder and I added an AV exception on the base folder.
And I used the latest TechBench final ISO  "Windows 10, version 2009 - 20 H2 (build 19042.XXX)" French x64 as source mounted in a drive, via imdisk.

I didn't encounter any problems during construction and at start-up.
It is good for APT as well. No idea what your problem is !

I just noted that:

Code: [Select]

C:\Windows\System32\bcdedit.exe /store "%BaseDir%\ISO\Boot\bcd" /set {default} bootmenupolicy legacy

Is not applied but it is not a problem, it's just cosmetic.

I updated the package with the same date Win10XPE_2020-10-29
It's just cosmetic to avoid 8 Warnings in the log: RegWrite - Overwrote existing key
With some System,ERROROFF added in Core.script and in GoogleChrome_86.0.4240.75_XPE.script

Finally, I found the reason!

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

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).

Please fix it.

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

confirmed, black screen and reboot (at least in VM) with full or basic build with above checked

Finally, I found the reason!

Good

I will try to see for "Use Full Win10 Software hive" build option. As soon as I have some time.

For korean input, what is the language of your Windows 10 20H2 source ?
If it is ko-KR, Ime_ko-KR.Script and Ime_Common.Script are automatically called.
There may be something missing but it's hard to know for a non-Korean and to fix it.
The original script was developed by Flower3 which is Korean. Maybe someone can help you on windowsforum.kr.

it is ko-KR.
I don't know yet whether korean input works or not because I can't boot with "Use Full Win10 Software hive" option checked.

Hi ChrisR,
I get the same error as circcc is seeing - black screen & reboot.  I am using a base 10.29 build with 20H2 English OS.
Unchecking this box fixes the black screen & reboot issue.
Changing the build from 20H2 to 2004 solves this reboot issue while leaving the "Use Full Win10 Software hive" option checked.

Thanks Chris for all your work!

I would suggest you use 20H1 or a Preview Release as the install.wim registry if messed up in 20H2 with all references to C: rather then X:
As the version in PE is 19041.1 anyway

Hi

I know we all like to ensure compatibility in the projects, but is there any actual advantage for PE in 20H2 whether it's the odd TechBench version or otherwise. I don't need the 'full software hive' so 20H2 is working for me, but I think I'll stick with 20H1 anyway for the time being, unless someone can give me a definitive reason not to.

confirmed, black screen and reboot (at least in VM) with full or basic build with above checked

sorry to hear you're having probs - not sure what to suggest, can only confirm that in my case building on a win7pro system using 20H2  - UK int from Techbench as source, I've built at least 6 times today without a problem.

There is a lot of BUGs are only happened in particular environment, pattern.
Windows 10 updates weekly, but I don't get any issue that Microsoft said they fixed.
No matter how many time you built successfully, not means others report is false.


>not sure what to suggest

We can suggest that  show more infomation about the build OS version, Windows ISO media.
We can suggest that try to extract to a new folder, and build with default settings.
upload the build log, to compare with the succecced one.
etc.

Finally, I found the reason!

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

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).

Please fix it.

I can confirm that Chinese IMEs work fine with or without Full Win10 Software hive. (Not work with WinBuilder, but OK with WimBuilder2.)

And I tested 20h2 with "Full Win10 Software hive" by WimBuilder2.
Boot is fine, and the Korean input works, too.



I tried Win10XPE_2020-10-29, got the same issues as you reported.

Compare the Win10XPE_x64.ISO/sources/boot.wim(WinBuilder) and BOOTPE.ISO/sources/boot.wim(WimBuilder2),
you can got the difference and fix this issue.

i' ve upgraded my OS to 20H2 (French OS)
Used 20H2 iso to build.
USB booted, system is up but black screen (cursor is Moving, you can launch taskmgr but no desktop)

If i use WINXSHELL, everything is ok.

Hope this help.

No matter how many time you built successfully, not means others report is false.

   Why would you imagine that anyone was considering the reports false, we can all, only report the symptoms we are seeing, in the environment we are using, in an effort to collectively find a resolution to a particlular problem.

I can confirm that Chinese IMEs work fine with or without Full Win10 Software hive. (Not work with WinBuilder, but OK with WimBuilder2.)

I agree that Korean IMEs, Chinese IMEs should work with or without Full Win10 Software hive.
I know it worked (at least before) but then I don't test with new Windows versions, so I need feedback from Korean, Chinese...
Let me know how it (IME) works with 20H1 and 20H2 with the Default Software hive (without Full Win10 Software hive).

I'm on the right path to fix the problem with the Full Software hive.
Iit seems to be inconsistencies in the registry between winre.wim and install.wim software registry. I'm on it.

Let me know how it (IME) works with 20H1 and 20H2 with the Default Software hive (without Full Win10 Software hive).

Hi, ChrisR

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

https://github.com/slorelee/wimbuilder2/commit/6d0637c03fdb612fec39a720a3afe4adfad4a68d#diff-bb5bb27d7d44887fd7e285c87a0014ab835e3d6b2086593a2724efc71e7afb3d
update 19h1 support
slore committed on 8 Apr 2019


But your Win10XPE_2019-04-18.7z release don't have that.

Add next code, Chinese IMEs can work without the Full SOFTWARE hive.

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

I don't use Korean IMEs, too. So Korean IMEs still need the Full SOFTWARE Hive.
I don't get fix patch for Ime_ko-KR.bat.

Litte  , should we reply in
Here(Win10XPE Project)
Or
Win10XPE Project General Discussions

I'm on the right path to fix the problem with the Full Software hive.
Iit seems to be inconsistencies in the registry between winre.wim and install.wim software registry. I'm on it.

In the morning, I had take a look on it as I already got the two boot.wim. But I don't know why it got lots of difference with Beyond Compare.
No Lucky, I don't find the specify keys.

(For build with 20h2 ISO by WimBuilder2.v2020.10.10, you need to go to [About] page, and click the [Update] button to checkout the latest source code.)