OSD Exits to Ctl-Alt-Del after Reboot from Software Update, leaves Clients in provisioning mode

We are seeing a problem where the Windows 7 SP1 OSD wrongly exits to the Ctl-Alt-Del screen:  This problem is occuring with about %25 of our Newly Imaged PCs during the Software Updates step of the Task Sequence (of which there is about 9 outstanding updates), the PCs are rebooted as 4 of these updates finish with COMPLETE_SOFT_REBOOT_NEEDED.

After the Software Updates Reboot the following errors are found:

SMSTS.log reports:

  Failed to set log directory. Some execution history may be lost. The system cannot find the file specified. (Error: 80070002; Source: Windows)

UpdatesDeployment.log reports:

  Failed to save an instance of CCM_TargetedUpdateEx1, error 80041033 UpdatesDeploymentAgent 3/04/2013 4:56:39 PM 3080 (0x0C08)
  Failed to get class instance for CCM_TargetedUpdateEx1, error 80041033 UpdatesDeploymentAgent 3/04/2013 4:56:39 PM 3080 (0x0C08)

ExecMgr.log Reports:

  Failed to open to WMI namespace '\\.\root\ccm\Policy\Machine' (8007045b) execmgr 3/04/2013 4:56:39 PM 3496 (0x0DA8)
  Failed to ConnectSettings for ICcmPolicyAgent in CSoftDistPolicyNamespace::ConnectToNamespace execmgr 3/04/2013 4:56:39 PM 3496 (0x0DA8)
  Failed to ConnectToNamespace in CSoftDistPolicyNamespace::GetMachinePolicy execmgr 3/04/2013 4:56:39 PM 3496 (0x0DA8)
  Failed to connect to machine policy name space. 0x8007045b execmgr 3/04/2013 4:56:39 PM 3496 (0x0DA8)
  Failed to connect to user policy name space execmgr 3/04/2013 4:56:39 PM 3496 (0x0DA8)

I have checked the logs based on other forum suggestions I can say the following:

-Network adapter is getting valid address;

-I do not have a step for "Install Roles and Features";

-I can apply registry changes for each machine to take them out of Provisioning mode, and after that I dont have any problems - this is far from the solution that I hope for.


April 4th, 2013 4:49am

what software updates are you installing, is there a service pack there ?
Free Windows Admin Tool Kit Click here and download it now
April 4th, 2013 10:27am

No there is definately no Service Pack there.

They consist of the following: 2532531, 982018, 2529073, 2732487 - cant distinguish others they only have localised update IDs.

These PCs use build and capture image with Office 2007 SP3 and Windows 7 SP1 already included.

April 4th, 2013 11:36am

and are they definietly failing on the Install Software Updates step ? have you tried pausing the task sequence at that point before it reboots to review the logs and check for ip address connectivity, it sounds like it could be dropping the ip address, losing network connectivity BEFORE it reboots and then fails, but only close analysis of the deployment (use pause scripts) will reveal the failure, a simple msgbox vbs script is enough (as a run command line) to pause the ts so that you can check stuff.

Free Windows Admin Tool Kit Click here and download it now
April 4th, 2013 7:22pm

Ok I've added the Pauses as suggested and added to the manual step - see below:

  1. The install passes through the 1st Pause (and its IP is OK),
  2. It restarts, then installs some other apps
  3. Then it successfully reaches the "install software updates" step.  There it looks like below - also it only installs 4 updates (as mentioned earlier 2532531, 982018, 2529073, 2732487).  NOTE: I could ping servers on our network during this phase by using F8. (WindowsUpdate.log show these as successfully installed but requiring Reboot)

4. Then the Software Updates step forces a reboot, due to the updates demanding it (it has not reached the 2nd Pause yet)

5. After this reboot the PC goes straight to the login Ctl-Alt-Del Screen and fails to complete the Forced Reboot and other steps afterward, leaving the PC in limbo.

It doesnt appear that the PC at any stage loses connection to the Network. 

