[SOLVED] W7 SP1 : Error 0x80070057 after having removed some telemetry related updates

J

Just

Well-known member
Joined
Jan 16, 2016
Posts
46
Hi,

For around half a year, I kept my W7 SP1 computer away from Microsoft's updates related to W10 (telemetry and the like), either by not installing them or uninstalling those already in place. Nearly all other updates have been routinely installed, excepted Skype and Silverlight which I do not use. In last december, such a "guerrilla" ended in a way that Windows Update Agent suddenly could not download new updates anymore ; however it can display the list of them. Windows Update service now loads the CPU at 100% and runs endlessly. Anyway, it is still possible on my PC to manually download and instal .msu packages.

Regular maintenance has been done already, trying to diagnose and cure the problem according to Microsoft's online knowledge base guidance. Windows Update Troubleshooter reports a stubborn error 0x80070057 which it fails to fix (an error 0x8007005 got reported once too, then vanished). The System Update Readiness tool did not helped at fixing error 0x80070057. The System File Checker tool reports no anomaly. Repairing file and registry permissions thanks to SubInACL tool and script from KB968003 made no visible changes. Eventually reseting Windows Update components as described in KB2700567 did not help neither. I even tried to install once again the latest version of Windows Update Agent (at present 7.6.7601.19077), with no better success.

:banghead:

Getting support from Sysnative forum's members may give me a chance to understand what went wrong and how to work around the same behaviour in the future.

A zip archive of the CBS folder is attached to the post. However, to keep the size of the archive reasonable, I excluded the CbsPersist_xxx.cab files from the archive. It then contains the following files : CBS.log, CheckSUR.log, CheckSUR.persist.log, DeepClean.log, FilterList.log.

Here is the output of SFCFix.txt:
Code: 
SFCFix version 2.4.5.0 by niemiro.
Start time: 2016-01-19 20:32:07.875
Microsoft Windows 7 Service Pack 1 - x86
Not using a script file.




AutoAnalysis::
SUMMARY: No corruptions were detected.
AutoAnalysis:: directive completed successfully.




Successfully processed all directives.
SFCFix version 2.4.5.0 by niemiro has completed.
Currently storing 0 datablocks.
Finish time: 2016-01-19 20:39:56.476
----------------------EOF-----------------------


Thanks for any further guidance.
 

Attachments

Last edited:
Hi and welcome to Sysnative. Let's take a look. Please do the following.

Logs Needed

1. Please download Farbar Recovery Scan Tool and save it to your Desktop.
Note: You need to run the 32-bit Version so please ensure you download that one.
2. Right click to run as administrator. When the tool opens click Yes to disclaimer.
3. Note: Ensure that the Addition.txt check box is checked at the bottom of the form within the Optional Scan area.
4. Press Scan button.
5. It will produce a log called FRST.txt in the same directory the tool is run from (which should now be the desktop)
6. Please copy and paste log back here.
7. The first time the tool is run it generates another log (Addition.txt - also located in the same directory as FRST.exe). Please also paste that along with the FRST.txt into your reply.
 
Well, this is depressing to read that the trouble might be related to a malware, taking into account how carefully I tried to manage the system over the past years, in order to avoid any infection : downloading binaries from official web pages and automatically running Windows Security Essentials. A soon as I can, I am going to run Farbar Recovery Scan Tool and to paste back its logs.

However, the situation suddenly became worse on that computer, as I made some very basic manipulations in order to try to solve a side issue. At present, the system cannot boot anymore.

I failed to fix the boot problem by running Windows in "repair mode", even from the original W7 installation DVD. I may still run FRST from a LiveCD. Should I do it from the PE Boot CD as advised on the FRST page ? I am asking, as PE Boot CD looks as a liveCD based on XP. Will the XP environment will be able to mount my NTFS partition in order for FRST to scan it ?

Thanks.
 
Well, this is depressing to read that the trouble might be related to a malware
Click to expand...
FRST is an analysis tool. It doesn't mean you have malware.

I failed to fix the boot problem by running Windows in "repair mode", even from the original W7 installation DVD. I may still run FRST from a LiveCD. Should I do it from the PE Boot CD as advised on the FRST page ? I am asking, as PE Boot CD looks as a liveCD based on XP. Will the XP environment will be able to mount my NTFS partition in order for FRST to scan it ?
Click to expand...
That would likely work but ideally if you boot to the Windows 7 System Recovery Environment that would work best.
 
Here is the FRST log file generated by running FRST.exe 32bits from the Windows 7 System Recovery Environment (booting from the install DVD). I found no "Addition.txt check box" within the Optional Scan area. However I checked all the box of that area in order to get the most comprehensive log.
 

