Solved Windows update giving return code 800736b3; restores giving x00000022

[jpaulm]

I recently noticed that the system was trying to do 7 updates every day at closedown, and found that update was giving a return code of 800736b3.

I have run SURT several times, and it doesn't seem to give any results (or should I be looking somewhere else?).

I ran sfc /scannow and extracted the results and they are in sfcdetails.txt (attached). SFC said there were some files it couldn't fix, even though sfcdetails.txt says it has fixed all of them.

CBS.zip is much too big to upload using the paperclip - is there another way?

I tried restoring to an earlier restore point, and unfortunately all the attempted updates have flushed my list of restore points - and the oldest few all give me a return code of x00000022.

Not sure if this is one problem or two...! I am reluctant to do a System Recovery as it sounds pretty drastic - help would be much appreciated!

PS Is any more info required?

 

[NoelDP]

The only errors in SFC are these...

2015-06-14 21:41:16, Info                  CSI    000005e7 [SR] Repairing 1 components
2015-06-14 21:41:16, Info                  CSI    000005e8 [SR] Beginning Verify and Repair transaction
2015-06-14 21:41:16, Info                  CSI    000005ea [SR] Cannot repair member file [l:24{12}]"utc.app.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 6.1.7601.18839, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2015-06-14 21:41:16, Info                  CSI    000005ec [SR] Cannot repair member file [l:66{33}]"telemetry.ASM-WindowsDefault.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 6.1.7601.18839, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch

...which are caused by an MS update which they messed up the file-coding on and may get around to fixing sometime.
It's not critical, but you could get rid of it by uninstalling KB3022345 and/or KB3068708 and hiding the latter when it reappers in your offered updates list.

Please post the C:\Windows\Logs\CBS\CheckSUR.log and C:\Windows\Logs\CheckSUR.Persist.log files.

 

[jpaulm]

Thanks! C:\Windows\Logs\CBS\CheckSUR.log and C:\Windows\Logs\CBS\CheckSUR.Persist.log files attached

BTW I run BidDefender Antivirus Plus 2015 regularly, and ran MalwareBytes yesterday and it just discovered a couple of PUPs, which I have deleted.

TIA

 

[NoelDP]

CheckSUR is happy now - it seems never to have had a problem.

0022 errors like this are often associated with hard drive problems - but I think it's unlikely here, as there are apparently no file problems to be seen.

Let's have a look at the Event logs...

Open Event Viewer

click on theWindows logs entry in the left pane to expand it.

Now click on theApplication entry - wait while it loads.

Click on 'File'in the menu bar and select Save...

Save the file asAppevt.evtx

Repeat for theSystem log

then zip both,and upload them.

 

[jpaulm]

Thanks in advance! Zip files attached

 

[NoelDP]

There are a number of Disk errors showing in the System log - but the latest CHKDSK log shows no bad sectors, and only minor errors.

Something is repeatedly corrupting the COMPONENTS registry hive - I suspect this could be bad RAM.
Please run at least 3 full passes with MemTest86+ and post the results - even one error is too many! http://www.sevenforums.com/tutorials/105647-ram-test-memtest86.html

 

[jpaulm]

Hi guys, many thanks for your help! A computer guru came to the house and ran some magic tools, and basically came to the same conclusion, so we decided my computer should be replaced. The new one is working fine, so I am going to mark this query closed! Thanks again, and have a good summer, everyone!

 

[NoelDP]

Good luck with it!