oobe.cmd errors

peter_58_ha

New Member
Hello from Germany!

I´m new to NTLite and i´m trying to integrate a couple of apps like Office 2019, 7zip annd greenshot to the ISO.

Integration of (DELL-) drivers and latest W10 64 online updates was the easy part.
But the oobe.cmd will not run.
This is what I have done to far:

creating the folder structure anbd placing the oobe.cmd to this folder:

C:\W10-20H2-Work\sources\$OEM$\$$\Setup\Scripts

the oobe.cmd was created by the step by step tutorial from this forum to integrate Office 2019 and install in silent mode using YAOCTRIR_Installer.cmd script.

I placed a couple of apps to the "setup" folder, see attached pics.

My autounattended
 

Attachments

  • O2019.jpg
    O2019.jpg
    14.4 KB
  • setup.jpg
    setup.jpg
    20.8 KB
  • structure.jpg
    structure.jpg
    43.7 KB
Last edited:

George King

Active Member
Hi,

there should be a more things why it doesn't work.
1) Missing Internet Explorer component - see RunOnceEx protector in tutorial
2) OEM key was detected by setup and OOBE.cmd was skipped
3) Please see again part about applications inside setup folder. Only 7z will be installed in your system due bad naming

First problem should be solved very easily.
Second problem is another cup of tea, but I have new workaround, it's still not perfect, but if you are interested let me know I can send you unreleased Autorun.dll patcher, this tool adds support for custom scripting using RunOnceEx.cmd as there is no need to use OOBE.cmd in new solution
Third problem is also easy to solve
 

peter_58_ha

New Member
Hi,

there should be a more things why it doesn't work.
1) Missing Internet Explorer component - see RunOnceEx protector in tutorial
2) OEM key was detected by setup and OOBE.cmd was skipped
3) Please see again part about applications inside setup folder. Only 7z will be installed in your system due bad naming

First problem should be solved very easily.
Second problem is another cup of tea, but I have new workaround, it's still not perfect, but if you are interested let me know I can send you unreleased Autorun.dll patcher, this tool adds support for custom scripting using RunOnceEx.cmd as there is no need to use OOBE.cmd in new solution
Third problem is also easy to solve

George King

thx for your answer!

Let me check no. 1 from your list. Will walk through the tutorial agian
OEM Key: no, I dont not use any (OEM-) key for the autounattend
bad naming: I have to idea, whats going on with those apps, even 7zip will not be installed.
What do you mean with "bad naming"?

Yes, pls sent the autorun.dll patcher. Im running into a problem using the official released patcher.
Thx and best regards

Peter
 

George King

Active Member
OOBE.cmd or RunOnceEx.cmd is designed for this naming structure
1618167608198.png

I'm not talking about OEM key added by you, but it can be caused by OEM key in BIOS. More info is in this topic

About unreleased patcher we can continue in PM
 
Top