No updates for Windows 7, 32-bit

[Shenzie]

Starting about a week ago, Windows Updater (WU) on my Win7 Home Premium 32-bit system began to act abnormally, has been degenerating in capability, and is now unable (or unwilling) to install any updates at all. The condition seemed to coincide with V320 of wuaueng.dll being installed automatically by WU.

First indication was that WU would take a much longer than usual time to search for updates (though the Systray icon advised that updates were available), then advise that a new, up-to-date update routine needed to be installed. (This has been reported here on SevenForums and elsewhere.) The installation was never successful—update history would show that Windows Update Agent 7.6.7600.320 installation had failed, time after time.

System Restore to a few days earlier got WU going again, but attempt to let WU manage installation of any selected update(s) would soon again yield essentially what I've described in the para. above. Another System Restore would get V256 of wuaueng.dll installed in place of V320, and I was able to download and install a handful of updates manually. Any attempt to use WU would fail the same way, however.

A day or so later, attempt to launch WU would result in failure, with error code 80070005 reported. Following instructions for this error code given by Support.Microsoft.com did not cure the problem. Searching for other help from Support.Microsoft.com turned up instructions to stop the Windows Update Service, re-register certain DLLs, re-start the Service. Following these resulted in the Windows Updater now launching...but with an anomalous dialog (attached).

Clicking the OK button yields a window containing this advisory: "Windows cannot access the specified device, path, or file. You may not have the appropriate permissions to access this item." (The title bar of the window begins ":{26EE0668-A00A-44D7-9371-BEB064C98683}\{36EEF7B...") This is definitely an Administrator account, with UAC cranked all the way down.

I checked the wuapp.exe and wuaueng.dll files residing in an alternative HD that runs the same version of Win7 as does my primary drive (I keep the alternative drive up-to-date) against the ones in my primary drive's C:\Windows\System32 folder—they are byte-for-byte identical. Starting Win7 from the alternative drive yields completely normal Windows Update operation...and V320 of wuaueng.dll is the version in the System32 folder.

Strangely, if I copy wuapp.exe from the System32 folder on my primary drive to any other folder on the drive and launch it, wuapp.exe starts up normally! However, no updates can be installed. This may tally with the fact that now I can't get any updates to install from downloaded installers.

I'm now having no success with System Restore.

Addressing the required "posting info":

1. System Update Readiness Tool (SURT) — will not install and run. No error number is reported.

2. SFC Scan — no corrupted or missing files are reported

3. Windows Update Error Codes — the only error code reported in this whole mess is 80070005...and it's no longer reported, because WU doesn't get that far.

4. Log Collection — Zip-ed version of CBS.log is attached

5. Start a New Thread — done herewith


Thx in advance for advice and instructions. If I need post more data, please advise.

I'm open to any/all guidance for "surgical" fixes...but if there is a "tac nuke" approach (e.g., restoring folders and files from Shadow Copies, copying folders and files from the alternative drive) short of a Repair Install of Win7 that I could try, I'm willing to give it a go. I keep extensive archives of the primary drive and have access to a fully-functional drive running the same version of Win7. In past years, I've been adept in replacing corrupted Default, Sam, Security Software, System config files to rescue a wacked Registry. A plethora of these (and other Windows-related folders and files) from the previous week and earlier are available in the large Shadow Copy folders on the primary drive.

Will do a repair install if absolutely necessary...but would really like to avoid that.

Shen

 

[ICIT2LOL]

Shen I don't know if this will be of any help but worth a try Error 0x80070005 in Windows Update when you try to install updates

You mentioned SFC and I think you could run this too

http://www.sevenforums.com/tutorials/433-disk-check.html < use the /f and maybe the /r switches in Option 2 ifnecessary

 

[NoelDP]

Please post the ENTIRE CBS folder - it may be too large for the forum to handle, so split it into chanks smaller than 8MB each.
Also please post the C:\Windows\windowsupdate.log file.

 

[Shenzie]

Thanks to both ICit2lol and NoelDP for replies. In deference to Noel's long track record sorting out Windows Update problems here, and knowing from personal experience how tough it is to hit a moving target, I'll elect not to make any attempt to install anything else yet.

A Zip file of the current contents of the CBS folder is attached, as well as the current Windows Update Log file. The 52+ MB "old" CBS log file arose from following one of Microsoft's instructions to rename the old log file.

FWIW, another anomaly occurring re this over the last week was one of Microsoft's FixIt tools not running because it was unable to respond to a Run As Administrator command. However, I am the Admin, with full privileges, and I was launching the EXE file directly, not via right-click.

Also, there are some updates-to-be-made queued up that arise on system shutdown.

I failed to mention in first post that I run Eset NOD32. I've seldom had trouble installing Windows updates with NOD32 running, but in this go-around I've had to suspend NOD32 while doing the few successful manual updates from installer EXE files.