Also one concern I have is that the "Setup is preparing your computer for first use" (or sysprep stuff) - could this be interfering with the Task Sequence from continuing? 

Also I would love to forcibly stop the reboot (which the Software Updates Step does on its own) but this is impossible, or is it?

The only consistent error I see in the smsts.log is

  • Failed to set log directory. Some execution history may be lost.
    The system cannot find the file specified. (Error: 80070002; Source: Windows) OSDSetupHook 5/04/2013 3:47:22 PM 988 (0x03DC)

Lastly I have also noticed that when the problem occurs: if 'clear PXE advertisement', then re-run OSD, it seems to fail again. Otherwise if I remove the client from SCCM, then re-create from scratch, it works.  Note: this is still occuring for BRAND new PCs so its not due to me re-using old PCs.
April 5th, 2013 8:36am

Did you choose conitue on error for updates task?
Free Windows Admin Tool Kit Click here and download it now
April 6th, 2013 1:38am

Yes I have selected "continue on error" and the problem still occurs.

The only consisent error is i smsts.log:

  • Failed to set log directory. Some execution history may be lost.
    The system cannot find the file specified. (Error: 80070002; Source: Windows)

Apart from removing the Updates step entirely I am without a clue - any help would be welcome..

April 10th, 2013 9:27am

Exactly same thing here. No solution though yet. Don't know if there's some faulty update doing this, haven't encountered this earlier.

Any suggestions welcome, as well.

Free Windows Admin Tool Kit Click here and download it now
April 16th, 2013 1:46pm

Did you find a sollution for this? I seem to be having a similar issue

July 12th, 2013 12:09pm

IME, systems wll be stuck in provisioning mode for one of two reasons: software installed during the TS installs a network driver and/or software installed during the TS initiates an unexpected reboot. the Cisco VPN client was the case I encountered multiple times. You should by a process of elimination, remove software installs until you find the culprit and from there you can troubleshoot what that installer specifically does to effect the TS. In the screenshot further up, I would immediately suspect Dameware and VNC viewer (ewww, VNC viewer, really?) and remove both of those and test again.

Free Windows Admin Tool Kit Click here and download it now
July 12th, 2013 4:25pm

Any update on this as I am struggling with this issue for the past few days ?

Our image was built last year so when I want to recreate it, it has to do 150 updates. We don't have WSUS updates into SCCM so I had to use a wsf script to get the updates from our WSUS server.

If I image the computer without doing the updates and do them manually by running the script here is what happens :

  • 1st execution of the script : 137 updates installed and a reboot is required
  • I manually reboot
  • 2nd execution of the script : 13 updates installed and a reboot is required
  • I manually reboot
  • 3rd execution of the script : 4 updates installed
  • I manually reboot
  • 4th execution of the script : no updates required.

If I only do 1 execution of the script in my TS : it works fine, it installs the 137 updates but then when the PC is done imaging, it still needs the 13+4 other updates which I don't really like.

At first, I tried adding this in my TS:

  1. WSUS 1/3
  2. System restart (triggered by the TS)
  3. WSUS 2/3
  4. System restart (triggered by the TS)
  5. WSUS 3/3
  6. System restart (triggered by the TS)

This stops at step #2, I see it do the 137 updates and then when it reboots, it goes into provisioning mode and doesn't continue. Looks like there is an issue with the reboot so...

I have tried removing the reboot as follows

  1. WSUS 1/3
  2. WSUS 2/3
  3. WSUS 3/3

This installs the 137 updates in step #1 and downloads the 13 updates in step 2 and 3 but log file says a reboot is required to install them. The TS then continues but once it meets a System restart triggered by the TS, it doesn't resume the TS and goes also in provisionning mode.

Any idea on why it goes into provisioning mode after installing the updates ? To me, it looks like there is a probably with the state that WSUS puts the computer in, like it is pending reboot but the System restart by the TS doesn't seem to work when trying the reboot ?


Thanks!!!!

August 28th, 2013 3:58pm

