Windows always has the same 82 updates at shutdown.

[dna316]

Ok so I am new here on the forum. Hi all...

I have had this HP ProBook 4540s for about 2 years now.
Windows 7 Pro SP1 x64
8GB ram
Intel i5-3210M CPU @ 2.05 GHz

For as long as I can remember there is always the shield with the exclamation mark on shutdown button.
I shut down the system and it says installing 82 updates. When I boot up it says installing and configuring updates.

Once the computer boots back up it takes about 2 minutes for the shield and exclamation mark to come back up. I have done the shut down many many times and it always comes back. I tried running windows update and it finds 82 updates, I install them and it finishes without any error codes but the same updates are always available for download.

I looked in the update history and their are 19 updates failed, further down the list all of the 19 failed updates are also listed as successfully installed on later dates. Im at a loss. I tried downloading the SURT and running it but it didn't seem to fix the problem.

I ran sfc /scannow and it did not find any problems....

I also have the CBS folder zipped but it is to large to upload... it is 13.6MB zipped.

Any help would be greatly appreciated.

 

[cyanna]

Hello and welcome to the Sevenforums!
Please note that for all the troubleshooting steps below you will have to work from an administrator account.
1. Press the Windows logo key + R, type cmd in the Run box, and then press Enter. Right-click cmd, and then select Run as Administrator.


2. The black window that opens is a command prompt window. Type the following commands and make sure that you press Enter after you type each command. (you can copy the commands from here, without the dot!, then right click in the command prompt windows and choose paste)

• net stop bits
• net stop wuauserv
• net stop appidsvc
• net stop cryptsvc
• Del "%ALLUSERSPROFILE%\Application Data\Microsoft\Network\Downloader\qmgr*.dat"
• Ren %systemroot%\SoftwareDistribution SoftwareDistribution.bak
• Ren %systemroot%\system32\catroot2 catroot2.bak
• net start bits
• net start wuauserv
• net start appidsvc
• net start cryptsvc

3. In Windows Explorer go to C:\Windows\system32 and find Wuaueng.dll. Right click an choose properties, click the Details tab and check that the file version number is 7.6.7600.256

Try windows update again....

 

[NoelDP]

Delete the older CBSPersist files from the archive until the compressed size comes under the 8MB limit - then post all the other files.

 

[dna316]

Thanks for the replies.....

Cyanna I am working on your procedure right now. Ill post back soon..

NoelDP heres the file.

 

[dna316]

Ok Cyanna here are screen shots of what I did. I have not run the windows update again in case you needed me to do something else.

 

[dna316]

Ok so I tried opening the windows update and it wanted to download an updated windows update client. So I let it do that, it restarted and "configured updates" then I launched the windows update again and it wanted to download the same thing. Now it wont even see any other updates, its constantly trying to update the update client.
View attachment 333269

View attachment 333270

View attachment 333271

 

[NoelDP]

That's the normal response when installing a new Windows Update Agent - what happens if you now do a Check For Updates?

 

[dna316]

That's the new issue. I have tried updating 3 times now. Every time I get the above shown screens. It says it needs to update the agent. Then downloads, restarts and "installs the update" then when I launch the windows update again it tells me I need to update the agent again. It seems to be stuck trying to update windows update itself.

 

[NoelDP]

OK - please follow these instructions and post the resulting files again...

Please follow the Windows Update Posting Instructions and post the requested data
If the file is too large (8MB compressed), remove the older CBSPersist cab files until the final file is below the limit - you can always post them separately after zipping them. (the forum doesn't allow the upload of bare CAB files, for a number of reasons)

 

[dna316]

Ok I followed all the steps and here is the CBS.zip

 

[dna316]

Hola,

has anyone had a chance to look at the file?

 

[NoelDP]

The background CBS.log shows this...

2014-09-13 15:01:28, Info                  CBS    Exec: Processing complete.  Session: 30396309_3702701484, Package: WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.6.7600.320 [HRESULT = 0x00000000 - S_OK]
2014-09-13 15:01:30, Info                  CBS    Session: 30396309_3832961713 initialized by client WindowsUpdateAgent.
2014-09-13 15:01:30, Info                  CBS    Session: 30396309_3833273714 initialized by client WindowsUpdateAgent.
2014-09-13 15:01:36, Info                  CBS    Session: 30396309_3893177819 initialized by client WindowsUpdateAgent.
2014-09-13 15:01:36, Error                 CBS    One transaction is already pended, client must specify that pending is allowed. [HRESULT = 0x800f0806 - CBS_E_PENDING]
2014-09-13 15:02:23, Info                  CBS    Session: 30396310_63403340 initialized by client WindowsUpdateAgent.
2014-09-13 15:02:23, Info                  CBS    Read out cached package applicability for package: Package_for_KB2840149~31bf3856ad364e35~amd64~~6.1.1.0, ApplicableState: 112, CurrentState:0
2014-09-13 15:02:23, Info                  CBS    Session: 30396310_63559340 initialized by client WindowsUpdateAgent.
2014-09-13 15:02:23, Info                  CBS    Read out cached package applicability for package: Package_for_KB2928562~31bf3856ad364e35~amd64~~6.1.1.0, ApplicableState: 112, CurrentState:0

You did reboot between attempt to install the Update Agent?

 

[dna316]

Yes sir. And I have tried to restart and shutdown multiple times.

 

[NoelDP]

We'll have to try and revert the pending update then...

Boot to the Repair Environment, and get into the Command Prompt
run the following command and wait for it to complete, before rebooting back into normal Windows.

dism.exe /image:C:\ /cleanup-image /revertpendingactions

(make sure that your normal Windows drive has the correct drive letter in the above path, or you'll get errors - it could be anything from C: to F: )

 

[dna316]

Hey sorry its been so long since I was able to try this.... Anyway I did as you mentioned and I get this error.....

I tried looking at the log and there is no entry for this error. While typing this message I realized that the reason theres no log created is because the log was located at the X:\windows \logs\dism\dism.log

I just realized that the picture might be difficult to read.....
Error:2
Unable to access the image.
Make sure that the image path and the windows directory for the image exist and you have read permissions on the folder.

 

[NoelDP]

That sounds as if you didn't check which drive letter was assigned to the installed Windows when you went into the Repair environment. although it's almost always C: when in Windows, it can be anything from C: to F (or higher) in the RE.

Please try again using D: as your drive letter.

 

[dna316]

Ok I ran the command again using /image:d:\
it returned.....

The scratch directory size might be insufficient to perform this operation. This can cause unexpected behavior.
Use the /Scratchdir option to point to a folder with sufficient scratch space. The recommended size is at least 1024 MB.

Reverting pending actions from the image...
The operation completed. Any revert of pending actions will be attempted after reboot.
The operation completed successfully.

Should I try it again after creating a folder for the scratch directory? and if so do I create the folder for the scratch directory in something like c:\scratch

 

[NoelDP]

Why not follow the instructions as given instead of inventing new ways to do things?

When in the repair environment, do DIR commands to find your normal \Windows installation and use that drive letter

 

[dna316]

I actually followed your instructions..........
My question is where do I point the scratchdir???

 

[NoelDP]

There is no need to point scratchdir anywhere so far as I know.