Shen

 

[NoelDP]

I think these are the operative errors in the windowsupdate log...

2014-09-20 23:41:14:598 4516 12dc Misc ===========  Logging initialized (build: 7.6.7600.320, tz: -0700)  ===========
2014-09-20 23:41:14:598 4516 12dc Misc   = Process: C:\Windows\system32\wuauclt.exe
2014-09-20 23:41:14:598 4516 12dc AUClnt FATAL: Error: 0x80070005. wuauclt handler: failed to spawn COM server
2014-09-20 23:41:14:598 1376 814 Handler FATAL: 0x80070005: ERROR: Remote update handler container process created (PID: 4516), but exited before signaling event
2014-09-20 23:41:14:598 1376 814 Agent   * WARNING: Exit code = 0x80070005
<skip>
2014-09-21 09:42:52:429 5960 ee8 Misc   = Process: C:\Windows\system32\wuauclt.exe
2014-09-21 09:42:52:428 5960 ee8 Setup Closing WU explorer windows
2014-09-21 09:42:52:439 5960 ee8 Setup WARNING: Failed to cocreate IShellWindows, error = 0x80070005[QUOTE][/QUOTE]
2014-09-21 09:42:53:442 1420 16ec Setup Launching WuSetupV.exe to complete SelfUpdate
2014-09-21 09:42:53:444 1420 16ec Setup WuSetupV.exe launched successfully
2014-09-21 09:42:53:444 1420 16ec Agent   * WARNING: Skipping scan, self-update check returned 0x8024001B
2014-09-21 09:42:53:444 1420 16ec Agent   * WARNING: Exit code = 0x8024001B

Here's a possible fix I found while googling...

1. launch regedit.exe
2. Locate the following key: HKEY_LOCAL_MACHINE\Software\Microsoft\Ole
3. Look for the value "DefaultAccessPermission" (NOT DefaultLaunchPermission)

If this value exists, it is possible that the value has been corrupted or are incorrect. If you don't have the need for specific default permissions, you can restore the original permissions on the machine by deleting this value (do not delete the entire reg key, just that one value.)

 

[Shenzie]

Thx for the very quick reply, Noel—

No joy. (BTW, here in southern California, "failure to spawn" is an affliction that is seldom admitted to. :: )

The specific Registry key did, in fact, exist. I exported it for safekeeping, then deleted it. Same anomalous action when attempting to launch WU, even after system restart.

I booted from the alternative Win7 drive—it has the same key defined. I exported that key, then compared it to the one I exported from the primary drive—they are byte-for-byte identical.

For completeness: The "alternative drive" to which I have referred is a 640GB unit that was my primary drive for several years. I cloned it to a new 750GB and partitioned it (the 750) to 300GB and 450GB to make ready to install an SSD when prices were "attractive." This operation was done roughly a year ago, and until a week+ ago, the 300GB partition has worked flawlessly in regards to Windows updates. The partition has about 100GB free space.

The 640 is up-to-date as far as Win7 is concerned, but it doesn't have some of the apps installed, and some apps are still installed on the "C:\Drive" and not a separate partition.

My reluctance to do a Repair Install is concern that changes I have made (installed applications and updates and patches thereto, et al.) may be affected adversely by the Repair Install. My experience goes back to the Days of DOS, and I've seen more than ample evidence that "tools" from Microsoft are quite self-centered and dismissive of the user's system's overall configuration.

No matter how this all goes, I would be very interested in your opinion of how/why Windows would get its knickers knotted in launching wuapp.exe from the System 32 folder (publisher unverified...no valid certificate), yet has no complaint at all about the exact same exe located in a different folder.

Standing by to try anything you think appropriate...

Shen

 

[NoelDP]

Please post the new windowsupdate.log file -
which exact folders did you relocate off the C: drive?

 

[Shenzie]

Thank you for your reply, Noel. Current WU log file is atch.

No folders containing any executables/dlls/etc. were "relocated" in a brute force manner. The only folders that I moved via cut/paste contained data files created by me, residing in folders created by me: graphic, sound, word processor files, and the like. There were no cut/paste liberties taken with the Windows (and subordinate) folder, Program Files, Program Data, Docs & Sets, Sys Vol Info, etc.

To reach the goal of having the Win7 "boot entity" (at this stage, a partition) no larger than 200GB, I uninstalled various non-Microsoft applications and reinstalled them on the other partition. The uninstallations were all done in the formal manner, under the aegis of Windows. I employed no redirection options that might confuse Windows. I left some applications that I use regularly and desire to load and run as quickly as possible (when I move to an SSD) where they have always been on the C:\ (logical) drive.

As best I can ascertain, everything I do on this machine goes as it has gone for the last many months...with the exception that at about the time that Microsoft "rolled out" its V360 update to WU, my ability to make updates has atrophied through several stages (varying anomalies) over a week's time to the current state of non-operation. Until V360 of wuaueng.dll was installed (automatically) vice V256, WU was quite well-behaved.

