Tommy, I must say thanks for creating this thread - I, too, have been messing around tweaking Windows images (from XP to Windows 7) for quite a while. It's a lot of work to customize Windows as one see fit.
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:)
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.
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.
George King Awesome tutorial. One question, like ege914 was saying, is it possible to add subdirectories for the setup folder under $OEM$ - see the snip below just to get general idea:
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.
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...
George King It's been a minute I ever do this RunOnce thingie since the Windows 7 days (and probably XP day too) - which is why I'm having bit of difficulty figuring out. But thanks for the that old tutorial of your - I'll look into that - appreciate it. Look forward to seeing your result with...
nuhi, cool I see what you are saying. For me I created an OOBE.cmd which is in the script folder along side the SetupCommand.cmd file. See the snip below.
Below is the $OEM$ structure
I've tested my customized WIN 10 Pro image in VM and it turned out couple of programs (Firefox & 7-Zip) got...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.