none
Preparing to Configure Windows - Do Not Turn Off Your Computer

    Question

  • My organization released the following patches via WSUS to my Windows 7 Enterprise Edition workstation, which installed them at 3:00 AM this morning:

    Update for Microsoft Office Outlook, KB2412171   
    Update for Windows 7, KB2454826   
    Update for Windows 7, KB2264107   
    Update for Microsoft Office Outlook 2007 Junk Email Filter, KB2483110   
    Security Update for Windows 7, KB2419640, MS11-002
    Update for Windows 7, KB976902   
    Windows Malicious Software Removal Tool - January 2011, KB890830

    This morning when I got to work, my machine presented a screen that said:

    Stage 2 of 2

    Preparing to configure Windows

    Do not turn off your computer

    I waited about 15 minutes for the screen to go away, but I finally powered my computer off and on.  The computer came up just fine (after reporting that it had been shut down improperly, of course).  Three other machines in our WSUS test group (which receives patches for testing prior to production deployment) experienced the same issue. 

    I want to determine which patch caused the problem as we need to release, at the very least, this month's two new security updates (MS11-001 & MS11-002) to our production network.  What are your recommendations for finding the culprit?

    Wednesday, January 12, 2011 9:24 PM

Answers

  • Hi Leo,

    Since my systems are all up and running, I don't need to go back in time via System Restore.

    I have tried the method of removing all updates and reinstalling (see earlier in this thread).  The only update that reproduced the issue was KB2264107.  After declining the update in WSUS, production machines still encountered the issue when receiving other updates. 

    As my efforts to reproduce the issue were fruitless, I'm looking for other suggestions.  I have opened a case with Microsoft:  SRX1147235517


    Thanks,

    Ignatius

    Wednesday, January 19, 2011 5:02 PM
  • I had a number of Windows 7 x86 Enterprise systems hang after applying the January 2011 updates. Updates were deployed using SCCM 2007 SP2 R2. Systems hung after rebooting stage 3. Pressing ctrl+alt+del would present the logon screen, but the systems were somewhat unstable until a reboot.

    Removed 976902 from my patch package, and I haven't been able to reproduce the issue since.

    Thursday, January 20, 2011 6:41 PM