Shen

 

[NoelDP]

here's one complete error sequence...

2014-09-20 19:06:21:658 3236 1774 Misc ===========  Logging initialized (build: 7.6.7600.320, tz: -0700)  ===========
2014-09-20 19:06:21:658 3236 1774 Misc   = Process: C:\Windows\system32\wuauclt.exe
2014-09-20 19:06:21:658 3236 1774 Misc   = Module: C:\Windows\system32\wucltux.dll
2014-09-20 19:06:21:658 3236 1774 CltUI FATAL: Failed to connect to AU engine to get notification handle, hr=80070005
2014-09-20 19:06:21:663 1376 1158 AU AU received handle event
2014-09-20 19:06:21:663 1376 1158 AU AU setting pending client directive to 'Install Approval'
2014-09-20 19:06:36:675 1376 1158 AU Launched new AU client for directive 'Install Approval', session id = 0x1

let's try this...
Download the all-in-one Windows Repair tool from here - Windows Repair (All In One)
run it - but ONLY the Windows Update repair section. UNCHECK everything else.

then reboot, and try another Check for Updates, and attempt to install only the oldest available update.

 

[Shenzie]

Did as you directed, Noel. There was a change (will detail), then a relapse.

The three screen shots atch show the reaction to launching WU after using the All-In-One Windows Repair Tool (only the Repair Windows Update option). I'd seen this alert several days ago, and the result of clicking "Check for updates" is shown in the next screen shot. (Had also seen that before.) Clicking "OK" brought up the advisary about the WU service, but as you can see from the last screen shot, the service was, in fact running.
View attachment 334158

View attachment 334159

View attachment 334160

I elected to restart the service and try WU again. This time I was advised that the system should be restarted, which I did...and was rewarded after restart with the same symptoms as I posted at the beginning of this thread: "publisher unknown...no valid certificate" and when clicking to proceed anyway, Windows advising that device, folder, file, et al. cannot be accessed.

I've attached the two log files that the Repair util created.

Over to you...and sincere appreciation for investing your time in my problem.

Shen

 

[NoelDP]

It looks like the repair tool had problems deleting some files that were in use.
Please try again, this time running the tool while in Safe Mode - with luck that will prevent this lockout.

 

[Shenzie]

No joy, Noel—exact same result (outwardly) as before. (wuapp.exe is treated with suspicion, then claim is made that WU service is not running.) Have attached Windows Repair log files. Perhaps the new log data will indicate something different and useful.

Are the files that the Repair util couldn't delete files that I could delete or rename manually? When taking ownership and stopping applicable service(s) is ineffectual, my next ploy is to start from another drive and gain unfettered access.

Shen

 

[NoelDP]

I'm always hesitant to use the external boot option, as it could throw a spanner in the works, and also means that we lose diagnostic data.

Let's have a deeper look at the system - please follow the http://www.sevenforums.com/bsod-help-support/96879-blue-screen-death-bsod-posting-instructions.html but just post the resulting data here.

 

[Shenzie]

Good evening (Zulu time), Noel—

I'm feeling a bit thick re your instructions. Overlaying the instructions at the URL you linked on my prior history (thread already started) and condensing, the options would seem to be these:

OPTION ONE
To Use DM Log Collector

1. Click/tap on the Download button below to download the file below.
... ... ... ...
9. In your BSOD post, upload the debug-YourComputerName-xxxx.zip file into your post.


OPTION TWO
To Use SF Diagnostic Tool

2. Download and run the SF_Diagnostic_Tool.exe file to use the Grab All button as instructed in the tutorial link below.

3. When finished with step 2, do either step 4 or 5 below.

4. If You Have Already Started a Thread in "BSOD Help and Support"
A) Go back to your original thread that you created for your BSOD issue, edit your existing post or reply with a new post, and go to step 6 below.
... ... ... ...
6. In your BSOD post, upload the renamed SF_DD_MM_YYYY.zip folder into your post.


Should I exercise Option 1? Option 2? Both? (As a retired engineer, I know that more information is better, but overkill just wastes time and bandwidth.)

Shen

 

[NoelDP]

Please use the SF Diagnostic Tool - sorry, I should have specified.

 

[Shenzie]

The Zip-ed folder created by the tool is attached, Noel. Am hoping it sheds some light on a solution.

Shen

 

[NoelDP]

You and me both!
Looking at the Event Logs....
You appear to have had problems with Novastor services - 'File not found'
Is the product still installed?

The NovaStor NovaBACKUP Backup/Copy Engine service failed to start due to the following error: 
The system cannot find the file specified.

There are similar problems with a driver...

  Keyword: Installation,Failure
  User: S-1-5-18
  User Name: NT AUTHORITY\SYSTEM
  Computer: HausFaust-II
  Description: 
