Win10XPE Project

I like to keep the "Switch to Administrator" button, but would prefer the default option is NO in stead of YES.
I expect this would need an edit in Core.script but couldn't find the parameter to be changed.
How can I change the default from No to YES?

How can I change the default from No to YES?

I ment from YES to NO of cause

In Build Core, use PecmdAdmin.ini button to edit it, change the default option:

Code: [Select]

MESS Switch to Administrator? @Switch to Administrator #YN *5000 $N

=>

Code: [Select]

MESS Switch to Administrator? @Switch to Administrator #YN *5000 $Y

Kyhi - has posted an updated fix for Black Screen (Desktop) with 19041-19042.572

In Build Core, use PecmdAdmin.ini button to edit it

Perfect, Thank you.

Kyhi - has posted an updated fix for Black Screen (Desktop) with 19041-19042.572

Great, thanks to James
Thanks for the info and for sharing here Jimehc

Serious bug,In WinXshell mode file open save dialogues not working..it closes application. Would you please fix it.

Serious bug,In WinXshell mode file open save dialogues not working..it closes application. Would you please fix it.

Hi nvbluestacks

I never use WinXshell so haven't seen any probs. Are we talking all apps here for you or one particular one? (that have a file,open save dialogue)
I've only tried notepad and it seems fine, or am I misunderstanding the problem?

edit:  I think ChrisR may have found a solution for you  - sorry Chris I jumped the gun 

No No, I'm just like you APT
I don't really use and in testing, Open/Save also works with the notepad. I don't get it

The addition I made is for MCT 19041.572, as for Explorer, Shell32.dll, SHCore.dll and KERNELBASE.dll from Install.wim are required for drag & drop, services.msc,...

I know this project is for the Desktop PE, but I am trying to make the Server PE work.  Running into the same black screen issue even with the updated Explorer.Script.  Anyone have experience getting Server PE to work, suggestions to try, or am I just wasting my time?

> Anyone have experience getting Server PE to work, suggestions to try, or am I just wasting my time?

Win10XPE project is for the Desktop PE. Less test with Windows Server.
I tried to build with Win10XPE_2020-11-20, yes it when select the Explorer shell, it cause flash black screen, it couldn't work.
The updated Explorer.Script is a fix for Windows 20h2 updated ISO/ESD, it is no help for the Windows Server source.

WinXShell is portable shell applaction, it can run directly in the orgin winre.wim (Windows Server).

Open/Save Dialog is not part of shell, but the Browser Dialog support requirement already be added in "Win10XPE_2020-11-20\Win10XPE\Projects\Win10XPE\Features\WinXShell_AddFiles.txt".
I tried Windows_InsiderPreview_Server_vNext_zh-cn_20262.iso  with Win10XPE_2020-11-20, use WinXShell as shell, the built PE can boot and show the desktop,
and the Save Dialog is fine(tested with notepad.exe Save As ... menu).

This project is contrabuted/tested for Windows 10, the same core version of Windows Server is Windows Server 2019.
If you use Windows Server 2019 as the source ISO, it should work.

Win10XPE_2020-12-15 update

Support for Windows 10 2009 - 20H2, continuation (19041.631)
Black Screen (Desktop) Fix Update
and a few small details updated in the base

GWT.exe: v20.0.10 Un-Upxed to avoid some false alarms
HostNetDrv.exe: Updated to v1.0.1.1
PowerShell Core: back to version 7.0.3 to support external commands. Waiting for the fix in version 7.2.0
Everything: Updated to v1.4.1.1000
Q-Dir: Updated to v9.0.4
Acronis TrueImage 2021: Updated to v34340. Update Language Code for 2021 version instead of lang ID
Macrium Reflect: Updated to v7.3.5365
HWinfo: Updated to v6.40
AnyDesk: Updated to v6.1.0.0
Mozilla Firefox Quantum ESR: Updated uBlock Origin v1.31.0
Mega Optional Application Download: Updated to 2020.12.15

Thank you for all the great updates! I was hoping to find an updated write protect script, asI have not been able to get it working on my own. The new version of IntelWinFE Protect.exe fixes the annoying ghost disks. Love this program. Thank you.

BSOD with this build  19041.631 x64 too when Directx plugin is enabled, and if Directx is disabled audio does not work.
Actually the last build that works without this issue is 19041.508

