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
    2018-01-05T01:59:32+00:00

    Worked like a charm, had a factory machine crashed, needed to fix ASAP, thank you very much for sharing and posting, saved me a lot of time.

    Was this answer helpful?

    10+ people found this answer helpful.
    0 comments
  2. Anonymous
    2017-08-28T21:22:34+00:00

    I just did this exact thing.  If only I had read your email first, I would not have cleaned up the updates.  Is there any way to get this fixed?

    Was this answer helpful?

    10+ people found this answer helpful.
    0 comments
  3. Anonymous
    2018-09-12T12:22:25+00:00

    Ok, I tried everything I could find on this.

    The situation was trigged by one of two things:

    * Either a windows update package that was loaded in on the 11. September, OR more likely:

    * The user ran a disk cleanup. It seems that this keeps reoccuring among many of those who has the problem.

    Windows 7 OS, the following was the situation:

    * Stuck on 35% configuration for ages

    * Booting to Safe Mode also lead it to being stuck on 35%

    * Reverting to previous state didn't work - there was no previous states to repair to

    * Running directory recovery mode didn't work - still stuck on 35%

    * Running anything - still stuck on 35%. 

    * Holding "F8" at boot and going into "repair computer" and "command line" to do some editing, didn't work either - albeit, I am not sure

    I tried two things in the command line - delete the c:\windows\sxssrs\ trick that somebody mentioned (please look into it, do not delete the entire folder), and renaming the WindowsUpdates-folder (find the article).

    However, even after this - the computer was still stuck on 35%.

    So I gave up. Let the computer sit on my desk working on 35%. Took it in the car, still spinning on 35%, brought it to the customer - still spinning on 35% - and then it suddenly arrived at the login-screen while I was talking to the client.

    SO.. what helped? Was it one of the things I did, or simply wait? I am not entirely sure - and can not know. However, if you have it spinning at 35%, I see that several people also report that just waiting helps.

    The computer I used had a fast SSD and an i5-processor, and still it was sitting there for at least an hour at 35% (with the icon spinning around), before it came about. If your computer has a slower disk, it might take even longer time.

    Just wanted to write this, because this was extremely frustrating. Hope it helps somebody out there.

    Was this answer helpful?

    10+ people found this answer helpful.
    0 comments
  4. Anonymous
    2018-05-18T03:45:49+00:00

    Same experience. Go to safe mode and stuck on 35% for a while until hard disk light not flesh, then hard rebot, go to normal starup, stuck on 35% again. Wait until i turn to clean up screen. Finally reach login screen.

    Was this answer helpful?

    10+ people found this answer helpful.
    0 comments
  5. Anonymous
    2018-12-28T21:04:02+00:00

    If you have a domain joined computer, you can connect via computer management to the machine. Disable the "windows module installer" service and then reboot. This allowed me to get in and fix the system so that i could continue performing the updates. in my case i was out of diskspace so i just disabled the page file.

    Was this answer helpful?

    6 people found this answer helpful.
    0 comments