WindowsUpdate_80070570

Dear all,

I am unable to install various updates for the past few months due to the above error, which I receive upon every attempt.

The most recent failed updates attempted are:
- Windows 7 SP1 for x64-based Systems (kb976932)
- Update for Windows 7 for x64-based Systems (kb2488113)

Please find attached files detailing errors, and update histories, which may be of use.

I have contacted Windows support, and followed through their suggestions, but I have received no further correspondence from them, after none of their suggestions worked. Please find attached txt file detailing their suggestions.

Any help would be appreciated.

Thank you in advance,

Matt

Matt,
* For trouble shooting -
I suggest you try to install one IMPORTANT update at a time.
See how that goes. If successful continue with the important ones only, one at a time.

* For SP1 KB 976932 use the link below - .

Download details: Windows 7 and Windows Server 2008 R2 Service Pack 1 (KB976932)

* Have you checked in Event Viewer ?
Event Viewer - Windows Logs - System & Application.
Check for any red error messages to do with this problem.

* Wouldn't harm to do a System File Check.
Go to Start > Run,. and type cmd,. now type sfc /scannow
Take note of the message at the end.

* How do I reset Windows Update components?
How do I reset Windows Update components?

* If the above gives you no joy -
Microsoft have provided you with sound advice thus far.
I would suggest you continue to take advantage of the no-charge support from Microsoft for Windows Update issues.
Mention your ID - Microsoft Support Incident: SRX1154568975
If necessary follow up by phone.

* FYI -
Windows Update errors – A troubleshooting guide - 4sysops

Hello Matt, and welcome to the Seven Forums!

Try what @JMH has said above first. I completely agree with everything @JMH has said. Not going to repeat it!

From your WindowsUpdate.log:

Code:

2011-05-19    19:56:04:555    3520    f24    Handler    FATAL: CBS called Error with 0x80070570,

Send Microsoft C:\Windows\Logs\CBS\CBS.log. Right click on it > Send To > Compressed (zipped) folder first.

Upload the .zip here as well, if you like, as that is the most important log for your error message.

Good luck!

Richard

Thank you for your help.

Upon running a system file check, it stopped at 13%. (Please find attached).

Event viewer highlighted multiple errors - a few of them sounding quite severe. Please find attached files.

Also, following Richard's advice I received an error stating the file was not found or no-read permission. I checked the permission of this folder and found access was ticked to both read and write for system, administrators, users (only me) so doesn't seem to be a problem there.

If it helps, I did receive a 'blue screen of death' last week with the error: IRQL not less or equal. (I think I had the same error last year, and needed to get the hard-drive replaced - hopefully it will not be the case here).

Thank you for your help.

P.S. I am continuing receiving support from Microsoft on this issue but response time is slower so would be keen to keep both channels flowing. Thanks again.

Hello again!

Firstly, please follow these instructions and post your logs here: https://www.sevenforums.com/crashes-d...tructions.html

Your SFC error can only be analysed from within that CBS.log!

Please copy the C:\Windows\Logs\CBS folder to your Desktop, right click on it > Send to > Compressed (zipped) folder, and upload the new file which is created on your Desktop here.

Thanks!

Richard

Thanks for your help.

Please find attached, as requested.

Much appreciated,

Matt

Perhaps time for a repair install Matt.

Does that mean wiping my computer, reinstalling my OS, then transferring files from a back-up?

Seems a bit extreme, considering the only issue is I can't install updates.

Could the cause be physical i.e. could the hard-drive replaced need replaced? Laptop is still in warranty.

While you are waiting for niemiro to return read through the link below -

Repair Install

Hello again, Matt!

Sorry for the delay in responding!

The CBS.log is usually quite helpful, but today it was extremely helpful!

Both your SFC and Windows Update errors are caused by one corrupt file.

This file:

Code:

%SystemRoot%\WinSxS\amd64_microsoft-windows-directx-direct3d10.1_31bf3856ad364e35_6.1.7600.20830_none_acd92199dc3ca79f\d3d10_1.dll

I can fix this. I can do a replace on reboot. Or I could do it from the offline environment. The other alternative is you do a Repair Install. Link is above. I am more than willing to fix it. There will be a tiny element of risk, as with all things, especially as this is a core Windows File, but I have done this procedure many times before, and so far have a completely clean record.

I am also not sure if a Repair Install is actually going to work. It may well fail and roll back.

It is your choice. If you ask around on this forum, people who see a SFC error will immediately run a mile, and quote Repair Install. (an ever so slight generalisation)

SFC corrupts are actually quite easy to fix. But since I seem to be the only person who does them, I have to offer you the alternative otherwise I might get into trouble!

If you have a disk, and just want to insert it and get this over with, then fine. If you don't have an SP1 disk, then give me the go ahead, and I shall perform a quick and simple switch in - switch out. It really isn't unsafe, and maybe the more people I do this on, the more people will see that SFC corruptions can be fixed!

Anyway, about your BSoDs, it looks very much like your network card driver is at fault here.

At the moment, the dumps are being very clear in their analysis. You are using an old, 2009 version of the netw5v64.sys driver. And the dumps point to a clear driver issue with this dump. The obvious solution is the update the driver using either your system manufacturer's website, or via Intel (please update whatever networking/Ethernet drivers you can find on those websites): Intel® Driver Update Utility

If the BSoDs do continue, we can widen our net, but I am not going to do that until the highly likely driver is updated!

Richard