"Failure configuring Windows updates reverting" loop +disk space error

jamesldavis · 30 Oct 2017

I’ve been caught in a “Failure configuring Windows updates reverting” update loop. The last time it reverted I rebooted again and it rebooted OK. I then ran the Win 7 disk cleanup and when that was done I had 20 gigs free on C drive. I then rebooted again and it did another “Failure configuring Windows updates reverting.” When booted I checked and my C drive had gone from 20 gigs free to 10 gigs free.

Following forum instructions, I ran the System Update Readiness Tool, and it finished OK.

I had run it a few days ago, but I again ran then sfc /scannow and got:

“Resource Protection did not find any integrity violations”

Win update showed 69 optional updates available. I picked the first one to test updates and it installed OK and it rebooted without reverting.

Since system still showed 10 gigs only free, I ran the Win 7 built in cleanup and removed all but most recent restore point. But the system said that Error reporting was taking up 45.9 Gb of space. But when cleaned it shows that only 10 gigs of space was being freed.

Next, I rebooted, and even though I’d not done any updates it did the “Failure configuring Windows updates reverting” again and now my c drive shows only 7 gigs free.

The control panel Win Update screen shows no errors and no “updates not installed” message.

screen shot attached, cbs.zip would not upload. Too large? It says 145 mb but dropbox upload was very slow. Here is link to cbs: https://www.dropbox.com/s/yb6tx1kc96giwhb/CBS.zip?dl=0

Note that checking c drive for errors inside Windows shows no errors.

Now, after last revert, the System queued Windows Error Reporting shows up as 71 GB

Just ran System Maintenance and it deleted the collection of errors which so C drive went back to 18 gb.
However it showed "Disk volume errors" but no details given and did not fix it.

NOTE: After all the above I just tried another test update and it installed without reverting.

Now there is the "Disk volume errors" issue as checkdisk did not fix it.

Ran checkdisk/fix on C at boot. Results seem to show no problems:

Log Name: Application
Source: Microsoft-Windows-Wininit
Date: 10/30/2017 11:42:14 AM
Event ID: 1001
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: mystic1-PC
Description:

Checking file system on C:
The type of the file system is NTFS.
Volume label is NewSSD7.

A disk check has been scheduled.
Windows will now check the disk.

CHKDSK is verifying files (stage 1 of 3)...
419840 file records processed.
File verification completed.
2777 large file records processed.
0 bad file records processed.
0 EA records processed.
45 reparse records processed.
CHKDSK is verifying indexes (stage 2 of 3)...
520986 index entries processed.
Index verification completed.
0 unindexed files scanned.
0 unindexed files recovered.
CHKDSK is verifying security descriptors (stage 3 of 3)...
419840 file SDs/SIDs processed.
Cleaning up 70 unused index entries from index $SII of file 0x9.
Cleaning up 70 unused index entries from index $SDH of file 0x9.
Cleaning up 70 unused security descriptors.
Security descriptor verification completed.
50574 data files processed.
CHKDSK is verifying Usn Journal...
34218160 USN bytes processed.
Usn Journal verification completed.
Windows has checked the file system and found no problems.

117210204 KB total disk space.
97212424 KB in 319948 files.
197856 KB in 50575 indexes.
0 KB in bad sectors.
525044 KB in use by the system.
65536 KB occupied by the log file.
19274880 KB available on disk.

4096 bytes in each allocation unit.
29302551 total allocation units on disk.
4818720 allocation units available on disk.

Internal Info:
00 68 06 00 66 a7 05 00 f6 48 0a 00 00 00 00 00 .h..f....H......
7f 73 00 00 2d 00 00 00 00 00 00 00 00 00 00 00 .s..-...........
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................

Windows has finished checking your disk.
Please wait while your computer restarts.

Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Wininit" Guid="{206f6dea-d3c5-4d10-bc72-989f03c8b84b}" EventSourceName="Wininit" />
<EventID Qualifiers="16384">1001</EventID>
<Version>0</Version>
<Level>4</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2017-10-30T18:42:14.000000000Z" />
<EventRecordID>61280</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>Application</Channel>
<Computer>mystic1-PC</Computer>
<Security />
</System>
<EventData>
<Data>

Checking file system on C:
The type of the file system is NTFS.
Volume label is NewSSD7.