Hi Oscar,
I do not reproduce for audio with 19041.631 x64 with the default configuration and Basic Build enabled. The sound works well here!
On the other hand, I reproduce the bsod with Directx enabled.
It is another version problem in 20H2 between winre.wim and Install.wim, grr



To fix in DirectX_XPE.script, you can comment out the drivers that already exist in winre.wim.

Code: [Select]

\Windows\System32\drivers\dxgkrnl.sys
\Windows\System32\drivers\dxgmms1.sys
\Windows\System32\drivers\gm.dls
\Windows\System32\drivers\ks.sys
\Windows\System32\drivers\mskssrv.sys
\Windows\System32\drivers\mspclock.sys
\Windows\System32\drivers\mspqm.sys
\Windows\System32\drivers\mstee.sys
\Windows\System32\drivers\stream.sys

==>

Code: [Select]

; \Windows\System32\drivers that already exist in Winre.wim: dxgkrnl.sys,dxgmms1.sys,ks.sys,mskssrv.sys,mspclock.sys,mspqm.sys,mstee.sys,stream.sys
\Windows\System32\drivers\gm.dls

20H2 is tricky for Win10XPE which is based on winre.wim and not on boot.wim. 20H1 is really safer.
Thanks for the feedback.

631 Basic build - audio works
631 with 18 non audio applets - no audio
Preview 20270 with same 18 applets - working audio
seems support for 20H2 is like a dog chasing its tail

seems support for 20H2 is like a dog chasing its tail

Totally, It's a mess, to try to maintain the 20H2 support

Up to Windows 10 1909 - 20H2 (10.0.18362.418)
winre.wim was updated at each Revision. at the same time as Install.wim and Boot.wim

It is no longer the case with 20H2 (10.0.19041.xxx)
winre.wim stays on the 1st revision (10.0.19041.1) while install.wim evolves
In addition to the C:\ drive in the registry instead of X:

I hope they will fix their process for the next versions.
otherwise, it would probably be good to warn in the pre-check step, before building, if the versions do not match
If,Question,"xxxxx#$x#$x Continue ?",10,True,Set,%answer%,Yes
Or plan to use boot.wim as base and add Rejuv, wifi...

But for the moment, the vacations are coming, I don't want to waste time on it.
It is just better to use 20H1 and to forget 20H2

To fix in DirectX_XPE.script, you can comment out the drivers that already exist in winre.wim.

Code: [Select]

\Windows\System32\drivers\dxgkrnl.sys
\Windows\System32\drivers\dxgmms1.sys
\Windows\System32\drivers\gm.dls
\Windows\System32\drivers\ks.sys
\Windows\System32\drivers\mskssrv.sys
\Windows\System32\drivers\mspclock.sys
\Windows\System32\drivers\mspqm.sys
\Windows\System32\drivers\mstee.sys
\Windows\System32\drivers\stream.sys

==>

BSOD Solved.

Also I have found that the problem of no sound was caused by the MS Wmplayer plugin.

The problem is 20H2
As I was able to reproduce No Sound with HD tasks & Office applets

and just to quote a commonly repeated  statement

It is just better to use 20H1 and to forget 20H2

Win10XPE_2020-12-17 update

After efforts to try to support 20H2. There is no need to go further
The result is not really reliable, depending on the components or applications used...

In Windows 10 version 2009 - 20H2 ISOs, update packages were not added to winre.wim, as it is normally done!
And so, the Versions between winre.wim and Install.wim do not match that is a source of incompatibilities and problems.
In addition to the C:\ drive in the registry instead of X:\ (already fixed)
TechBench ISOs and Media Creation Tool ISOs are concerned, ISOs created via UUP files look good.

Except for UUP ISOs, It is preferable to use Windows 10 version 2004 - 20H1  and forget Windows 10 version 2009 - 20H2

In case the versions do not match, I have added a message to inform and ask to continue construction or not (No by default).

Winre.wim Version (10.0.19041.1) Does Not match Install.wim Version (10.0.19041.631)

Incompatibilities Are Likely to Occur With Perhaps an Unreliable Result.

Preferably Use Windows 10 version 2004 - 20H1

Continue Anyway ?