Attachments

Thanks. Have you tried restoring your machine to the most recent restore point? I see from your other thread that you may have tried this but want to confirm. Removing any internal card while the machine is on isn't a good ideas so I'm not sure what damage could have occured.

Code: 
==================== Restore Points  =========================
Restore point date: 2016-01-19 14:48
 
Hi Brian,
BrianDrab said:
Have you tried restoring your machine to the most recent restore point? I see from your other thread that you may have tried this but want to confirm.
Click to expand...

Restoring the system to the most recent point was tried around two weeks ago by running the Windows 7 System Recovery Environment. However, it failed. The recovery environment made me reboot the computer a few time, but failed to pull back Windows into a working state.

Removing any internal card while the machine is on isn't a good ideas so I'm not sure what damage could have occured.
Click to expand...

Sure. However, I thought that PCMCIA / PC Cards were hot-swappable. Obviously PCI cards are not.

BTW, the FRST logs reported drivers and dlls with legit md5 hash digest, however not all of them. I am worry about these binaries with unknown digests ; does it confirms the presence of a malware ?
 
The Last Known Good Configuration did not help, but Safe Mode did. I removed the pseudo graphic card wrongly linked to ENE CB-710 chipset then regain a fully working Windows. Here are FRST.txt and Addition.txt logs generated by FRST after having booted the machine in normal mode. Hope it makes us closer to solving the Windows Update issue.
 

Attachments

Great news. Good job. Please do the following.

System Update Readiness Tool (SUR)
1. Download and run the following file.
2. When it asks you if you wish to install, please answer yes. Note: It could take 15 minutes or more to run. Please don't cancel.
3. You will get an Installation Complete screen when it's done running.
4. Please post the contents of the log from the following location. C:\Windows\Logs\CBS\CheckSUR.log
 
The System Update Readiness Tool (KB947821) has been running for hours without success today. It stalled during "installation" and never completed it. I tried it twice, getting repeatedly the same behaviour. I preferred to cancel installation and report the problem here rather than letting the computer run with its CPU loaded at 100% for the next 24h or so.

Capture_KB947821.PNG​

BTW, that fix has already been successfully installed on the machine several times in december and january. As a result of what CheckSUR.persist.log has already been uploaded attached to my first post in this thread. Each and every CheckSUR log reports no errors at all.

Code: 
=================================
Checking System Update Readiness.
Binary Version 6.1.7601.22471
Package Version 26.0
2016-01-10 17:28

Checking Windows Servicing Packages

Checking Package Manifests and Catalogs

Checking Package Watchlist

Checking Component Watchlist

Checking Packages

Checking Component Store

Summary:
Seconds executed: 1484
 No errors detected
 
After a clean boot, the Windows Update Agent unfortunately keeps cycling without reporting any available update.

Capture_WU2.PNG​
 
How long have you let this run before cancelling out? Is it possible that you can leave it check overnight to see if anything shows up?
 
You were right.

Killing first Windows Update service which took 97% of CPU ressources then letting KB947821 fix running overnight made the installation successful. Here is the CheckSUR log which I found this morning :

Code: 
=================================
Checking System Update Readiness.
Binary Version 6.1.7601.22471
Package Version 26.0
2016-02-03 22:31

Checking Windows Servicing Packages

Checking Package Manifests and Catalogs

Checking Package Watchlist

Checking Component Watchlist

Checking Packages

Checking Component Store

Summary:
Seconds executed: 12008
 No errors detected
 
Great. After a Clean boot can you run Windows Update again and let it go all day or overnight to see if any updates show up that need installed?
 
You have hit the nail on the head.

Available updates that needed to be installed showed up immediately.

Capture_WU_maj.PNG​

It took half the night :huh: for Windows Update Agent to download and install these poor 69MB.

Capture_WU_maj2.PNG​

After a reboot and the latest updates have gotten installed, Windows Update service does not load anymore the CPU at 100%. The computer works now as usual. Thank you for your help. I wished I would have been clever enough to let WU agent running overnight on my own earlier in the month ! I did not have expected that running during a few hours without visible result is a regular behaviour.

Capture_WU_maj3.PNG​

BTW, there is still an issue with Windows Update, which fails to update the WDDM driver available for my graphic card (error code 80070103). I never installed driver directly from NVIDIA, so I do not know what the conflict might be here.

Capture_WU_maj4.PNG​

However, this is likely better to open another thread to address that specific issue.
 
You must log in or register to reply here.

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top