A disk check has been scheduled.
Windows will now check the disk.

CHKDSK is verifying files (stage 1 of 3)...
419840 file records processed.
File verification completed.
2777 large file records processed.
0 bad file records processed.
0 EA records processed.
45 reparse records processed.
CHKDSK is verifying indexes (stage 2 of 3)...
520986 index entries processed.
Index verification completed.
0 unindexed files scanned.
0 unindexed files recovered.
CHKDSK is verifying security descriptors (stage 3 of 3)...
419840 file SDs/SIDs processed.
Cleaning up 70 unused index entries from index $SII of file 0x9.
Cleaning up 70 unused index entries from index $SDH of file 0x9.
Cleaning up 70 unused security descriptors.
Security descriptor verification completed.
50574 data files processed.
CHKDSK is verifying Usn Journal...
34218160 USN bytes processed.
Usn Journal verification completed.
Windows has checked the file system and found no problems.

117210204 KB total disk space.
97212424 KB in 319948 files.
197856 KB in 50575 indexes.
0 KB in bad sectors.
525044 KB in use by the system.
65536 KB occupied by the log file.
19274880 KB available on disk.

4096 bytes in each allocation unit.
29302551 total allocation units on disk.
4818720 allocation units available on disk.

Internal Info:
00 68 06 00 66 a7 05 00 f6 48 0a 00 00 00 00 00 .h..f....H......
7f 73 00 00 2d 00 00 00 00 00 00 00 00 00 00 00 .s..-...........
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................

Windows has finished checking your disk.
Please wait while your computer restarts.
</Data>
</EventData>
</Event>

torchwood · 30 Oct 2017

Hi James,

Ive never seen such a huge SURT report
Summary:
Seconds executed: 200
Found 28412 errors
Fixed 197 errors
CSI Unexpected Failure Total count: 6
CSI Missing Deployment Key Total count: 595
CSI Payload File Missing Total count: 5
Fixed: CSI Payload File Missing. Total count: 5
CSI F Mark Bad Type Total count: 179
Fixed: CSI F Mark Bad Type. Total count: 179
CSI F Mark Missing Total count: 5
Fixed: CSI F Mark Missing. Total count: 5
CBS Watchlist Package Missing Total count: 15300
CBS Watchlist Component Missing Total count: 12308
CSI Missing Winning Component Key Total count: 14
Fixed: CSI Missing Winning Component Key. Total count: 8

Im not surpised at those log file sizes seeing whats wrong, i was actually really sceptical about the sizes

Hundreds of updates are misconfiguered or corrupted.
Bearing in mind there are over 28000 errors
To be honest your better of clean installing.

BEFORE YOU DO anything, CREATE an image of your personal data, most here use Macrium free
because of this Disk volume errors -- sounds like your SSD is failing
then update its firmware and use the manufacturers tool to check its health status
Its also likely that this is whats corrupting the updates

Do you have a set of discs to reinstall with.

Roy

jamesldavis · 30 Oct 2017

torchwood said:

Hi James,

Ive never seen such a huge SURT report
Summary: 28000 errors
To be honest your better of clean installing.

BEFORE YOU DO anything, CREATE an image of your personal data, most here use Macrium free
because of this Disk volume errors -- sounds like your SSD is failing
then update its firmware and use the manufacturers tool to check its health status
Its also likely that this is whats corrupting the updates

Do you have a set of discs to reinstall with.

Roy

Thanks.

Yes, I use Macrium and have my C drive backed up and am making backups daily until my new hard drive arrives. I have a ton of programs installed and it would take a week to reinstall and configure everything from scratch. Would it be OK to install a new Win 7 on a new C drive while retaining programs: https://www.pcworld.com/article/2431...tallation.html

Or is it worth taking a week of my life to reinstall and configure everything on my system? What do you think?

Also, was it the hard drive going bad that created the windows update mess?

James

torchwood · 30 Oct 2017

Hi James,

You can go the repair install route, full tutorial here
Repair Install - Windows 7 Help Forums

certainly wont take a week
Usefull if you have a lot of your own programs/customizations on the system

The choice is yours, IF everything else is running smoothly go the repair route
(note run Belarc Advisor it will pick-up all programs/passwords and product keys)

I do believe that the disc problems caused your update corruption.

