Post-Setup not installing any programs

Zoom7000

New Member
I've been using the same preset for my Windows 10 images with NTLite and just creating a new image every time there was a major release. I created an image using 1909 and the post setup worked fine. However, when I now try to create an image using Windows 10 2004, the post setup won't install any of the programs.

I'm not getting any errors at all. Any idea what's going wrong?
 

Attachments

  • Preset.xml
    65.3 KB
ege914 I already tried the method you recommended (have the software on the roof of USB/ISO) and for whatever reason, the oobe.cmd script did not execute before Windows logon to desktop. I'm still currently investigating to find a solution. I suspect Microsoft did some changes to Windows 10 itself. This wasn't an issue with WIndows 7, 8/8.1before.

:cool:Has anyone else come up with a solution for programs install via post setup, feel free to share

put it inside setupcomplete.cmd
and enable setupcomplete under unattended part in ntlite...
 
George King Alrighty I'll check out your new tutorial.

@ega914 I assume you are talking about adding the code for the oobe.cmd into the setupcomplete.cmd script to be execute, right.
If you don't mind, can you kindly show the code you used for the oobe.cmd inside setupcomplete.cmd? Thanks.
 
@ega914 I assume you are talking about adding the code for the oobe.cmd into the setupcomplete.cmd script to be execute, right.
If you don't mind, can you kindly show the code you used for the oobe.cmd inside setupcomplete.cmd? Thanks.
NTLite - Unattended page - OEM SetupComplete (check the checkbox in toolbar)
 
Kasual Thanks but I already have the OEM SetupComplete checked in Unattended page. What I meant was I assumed one much add the OOBE.cmd on in the Post-Setup page so that NTLite can add it to the SetupComplete.cmd (assuming this is what ege914 meant) which I'm currently testing out.
 
oobe.cmd runs by (Ms) design before setupcomplete.cmd, Post-Setup page (aka Setupcomplete.cmd) runs between 6 & 20 seconds later.
 
I want to give an update, I'm able to add the OOBE.cmd into SetupComplete.cmd and able to see software install at Post-Setup before the Desktop appear. See the snip below. Thanks to ege914 and Kasual (and anyone else I missed) - I wouldn't have gotten this far without your helps.
WIN10PRO_VM_ROE_SUCCESS.JPG
 
George King Alrighty I'll check out your new tutorial.

@ega914 I assume you are talking about adding the code for the oobe.cmd into the setupcomplete.cmd script to be execute, right.
If you don't mind, can you kindly show the code you used for the oobe.cmd inside setupcomplete.cmd? Thanks.

Actually no i was only putting that code inside setupcomplete.cmd, i'm not using oobe.cmd right now.... unattended software setups will work fine both under oobe.cmd and setupcomplete.cmd since they are adding runonce commands to regedit. and they work after user logged in... placing runonce commands to where ever you like doesn't matter...
 
Actually no i was only putting that code inside setupcomplete.cmd, i'm not using oobe.cmd right now.... unattended software setups will work fine both under oobe.cmd and setupcomplete.cmd since they are adding runonce commands to regedit. and they work after user logged in... placing runonce commands to where ever you like doesn't matter...

Oh okay I see what you are saying, cool.
 
I want to give an update, I'm able to add the OOBE.cmd into SetupComplete.cmd and able to see software install at Post-Setup before the Desktop appear. See the snip below.

SetupComplete.cmd works ok in virtual machines, seems like it doesn't in OEM branded with product key embedded computers.
 
SetupComplete.cmd works ok in virtual machines, seems like it doesn't in OEM branded with product key embedded computers.

Well, the purpose of VM is to test out to make sure W10 customize image working as intend before using it on actual PC. We all don't like unexpected surprises when it come to this kind of stuff:)
 
Back
Top