[SOLVED] Error 0x8007371b when installing Windows Update KB5022282 and KB5019275

[robrazil]

Hi everyone.
Well... since 01/10/23 I have been trying to install the KB5022282 update through windows update, and it has been giving error 0x8007371b.
Same thing, since 01/19/23 the KB5019275 update, with the same errors 0x8007371b.
On 01/23/23, updates KB4023057 and KB5022546 were installed by windows update without errors.
My PC is a DELL 3030 All In On.
Processor: Intel(R) Core(TM) i3-4150 CPU @ 3.50GHz 3.50GHz
Installed RAM: 16.0 GB
System type: 64-bit operating system, x64-based processor
Edition: Windows 10 Home Single Language
Version: 22H2
OS Build: 19045.2311
Experience: Windows Feature Experience Pack 120.2212.4190.0

What I've already tried, reading other help articles:
1- Command Sfc /scannow;
2- DISM command together with Scanhealth, with CheckHealth, with Restorehealth and with startComponentCleanup;
3- Subinacl commands to restore the default permissions HKEY_LOCAL_MACHINE, HKEY_CURRENT_USER, HKEY_CLASSES_ROOT and %SystemDrive%;
4- I uninstalled the antivirus and disabled the Firewall;
5- I tried the previous items in safe mode;
6- I ran chkdsk;
7- I deleted the files in the folder C:\Windows\SoftwareDistribution\Download;
8- I ran the Additional Troubleshooting for "windows update";
9- I tried to install the 02 KB manually through CMD as an administrator, using the command DISM.exe /Online /Add-Package /PackagePath:C:\...(path to the .cab file) but it didn't work.
10- I also used the programs "Windows Repair - Tweaking.com" and "Free Windows Registry Repair" to correct the permissions of the registry keys HKEY_LOCAL_MACHINE, HKEY_CURRENT_USER, HKEY_CLASSES_ROOT and HKEY_USERS, but nothing solved.
11- I ran PANDA antivirus and Malwarebytes and no virus was found.
12- Login in Windows with other Administrator account to run windows update.
For 02 days I've been analyzing the solved topic [Win7SP1 x64] Can't install Security monthly Quality Rollup KB4034664 - 80073712 comparing the posted files with mine, because the error message is the same from message #12 but I couldn't understand how the expert user zcomputerwiz concluded that the error was in "the version number for the winner in the SideBySide registry is incorrect".
I also read the topic [SOLVED] - [Win7SP1 x64] KB4025341 causes error 0x8007371b but I didn't find something that help me.
Sorry... but I really tried to solve this myself but I couldn't.

Below is the error message in CMD after trying to manually install KB 5019275 with the DISM command:


Below is the error message in CMD after trying to manually install KB 5022282 with the DISM command:


I have attached the ComponentsScanner.txt file but not the CBS folder, because as there are 02 KB with the same problem, I will wait for support to decide which KB will get support first.
Microsoft support advised to do the "inplace upgrade" procedure but I believe it is not necessary.
So I appreciate any help.

P.S: Sorry for my English but Google translator is helping me.

 

[robrazil]

Hi.
Well... in this time I used the defrag and chkdsk commands to fix possible errors on the SSD, but nothing was found to be fixed. Then I used the commands again:
Dism /online /cleanup-image /startcomponentcleanup /resetbase
Dism /Online /Cleanup-Image /ScanHealth
No problems were found.
I also used the sfc /scannow command.
Finally, I deleted all the contents of the C:\Windows\SoftwareDistribution\Download\ folder and ran windows update to install KB5022282 to download and install it again, but I got the error 0x8007371b again.
Below are the files normally requested for verification.
Thank you for any help.

 

[robrazil]

