[SOLVED] Windows 8.1 Update always fails with 80073701 (>1year)
- Thread starter someone
- Start date
- Status
24/05/2020 10:40:09 Event viewer shows: 0 of 2 instances of system store corruption have been repaired. Unrepaired corruptions may lead to failures in future system servicing.
then
24/05/2020 10:40:32 Package KB4556846 failed to be changed to the Installed state. Status: 0x80073701.
Looks like when the windows update is installing it detects corruption and runs DISM quietly which is why they always take so long.
2 instances of system store corruption is down from 6 earlier, so that is good I guess?
CBS logs after windows update failed to install with the usual error. Fixlog too.
cbs.24.05.2020.0.of.2.store.corruption.fixed.zip
then
24/05/2020 10:40:32 Package KB4556846 failed to be changed to the Installed state. Status: 0x80073701.
Looks like when the windows update is installing it detects corruption and runs DISM quietly which is why they always take so long.
2 instances of system store corruption is down from 6 earlier, so that is good I guess?
CBS logs after windows update failed to install with the usual error. Fixlog too.
cbs.24.05.2020.0.of.2.store.corruption.fixed.zip
- Nov 22, 2017
- 2,458
Hi
Please do the following.
Step#1 - Amend permissions to registry
1. Click your Start button and type regedit in the search box.
2. Right-click on regedit.exe that comes up in the search results and select Run as administrator. Answer Yes to the UAC prompt.
3. The registry editor will open which is a window divided vertically into two panes. Make sure you scroll all the way to the top of the screen and click any black downward pointing arrows so that they turn white and all the keys are collapsed.
4. Now click the arrow next to HKEY_LOCAL_MACHINE and it will expand all the subkeys beneath it.
5. Scroll down and find the subkey named SOFTWARE and expand that. Continue expanding the following ones Microsoft\Windows\CurrentVersion\Component Based Servicing\PackageDetect
6. Beneath Component Based Servicing you should see a key named PackageDetect
7. Right-click on the key named PackageDetect and select Permissions...
8. On the Permissions dialog click the Advanced button.
9. Beside the Owner click on Change.
10. In the Enter object name to select type Everyone and click check names
11. Click OK.
12. On the Permissions tab click Add.
13. Click the Select a Principal and type in Everyone and then click check names. Click OK.
14. Make sure the Everyone group is shown in the Permissions dialog and ensure that the checkbox for Full Control is checked. Click OK.
15. Click on Disable Inheritance.
16. Select Remove all inherited permissions from this object
17. Click OK
18. Exit the registry.
Step#2 - FRST Fix
NOTICE: This script was written specifically for this user, for use on that particular machine. Running this on another machine may cause damage to your operating system
1. Please download Farbar Recovery Scan Tool and save it to your Desktop.
Note: You need to run the 64-bit Version so please ensure you download that one.
2. Download the attached fixlist.txt and save it to the Desktop.
Note. It's important that both files, FRST64 and fixlist.txt are in the same location or the fix will not work (in this case...the desktop).
3. Run FRST64 by Right-Clicking on the file and choosing Run as administrator.
4. Press the Fix button just once and wait. 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.
5. When finished FRST64 will generate a log on the Desktop (Fixlog.txt). Please post the contents of it in your reply.
Please do the following.
Step#1 - Amend permissions to registry
1. Click your Start button and type regedit in the search box.
2. Right-click on regedit.exe that comes up in the search results and select Run as administrator. Answer Yes to the UAC prompt.
3. The registry editor will open which is a window divided vertically into two panes. Make sure you scroll all the way to the top of the screen and click any black downward pointing arrows so that they turn white and all the keys are collapsed.
4. Now click the arrow next to HKEY_LOCAL_MACHINE and it will expand all the subkeys beneath it.
5. Scroll down and find the subkey named SOFTWARE and expand that. Continue expanding the following ones Microsoft\Windows\CurrentVersion\Component Based Servicing\PackageDetect
6. Beneath Component Based Servicing you should see a key named PackageDetect
7. Right-click on the key named PackageDetect and select Permissions...
8. On the Permissions dialog click the Advanced button.
9. Beside the Owner click on Change.
10. In the Enter object name to select type Everyone and click check names
11. Click OK.
12. On the Permissions tab click Add.
13. Click the Select a Principal and type in Everyone and then click check names. Click OK.
14. Make sure the Everyone group is shown in the Permissions dialog and ensure that the checkbox for Full Control is checked. Click OK.
15. Click on Disable Inheritance.
16. Select Remove all inherited permissions from this object
17. Click OK
18. Exit the registry.
Step#2 - FRST Fix
NOTICE: This script was written specifically for this user, for use on that particular machine. Running this on another machine may cause damage to your operating system
1. Please download Farbar Recovery Scan Tool and save it to your Desktop.
Note: You need to run the 64-bit Version so please ensure you download that one.
2. Download the attached fixlist.txt and save it to the Desktop.
Note. It's important that both files, FRST64 and fixlist.txt are in the same location or the fix will not work (in this case...the desktop).
3. Run FRST64 by Right-Clicking on the file and choosing Run as administrator.
4. Press the Fix button just once and wait. 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.
5. When finished FRST64 will generate a log on the Desktop (Fixlog.txt). Please post the contents of it in your reply.
2020-05 Security Monthly Quality Rollup for Windows 8.1 for x64-based Systems (KB4556846)
Installation date: 25/05/2020 11:37
Installation status: Succeeded
Update type: Important
A security issue has been identified in a Microsoft software product that could affect your system. You can help protect your system by installing this update from Microsoft. For a complete listing of the issues that are included in this update, see the associated Microsoft Knowledge Base article. After you install this update, you may have to restart your system.
More information:
https://support.microsoft.com/help/4556846
Help and Support:
https://support.microsoft.com/help/4556846
Installation date: 25/05/2020 11:37
Installation status: Succeeded
Update type: Important
A security issue has been identified in a Microsoft software product that could affect your system. You can help protect your system by installing this update from Microsoft. For a complete listing of the issues that are included in this update, see the associated Microsoft Knowledge Base article. After you install this update, you may have to restart your system.
More information:
https://support.microsoft.com/help/4556846
Help and Support:
https://support.microsoft.com/help/4556846
bruce1270 you Sir are a legend!
I'll be making a donation as soon as I get a free moment!
Can you post a brief explanation of the root cuses and solutions to my issue.
It looks to me like fixing the Component Based Servicing registry permissions were key?
For completeness of this thread and to benefit those wandering the wasteland of the internet searching for answers, attached are the CBS logs dated today from this FINALLY successful update.
Interestingly after the final permissions change above I found an event viewer log that looks like a resolution to the "0 of 2"/"0 of 6 store corruption not fixed" issue.
25/05/2020 11:33:11 The access history in hive \??\C:\Windows\System32\SMI\Store\Machine\SCHEMA.DAT was cleared updating 0 keys and creating 0 modified pages.
25/05/2020 11:30:34 Installation Started: Windows has started installing the following update: 2020-05 Security Monthly Quality Rollup for Windows 8.1 for x64-based Systems (KB4556846)
I'll be making a donation as soon as I get a free moment!
Can you post a brief explanation of the root cuses and solutions to my issue.
It looks to me like fixing the Component Based Servicing registry permissions were key?
For completeness of this thread and to benefit those wandering the wasteland of the internet searching for answers, attached are the CBS logs dated today from this FINALLY successful update.
Interestingly after the final permissions change above I found an event viewer log that looks like a resolution to the "0 of 2"/"0 of 6 store corruption not fixed" issue.
25/05/2020 11:33:11 The access history in hive \??\C:\Windows\System32\SMI\Store\Machine\SCHEMA.DAT was cleared updating 0 keys and creating 0 modified pages.
25/05/2020 11:30:34 Installation Started: Windows has started installing the following update: 2020-05 Security Monthly Quality Rollup for Windows 8.1 for x64-based Systems (KB4556846)
- Nov 22, 2017
- 2,458
Hi there
Thank you for the kind words and I'm delighted the issue appears to be resolved.
There was some corruption in the CBS hive where it looks like packages belonging to previous updates had not installed correctly and had left orphaned data.
Once that was tracked down and removed it allowed the cumulative updates to go through again.
Unfortunately I have no idea of the root cause - it could be a number of things such as power outage, hardware issues or the update just didn't install correctly. It might be worth carrying out a test of your RAM (you could use memtest 86 - see here) and also a HDD check.
You also mentioned about the restore points failing. Might be worth checking the setting. You may have a 3rd party security application controlling your backups so windows restore points may be disabled to avoid conflict.
If everything now looks good, then I'll close the thread as solved.
Take care and stay safe.
Thank you for the kind words and I'm delighted the issue appears to be resolved.
There was some corruption in the CBS hive where it looks like packages belonging to previous updates had not installed correctly and had left orphaned data.
Once that was tracked down and removed it allowed the cumulative updates to go through again.
Unfortunately I have no idea of the root cause - it could be a number of things such as power outage, hardware issues or the update just didn't install correctly. It might be worth carrying out a test of your RAM (you could use memtest 86 - see here) and also a HDD check.
You also mentioned about the restore points failing. Might be worth checking the setting. You may have a 3rd party security application controlling your backups so windows restore points may be disabled to avoid conflict.
If everything now looks good, then I'll close the thread as solved.
Take care and stay safe.
- Status
Has Sysnative Forums helped you? Please consider donating to help us support the site!