Windows 7 update fails
- Thread starter slinger
- Start date
Step 1:
Warning: This script was written specifically for this user, for use on that particular machine. Do not run this script on another machine.
Step 2:
Check Windows Update again and report the result.
Warning: This script was written specifically for this user, for use on that particular machine. Do not run this script on another machine.
- Download the attachment fixlist.txt and save it to your desktop.
- Right-click on FRST64.exe and select "Run as administrator".
- Press the Fix button.
- The tool will now process fixlist.txt.
- If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run.
- When finished, a log called Fixlog.txt will appear in the same directory the tool is run from.
- Post the logfile Fixlog.txt as attachment in your next reply.
Step 2:
Check Windows Update again and report the result.
Thanks!
Windows update still fails, CBS log attached
EDIT, including fixlog:
Fix result of Farbar Recovery Scan Tool (x64) Version: 15-05.2019
Ran by Administrator (15-05-2019 08:01:02) Run:2
Running from
Loaded Profiles:
Boot Mode: Normal
==============================================
fixlist content:
*****************
CMD: REG LOAD HKLM\COMPONENTS C:\Windows\System32\config\COMPONENTS
StartRegedit:
[HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\6.1.7601.24383 (win7sp1_ldr_escrow.190215-1954)\ComponentFamilies\msil_srpuxsnapin_31bf3856ad364e35_none_ea031670d74b9de7\v!6.1.7601.17514]
EndRegedit:
*****************
========= REG LOAD HKLM\COMPONENTS C:\Windows\System32\config\COMPONENTS =========
The operation completed successfully.
========= End of CMD: =========
====> Registry
==== End of Fixlog 08:01:05 ====
Windows update still fails, CBS log attached
EDIT, including fixlog:
Fix result of Farbar Recovery Scan Tool (x64) Version: 15-05.2019
Ran by Administrator (15-05-2019 08:01:02) Run:2
Running from
Loaded Profiles:
Boot Mode: Normal
==============================================
fixlist content:
*****************
CMD: REG LOAD HKLM\COMPONENTS C:\Windows\System32\config\COMPONENTS
StartRegedit:
[HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\VersionedIndex\6.1.7601.24383 (win7sp1_ldr_escrow.190215-1954)\ComponentFamilies\msil_srpuxsnapin_31bf3856ad364e35_none_ea031670d74b9de7\v!6.1.7601.17514]
EndRegedit:
*****************
========= REG LOAD HKLM\COMPONENTS C:\Windows\System32\config\COMPONENTS =========
The operation completed successfully.
========= End of CMD: =========
====> Registry
==== End of Fixlog 08:01:05 ====
Step 1:
Warning: This script was written specifically for this user, for use on that particular machine. Do not run this script on another machine.
Step 2:
Check Windows Update again and report the result.
Warning: This script was written specifically for this user, for use on that particular machine. Do not run this script on another machine.
- Download the attachment fixlist.txt and save it to your desktop.
- Right-click on FRST64.exe and select "Run as administrator".
- Press the Fix button.
- The tool will now process fixlist.txt.
- If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run.
- When finished, a log called Fixlog.txt will appear in the same directory the tool is run from.
- Post the logfile Fixlog.txt as attachment in your next reply.
Step 2:
Check Windows Update again and report the result.
That key was unable to be deleted. Fixlog listed below. Also attached cbs.log
Fix result of Farbar Recovery Scan Tool (x64) Version: 15-05.2019 01
Ran by Administrator (15-05-2019 20:39:00) Run:3
Running from C:\Users\wmeyer\Downloads
Loaded Profiles: wmeyer & Administrator (Available Profiles: Christine & jvheitz & svitale & wmeyer & Administrator)
Boot Mode: Normal
==============================================
fixlist content:
*****************
CMD: REG LOAD HKLM\COMPONENTS C:\Windows\System32\config\COMPONENTS
DeleteKey: HKLM\COMPONENTS\DerivedData\VersionedIndex\6.1.7601.24383 (win7sp1_ldr_escrow.190215-1954)\ComponentFamilies\msil_srpuxsnapin_31bf3856ad364e35_none_ea031670d74b9de7
StartRegedit:
[HKLM\COMPONENTS\DerivedData\VersionedIndex\6.1.7601.24383 (win7sp1_ldr_escrow.190215-1954)\ComponentFamilies\msil_srpuxsnapin_31bf3856ad364e35_none_ea031670d74b9de7\v!6.1.7601.17514]
EndRegedit:
*****************
========= REG LOAD HKLM\COMPONENTS C:\Windows\System32\config\COMPONENTS =========
The operation completed successfully.
========= End of CMD: =========
HKLM\COMPONENTS\DerivedData\VersionedIndex\6.1.7601.24383 (win7sp1_ldr_escrow.190215-1954)\ComponentFamilies\msil_srpuxsnapin_31bf3856ad364e35_none_ea031670d74b9de7 => could not remove, key could be protected
====> Registry
Fix result of Farbar Recovery Scan Tool (x64) Version: 15-05.2019 01
Ran by Administrator (15-05-2019 20:39:00) Run:3
Running from C:\Users\wmeyer\Downloads
Loaded Profiles: wmeyer & Administrator (Available Profiles: Christine & jvheitz & svitale & wmeyer & Administrator)
Boot Mode: Normal
==============================================
fixlist content:
*****************
CMD: REG LOAD HKLM\COMPONENTS C:\Windows\System32\config\COMPONENTS
DeleteKey: HKLM\COMPONENTS\DerivedData\VersionedIndex\6.1.7601.24383 (win7sp1_ldr_escrow.190215-1954)\ComponentFamilies\msil_srpuxsnapin_31bf3856ad364e35_none_ea031670d74b9de7
StartRegedit:
[HKLM\COMPONENTS\DerivedData\VersionedIndex\6.1.7601.24383 (win7sp1_ldr_escrow.190215-1954)\ComponentFamilies\msil_srpuxsnapin_31bf3856ad364e35_none_ea031670d74b9de7\v!6.1.7601.17514]
EndRegedit:
*****************
========= REG LOAD HKLM\COMPONENTS C:\Windows\System32\config\COMPONENTS =========
The operation completed successfully.
========= End of CMD: =========
HKLM\COMPONENTS\DerivedData\VersionedIndex\6.1.7601.24383 (win7sp1_ldr_escrow.190215-1954)\ComponentFamilies\msil_srpuxsnapin_31bf3856ad364e35_none_ea031670d74b9de7 => could not remove, key could be protected
====> Registry
ChkDsk Scan
- Click on Start - All programs - Accessories.
- Rightclick on Command-prompt and select Run as administrator.
- When command prompt opens, typ chkdsk into it, then press enter.
- Wait for this to complete.
- Download ListChkdskResult.exe by SleepyDude and save it on your desktop.
- Rightclick
ListChkdskResult.exe and select Run as administrator. Notepad will open the file ListChkdskResult.txt on completion. (The file ListChkdskResult.txt can be found on your desktop.)
- Copy and paste this in your next reply.
ListChkdskResult by SleepyDude v0.1.7 Beta | 21-09-2013
------< Log generate on 5/16/2019 6:36:53 AM >------
Category: 0
Computer Name:
Event Code: 26212
Record Number: 209167
Source Name: Chkdsk
Time Written: 05-16-2019 @ 10:29:13
Event Type: Information
User:
Message: Chkdsk was executed in read-only mode on a volume snapshot.
Checking file system on C:
The type of the file system is NTFS.
Volume label is OS.
WARNING! F parameter not specified.
Running CHKDSK in read-only mode.
CHKDSK is verifying files (stage 1 of 3)...
Cleaning up instance tags for file 0x2c13.
294656 file records processed.
File verification completed.
7066 large file records processed.
0 bad file records processed.
2 EA records processed.
111 reparse records processed.
CHKDSK is verifying indexes (stage 2 of 3)...
385828 index entries processed.
Index verification completed.
0 unindexed files scanned.
0 unindexed files recovered.
CHKDSK is verifying security descriptors (stage 3 of 3)...
294656 file SDs/SIDs processed.
Cleaning up 55 unused index entries from index $SII of file 0x9.
Cleaning up 55 unused index entries from index $SDH of file 0x9.
Cleaning up 55 unused security descriptors.
Security descriptor verification completed.
45587 data files processed.
CHKDSK is verifying Usn Journal...
41753568 USN bytes processed.
Usn Journal verification completed.
Windows has checked the file system and found no problems.
476042239 KB total disk space.
160282072 KB in 239055 files.
178716 KB in 45588 indexes.
0 KB in bad sectors.
419615 KB in use by the system.
65536 KB occupied by the log file.
315161836 KB available on disk.
4096 bytes in each allocation unit.
119010559 total allocation units on disk.
78790459 allocation units available on disk.
-----------------------------------------------------------------------
------< Log generate on 5/16/2019 6:36:53 AM >------
Category: 0
Computer Name:
Event Code: 26212
Record Number: 209167
Source Name: Chkdsk
Time Written: 05-16-2019 @ 10:29:13
Event Type: Information
User:
Message: Chkdsk was executed in read-only mode on a volume snapshot.
Checking file system on C:
The type of the file system is NTFS.
Volume label is OS.
WARNING! F parameter not specified.
Running CHKDSK in read-only mode.
CHKDSK is verifying files (stage 1 of 3)...
Cleaning up instance tags for file 0x2c13.
294656 file records processed.
File verification completed.
7066 large file records processed.
0 bad file records processed.
2 EA records processed.
111 reparse records processed.
CHKDSK is verifying indexes (stage 2 of 3)...
385828 index entries processed.
Index verification completed.
0 unindexed files scanned.
0 unindexed files recovered.
CHKDSK is verifying security descriptors (stage 3 of 3)...
294656 file SDs/SIDs processed.
Cleaning up 55 unused index entries from index $SII of file 0x9.
Cleaning up 55 unused index entries from index $SDH of file 0x9.
Cleaning up 55 unused security descriptors.
Security descriptor verification completed.
45587 data files processed.
CHKDSK is verifying Usn Journal...
41753568 USN bytes processed.
Usn Journal verification completed.
Windows has checked the file system and found no problems.
476042239 KB total disk space.
160282072 KB in 239055 files.
178716 KB in 45588 indexes.
0 KB in bad sectors.
419615 KB in use by the system.
65536 KB occupied by the log file.
315161836 KB available on disk.
4096 bytes in each allocation unit.
119010559 total allocation units on disk.
78790459 allocation units available on disk.
-----------------------------------------------------------------------
Did you install/uninstall any Windows Update after you posted message #21 ?
No updates installed/uninstalled. I keep windows update turned off/disabled and only run it after performing one of the troubleshooting steps. It failed each time, was unable to retrieve updates. After the failure, I stop/disable it and then post logs results in this thread.
Replace the components hive once again.
Replace Components Hive
Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.
Try sfc /scannow and Windows Update again and report the result.
Replace Components Hive
Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.
- Download COMPONENTS.ZIP and save it to your desktop.
- Right-click on it and select Extract all.... Make sure the "Show extracted files when complete" is checked and click Extract.
- Now we have the COMPONENTS file that we will be using to replace your current one.
- Navigate to C:\Windows\System32\config
- Right-click on the current COMPONENTS file and select rename. Rename it to COMPONENTS.bad.
Note: If you get an error that the file is in use, reboot your computer and then try again. - Take the file from the Components folder on your desktop and paste it into C:\Windows\System32\config
Try sfc /scannow and Windows Update again and report the result.
3 other corruptions have been fixed. Replace the components hive once again.
Replace Components Hive
Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.
Try sfc /scannow and Windows Update again and report the result.
Replace Components Hive
Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.
- Download COMPONENTS.ZIP and save it to your desktop.
- Right-click on it and select Extract all.... Make sure the "Show extracted files when complete" is checked and click Extract.
- Now we have the COMPONENTS file that we will be using to replace your current one.
- Navigate to C:\Windows\System32\config
- Right-click on the current COMPONENTS file and select rename. Rename it to COMPONENTS.bad.
Note: If you get an error that the file is in use, reboot your computer and then try again. - Take the file from the Components folder on your desktop and paste it into C:\Windows\System32\config
Try sfc /scannow and Windows Update again and report the result.
OK, here is my latest COMPONENTS hive:
COMPONENTS.zip
COMPONENTS.zip
Replace Components Hive
Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.
Try sfc /scannow and Windows Update again and report the result.
Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.
- Download COMPONENTS.ZIP and save it to your desktop.
- Right-click on it and select Extract all.... Make sure the "Show extracted files when complete" is checked and click Extract.
- Now we have the COMPONENTS file that we will be using to replace your current one.
- Navigate to C:\Windows\System32\config
- Right-click on the current COMPONENTS file and select rename. Rename it to COMPONENTS.bad.
Note: If you get an error that the file is in use, reboot your computer and then try again. - Take the file from the Components folder on your desktop and paste it into C:\Windows\System32\config
Try sfc /scannow and Windows Update again and report the result.
Test RAM With Memtest86+
Please ensure you allow 8 passes of the program!
Download Memtest86+ here: Memtest86+ - Advanced Memory Diagnostic Tool
Which should I download?
You can either download the pre-compiled .ISO that you would burn to a CD and then boot from the CD, or you can download the auto-installer for the USB key. What this will do is format your USB drive, make it a bootable device, and then install the necessary files. Both do the same job, it's just up to you which you choose, or which you have available (whether it's CD or USB).
Do note that some older generation motherboards do not support USB-based booting, therefore your only option is CD (or Floppy if you really wanted to).
How Memtest works (you don't need to read, it's only for those interested in the specifics):
Memtest uses algorithms (specifically two), namely moving inversion & what is deemed Modulo-X. Essentially, the first algorithm fills the memory with a pattern. Starting at the low address, it checks to see if the pattern was changed (it should not have been), writes the patterns complement, increments the address, and repeats. Starting at the highest address (as opposed to the lowest), it follows the same checklist.
The reason for the second algorithm is due to a few limitations, with the first being that not all adjacent cells are being tested for interaction due to modern chips being 4 to 16 bits wide regarding data storage. With that said, patterns are used to go ahead and ensure that all adjacent cells have at least been written with all possible one and zero combinations.
The second is that caching, buffering and out of order execution will interfere with the moving inversions algorithm. However, the second algorithm used is not affected by this. For starting offsets of 0-20, the algorithm will write every 20th location with a pattern, write all other locations with the patterns complement, repeat the previous one (or more) times, and then check every 20th location for the previously mentioned pattern.
Now that you know how Memtest actually works, it's important to know that the tests it goes through all mean something different. It goes from Test 0 through Test 12, many of which use either one or the other algorithm discussed above, among many other things.
Any other questions, they can most likely be answered by reading this great guide here:
FAQ : please read before posting
If needed, a tutorial on using this is here.
Please ensure you allow 8 passes of the program!
Download Memtest86+ here: Memtest86+ - Advanced Memory Diagnostic Tool
Which should I download?
You can either download the pre-compiled .ISO that you would burn to a CD and then boot from the CD, or you can download the auto-installer for the USB key. What this will do is format your USB drive, make it a bootable device, and then install the necessary files. Both do the same job, it's just up to you which you choose, or which you have available (whether it's CD or USB).
Do note that some older generation motherboards do not support USB-based booting, therefore your only option is CD (or Floppy if you really wanted to).
How Memtest works (you don't need to read, it's only for those interested in the specifics):
Memtest uses algorithms (specifically two), namely moving inversion & what is deemed Modulo-X. Essentially, the first algorithm fills the memory with a pattern. Starting at the low address, it checks to see if the pattern was changed (it should not have been), writes the patterns complement, increments the address, and repeats. Starting at the highest address (as opposed to the lowest), it follows the same checklist.
The reason for the second algorithm is due to a few limitations, with the first being that not all adjacent cells are being tested for interaction due to modern chips being 4 to 16 bits wide regarding data storage. With that said, patterns are used to go ahead and ensure that all adjacent cells have at least been written with all possible one and zero combinations.
The second is that caching, buffering and out of order execution will interfere with the moving inversions algorithm. However, the second algorithm used is not affected by this. For starting offsets of 0-20, the algorithm will write every 20th location with a pattern, write all other locations with the patterns complement, repeat the previous one (or more) times, and then check every 20th location for the previously mentioned pattern.
Now that you know how Memtest actually works, it's important to know that the tests it goes through all mean something different. It goes from Test 0 through Test 12, many of which use either one or the other algorithm discussed above, among many other things.
Any other questions, they can most likely be answered by reading this great guide here:
FAQ : please read before posting
If needed, a tutorial on using this is here.
Has Sysnative Forums helped you? Please consider donating to help us support the site!