Well... as I didn't get any support, I looked for information on how to solve the problem and did it myself.
I'm going to leave the entire procedure described below to serve as a help to everyone who has the same error codes in windows update for windows 10, remembering that each case is different and that this report only serves to try to give a direction in identifying your problem .
First I needed to know what error codes 0x8007371b and 0x80070005 mean, and Found out by querying the Page Common Windows Update Errors - Windows Client | Microsoft Learn.
The error 0x80070005 "E_ACCESSDENIED; General access error denied" is basically lack of permission to files or registry keys. I found out by chance, following one of the common procedures of attempting to fix, that I could not delete the files from folder C:\Windows\SoftwareDistribution\Download because one of them was in "use" by Panda Cloud Antivirus Service.
I solved the 0x80070005 by disabling the "Panda Cloud Antivirus Service" service, but when running windows update again the problem 0x8007371b appeared. First on the installation of KB5022282 and then on KB5019275.
I also want to anticipate that when troubleshooting 0x8007371b for the installation of KB5022282 also solved for the installation of KB5019275.
I started searching the net about the error code 0x8007371b:
"ERROR_SXS_TRANSACTION_CLOSURE_INCOMPLETE; One or more required members of the transaction are not present.
Desrition: Component Store Corruption."
In this search, I found the page [SOLVED] - [Win7SP1 x64] KB4025341 causes error 0x8007371b | Sysnative Forums and on this site I started looking for other posts that had the same error message "STATUS_SXS_TRANSACTION_CLOSURE_INCOMPLETE" to try to apply the same procedures.
Because it is about analyzing LOG files, I opened this topic asking for help but no answer. So, I looked for information on how to solve it myself.
I knew that in the analysis of log files I needed:
1º) Identify what the error was;
2º) Where it was occurring;
3º) How to proceed to correct it.
I found the tutorial How to fix Windows Update errors using DISM (DISM.log) or the System Update Readiness Tool / SURT (CheckSUR.log) | Sysnative Forums which, although it was intended for windows 7, brought many explanations of how to identify the problem (obviously I used the Google translator... hehehe).
So let's go to the procedure I did to solve my error problem 0x8007371b for installing KB5022282 and KB5019275 by windows update:
1- I installed KB5022282 by windows update and obviously gave the error 0x8007371b, but I did it just to log the errors in the CBS.log file, in the Folder C:\Windows\Logs\CBS, so i could analyze it;
2- I copied the CBS.log from folder C:\Windows\Logs\CBS and pasted it to the desktop;
3- I opened the CBS.log the desktop file with the Notepad++ program;
4- In the tutorial cited earlier says that a "(F)" in the lines of the LOG file indicates where the failure occurred and what failure it was. So I did a search for "(F)" in "the entire current document", and as a result a listing appeared at the bottom of the page, as can be seen below:



5- In the listing that appeared at the bottom of the page, I rotated the scroll bar to the end of the listing and clicked 02 (twice) times over the 1st line that contained the text "STATUS_SXS_TRANSACTION_CLOSURE_INCOMPLETE" (red arrow), because it is the text of the 0x8007371b error, and at the top the respective line was pointed (red arrow);
6- I searched Googe for the text "STATUS_SXS_TRANSACTION_CLOSURE_INCOMPLETE" and the first search result was Windows: Windows Update error STATUS_SXS_TRANSACTION_CLOSURE_INCOMPLETE page, and it was where I found that the contents of the 1 (six) top lines following the text "STATUS_SXS_TRANSACTION_CLOSURE_INCOMPLETE", quoted in item 05, is that interested me:
2023-02-06 16:33:54, Info CBS FLOW: Enter Installation Stage: Closure Analysis, Current Operation Stage: Installing
2023-02-06 16:34:06, Info CSI 00000405 Changelist shadowed missing its manifest - microsoft-windows-client-features-deployment010, version 10.0.19041.1865, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}
2023-02-06 16:34:06, Info CSI 00000406 Changelist shadowed missing its manifest - microsoft-windows-client-features-deployment03160, version 10.0.19041.2075, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}
2023-02-06 16:34:06, Info CSI 00000407 Changelist shadowed missing its manifest - Microsoft-Windows-Application-Experience-Mitigations-C3, version 10.0.19041.2075, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}
2023-02-06 16:34:06, Error CSI 00000408@2023/2/6:19:34:06.332 (F) Attempting to mark store corrupt with category [l:15 ml:16]'CorruptManifest'[gle=0x80004005]
2023-02-06 16:34:06, Error CSI 00000409@2023/2/6:19:34:06.332 (F) onecore\base\wcp\componentstore\csd_winners.cpp(1329): Error STATUS_SXS_TRANSACTION_CLOSURE_INCOMPLETE originated in function OriginateManifestsMissingError expression: (null)
[gle=0x80004005]
7- Based on the information obtained from the page quoted in item 6 and the 2nd line, which begins with "CSI 00000405", I opened the windows powershell, running it as administrator, typed dir C:\Windows\WinSxS\Manifests\*-deployment010* and pressed the ENTER key. In the result that appeared, I selected the amd64_microsoft-windows-c..tures-deployment010_31bf3856ad364e35 by copying it and pasting it into a notepad to use it posteiormente;




