Stuck at OEM logo

[bunnxr]

my image on my friend's computer, gets stuck on OEM logo, we try to restart it does move forward but then it gets stuck on windows logon screen. doesn't move forward.

I've attached the files below, as well as the registry files I've been adding to it.
The image on my PC works flawlessly, also in my other friend's PC which aren't OEM based.

kindly help. : (

 

[garlin]

1. OEM SetupComplete is enabled, but you don't have any Post-Setup commands to run.

2. Disable SkipMachineOOBE & SkipUserOOBE because you only partially created the user logon settings.

3. Check for missing driver support (stuck at logo).

 

[nuhi]

Hm, if an image works on 2 out of 3 PCs, then it's about Windows/drivers/hardware somehow.

Non-edited ISO should have issues for him as well. Try booting to UEFI on that PC, try disabling CSM if possible.
Or the other way around, enable CSM in the BIOS if not already and boot non-EFI.
Point is there are 2 ways of installing Windows, UEFI is recommended.

 

[nuhi]

1. OEM SetupComplete is enabled, but you don't have any Post-Setup commands to run.

2. Disable SkipMachineOOBE & SkipUserOOBE because you only partially created the user logon settings.

Nice catch, that also could be it. In which case there will need to be auto-skip of it if no Post-setup actions.

edit: it is already skipped if no setupcomplete, so no change necessary and this cannot be the cause

 

[bunnxr]

1. OEM SetupComplete is enabled, but you don't have any Post-Setup commands to run.

2. Disable SkipMachineOOBE & SkipUserOOBE because you only partially created the user logon settings.

3. Check for missing driver support (stuck at logo).

1. i had OEM setupcomplete disabled before, but i thought that might be it so i tried enabling it.

2. that's exactly what i thought i could do for this. having unattended to default may do it

3. as i am fairly new to this, learning as i progress. i tried to include nvidia drivers before but it made the installation of 80gbs, since all the drivers are automatically installed via windows if connected to a network. i decided to not bother with drivers.

as a noob question - can i not have an ISO or preset created/made that i can deploy to any hardware i want? if it's the unattended that causes such problems then I'd rather keep it to default than have to work around for configurations for each individual hardware. lemme know if that's possible.

anyways thanks for yall's help. I'm grateful

 

[garlin]

Every Windows release includes a basic set of default drivers collected by MS at the release date. They can't include every possible driver because the image size would be too big. MS works with the major OEM & chipset companies to agree what should be included.

But you may have a new (or very old) PC that really needs a storage/USB/ACPI driver to work. Then you have to customize the image by integrating drivers. You won't know until you try installing the image.

Adding more drivers increases the chance your ISO will work on all PC's -- but it makes both the ISO and the installed image size larger.
Some users choose to add the most popular drivers like the latest AMD, NVIDIA, Intel USB, Intel NIC, etc.

The trick with NVIDIA drivers is you need to know the EXACT driver instance (nv*.inf).

When you import the NVIDIA driver folder, it loads all the different model types. Each driver instance wants a separate copy of the same NVIDIA library DLL's, and you end up with 80 GB of duplicated DLL's. After you find out which nv*.inf the specific one for your card, just install that INF instead of importing the whole NVIDIA folder.

 

[bunnxr]

Hm, if an image works on 2 out of 3 PCs, then it's about Windows/drivers/hardware somehow.

Non-edited ISO should have issues for him as well. Try booting to UEFI on that PC, try disabling CSM if possible.
Or the other way around, enable CSM in the BIOS if not already and boot non-EFI.
Point is there are 2 ways of installing Windows, UEFI is recommended.

he did boot in UEFI only, didn't try mbr

 

[garlin]

Your friend might also try disabling SecureBoot, if there's an unsigned driver problem.

 

[bunnxr]

Every Windows release includes a basic set of default drivers collected by MS at the release date. They can't include every possible driver because the image size would be too big. MS works with the major OEM & chipset companies to agree what should be included.

But you may have a new (or very old) PC that really needs a storage/USB/ACPI driver to work. Then you have to customize the image by integrating drivers. You won't know until you try installing the image.

Adding more drivers increases the chance your ISO will work on all PC's -- but it makes both the ISO and the installed image size larger.
Some users choose to add the most popular drivers like the latest AMD, NVIDIA, Intel USB, Intel NIC, etc.

The trick with NVIDIA drivers is you need to know the EXACT driver instance (nv*.inf).

When you import the NVIDIA driver folder, it loads all the different model types. Each driver instance wants a separate copy of the same NVIDIA library DLL's, and you end up with 80 GB of duplicated DLL's. After you find out which nv*.inf the specific one for your card, just install that INF instead of importing the whole NVIDIA folder.

that's helpful and saddening at the same : (

i only want few $OEM$ folder files changed, have some of my files in it. some of the settings removed along with components. and just my registry tweaks. I'd try skipping the unattended part and see if it does work.