Jump to content

setupcomplete.cmd does not run


Recommended Posts

Hi all

I am doing an unattended Windows 2008 R2 build and try to use setupcomplete to install drivers and customize the OS. The Windows 2008 R2 image was syspreped with /generalize and /oobe switch. The image was deployed to another machine and manipulated by booting up in WINPE to place the setupcomplete.cmd into appropriate path. I found that there 2 paths for Windows to pickup setupcomplete.cmd from different web postings

1) %windir%\setup\scripts\setupcomplete.cmd

2) $OEM$\$$\setup\scripts\setupcomplete.cmd, it will then be copied to %windir%\setup\scripts\ and executed

I have been trying to get Windows to run setupcomplete.cmd to no avail, the copy of setupcomplete.cmd in %windir%\setup\scripts got deleted; it is gone when the system autologon after the setup is completed. However, it showed no sign of setupcomplete.cmd being ran (the log that setupcomplete.cmd supposed to create did not show up)

I have also tried placing setupcomplete.cmd in c:\$OEM$\$$\setup\scripts, c:\sources\$$\setup\scripts, c:\sources\i386\$$\setup\scripts; as I read that it would be copied by the OS to the appropriate path and then executed. None of the paths worked.

Just wondering what is the proper place for setupcomplete.cmd so that it will run.

Any help is appreciated.

Link to comment
Share on other sites


Setupcomplete.cmd should be in \sources\$oem$\$$\setup\scripts

Thanks for the reply. I already tried placing setupcomplete.cmd in c:\sources\$oem$\$$\setup\scripts, the setupact.log did not record that c:\windows\setup\scripts\setupcomplete.cmd was found and hence not ran.

Any other ideas?

Thanks a lot for your help.

Link to comment
Share on other sites

Thanks for the reply. I already tried placing setupcomplete.cmd in c:\sources\$oem$\$$\setup\scripts, the setupact.log did not record that c:\windows\setup\scripts\setupcomplete.cmd was found and hence not ran.

Any other ideas?

Thanks a lot for your help.

unattendant, here is the complete path to the log:"?:\Windows\Panther\UnattendGC\setupact.log", where ? is your W7 system drive after install. You say you placed the setupcomplete.cmd in "c:\sources\$oem$\$$\setup\scripts". I assume you mean that it is in the root of your install image, not necessarily in the C: drive? Enjoy, John.

Link to comment
Share on other sites

unattendant, here is the complete path to the log:"?:\Windows\Panther\UnattendGC\setupact.log", where ? is your W7 system drive after install. You say you placed the setupcomplete.cmd in "c:\sources\$oem$\$$\setup\scripts". I assume you mean that it is in the root of your install image, not necessarily in the C: drive? Enjoy, John.

Hi Johnhc

You are correct, c:\ refers to the root of the image. I found the setupact.log at c:\Windows\Panther\UnattendGC\ (after Windows finished setup) and it did not say that C:\windows\setup\scripts\setupcomplete.cmd was found.

Link to comment
Share on other sites

Hi Johnhc

You are correct, c:\ refers to the root of the image. I found the setupact.log at c:\Windows\Panther\UnattendGC\ (after Windows finished setup) and it did not say that C:\windows\setup\scripts\setupcomplete.cmd was found.

unattendant, I am pretty much out of ideas. Are you testing on a virtual system? All the information I have ever seen show $OEM$ in all capitals. You show it sometime in caps and sometime in lower case. I would think it would make no difference, but I am surprised often. I should note that after I install W7 (Ultimate x64), my setupcommand.cmd is still present in the Windows\setup\scripts folder. Is your setup\scripts folder there? If not, then I would think it is not getting copied. Enjoy, John.

Link to comment
Share on other sites

  • 1 year later...

Hi Johnhc

You are correct, c:\ refers to the root of the image. I found the setupact.log at c:\Windows\Panther\UnattendGC\ (after Windows finished setup) and it did not say that C:\windows\setup\scripts\setupcomplete.cmd was found.

unattendant, I am pretty much out of ideas. Are you testing on a virtual system? All the information I have ever seen show $OEM$ in all capitals. You show it sometime in caps and sometime in lower case. I would think it would make no difference, but I am surprised often. I should note that after I install W7 (Ultimate x64), my setupcommand.cmd is still present in the Windows\setup\scripts folder. Is your setup\scripts folder there? If not, then I would think it is not getting copied. Enjoy, John.

did your commands in setupcomplete.cmd auto run after system boot up? my commands seemed did not run. i just put some test commands such as mkdir c:\11

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...