Installation Failure: Windows failed to install the following update with error 0x80070005: Windows Update Setup Handler.

There are problems also involving Acronis...

Activation context generation failed for "C:\Program Files\Common Files\Acronis\DiskDirector\WinPE\Files\systeminfo.exe". Dependent Assembly Microsoft.VC80.CRT,processorArchitecture="x86",type="win32",version="8.0.50727.762" could not be found. Please use sxstrace.exe for detailed diagnosis.

(amongst a few others)
VC80 is a very old version - which suggest that the copy of Acronis is also approaching retirement

There's also this error...

Product: Adobe Reader XI (11.0.09) -- Configuration failed.

This last could be the result of the hack you appear to have installed to prevent validation of an installed Adobe product - a modified HOSTS file to prevent access to the validation/activation servers at Adobe.


However - there is something that may help...

You're also showing the following error...

Event[34654]:
  Log Name: Application
  Source: MsiInstaller
  Date: 2014-09-22T16:59:24.000
  Event ID: 1015
  Task: N/A
  Level: Warning
  Opcode: Info
  Keyword: Classic
  User: S-1-5-21-4011791304-1166479289-1744321215-1001
  User Name: HAUSFAUST-II\Ol' JP hisself
  Computer: HausFaust-II
  Description: 
Failed to connect to server. Error: 0x800401F0

This may help...

1. On the "Start" menu, click "Run:.

2. In the "Open" box, type "msiexec /unreg", and then press ENTER.

3. On the "Start" menu, click "Run".

4. In the "Open" box, type "msiexec /regserver", and then press ENTER.

(Poached from MSI Installer and Failed to connect to server Event - Mike Poulson's Thoughts on lots of stuff - Site Home - MSDN Blogs)

Bearing in mind that routine was written for XP, it may well not work for Win7, so we'll do an alternative method....

Open an Elevated Command Prompt, and run the following commands...

msiexec /unreg
msiexec /regserver

Once complete, reboot TWICE (please leave at least 15 mins between boots) and then do a new Check for updates and attempt to install the oldest update found.

 

[Shenzie]

Thank you for your analysis and detailed response.

I'll comment as far as I can...but the precis is that there has been zero change in WU's willingness to run after following your instructions. The first error indication is UAC-ish observation that wuapp.exe is suspicious, and after attempting to run anyway, advisement that the WU service is not running (even though it is).

You appear to have had problems with Novastor services - 'File not found' Is the product still installed?

Novastor was uninstalled in 2011, after a few minutes of test and assessment. I (today) found the company's instructions for manual uninstall and carried them out. (Only a few remnants were found.) I also disabled the service that was still loading.
There are problems also involving Acronis...

I use Acronis True Image 11, but don't use Acronis Disk Director. I uninstalled the latter today. If your comment that VC80 is old suggests that Acronis TI 11 is similarly old, I'll take it under advisement...but am not inclined to update an application that has and continues to function flawlessly.

There's also this error... Code: --------- Product: Adobe Reader XI (11.0.09) -- Configuration failed.

Strange, the (free) app is current (11.0.09) and runs as expected and updates from time to time, at Adobe's whim. I think that the changes I made to the Hosts file (three years ago) were because of problems of slowness encountered in the Adobe validation/activiation process. All my Adobe applications are legit.

You're also showing the following error... Code: --------- Event[34654]: Log Name: Application Source: MsiInstaller . . .

I looked at the Event Viewer and found literally scores of MsiInstaller warnings and errors, the vast majority of them beginning at about the time that WU began its descent into madness. There are repetitious instances of MS Office 2003 attempting to do something untoward in a protected section of the Registry, for instance. I don't understand this—my copy of MS Office 2003 is legit/validated/activated/et al.


Noel, you have been extraordinarily generous with your time and mental acuity, for which I am very grateful. My problem would seem to be perhaps not worth trying anymore to solve surgically...as long as there is a way to avoid it. I am able to back the system up in time in increments of days, weeks, and even months (to a system image in July of this year). However, since failure for WU to operate properly arose only at about the time that the Windows Update Agent was updated by Microsoft to V7.6.7600.320—and reports of problems like mine began pouring in—it seems possible that my problem would soon recur.

Is there any other approach that could clean up Windows (especially WU) in a broad fashion?

Shen

 

[Shenzie]

Sorry for the poorly-organized previous post, Noel. I used different fonts in composing it in order to differentiate my comments from yours. It looked fine in Preview mode, but has degraded now that it's been posted.

::shrug::

Shen

 

[NoelDP]

please run the msiexec commands I posted earlier, and see if they make any difference - we may need to try some variants on them.

The other option is a repair install - see here for instructions... http://www.sevenforums.com/tutorials/3413-repair-install.html?ltr=R