Windows 8.1 corrupted update files

1670883912761.png
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate
SusClientIdValidation REG_BINARY 060228021C0820002000200020002000570044002D005700580037003100450041003300450057005400560031000600FF08D8104B06448A5B433D954200530053002D0030003100320033003400350036003700380039004E006F006E006500
SusClientId REG_SZ 0cdf2221-071b-4f5d-a26d-e29e82241f62
ResetClient REG_DWORD 0x1
LastTaskOperationHandle REG_DWORD 0x29
ExtendedModel REG_DWORD 0x3c
ExtendedFamily REG_DWORD 0x6
ProcessorSignature REG_DWORD 0x306c3
VendorName REG_SZ GenuineIntel

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update
IsOOBEInProgress REG_DWORD 0x0
ElevateNonAdmins REG_DWORD 0x1
AUOptions REG_DWORD 0x4
IncludeRecommendedUpdates REG_DWORD 0x1
NonFirmwareUpdatesAvailableForInstall REG_DWORD 0x0
ForcedReboot REG_DWORD 0x2
NextDetectionTime REG_SZ 2022-12-12 22:18:42
CachedAUOptions REG_DWORD 0x4
InstallInProgress REG_DWORD 0x0
UpdatesAvailableForDownloadLogon REG_DWORD 0x0
UpdatesAvailableForInstallLogon REG_DWORD 0x0
UpdatesAvailableWithUiOrEulaLogon REG_DWORD 0x0
UpdatesAvailableWithUiLogon REG_DWORD 0x0
FirmwareUpdatesNotDownloaded REG_DWORD 0x0
FirmwareUpdatesNotInstalled REG_DWORD 0x0
OfflineDetectionPending REG_DWORD 0x1

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update\Power
Firmware-Final REG_DWORD 0x1e
OfferInstallAtShutdown-Final REG_DWORD 0x28
ContinueInstallAtShutdown-Final REG_DWORD 0xa
FirmwareForcedInstall-Final REG_DWORD 0x23

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update\RequestedAppCategories

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update\RequestedAppCategories\117cab2d-82b1-4b5a-a08c-4d62dbee7782
de8f75c4-b44e-9839-08d5-a151294c5611 REG_SZ 2022-12-11 21:56:31

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update\RequestedAppCategories\438955f5-20a7-45f2-8723-2d2642e89541

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update\RequestedAppCategories\7971f918-a847-4430-9279-4a52d1efe18d

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update\RequestedAppCategories\8ab51212-6757-44e0-ab73-5b9ccc932c00

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update\RequestedAppCategories\9482f4b4-e343-43b6-b170-9a65bc822c77

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update\RequestedAppCategories\e80f4a56-d432-422d-95e7-123054686553

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update\UAS
UpdateCount REG_DWORD 0x0

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update\Volatile
PostRebootResultsProcessed REG_DWORD 0x1

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\OSUpgrade
Refresh REG_DWORD 0x1

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\OSUpgrade\State
OSUpgradeState REG_DWORD 0x9
OSUpgradeStateTimeStamp REG_SZ 2016-04-17 04:17:55

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Reporting
SamplingValue2 REG_DWORD 0x147
BatchFlushAge REG_DWORD 0x1162

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Reporting\EventCache.v2

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Reporting\EventCache.v2\Legacy

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Reporting\RebootWatch

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Services
DefaultService REG_SZ 7971f918-a847-4430-9279-4a52d1efe18d

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Services\117cab2d-82b1-4b5a-a08c-4d62dbee7782
RegisteredWithAU REG_DWORD 0x1

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Services\7971f918-a847-4430-9279-4a52d1efe18d
RegisteredWithAU REG_DWORD 0x1

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Services\855e8a7c-ecb4-4ca3-b045-1dfa50104289
RegisteredWithAU REG_DWORD 0x1

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Services\Pending
ValidatedPreWsus3RegistrationRequests REG_DWORD 0x1

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Services\Pending\855e8a7c-ecb4-4ca3-b045-1dfa50104289
ClientApplicationID REG_SZ Service Recovery

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Setup
SelfUpdateStatus REG_DWORD 0x0
SelfupdateUnmanaged REG_DWORD 0x0

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\SLS
ClientHash REG_DWORD 0x29
ClientHash2 REG_DWORD 0x350

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\SLS\{117CAB2D-82B1-4B5A-A08C-4D62DBEE7782}
ResponseHash REG_BINARY 194C3E3CF561BA36EEFFDDB0748CB1A9870C9F57B63DCDFB556EDE29E00C3921
ResponseMarker REG_QWORD 0x1d50f5374980117

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\SLS\{7971F918-A847-4430-9279-4A52D1EFE18D}
ResponseHash REG_BINARY 758DE8F59FC336A43D112AF8ABC66FB52B89F3B70088A2A36E1EB0535B829972
ResponseMarker REG_QWORD 0x1d50f57c2c10f85

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\SLS\{855E8A7C-ECB4-4CA3-B045-1DFA50104289}
ResponseHash REG_BINARY 659B80CE9FF252F9187670A74D85EC8FAE1AAA85607A50608C83DAB8C060FF40
ResponseMarker REG_QWORD 0x1d51016d06441f0

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\SLS\{9482F4B4-E343-43B6-B170-9A65BC822C77}
ResponseHash REG_BINARY 1A4857FCE58B721334EE814AA39C70D6ED55C5D8969B77EFF901FEAA5A4B82C1
ResponseMarker REG_QWORD 0x1d50f57c1f99b7a
 
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.
  1. Download the attachment fixlist.txt and save it to your desktop.
  2. Right-click on FRST64.exe and select "Run as administrator".
  3. Press the Fix button.
  4. The tool will now process fixlist.txt.
  5. 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.
  6. When finished, a log called Fixlog.txt will appear in the same directory the tool is run from.
  7. Attach the logfile Fixlog.txt to your next reply.

