[SOLVED] Problem to install the KB5032189 for Windows 10 Version 22H2

[robrazil]

Hi everyone.
I wasted a day trying fix the problem myself reading others post that has a part of error message but I can't got the solution.
There are many error messaes like "Store corruption detected in function CCSDirectTransaction::ShouldKeepAliveFromInstallmap expression: (null)" on CBS.log file followed by [gle=0x80004005].
I ran several commands like scannow amd DISM but not solved.
So, I appreciate any help.

 

[robrazil]

I GOT IT !!
Researching more about the code About the code [gle=0x80004005] I saw that it was about the registration signature. So, I disabled "Driver Signature Enforcement" on the windows, in Computer Settings->Update and Security->Recovery->in the Advanced Restart option I clicked the Restart Now button.
When rebooting into advanced mode, I clicked Troubleshooting->Advanced Options->Startup Settings and then clicked in “Restart” button to enter the “Startup Settings” screen.
On the screen, I chose the option "Disable driver signature enforcement".
After restarting the PC with the drive signature disabled, I manually installed KB5032189 using the command below:
Dism /online /Add-Package /PackagePath:C:\Windows\SoftwareDistribution\Download\2646d05b7b9df7abbff707698f6ce8bc\Windows10.0-KB5032189-x64.cab
In this time the KB was almost installed but it still gave the error log below:

2023-12-07 15:50:39, Info CBS FLOW: Enter Installation Stage: Closure Analysis, Current Operation Stage: Installing
2023-12-07 15:51:07, Info CSI 000003d3 Changelist shadowed missing its manifest - Microsoft-Windows-TabletPC-MathInputControl, version 10.0.19041.1865, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}
2023-12-07 15:51:08, Error CSI 000003d4@2023/12/7:18:51:08.357 (F) Attempting to mark store corruption with category [l:15 ml:16]'CorruptManifest'[gle= 0x80004005]
2023-12-07 15:51:08, Error CSI 000003d5@2023/12/7:18:51:08.357 (F) onecore\base\wcp\componentstore\csd_winners.cpp(1329): Error STATUS_SXS_TRANSACTION_CLOSURE_INCOMPLETE originated in function OriginateManifestsMissing Error expression: (null)
[gle=0x80004005]
2023-12-07 15:51:08, Info CBS Added C:\WINDOWS\Logs\CBS\CBS.log to WER report.
2023-12-07 15:51:08, Info CBS Added C:\WINDOWS\Logs\CBS\CbsPersist_20231207183832.log to WER report.
2023-12-07 15:51:08, Info CBS Added C:\WINDOWS\Logs\CBS\CbsPersist_20231207180901.log to WER report.
2023-12-07 15:51:08, Info CBS Added C:\WINDOWS\Logs\CBS\CbsPersist_20231207165623.log to WER report.
2023-12-07 15:51:08, Info CBS Added C:\WINDOWS\Logs\CBS\CbsPersist_20231207011440.cab to WER report.
2023-12-07 15:51:08, Info CBS Added C:\WINDOWS\Logs\CBS\CbsPersist_20231207004025.cab to WER report.
2023-12-07 15:51:08, Info CBS Not able to add pending.xml to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2023-12-07 15:51:08, Info CBS Not able to add pending.xml.bad to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2023-12-07 15:51:08, Info CBS Not able to add poqexec.log to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]

When I read the text "STATUS_SXS_TRANSACTION_CLOSURE_INCOMPLETE" I remembered my last post about this same text in the error log message. There, I found the "Windows Update error STATUS_SXS_TRANSACTION_CLOSURE_INCOMPLETE" page that had this subject and gave me the direction to solve the problem.
Based on the article of the page mentioned above, I opened the windows powershell running it as administrator, typed dir dir C:\Windows\WinSxS\Manifests\*MathInputControl*, pressed the ENTER key and the result was the appear below:


So, in notepad I created the text HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SideBySide\Winners\amd64_microsoft-windows-t..pc-mathinputcontrol_31bf3856ad364e35_, opened REGEDIT, pasted the text in the address bar, after Computer\ getting like this:


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.1865), needing to be changed to the CORRECT windows version number, which is the blue key number just below it (10.0.19041.2193):


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.1865 to 10.0.19041.2193 and click on the OK button:


Finally, in Powershell I ran the command again to manually install KB5032189 and... VOILÀ!!

The update was carried out successfully!!

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.