Windows 7 Update Stuck at 35% (Configuring Windows Updates 35% Complete)

Anonymous
2011-04-08T01:14:51+00:00

Hi, I have a Windows 7 Ultimate laptop that is stuck at 35% complete update. After rebooting the computer, we get the Windows login sound, then it states it is configuring Windows updates at 35%. I have let this thing go overnight and yet nothing. Below is the C:\Windows\WindowsUpdate.log. (I've even tried plugging the computer into an Ethernet jack to see if it would work, but still no go...)

2011-04-07 18:11:33:178 904 51c Misc ===========  Logging initialized (build: 7.3.7600.16385, tz: -0600)  ===========

2011-04-07 18:11:33:240 904 51c Misc  = Process: C:\Windows\system32\svchost.exe

2011-04-07 18:11:33:302 904 51c Misc  = Module: c:\windows\system32\wuaueng.dll

2011-04-07 18:11:33:178 904 51c Service *************

2011-04-07 18:11:38:372 904 51c Service ** START **  Service: Service startup

2011-04-07 18:11:38:684 904 51c Service *********

2011-04-07 18:11:38:887 904 51c Agent  * WU client version 7.3.7600.16385

2011-04-07 18:11:38:887 904 51c Agent  * Base directory: C:\Windows\SoftwareDistribution

2011-04-07 18:11:38:903 904 51c Agent  * Access type: No proxy

2011-04-07 18:11:38:918 904 51c Agent  * Network state: Disconnected

2011-04-07 18:12:24:970 904 51c Report CWERReporter::Init succeeded

2011-04-07 18:12:24:970 904 51c Agent ***********  Agent: Initializing Windows Update Agent  ***********

2011-04-07 18:12:24:970 904 51c Agent ***********  Agent: Initializing global settings cache  ***********

2011-04-07 18:12:24:970 904 51c Agent  * WSUS server: <NULL>

2011-04-07 18:12:24:970 904 51c Agent  * WSUS status server: <NULL>

2011-04-07 18:12:24:970 904 51c Agent  * Target group: (Unassigned Computers)

2011-04-07 18:12:24:970 904 51c Agent  * Windows Update access disabled: No

2011-04-07 18:12:25:001 904 51c Agent  * Found 9 persisted download calls to restore

2011-04-07 18:12:25:126 904 51c DnldMgr Download manager restoring 0 downloads

2011-04-07 18:12:25:126 904 51c Agent  * Successfully loaded 9 persisted download calls.

2011-04-07 18:12:25:172 904 51c AU ###########  AU: Initializing Automatic Updates  ###########

2011-04-07 18:12:25:172 904 51c AU AU setting next detection timeout to 2011-04-08 00:12:25

2011-04-07 18:12:25:172 904 51c AU AU setting next sqm report timeout to 2011-04-08 00:12:25

2011-04-07 18:12:25:172 904 51c AU  # Approval type: Scheduled (User preference)

2011-04-07 18:12:25:172 904 51c AU  # Scheduled install day/time: Every day at 3:00

2011-04-07 18:12:25:172 904 51c AU  # Auto-install minor updates: Yes (User preference)

2011-04-07 18:12:25:172 904 51c AU  # Will interact with non-admins (Non-admins are elevated (User preference))

2011-04-07 18:12:25:172 904 51c AU  # Will display featured software notifications (User preference)

2011-04-07 18:12:25:453 904 51c AU Initializing featured updates

2011-04-07 18:12:25:453 904 51c AU Found 0 cached featured updates

2011-04-07 18:12:26:374 904 51c Report ***********  Report: Initializing static reporting data  ***********

2011-04-07 18:12:26:374 904 51c Report  * OS Version = 6.1.7600.0.0.65792

2011-04-07 18:12:26:374 904 51c Report  * OS Product Type = 0x00000001

2011-04-07 18:12:26:405 904 51c Report  * Computer Brand = Acer

2011-04-07 18:12:26:405 904 51c Report  * Computer Model = TravelMate 4200

2011-04-07 18:12:26:436 904 51c Report  * Bios Revision = V1.70

2011-04-07 18:12:26:452 904 51c Report  * Bios Name = Ver 1.00PARTTBL

2011-04-07 18:12:26:452 904 51c Report  * Bios Release Date = 2006-02-21T00:00:00

2011-04-07 18:12:26:452 904 51c Report  * Locale ID = 1033

2011-04-07 18:12:26:530 904 51c AU Successfully wrote event for AU health state:0

2011-04-07 18:12:26:530 904 51c AU Successfully wrote event for AU health state:0

2011-04-07 18:12:26:530 904 51c AU AU finished delayed initialization

2011-04-07 18:12:26:530 904 51c AU AU setting next sqm report timeout to 2011-04-09 00:12:26

2011-04-07 18:12:26:530 904 51c AU #############

2011-04-07 18:12:26:530 904 51c AU ## START ##  AU: Search for updates

2011-04-07 18:12:26:530 904 51c AU #########

2011-04-07 18:12:26:748 904 51c AU <<## SUBMITTED ## AU: Search for updates [CallId = {14F9DA0D-AF2A-480B-9E05-5ED04C5DFAA7}]

2011-04-07 18:12:26:998 904 284 Agent *************

2011-04-07 18:12:26:998 904 284 Agent ** START **  Agent: Finding updates [CallerId = AutomaticUpdates]

2011-04-07 18:12:26:998 904 284 Agent *********

2011-04-07 18:12:26:998 904 284 Agent  * Online = No; Ignore download priority = No

2011-04-07 18:12:26:998 904 284 Agent  * Criteria = "IsInstalled=0 and DeploymentAction='Installation' or IsPresent=1 and DeploymentAction='Uninstallation' or IsInstalled=1 and DeploymentAction='Installation' and RebootRequired=1 or IsInstalled=0 and DeploymentAction='Uninstallation' and RebootRequired=1"

2011-04-07 18:12:26:998 904 284 Agent  * ServiceID = {7971F918-A847-4430-9279-4A52D1EFE18D} Third party service

2011-04-07 18:12:26:998 904 284 Agent  * Search Scope = {Machine}

2011-04-07 18:12:48:885 904 51c AU Forced install timer expired for scheduled install

2011-04-07 18:12:48:885 904 51c AU UpdateDownloadProperties: 0 download(s) are still in progress.

2011-04-07 18:12:48:885 904 51c AU Setting AU scheduled install time to 2011-04-08 09:00:00

2011-04-07 18:12:48:885 904 51c AU Successfully wrote event for AU health state:0

2011-04-07 18:13:31:005 904 284 Agent WARNING: Failed to evaluate Installed rule, updateId = {B6B62539-AF33-4073-8D78-32EC53FE2AD8}.102, hr = 80080005

2011-04-07 18:14:31:034 904 284 Agent WARNING: Failed to evaluate Installable rule, updateId = {B6B62539-AF33-4073-8D78-32EC53FE2AD8}.102, hr = 80080005

2011-04-07 18:16:31:091 904 284 Agent WARNING: Failed to evaluate Installed rule, updateId = {43845711-F505-43A7-9EAB-592A2E7453DF}.103, hr = 80080005

2011-04-07 18:17:31:120 904 284 Agent WARNING: Failed to evaluate Installable rule, updateId = {43845711-F505-43A7-9EAB-592A2E7453DF}.103, hr = 80080005

2011-04-07 18:19:31:178 904 284 Agent WARNING: Failed to evaluate Installed rule, updateId = {56745877-75B3-4B52-85F5-6648928A5FF6}.103, hr = 80080005

2011-04-07 18:20:31:207 904 284 Agent WARNING: Failed to evaluate Installable rule, updateId = {56745877-75B3-4B52-85F5-6648928A5FF6}.103, hr = 80080005

2011-04-07 18:22:31:265 904 284 Agent WARNING: Failed to evaluate Installed rule, updateId = {3CF0933C-65EB-4825-B1EE-84157F638463}.103, hr = 80080005

2011-04-07 18:23:31:294 904 284 Agent WARNING: Failed to evaluate Installable rule, updateId = {3CF0933C-65EB-4825-B1EE-84157F638463}.103, hr = 80080005

2011-04-07 18:25:31:351 904 284 Agent WARNING: Failed to evaluate Installed rule, updateId = {373F82CB-B6C9-4C6B-8AF2-9A5C4D9E7251}.103, hr = 80080005

2011-04-07 18:26:31:380 904 284 Agent WARNING: Failed to evaluate Installable rule, updateId = {373F82CB-B6C9-4C6B-8AF2-9A5C4D9E7251}.103, hr = 80080005

2011-04-07 18:28:31:438 904 284 Agent WARNING: Failed to evaluate Installed rule, updateId = {844CC496-4441-4318-8C4D-385F4D382035}.102, hr = 80080005

2011-04-07 18:29:31:467 904 284 Agent WARNING: Failed to evaluate Installable rule, updateId = {844CC496-4441-4318-8C4D-385F4D382035}.102, hr = 80080005

2011-04-07 18:31:31:525 904 284 Agent WARNING: Failed to evaluate Installed rule, updateId = {07A8DC2B-35DA-4FD6-AB3C-D72C7B92CE13}.101, hr = 80080005

2011-04-07 18:32:31:554 904 284 Agent WARNING: Failed to evaluate Installable rule, updateId = {07A8DC2B-35DA-4FD6-AB3C-D72C7B92CE13}.101, hr = 80080005

2011-04-07 18:34:31:612 904 284 Agent WARNING: Failed to evaluate Installed rule, updateId = {6185C9C5-E3D2-4443-8D6D-29A3196CFAF8}.105, hr = 80080005

2011-04-07 18:35:31:641 904 284 Agent WARNING: Failed to evaluate Installable rule, updateId = {6185C9C5-E3D2-4443-8D6D-29A3196CFAF8}.105, hr = 80080005

2011-04-07 18:56:05:126 924 748 Misc ===========  Logging initialized (build: 7.3.7600.16385, tz: -0600)  ===========

2011-04-07 18:56:05:142 924 748 Misc  = Process: C:\Windows\system32\svchost.exe

2011-04-07 18:56:05:142 924 748 Misc  = Module: c:\windows\system32\wuaueng.dll

2011-04-07 18:56:05:126 924 748 Service *************

2011-04-07 18:56:05:142 924 748 Service ** START **  Service: Service startup

2011-04-07 18:56:05:142 924 748 Service *********

2011-04-07 18:56:05:298 924 748 Agent  * WU client version 7.3.7600.16385

2011-04-07 18:56:05:298 924 748 Agent  * Base directory: C:\Windows\SoftwareDistribution

2011-04-07 18:56:05:376 924 748 Agent  * Access type: No proxy

2011-04-07 18:56:05:376 924 748 Agent  * Network state: Disconnected

2011-04-07 18:56:51:349 924 748 Report CWERReporter::Init succeeded

2011-04-07 18:56:51:349 924 748 Agent ***********  Agent: Initializing Windows Update Agent  ***********

2011-04-07 18:56:51:349 924 748 Agent ***********  Agent: Initializing global settings cache  ***********

2011-04-07 18:56:51:349 924 748 Agent  * WSUS server: <NULL>

2011-04-07 18:56:51:349 924 748 Agent  * WSUS status server: <NULL>

2011-04-07 18:56:51:349 924 748 Agent  * Target group: (Unassigned Computers)

2011-04-07 18:56:51:349 924 748 Agent  * Windows Update access disabled: No

2011-04-07 18:56:51:364 924 748 Agent  * Found 9 persisted download calls to restore

2011-04-07 18:56:51:505 924 748 DnldMgr Download manager restoring 0 downloads

2011-04-07 18:56:51:505 924 748 Agent  * Successfully loaded 9 persisted download calls.

2011-04-07 18:56:51:536 924 748 AU ###########  AU: Initializing Automatic Updates  ###########

2011-04-07 18:56:51:536 924 748 AU AU setting next detection timeout to 2011-04-08 00:56:51

2011-04-07 18:56:51:536 924 748 AU  # Approval type: Scheduled (User preference)

2011-04-07 18:56:51:536 924 748 AU  # Scheduled install day/time: Every day at 3:00

2011-04-07 18:56:51:536 924 748 AU  # Auto-install minor updates: Yes (User preference)

2011-04-07 18:56:51:536 924 748 AU  # Will interact with non-admins (Non-admins are elevated (User preference))

2011-04-07 18:56:51:536 924 748 AU  # Will display featured software notifications (User preference)

2011-04-07 18:56:51:879 924 748 AU Setting AU scheduled install time to 2011-04-08 09:00:00

2011-04-07 18:56:52:612 924 748 Report ***********  Report: Initializing static reporting data  ***********

2011-04-07 18:56:52:612 924 748 Report  * OS Version = 6.1.7600.0.0.65792

2011-04-07 18:56:52:612 924 748 Report  * OS Product Type = 0x00000001

2011-04-07 18:56:52:644 924 748 Report  * Computer Brand = Acer

2011-04-07 18:56:52:644 924 748 Report  * Computer Model = TravelMate 4200

2011-04-07 18:56:52:659 924 748 Report  * Bios Revision = V1.70

2011-04-07 18:56:52:659 924 748 Report  * Bios Name = Ver 1.00PARTTBL

2011-04-07 18:56:52:659 924 748 Report  * Bios Release Date = 2006-02-21T00:00:00

2011-04-07 18:56:52:659 924 748 Report  * Locale ID = 1033

2011-04-07 18:56:52:737 924 748 AU Successfully wrote event for AU health state:0

2011-04-07 18:56:52:737 924 748 AU Initializing featured updates

2011-04-07 18:56:52:737 924 748 AU Found 0 cached featured updates

2011-04-07 18:56:52:737 924 748 AU Successfully wrote event for AU health state:0

2011-04-07 18:56:52:768 924 748 AU Successfully wrote event for AU health state:0

2011-04-07 18:56:52:768 924 748 AU The system has been restored. Hence triggering AU detection through DetectNow API.

2011-04-07 18:56:52:768 924 748 AU Triggering AU detection through DetectNow API

2011-04-07 18:56:52:768 924 748 AU Triggering Online detection (non-interactive)

2011-04-07 18:56:52:768 924 748 AU AU finished delayed initialization

2011-04-07 18:56:52:768 924 748 AU #############

2011-04-07 18:56:52:768 924 748 AU ## START ##  AU: Search for updates

2011-04-07 18:56:52:768 924 748 AU #########

2011-04-07 18:56:52:768 924 748 AU  # WARNING: Failed to find updates with error code 8024001F

2011-04-07 18:56:52:768 924 748 AU #########

2011-04-07 18:56:52:768 924 748 AU ##  END  ##  AU: Search for updates [CallId = {00000000-0000-0000-0000-000000000000}]

2011-04-07 18:56:52:768 924 748 AU #############

2011-04-07 18:56:52:768 924 748 AU Network connection not detected, subscribing for network reconnect for AU detection to happen

2011-04-07 18:56:52:768 924 748 AU Successfully wrote event for AU health state:0

2011-04-07 18:56:52:768 924 748 AU Setting AU scheduled install time to 2011-04-08 09:00:00

2011-04-07 18:56:52:768 924 748 AU Successfully wrote event for AU health state:0

2011-04-07 18:56:52:831 924 748 AU Successfully wrote event for AU health state:0

2011-04-07 18:56:57:776 924 11c Report REPORT EVENT: {FB13EA4D-E473-4947-B207-633C2A33004E} 2011-04-07 18:56:52:737-0600 1 202 102 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Content Install Reboot completed.

2011-04-07 18:56:58:010 924 11c Report CWERReporter finishing event handling. (00000000)

Windows for home | Previous Windows versions | Windows update

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

56 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2011-04-10T02:25:41+00:00

    And one other thing:

    I did reboot and try the DISM thing again. It worked this time, but is now stuck on "Failure configure Windows updates. Reverting changes."

    Was this answer helpful?

    400+ people found this answer helpful.
    0 comments
  2. Anonymous
    2016-04-28T20:34:06+00:00

    Hi 

     after the computer was frozen on 35%. Configuration for an hour, now it is saying "cleaning up do not turn off your computer". So now what do I do to get into my computer. I need help !!!!!!!!!

    Was this answer helpful?

    200+ people found this answer helpful.
    0 comments
  3. Anonymous
    2017-08-15T18:38:03+00:00

    This is still true today, in 2017.

    I work in a predominantly Windows 7 environment(it's slowly becoming Windows 10).  You can pretty much count on re-creating this issue by simply running an elevated Disk Cleanup(gives you the Windows Updates Cleanup option), check off pretty much every box, clean, and restart. As you shutdown you'll notice a "Configuring Windows..." process. It will complete, proceed to restart, and upon startup, will go back to "Configuring Windows" where it will hang at 100%, indefinitely. Once you force it to shutdown, the next time it comes up it will get stuck at 35% for an indefinite amount of time. Should you force it down again, it will want to run check disk. Once check disk completes it will finally load into Windows...just kidding, it goes back to getting stuck at 35% again. All for helping someone clear out 9GB of temps and Windows Update cleanup files. Microsoft is wonderful.

    They've always had the worst update system. In fact, their updating so horrible it has carried over to the Xbox console because our favorite thing to do is get home from a long day of work and then watch the Xbox update for an hour.

    The time it takes for Xbox to download and apply a 350MB update, the PS4 would have downloaded and installed 3GB update, twice. I know, because if I go months without playing either, I will turn them on, each, once at a time, and let them download whatever they need to update with. And should Microsoft have a large console update...game over. You're not playing that evening, may as well pop in a movie and forget about it...oh, but wait...you can't if you use your Xbox as streaming device.

    This has been the case since Windows 95 and 98. A Mac or Android will update circles around a Windows machine.

    Was this answer helpful?

    100+ people found this answer helpful.
    0 comments
  4. Anonymous
    2017-11-03T07:24:05+00:00

    Ok, I had this same thing happen to a clients computer after disk cleanup on a remote session to a workstation.  Stuck at 100%  after being rebooted after the cleanup. I forced a remote hard reset after waiting 20 minutes. It rebooted and stuck at 35%.

    This machine was part of a domain so at 35% I could log into the server and gain acces to the boot drive of the stuck workstation. I went to the \windows\logs\CBS folder and deleted all the files except the CBS.log file (not sure if this did anything) then I went to \windows\SoftwareDistribution\Downloads folder and moved it, you can probably just rename it and delete it later if it all works out.  I could not delete the SoftwareDistribution folder as it was in use for me, remember the machine was running and stuck at 35%. I checked the workstation and it now was at "cleaning up do not turn off your computer" a minute later (it has a SSD) it went to the login screen! Awesome.

    Updates failed to install error 80070308. Bummer...  I found this solution and it fixed the update problem!

    Windows Update error 80070308 solution

    First, use FixIt for Windows update and try delete or rename %windir%/SoftwareDistribution

    If rename SoftwareDistribution not solve the problem, try this:

    ----I ran the fixit, no joy.

    1. Open Regedit
    2. Go to HKLM\Components
    3. Delete or rename REG_DWORD "pendingrequired=1"
    4. Profit! 

    ----This worked, I renamed the key and without rebooting ran updates and installed no problem. All is well.

    Other thoughts....

    You may be able to remove the hard drive and Rename the SoftwareDistribution or Downloads directory using another computer, then reboot.

    or

    Get to a command prompt using recovery options and rename the folder.

    Remember I did it while it was stuck at 35% from a networked computer as I had access to the boot drive but I would think that renaming that folder by any method should work.

    Most of you are not part of a domain, but the key seems to be the SoftwareDistribution or just the  download folder, thus breaking the  update that is preventing the computer from booting all the way.

    Hope this helps somebody.

    Ken

    Was this answer helpful?

    100+ people found this answer helpful.
    0 comments
  5. Anonymous
    2011-04-08T13:15:21+00:00

    Hi,

    ·         Are you able to login to the machine?

    ·         Which update is being installed on the machine?

    If you are unable to boot to the machine, try the following steps to revert windows update changes and check if you can boot.

    a) Try to revert the update installation by running  DISM command  from Windows Recovery Environment (WinRE) & check if you are able to boot to the desktop normally.

    Follow the steps from this link to boot into Windows Recovery Environment. For more information, follow the section  ‘To open the System Recovery Options menu on your computer’

    b) You will need to know the date and time that the update was installed for this procedure.

    c) From the command prompt run the following command: "DISM /Image:C:\ /Cleanup-Image /RevertPendingActions"

    d) Then reboot your PC.

    Hope the information helps.

    Was this answer helpful?

    50+ people found this answer helpful.
    0 comments