Step 2:
Check Windows Update again.
Does it report any available updates ?
 

Attachments

10 gives the same error as above. RegEdit lacks the folder. Same problems with updater, although the troubleshooter just says it fixes one item now, rather than two.
 
It still lacks the Windows Update folder mentioned in my earlier post. The one that held the folder that held the entry for refusing Windows 10
 
It still lacks the Windows Update folder mentioned in my earlier post
I don't think that folder is required but you can create it to check. If you need help with that just ask.
Report the result.
 
Ah, thanks. Yeah. I have no idea how to make that or associate it with all the 'goodies' that would normally be in that folder. I really don't know if it matters either, just a guess as to why the 10 updater is acting weird.
 
One installed successfully (the tool), one was supposedly already there, and one failed.
also this:
1670977323708.png
 
Restart the machine.
Try to install KB5021294 only and report the result.
If it fails attach the zipped cbs.log to your next reply.
 
Good new is that the computer installed that KB on its own. Furthermore, Windows defender actually started on its own. Troubleshooter still claimed if found something wrong for Windows update that it corrected. Shrug. Not sure if the machine is 'ok' now? Still blocked from 10 upgrade.
 
Warning: This script was written specifically for this user, for use on that particular machine. Do not run this script on another machine.
  1. Download the attachment fixlist.txt and save it to your desktop.
  2. Right-click on FRST64.exe and select "Run as administrator".
  3. Press the Fix button.
  4. The tool will now process fixlist.txt.
  5. 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.
  6. When finished, a log called Fixlog.txt will appear in the same directory the tool is run from.
  7. Attach the logfile Fixlog.txt to your next reply.
 

Attachments

Um, kind of mixed. So, we do have the windows update folder now, but it didn't autopopulate with the sort of nonsense I might expect to be in there (in regedit). Defender had trouble kicking in on startup, but it works. The system still assures me that it can't update to Windows 10.

So, it's still kind of broken? But it some ways I do believe it's better than when we started. Hmm. I'll leave it on overnight. Maybe it will decide it needs another update. Running restorehealth just to see what that does
 
So, we do have the windows update folder now, but it didn't autopopulate with the sort of nonsense I might expect to be in there (in regedit)
I think it should be empty.

Running restorehealth just to see what that does
Okay.
 
Step 1:
Attach the cbs.log as zipped file to your next reply.

Step 2:
  1. Right-click to run the tool FRST64.exe as administrator.
  2. Note: Ensure that the Addition.txt check box is checked at the bottom of the form within the Optional Scan area.
  3. Press the Scan button.
  4. Please wait for the tool to finish. It will produce two logfiles called FRST.txt and Addition.txt in the same directory the tool is run from (which should be the desktop)
  5. Post the logfiles FRST.txt and Addition.txt as attachment in your next reply.
 

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

Back
Top