Jump to content

0xc000142 Issue during oobe pass


Recommended Posts

I seem to have an issue that I cannot fix directly.... I will try my best to describe it - but I am currently stumped.

I have two answer files that process my unattended windows installation for our image. In the OOBE answer file, under the first logon commands: I have 5 VBS scripts that get called.

After the 1st script finishes, the computer restarts. Then it calls 4 other scripts before restarting. My logs show that it skips/errors on scripts #2, #3, #4 and then it completes script #5... I then had to record the oobe phase with my phone because the error is so quick!

I am calling my vbs with cscript, so:

<SynchronousCommand wcm:action="add">
<Order>2</Order>
<CommandLine>C:\Windows\System32\cscript.exe "C:\hpcompaq\commands\test.vbs"</CommandLine>
<Description>test</Description>
<RequiresUserInput>false</RequiresUserInput>
</SynchronousCommand>

I end up getting a cscript error ( which I viewed via my paused video):

The application was unable to start correctly (0xc0000142). Click OK to close the application.

When I test the script not via my answer file and using cscript, it does not error on me and performs the task as required. The script modifies our description field in our Active Directory after the computer is named, and attached to the domain.

Any ideas? I know everything works as my 64 bit image calls the same scripts and has no issues...

Link to comment
Share on other sites


you probably don't need the "" with no blank spaces but if you do add then use this instead " in place of

also remove the <RequiresUserInput> since you are putting in a default value

You can capture the logs in Panther folder and be able to see if it is setup error or your script

Link to comment
Share on other sites

@Tripredacus : I couldnt find anything in the event viewer once I got to my desktop. I dont think its the VBS as there is nothing being called that would require a 64 bit or 32 bit OS. ( plus it works when I test the script outside of the answer files - in a 32 bit OS)

@maxXPsoft I will have to re-sysprep it during my testing today to look in that panther location. Is this located: C:\windows\Panther ? Setuperr.txt ?

I have looked there already, and it said something about a DHCP issue with IPv6... but I will have to reconfirm as that might be from a previous sysprep.

Link to comment
Share on other sites

C:\windows\Panther

usually the errors are within setupact.log and easy to find. Best to capture ASAP after error so it will be in very bottom.

Okay, I just syspreped my test machine, and it did NOT pick up its tasks where it left off of after it restarted.... So:

First logon commands:

1) rename - succeeded

2) Restart -suceeded

3) do scripts 2-5 - Failed!

I have the login count set to the proper amount under the local administrator, so that isnt the issue. I also checked the panther file and could not find anything jump out at me... but here is the log:

setupact.txt

SIDE QUESTION:

What are the best practices when calling scripts? Using a batch file that calls my script? Call cscript which calls my vbs? Call my vbs directly? 95% of all my scripts ran during FirstLogonCommands are vbs'.

Edited by ZeroStack
Link to comment
Share on other sites

Okay Update:

I changed them to all use cscript ( except the batch script in my FirstlogonCommands) and I am back to square one....:

1st script: Rename - passed

2nd script modify active directory description on computer's information pulled from DHCP... - SKIPPED ?!

3rd script Activate some software keys - passed

4th do a post driver installation fix - passed

5th do some file deletions - passed

I know/have troubleshooting & debugging skills - I just came on here because I was confused that it worked on 64 bit, but not 32 bit. :/

I have logging set up in that script that writes to a file once specific events occur and yet it seems like the script is skipped entirely...

I will do some debugging steps via that script - any ideas??

Link to comment
Share on other sites

Only error I seen was

Warning SYSPRP SPPNP: Error 0xE000020B occurred while adding device Root\LEGACY_MPIO\0000 to the device info set.

Nothing I see would cause failure so must be somehow in the script. Like you said works on 64 bit, but not 32 bit is strange.

Link to comment
Share on other sites

Figured it out. For some reason the scheduled reboot in my first script breaks everything after that.... Like it doesnt know where to come back to after it restarts....

Thanks for the help guys / letting me just talk it out.

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...