blank screen 2020-11-01

build win10xpe_2020-11-01, virtualbox vm, x86 or x64

I am trying to make a build with all un-necessary apps removed.

Base build (as is) with either x86 or x64 works fine, but when I remove any of the app components - it appears to start (win logo spinning wheel) - but then a black screen (with moving mouse arrow).  refreshed before the build after the apps were removed.

Any ideas what the problem would be?

Base build (as is) with either x86 or x64 works fine, but when I remove any of the app components

Are you doing it by using the 'Basic Build' or is it over and above the use of 'Basic Build' in which case what are the apps you're removing?

Hi APT

downloaded winxpe_2020-11-01, attached win10x86_20h4 (latest build) os, pushed blue button ..... worked fine.  went back to project and removed check first 3 app items, did a refresh, and pushed blue button again.  Job created the ISO.  Then built vb vm for x86 os and installed the ISO.  Windows logo came up, spinning dots   ..... then blank screen (waited 15 minutes to make sure).  Have done this a bunch of times on previous builds with success, but no luck with the new build.  Have tried every combination I can think of to make it work .... but no go.

garyd

Hi

I'm not sure what Win10 20H4 is, but with the current problems around 20H2, I wouldn't even try, I'd stick with 20H1 if I were you, unless you have a specific need for it. But I'm still trying to find out if your project will complete and run with 'Basic Build' checked?

got to laugh am myself .... I didn't know what basic build was.  Now I realize it is right under build core ... and the answer is:  NO I don't have it checked.

We use winxpe to verify a pc will run windows 10, win10 20h4 is the latest build, so I was trying to move our utilities to that build (which I think was referenced in the new win10xpe build notice).  Not critical ... just trying to get it to run.

g

OK, just tried a build with "basic build" checked ... and got the same blank screen.


g

I didn't know what basic build was.  Now I realize it is right under build core ... and the answer is:  NO I don't have it checked.

It's worth using, not just to check the basic works (very quickly) but you can also select individual apps and check them out by themselves, which can let you know if it's that app causing a prob or it's interaction with another

We use winxpe to verify a pc will run windows 10, win10 20h4 is the latest build, so I was trying to move our utilities to that build (which I think was referenced in the new win10xpe build notice).

The last referenced Win10XPE version in the package description is Oct 2020 (2009) which for me is 20H2, anything after that is not supported at the moment (Windows Insider Builds). If it is the Win10 Oct2020 release your testing with, downloaded from TechBench, then you may see odd errors still I guess,
however, I believe I'm correct in saying if you d/l the official ESD based iso and convert it a Wim based iso (so as to speak), it would be OK

nb. 20H1 also suggested by project author http://theoven.org/index.php?topic=2421.msg39101#msg39101  for various reasons, that started off with 20H2 giving similar symptoms to that which your describing

A "Basic Build" just runs the "Build Core" options
So if it is crashing then the issue is with an option selected in "Build Core"
You need to find what option is causing the crash by removing "Build Core" options one at a time...
Most likely a "Driver" issue as I have tested up to Preview Release 20251