Windows update error - 8E5E03FB & 80070490

That seems to have merely confirmed the problem, without attempting to fix it.
It does say it found errors in the CBS log, though - which I don't recall seeing...

Ah- I may have found at least one of them...

Code:

2014-04-11 10:41:26, Info                  CBS    Appl: Package: Package_2_for_KB2817183~31bf3856ad364e35~amd64~~9.4.1.0, Update: 2817183-40_neutral_GDR, Applicable: Applicable, Disposition: Installed
2014-04-11 10:41:26, Info                  CBS    Plan: Package: Package_2_for_KB2817183~31bf3856ad364e35~amd64~~9.4.1.0, Update: 2817183-40_neutral_GDR, current: Resolved, pending: Default, start: Resolved, applicable: Installed, targeted: Installed, limit: Installed, selected: Default
2014-04-11 10:41:26, Info                  CBS    Perf: Resolve chain started.
2014-04-11 10:41:26, Info                  CSI    0000000b@2014/4/11:05:11:26.071 CSI Transaction @0x32e840 initialized for deployment engine {d16d444c-56d8-11d5-882d-0080c847b195} with flags 00000002 and client id [79]"TI1.30364996_1918766890:2/Package_for_KB2817183~31bf3856ad364e35~amd64~~9.4.1.0"
2014-04-11 10:41:26, Info                  CBS    Failed call to CryptCATAdminAddCatalog. [HRESULT = 0x8e5e03fb - JET_errPageNotInitialized]
2014-04-11 10:41:26, Info                  CBS    Failed to install catalog file \\?\C:\Windows\SoftwareDistribution\Download\7db1ab87f88a1548e26a666f4c7bb445\inst\Package_2_for_KB2817183~31bf3856ad364e35~amd64~~9.4.1.0.cat for package [HRESULT = 0x8e5e03fb - JET_errPageNotInitialized]
2014-04-11 10:41:26, Info                  CBS    Failed to install catalog for package: Package_2_for_KB2817183~31bf3856ad364e35~amd64~~9.4.1.0 [HRESULT = 0x8e5e03fb - JET_errPageNotInitialized]
2014-04-11 10:41:26, Info                  CBS    Failed to stage package manifest. [HRESULT = 0x8e5e03fb - JET_errPageNotInitialized]
2014-04-11 10:41:26, Info                  CBS    Failed to add package. [HRESULT = 0x8e5e03fb - JET_errPageNotInitialized]
2014-04-11 10:41:26, Info                  CBS    Failed to persist package: Package_2_for_KB2817183~31bf3856ad364e35~amd64~~9.4.1.0. [HRESULT = 0x8e5e03fb - JET_errPageNotInitialized]
2014-04-11 10:41:26, Info                  CBS    Failed to update states and store all resolved packages. [HRESULT = 0x8e5e03fb - JET_errPageNotInitialized]
2014-04-11 10:41:26, Info                  CSI    0000000c@2014/4/11:05:11:26.945 CSI Transaction @0x32e840 destroyed

I have no knowledge of this error type - so I'll have to research it.

Supposedly, the fixit from here should work.
Please run the one from the page itself, not the one from the popover overlay.

How do I reset Windows Update components? (and yes, it does work on Win7)

That does at least give me something to work on :)

I was hoping to avoid this - but it seems I'll have to go the route of the Repair Environment.

Let's see how your system is set up...
First - is your Windows 7 the only OS installed?

Please reboot to the Repair Environment - as soon as the machine restarts, start tapping F8 - this should bring up the Advanced Boot Menu, at the top of which should be the option 'Repair my Computer'
Pick that
You'll have to log in with your username and password.

Pick the option to use a Command Prompt
At the prompt type
DIR C:\Users

If you get a 'not found' error, try
DIR D:\Users
or
DIR E:\Users

Which one lists your username? (or anything?)

boot back to normal Windows - type Exit, and click on Restart - and post back with your results.

I'll then adjust the batch file accordingly.

Sorry - real life keeps getting in the way...
back later today with the (hopeful) solution:)

Here we go...


I've uploaded afile - svdac.zip - to my OneDrive at Noel'sOneDrive

Please downloadand save it.



Right-click onthe saved file and select Extract all...

Change the targetto C:\ and click on Extract

Close all windows(it would be a good idea to print these instructions!)


Now reboot to theRepair Environment - as soon as the machine restarts, start tapping F8 - this should bring up the Advanced BootMenu, at the top of which should be the option'Repair my Computer'

Pick that

You'll have tolog in with your username and password.



Pick the optionto use a Command Prompt

At the prompttype

I:\svdac.bat

It should run the batch file again - and will create a new log file

Once complete, reboot to normal Windows and post the new log file - C:\npres.txt

Now run CheckSUR again,

then reboot andupload the new CBS.log and CheckSUR.log file to your reply

Oh bother!
either the script was wrong, or the filenames don't exist in the Recovery Environment.
I suspect the former is more likely

I'll have to get back to you for round 3 :)