Hi Pierre-Luc,  This sounds very similar to my symptoms.  Unfortunately I gave up running updates during the Task Sequence and only push them out afterwards.  This is not ideal as you must wait sometime after OSD before the system is fully completed.  I am hoping SCCM 2012 resolves this issue...
Free Windows Admin Tool Kit Click here and download it now
August 30th, 2013 7:16am

Thanks for the reply...After a week of testing, I am pretty sure there is a problem with one of those Windows Updates that when the computer reboots, instead of going through the Task Sequence to continue, it overrides this and the update finishes installing itself which exits the computer out of the TS and leaves the client in Provisionning mode.

The problem is that I have 147 updates that are being installed so I guess I'll need to find out which one causes this :) I have checked the logs of Windows Updates and smsts and everything exits fine. I also checked the eventvwr of the computer but didn't find anything relevant..

I'll let you know if I find.

Thanks!

September 3rd, 2013 5:21pm

Any luck finding a solution to this? I have the same issue
Free Windows Admin Tool Kit Click here and download it now
September 6th, 2013 9:08pm

Hello, yes I might have found something...it's long though but here it is...

The problem was indeed, for some reason, some Windows patches were causing an issue with OSD.. Since my image (French W7 x32 SP1) was built in june 2012, we had 136 updates to apply. Hopefully you have less...!

What I did is try to install in OSD all the patches by group to guess and pinpoint which update was causing issue...

I applied the updates

  • 1 - 50 - worked
  • 1 - 100 - failed
  • 51 to 75 - worked
  • 76 to 85 - failed
  • 76 to 80 - worked
  • 81 to 83 - failed
  • 81 and 82 worked so #83 was the cause... and so on. So far, I know that in my case, updates KB2661254 and KB2698365 are causing issue. Now I am testing the updates from 120 to 136 and there are still some issues so I will let you know once I find them all - I can't explain why these 2 updates were causing issue and I'm curious if they work for some other people but, at least I will be able to include them in my .WIM image...

Oh, and to exclude the updates, you need to add a line this like for each updates you want to exclude in the ZTIWindowsUpdate.wsf

BadKBArticlesList.Add "2792100", "" 'Only put the KB number, do not include KB...

...don't forget to update your DP :)


Hope this helps!!!!

September 9th, 2013 4:23pm

Hello, yes I might have found something...it's long though but here it is...

The problem was indeed, for some reason, some Windows patches were causing an issue with OSD.. Since my image (French W7 x32 SP1) was built in june 2012, we had 136 updates to apply. Hopefully you have less...!

What I did is try to install in OSD all the patches by group to guess and pinpoint which update was causing issue...

I applied the updates

  • 1 - 50 - worked
  • 1 - 100 - failed
  • 51 to 75 - worked
  • 76 to 85 - failed
  • 76 to 80 - worked
  • 81 to 83 - failed
  • 81 and 82 worked so #83 was the cause... and so on. So far, I know that in my case, updates KB2661254 and KB2698365 are causing issue. Now I am testing the updates from 120 to 136 and there are still some issues so I will let you know once I find them all - I can't explain why these 2 updates were causing issue and I'm curious if they work for some other people but, at least I will be able to include them in my .WIM image...

Oh, and to exclude the updates, you need to add a line this like for each updates you want to exclude in the ZTIWindowsUpdate.wsf

BadKBArticlesList.Add "2792100", "" 'Only put the KB number, do not include KB...

...don't forget to update your DP :)


Hope this helps!!!!

Jesus Christ, nice work. How long did that take you? :)
Free Windows Admin Tool Kit Click here and download it now
February 13th, 2014 4:03pm

Something like 3 weeks...! haha...

Did you have the same issue and that solved your problem too??? If so, I'd like to hear about Microsoft on this...

February 13th, 2014 4:11pm

Having the same issue and stumbled upon http://support.microsoft.com/kb/2894518
Free Windows Admin Tool Kit Click here and download it now
February 14th, 2014 4:23pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics