Windows always has the same 82 updates at shutdown.

Hola,

has anyone had a chance to look at the file?

The background CBS.log shows this...

Code:

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?

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

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: )

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.

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.

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

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

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

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