Roy

jamesldavis · 30 Oct 2017

We must be having telepathy. I just downloaded and ran Belarc Advisor a half-hour before I saw your answer. :)

thanks again

jamesldavis · 04 Nov 2017

So I got another SSD hard drive and did an in-place reinstall of Windows. Everything seemed to go OK. I updated the new Windows with no problem. Then I ran Win 7's "Perform System Maintenance" and the result was "Disk volume errors" detected. So I ran checkdisk at DO level to detect and fix problems and none were found. What's going on? Is my new SSD drive also bad or is it something else?

I ran the SanDisk SSD Dashboard and it said there were no problems. ??

torchwood · 05 Nov 2017

Hi James,

did you use the r switch? (chkdsk /r).

And is the firmware upto date??

Roy

jamesldavis · 05 Nov 2017

Thanks much for your replies.

SSD drive firmware is upto date.

I did not use the "Scan for and attempt recovery of bad sectors" option when scheduling the scan in Windows because I had read that: "..using the "/r" option is completely unnecessary because your SSD's firmware should already taking care of this issue with wear leveling. "

No??

I ran the sfc /scannow again just now and got:

"Windows Resource Protection found corrupt files and successfully repaired them. Details are included in the CBS.Log" File attached.

I rebooted and ran maintenance again and still shows the "disk volume" error message.

11/6

In my ongoing effort to solve Disk Volume Errors, I ran the Windows DeviceDiagnostic.diagcab and it found no errors.

I then tried to run DeviceCenterDiagnostic.diagcab and it gave me error 0x80070002. Rebooted and tried again. Same result.

Tried the fix methods here: How to fix Windows update error code 0x80070003 or 0x80070002 under Windows 8, 7 or vista - wintips.org - Windows Tips How-tos Rebooted. Error still present.

jamesldavis · 06 Nov 2017

I just had the following conversation with Sandisk tech support:

Daniel B.: The error seems to be related to WMI registration and can be ignored as this is not related to the SSD or any hardware

James Davis: What is WMI registration?

Daniel B.: It is related to Windows operating system

James Davis: And the error you are speaking of is the Disk volume errors?

Daniel B.: It is related to the operating system and not the hard drive. However, it does not have affect the usage or application

Daniel B.: Or any Hardware

James Davis: So is there a bug in Win 7 that is generating a Disk volume error message when in fact there is none?

Daniel B.: We cannot confirm the exact issue as the issue is not related to the SSD

James Davis: So it is a Windows issue as it tries to function in relation to the SSD?

Daniel B.: The issue is not related to the SSD

James Davis: That suggest to me that it is a bug in Windows 7 since its is telling me there is an error on my ssd drive and you are saying there is no hardware error.

Daniel B.: You can try updating the windows and see if that resolves the issue or try a installing it again using Different window DVD (Original OS DVD)

James Davis: Is there another SSD utility you can recommend that checks drives and confirms that there is a problem or not.

James Davis: Windows is fully up to date.

Daniel B.: SSD dashboard is the one that check the drive status

James Davis: I installed from the Windows 7 download using usb.
Daniel B.: However, I see that you are not getting the proper screen while running the SSD Dashboard application. If possible you can try connecting the SSD to any other computer as secondary drive and then download and run the SSD dashboard to test the SSD.

James Davis: Original install was from a cd and I had same probloem.

James Davis: As I said, I when I first ran your utility a few days ago it did given other information including saying it fond no problems with the drive.

Daniel B.: Alright, I will escalate your case to the level 3 engineers and so we can investigate the issue further and see if there is anything that can be done on SSD part to help you with the resolution

Daniel B.: Please provide us your contact number which is required for escalation

James Davis: OK, thanks very much.

jamesldavis · 09 Nov 2017

About SSD drives and the "Disk volume errors" generated by Windows, apparently for some of us there is as yet no solution.

For the benefit of any who may come this way, I will append this final note.
Windows has what purports to be a fix, but for some of us, it simply does not work:

https://answers.microsoft.com/en-us/...d-7e3094d126e0

That leaves hardware, and after a long exchange with Level 3 Sandisk tech support, I was told that the the disk was OK and that the error message was not their fault.

Maybe it is an unacknowledged bug in Windows or something they do not have a fix for. Users are left in the dark.