All replies

  • Hi,

     

    That’s hard to say which patches cause this problem. But you can try to login with Safe Mode, and go to “Programs and Features”, click “installed updates”, then  to reinstall the updates one by one to find the root cause.

     

    Hope it helps.

     

    Regards,

    Leo   Huang

    TechNet Subscriber Support in forum. If you have any feedback on our support, please contact tngfb@microsoft.com


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    Thursday, January 13, 2011 6:45 AM
  • Update for Windows 7, KB2454826   
    Update for Windows 7, KB2264107   

    I want to determine which patch caused the problem as we need to release, at the very least, this month's two new security updates (MS11-001 & MS11-002) to our production network.  What are your recommendations for finding the culprit?

    one of these 2 updates.

    "A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/
    Thursday, January 13, 2011 3:11 PM
  • Thanks Leo and Andre.

    Leo, I'm following your technique and reinstalling one by one. 

    Andre, so far KB2454826 and KB2419640 have uninstalled and reinstalled without problem.  KB2264107 did hang for over an hour when reinstalling, though.  I'm going to test the others, but I think this is the culprit.

    Thursday, January 13, 2011 5:02 PM
  • same issue on Windows 7 64 bit.  Have not seen the issue on Windows 7 32 bit

    Patches in common (may help cut down testing).

    • 2264107 
    • 2419640  <--- ruled out by Ignatius
    • 2454826  <--- ruled out by Ignatius
    • 890830
    • 976902
    Thursday, January 13, 2011 6:58 PM
  • We are seeing the problem as well, but replication has been challenging.  In a VM, we had it reoccur once but not again, on a real PC with rollback features, it occurs about 80% of the time.  After watching it closely, after STAGE 2of 2, the CTRL-ALT-DEL screen appears for a second, then it reverts back to STAGE 2 of 2 indefinately.  A CTRL-ALT-DEL actually brings us immediately back to the logon screen without having to power off and on the computer, but user confusion would have them call support or power off hard, so we have to find a solution.

    We have been working for some time to isolate but since it is not repeatable, it takes many tests to ensure we have the culprit.  We will post back if we can isolate as well.  Good luck...

      

    Thursday, January 13, 2011 7:00 PM
  • KB2264107 did hang for over an hour when reinstalling, though.  I'm going to test the others, but I think this is the culprit.

    I have no idea why this update takes so long.I installed this update some times ago and had no issue.

    "A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/
    Thursday, January 13, 2011 8:28 PM
  • Staples123 - I'm checking with my testers to see if their machines were 32-bit or 64-bit.  I'll reply shortly.

    Andre - Did you experience the long installation time when you installed the re-issued KB2264107 update?

    Thursday, January 13, 2011 9:24 PM
  • Andre - Did you experience the long installation time when you installed the re-issued KB2264107 update?

    No. When I installed the v1 the installation was fast and the same for v2. I have no idea why it happens for you. Which 3rd software do you and the 2 others use? Maybe you all use a software (maybe an antivirus tool?) which causes it.

    "A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/
    Thursday, January 13, 2011 9:35 PM
  • I am running Sophos Antivirus.  Any others running Sophos?
    Thursday, January 13, 2011 9:43 PM
  • I run NOD32 and don't have it. So lets wait from a response of the 2 other users who have the same issue.

    "A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/
    Thursday, January 13, 2011 9:54 PM
  • We use neither.  We have been playing with combinations of this months patches and are trying to narrow it down.  We know that it is none of the critical, high, or important updates as we can consistently deploy those without issue.  As I said in my previous thread, we are having trouble consistently reproducing the problem.  Our gut feel is that the problem is a combination effect.  In any case, our decision is to split up deployment and deploy what needs to be deployed and research the rest.  Again, good look and I'll post when we isolate if I don't see a resolution before we find one.
    Friday, January 14, 2011 12:58 AM
  • I wanted to post my findings regarding testing each patch via an uninstall and reinstall:

    Update for Microsoft Office Outlook (KB2412171), - No issue   
    Update for Windows 7  (KB2454826) -  No issue   
    Update for Windows 7   (KB2264107) - Issue - Long time going down for restart after patch removal
    Update for Microsoft Office Outlook 2007 Junk Email Filter (KB2483110) - No issue   
    Security Update for Windows 7  (KB2419640) - No issue - Slight delay on reboot after uninstall
    Update for Windows 7  (KB976902) - Can't uninstall
    Windows Malicious Software Removal Tool - January 2011 (KB890830) - Can't uninstall

    My plan is to deploy all patches to production except for KB2264107.

    Friday, January 14, 2011 2:17 PM
  • install the KB2264107 separated from the others.

    "A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/
    Friday, January 14, 2011 3:40 PM
  • Andre - I've done so and my machine hung for over an hour after removing the patch.

    Staples123 - The test machines were all 32-bit.

    Friday, January 14, 2011 4:13 PM
  • this is strange. MS provides free support for WindowsUpdate issues. So try to contact the MS support about it.

    "A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/
    Friday, January 14, 2011 4:41 PM
  • 32 Bit (Dell) Hung this morning when the following were installed:

    KB890830
    KB976902
    KB915597
    KB2419640
    KB2483110
    KB2264107
    KB2425826
    KB2412171

    I rebooted and it came up fine.  No obvious events logged.

    Friday, January 14, 2011 5:23 PM
  • We are experiencing the same issue, all Windows 7 x64 clients hanging at Stage 3 of 3 of Windows Update after a reboot.

    The following updates were released via SCCM 2007 R2:

    KB976902
    KB890830
    KB2483110
    KB2467659
    KB2454826
    KB2443685
    KB2442962
    KB2436673
    KB2433299
    KB2423089
    KB2419640
    KB2416400
    KB2413186
    KB2412171
    KB2409055
    KB2385678
    KB2305420
    KB2296199
    KB2289078
    KB2288931
    KB2284697
    KB2264107

    Have taken out KB2264107 from our updates deployment after reading this thread and the issue remains so I am disregarding this one.

    One final note, if we press Ctrl + Alt + Del once the machine sits at the Stage 3 of 3 - Configuring Machine for updates then the logon screen is shown.

    Monday, January 17, 2011 12:40 AM
  • Hi Loyola,

     

    That’s seems your issue related with KB2264107. Please go to Safe Mode and remove it for test.

     

    This is the information about KB 2264107: http://support.microsoft.com/kb/2264107

     

     

    Regards,

    Leo   Huang

    TechNet Subscriber Support in forum. If you have any feedback on our support, please contact tngfb@microsoft.com


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    Monday, January 17, 2011 1:35 AM
  • Hi,

     

    Usually when your pc have issue after Windows Update, you can perform a system restore first, then install update packages one by one to troubleshoot which package cause the issue.

     

    Regards,

    Leo   Huang

    TechNet Subscriber Support in forum. If you have any feedback on our support, please contact tngfb@microsoft.com


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    Monday, January 17, 2011 1:39 AM
  • I experienced this this morning with 2 laptops. I let the laptop I was setting up for a new user just sit there for about 2 hours and it was sitting at the preparing portion. After seeing posts here that stated I could just restart it and it would work fine I pressed CTRL+ALT+DEL and it actually brought me to the login screen and asked for my password. I was able to login and it showed updates had been applied(the ones mentioned above). After a restart from the start menu I was able to bring it up normally.

    So maybe it's just not bringing up the normal login screen but when you press CTRL+ALT+DEL it wakes it up? Anyone else seen this?

    Monday, January 17, 2011 4:34 PM
  • After releasing updates to my production network, many Windows 7 machines experienced the "Preparing to configure Windows.  Do not turn off your computer" message.  I did not release KB2264107.

    I am back to the drawing board and am not sure which update caused the issue.  Pressing CTRL+ALT+DEL when presented with the message has reportedly allowed many users to see the login prompt.  Other users, though, had to hard restart their machines.

    Tuesday, January 18, 2011 8:27 PM
  • Hi,

     

    The problem may happens if certain installed program is not compatible with installed updates. Usually we can use system restore to solve this kind of problem.

     

    I suggest to install these updates one by one to make sure which update cause this incompatibility issue.

     

    These similar thread maybe helpful to you:

    http://social.answers.microsoft.com/Forums/en-GB/vistawu/thread/db3e836c-7e3a-4403-837f-a776fa3b4ef6

    http://social.answers.microsoft.com/Forums/en-US/vistawu/thread/99a1e8f6-5939-43f4-b884-1b48f85555fa

    http://social.technet.microsoft.com/Forums/en-US/w7itproinstall/thread/f0bf7db8-d667-4257-9ad0-edd82dc6b9bd

     

    Hope that helps.

     

    Regards,

    Leo   Huang

    TechNet Subscriber Support in forum. If you have any feedback on our support, please contact tngfb@microsoft.com


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    Wednesday, January 19, 2011 2:39 AM
  • Hi Leo,

    Since my systems are all up and running, I don't need to go back in time via System Restore.

    I have tried the method of removing all updates and reinstalling (see earlier in this thread).  The only update that reproduced the issue was KB2264107.  After declining the update in WSUS, production machines still encountered the issue when receiving other updates. 

    As my efforts to reproduce the issue were fruitless, I'm looking for other suggestions.  I have opened a case with Microsoft:  SRX1147235517


    Thanks,

    Ignatius

    Wednesday, January 19, 2011 5:02 PM
  •  I have opened a case with Microsoft:
    this is the only solution which helps. We can't fix this.

    It would be nice if you can report what was thew cause and the fix for the issue.

    "A programmer is just a tool which converts caffeine into code" CLIP- Stellvertreter http://www.winvistaside.de/
    Wednesday, January 19, 2011 8:16 PM
  • Andre,

    Will do.  Appreciate the assistance!

    Ignatius

    Wednesday, January 19, 2011 8:51 PM
  • I have to agree with you Ignatius,

    We run an Enterprise level of service and are managing machines in more than 100 sites around the world hence System Restore has no real place in our environment, our only hope is that we can identify a true fix to the problem.

     

    As with Andre, I am eager to see what Microsoft have to say about the issue.

    Cheers

    Tony

    Wednesday, January 19, 2011 9:46 PM
  • Getting the same thing here. Updates pushed out overnight by SCCM 2007 R3. I'm pushing out :

    Update for Windows 7 (KB976902)
    Update for Windows 7 for x64-based Systems (KB976902)
    Update for Microsoft Office Outlook 2007 (KB2412171)
    Update for Microsoft Office Outlook 2007 Junk Email Filter (KB2483110)
    Definition Update for Microsoft Office 2010 (KB982726), 64-Bit Edition
    Definition Update for Microsoft Office 2010 (KB982726), 32-Bit Edition
    Update for Windows 7 (KB2454826)
    Windows Malicious Software Removal Tool - January 2011 (KB890830)
    Windows Malicious Software Removal Tool x64 - January 2011 (KB890830)
    Security Update for Windows XP (KB2419632)
    Update for Windows 7 for x64-based Systems (KB2454826)
    Security Update for Windows 7 (KB2419640)
    Security Update for Windows 7 for x64-based Systems (KB2419640)

    Had three reports so far, all on Win7 32bit with NOD32 Anti Virus. In all three cases just pressing Ctrl-Alt-Del has cleared the message and presented our normal login screen and everything appears normal.

    SCCM says over 600 workstations patched so far so only 3 reports is pretty good but it would be nice to identify the cause. I did not get it in any of my test patch runs.

     

    Thursday, January 20, 2011 2:44 AM
  • I had a number of Windows 7 x86 Enterprise systems hang after applying the January 2011 updates. Updates were deployed using SCCM 2007 SP2 R2. Systems hung after rebooting stage 3. Pressing ctrl+alt+del would present the logon screen, but the systems were somewhat unstable until a reboot.

    Removed 976902 from my patch package, and I haven't been able to reproduce the issue since.

    Thursday, January 20, 2011 6:41 PM
  • Hi Ignatius,

     

    You can try the suggestion mentioned by General_Zod, exclude KB976902 and see if the same issue occurs.

     

    Hope that helps.

     

    Regards,

    Leo   Huang

    TechNet Subscriber Support in forum. If you have any feedback on our support, please contact tngfb@microsoft.com

     

     


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    Friday, January 21, 2011 1:34 AM
  • The same thing happened to me today as well on a Windows 7 Professional 32-Bit laptop. But as General_Zod mentioned above I actually got to the logon screen after pressing CTRL+ALT+DEL. Also as suggested above I rebooted once more afterwards and everything seems to run just fine so far.

    Just for information, here are the two updates I was installing:

    - Update for Windows 7 (KB976902)

    - Security Update for Windows 7 (KB2419640)

    • Edited by mighty_mt Friday, January 21, 2011 11:31 AM corrected typos
    Friday, January 21, 2011 11:30 AM
  • Hi Ignatius,

     

    Did your issue solved? Please feel free to give me any update.

     

    Thanks for your cooperation!

     

    Regards,

    Leo   Huang

    TechNet Subscriber Support in forum. If you have any feedback on our support, please contact tngfb@microsoft.com


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    Friday, January 28, 2011 1:42 AM
  • Hi Ignatius,

     

    I will mark your reply as answer. It could help other communities here who have the same issue.

     

    Thanks for your understanding,

     

    Regards,

    Leo   Huang

    TechNet Subscriber Support in forum. If you have any feedback on our support, please contact tngfb@microsoft.com

     


    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    Monday, January 31, 2011 1:39 AM
  • Hi everyone, After more than 6hours in searching heres how to fix this:

    First Step

    through command prompt type:

    del C:\windows\winsxs\pending.xml

    Second Step

    also through command prompt type:

    del c:\windows\softwaredistribution

    Final Step

    Shutdown your  PC then Switch on It and the problem is fixed inchaalah

    May this will help everyone

     

     

     


    Saturday, November 12, 2011 9:23 PM