8- Based on the information obtained from the page cited in item 6 and using the text amd64_microsoft-windows-c..tures-deployment010_31bf3856ad364e35, in the same notepad I created the text HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_microsoft-windows-c..tures-deployment010_31bf3856ad364e35 to be used below;
9- I opened the Windows Registry Editor, pasted the text quoted in item 8 in the address bar, after Computer\ getting like this:



Then, I was erasing the line, back to front, digit by digit, until other key options appear, as shown below...



... being the first key I was interested in.
After selecting it, I clicked on folder 10.0 on the left side of the page, just below the respective key (red arrow) and some information appeared on the right side. Note that on the line where the text is (Default) contains the WRONG number of windows version (10.0.19041.2311), needing to be changed to the CORRECT windows version number, which is the blue key number just below it (10.0.19041.2486):



To change the version number of windows, just click 02 (two) times on the text (Default) and a small window will open. Then, you just replace the number 10.0.19041.2311 to 10.0.19041.2486 and click on the OK button.



10- I did the same correction procedure, from item 7, for the 3rd and 4th line mentioned in item 6, those that start with CSI 00000406 and CSI 00000407I, respectively, being as follows:
- From the 3rd line CSI 00000406 Changelist shadowed missing its manifest - microsoft-windows-client-features-deployment03160, version 10.0.19041.2075, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35} :
* The search text to be inserted into the "poweshell": dir C:\Windows\WinSxS\Manifests\*-deployment03160*



* The address to be placed in the Windows Registry Editor address bar:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_microsoft-windows-c..res-deployment03160_31bf3856ad364e35
* The key to be corrected:



In this case, the CORRECT version number in the (Default) key of the 10.0 folder was 10.0.19041.2546.
- Da 4ª linha CSI CSI 00000407 Changelist shadowed missing its manifest - Microsoft-Windows-Application-Experience-Mitigations-C3, version 10.0.19041.2075, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}:
* The search text to be inserted into the "poweshell": dir C:\Windows\WinSxS\Manifests\*-Mitigations-C3*



* The address to be placed in the Windows Registry Editor address bar:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_microsoft-windows-a..ence-mitigations-c3_31bf3856ad364e35
* The key to be corrected:



In this case, the CORRECT version number in the (Default) key of the 10.0 folder was 10.0.19041.2193.

I made these 03 fixes, i didn't even have to restart windows, just repeat windows update to kb5022282 and installed without problems. Then windows prompts restart, but then just install the KB5019275 by windows update too and restart again and... VOILÀ!!

I hope to have contributed in some way, but remember that the above procedures were to fix my specific problem, so that each CBSfile.log brings the peculiar information of each windows system installed as of each windows update error.

Sorry for my english. I used the Google Translator to help me.