Borked OOBE, looking for some fresh eyes

domainofthegods

domainofthegods

New Member
Hey all.

I must've been a bit overzealous, trying to create the most barebones install for Steam games ONLY that won't work on Linux (which I'm switching my main OS over to). On Windows 10 LTSC IoT x64 21H2, and the OOBE blue screens and perpetually reboots when it restarts after picking drive and letting it install files. Looked over every setting for OOBE for an hour or two and enabled, retested, still the same thing. Anyone have some advice on what specifically could be causing it? What I was working toward:
  • No Windows Update (CUs missing downloaded, only updating from Host Refresh)
  • No Defender, Firewall, or Windows Search (from Taskbar)
  • No Xbox services (except for peripherals)
  • Wifi & Bluetooth but no printing
I've uploaded the .xml preset if anyone wants to check it out. Thank you.
 

Attachments

  • preset.xml
    46.6 KB
Last edited:
1. Disable CompactOS in Unattended. I doubt it's causing your BSOD, but it temporarily removes one possibility.

2. This component is required for a normal system:
Code: 
<c>onecoreuapcommonproxystub32 'OneCore UAP Common Proxy Stub - 32 bit'</c>

3. After OOBE crashes, I would turn off the system (don't allow it to reboot). Boot from a normal (unedited) Windows ISO. When you reach the first Setup screen, stop and enter shift-F10 to open a CMD window.

4. Browse folder "\Windows\Panther“ on the mounted boot drive. Copy setupact.log & setuperr.log to the USB device.h

5. Transfer these files to a working PC, ZIP them and post here. Those files will explain the last steps Windows setup was running.
 
Here it is! setuperr.log was empty, but I included it anyway. See some warnings on the other log file, that might be why? Uploaded the zip. If this ends up being something small I will never live it down. The post-setup script I have is supposed to run on first-logon, according to a thread I read, but maybe that should be removed just in case? Not sure at this point
 

Attachments

  • logs.zip
    749 bytes
Got it, testing now. I have a quick question, however.

  1. Turning off Cumulative Update cache (LCU) in "Remoting and Privacy -> Windows Update Service -> Windows Update" disables enqueued updates (or specifically CUs) from being included in the ISOs during processing?
 
Last edited:
Yep, got disk.inf back and it purred like a kitten. 42 processes, and everything looks alright (praying that I haven't broken something somewhere that I need). Appreciate the help, def should be looked at to add to OOBE compatibility.
 
domainofthegods said:
Turning off Cumulative Update cache (LCU) in "Remoting and Privacy -> Windows Update Service -> Windows Update" disables enqueued updates (or specifically CUs) from being included in the ISOs during processing?
Click to expand...
When LCU updates are applied to an image, they're staged under \Windows\SoftwareDistribution. Clearing this cache will shrink the install image by the size of the downloaded updates, but eventually if you install new updates on a live system -- the same folder gets re-populated with new update files.

The end result is one-time disk savings on the install image, but no permanent change on a live system.
 
garlin said:
When LCU updates are applied to an image, they're staged under \Windows\SoftwareDistribution. Clearing this cache will shrink the install image by the size of the downloaded updates, but eventually if you install new updates on a live system -- the same folder gets re-populated with new update files.

The end result is one-time disk savings on the install image, but no permanent change on a live system.
Click to expand...

Makes sense, I included it anyway since I'm trying as few updates as possible, good to have it up-to-date to start. Thanks for the break down!
 
No offense to nuhi, but LOL that NTLite allows you to remove the Windows disk driver.

The reason it fails is because WinPE has its own separate drivers. Setup begins by extracting the image to the system partition, and makes the installed Windows ready for its first boot. Setup and WinPE exit by restarting into new Windows. And now your trouble starts, and I suspect it's not actually making it anywhere close to the 2nd reboot, when OOBE actually runs.
 
You must log in or register to reply here.
Back
Top