windows update problem with installing KB5032198 (OS build 20348.2113)

Hello Andrzej Dulian.

I also had a problem with KB5032198, but my error was 0x80070005. After a lot of research I managed to solve this way.

Access the C:\Windows\INF\ folder and get the file "usbstor.inf", I right-clicked and went to properties and then security, put administrators as owner and restarted the computer, then went to the file again and put it to inherit the permissions. I ran Windows Update again and it updated correctly.

Enabling net framework did not help. I also checked the partitions according to the instructions here, and they are probably ok. I found something like this in the logs, see below. Does this mean anything to anyone?

C:\Windows\Logs\CBS

[gle=0x80004005]

2023-11-26 23:12:16, Info CSI 000002f8 Seems Playback delta generation failed for file: ServerDatacenter-VT-IA-1-ul-rtm.xrm-ms of the component: Microsoft-Windows-Security-SPP-Component-SKU-ServerDatacenter-License, version 10.0.20348.1194, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}, Hence using reverse delta from package.

2023-11-26 23:12:16, Error CSI 000002f9@2023/11/26:22:12:16.027 (F) onecore\base\wcp\sil\ntsystem.cpp(2823): Error STATUS_DELETE_PENDING originated in function Windows::Rtl::SystemImplementation::DirectFileSystemProvider::SysCreateFile expression: (null)

[gle=0x80004005]

2023-11-26 23:12:16, Error CSI 000002fa (F) STATUS_DELETE_PENDING #14133602# from Windows::Rtl::SystemImplementation::DirectFileSystemProvider::SysCreateFile(flags = (AllowSharingViolation), handle = {provider=NULL, handle=0, name= ("null")}, da = (DELETE|SYNCHRONIZE|FILE_READ_ATTRIBUTES|FILE_WRITE_ATTRIBUTES), oa = @0xfa3f07c418->OBJECT_ATTRIBUTES {s:48; rd:NULL; on:[129]'\SystemRoot\WinSxS\Temp\InFlight\6d44289cb520da01bc900000d42b4c1d\0666389cb520da01b8910000d42b4c1d_serverdatacent..ore-rtm.xrm-ms'; a:(OBJ_CASE_INSENSITIVE)}, iosb = [gle=0xd0000056]

2023-11-26 23:12:16, Error CSI @0xfa3f07c498, as = (null), fa = (FILE_ATTRIBUTE_NORMAL), sa = (FILE_SHARE_READ|FILE_SHARE_WRITE|FILE_SHARE_DELETE), cd = FILE_OPEN, co = (FILE_NON_DIRECTORY_FILE|FILE_SYNCHRONOUS_IO_NONALERT|0x00004000), eab = NULL, eal = 0, disp = Invalid)

[gle=0xd0000056]

2023-11-26 23:12:16, Error CSI 000002fb (F) STATUS_DELETE_PENDING #14133598# from Windows::Rtl::SystemImplementation::CDirectory::Internal_DeleteRecursively(...)[gle=0xd0000056]

2023-11-26 23:12:16, Error CSI 000002fc (F) 800f0982 [Error,Facility=(000f),Code=2434 (0x0982)] #14079398# from Windows::COM::CComponentStore::InternalTransact(...)[gle=0x800f0982]

2023-11-26 23:12:16, Error CSI 000002fd (F) 800f0982 [Error,Facility=(000f),Code=2434 (0x0982)] #14079199# from Windows::ServicingAPI::CCSITransaction::ICSITransaction2_AddFiles(Flags = 49, a = @0x2f97bdbf4a0, fn = @0x2f97bdbfca0, fp = @0x2f97bdc04a0, disp = 0, op = 0)[gle=0x800f0982]

2023-11-26 23:12:16, Info CBS Failed to add to transaction package: Package_4_for_KB5014864~31bf3856ad364e35~amd64~~10.0.4535.4 [HRESULT = 0x800f0982 - PSFX_E_MATCHING_COMPONENT_NOT_FOUND]

2023-11-26 23:12:16, Error CBS Failed to stage execution package: Package_4_for_KB5014864~31bf3856ad364e35~amd64~~10.0.4535.4 [HRESULT = 0x800f0982 - PSFX_E_MATCHING_COMPONENT_NOT_FOUND]

2023-11-26 23:12:16, Info CBS CommitPackagesState: Started persisting state of packages

2023-11-26 23:12:16, Info CBS CommitPackagesState: Completed persisting state of packages

2023-11-26 23:12:16, Info CSI 000002fe@2023/11/26:22:12:16.110 CSI Transaction @0x2f9789a7ba0 destroyed

2023-11-26 23:12:16, Info CBS Perf: Stage chain complete.

2023-11-26 23:12:16, Info CBS Failed to stage execution chain. [HRESULT = 0x800f0982 - PSFX_E_MATCHING_COMPONENT_NOT_FOUND]

2023-11-26 23:12:16, Error CBS Failed to process single phase execution. [HRESULT = 0x800f0982 - PSFX_E_MATCHING_COMPONENT_NOT_FOUND]

2023-11-26 23:12:16, Info CBS WER: Generating failure report for package: Package_for_RollupFix~31bf3856ad364e35~amd64~~20348.2113.1.22, status: 0x800f0982, failure source: Stage, start state: Resolved, target state: Installed, client id: UpdateAgentLCU

2023-11-26 23:12:16, Info CBS Not able to query DisableWerReporting flag. Assuming not set... [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]

2023-11-26 23:12:16, Info CBS Added C:\Windows\Logs\CBS\CBS.log to WER report.

Thank you very much for your quick reply. Unfortunately, like Alfredo Chinszyla, I did all the above-mentioned activities and nothing. I am very disappointed with the Windows server recently put into production. Several MSSQL databases, MYSQL, AD and other components are already in production. I can't imagine installing everything again now. These are huge costs and problems for the company itself. Does anyone know what else can be done to get this type of error on a new machine?

I ran all Dism commands as well as sfc and all showing nothing is corrupt but the updates keep failing. I even even downloaded the standalone but it still fails to install

Hello,

Error code 0x800f0982 (Fix Windows Update errors via DISM or System Update Readiness tool - Windows Server | Microsoft Learn) usually indicates that can't identify matching component for hydration. The issue you are experiencing may be due to some system files that are corrupted or missing. Here are some possible solutions:

1.Run the DISM tool: Try running the DISM tool to fix any system file corruption. You can do this by following the steps below:

a. Open the Command Prompt (administrator privileges).

b. Enter the following command and press Enter to run:

      DISM /Online /Cleanup-Image /RestoreHealth 

c. Wait for the command to complete and then restart your computer.

2. Run the SFC tool: If the DISM tool does not resolve the issue, try running the SFC tool. You can do this by following these steps:

a. Open the Command Prompt (administrator privileges).

b. Enter the following command and press Enter to run:

      sfc /scannow 

c. Wait for the command to complete and then restart your computer.

3. Disable antivirus software: Sometimes, antivirus software may block the installation of Windows updates. Try disabling your antivirus software and then re-running the update.

4.If the above solutions don't solve the problem, please try to install this KB manually. You can download it in Microsoft Update Catalog.

Hope it helps.

Best regards,

Lei