Server 2012 R2 won't install latest rollup

C

collinsit

Member
Joined
Jun 4, 2020
Posts
13
Good morning everyone, I am having an issue with a Windows Server 2012 R2 server not installing the latest (May 2020) rollup. I was able to install all the other updates for this month but this one keeps failing.

The update downloads fine but during install I am getting an 80092004 error which is saying it is failing on component hashes. I know this was an issue with Windows 7/2008 R2 and needing updates to support SHA2 signed patches but that doesn't relate to Server 2012 R2. I have the latest Servicing Stack Update installed and the server scans for patches fine.

I have run sfc /scannow and it says there was no corruption found. I have run DSIM cleanup as well and had no effect. I ran the Windows Update troubleshooter and it said it fixed some registrations and registry entries but the update still won't install.

I am getting the lines below at the end of the CBS.LOG file when it errors out.

2020-06-04 08:16:04, Error CSI 00000015 (F) 80092004 [Warning,Facility=FACILITY_NTSSPI,Code=8196 (0x2004)] #1269949# from CCSDirectTransaction::PrepareForCommit(...)[gle=0x90092004]
2020-06-04 08:16:04, Error CSI 00000016 (F) 80092004 [Warning,Facility=FACILITY_NTSSPI,Code=8196 (0x2004)] #1269948# from CCSDirectTransaction::ExamineTransaction(...)[gle=0x90092004]
2020-06-04 08:16:04, Error CSI 00000017 (F) 80092004 [Warning,Facility=FACILITY_NTSSPI,Code=8196 (0x2004)] #1269947# from CCSDirectTransaction_IRtlTransaction::ExamineTransaction(...)[gle=0x90092004]
2020-06-04 08:16:04, Error CSI 00000018 (F) CRYPT_E_NOT_FOUND #1269685# from Windows::COM::CPendingTransaction::IStorePendingTransaction_Analyze(...)[gle=0x80092004]
2020-06-04 08:16:04, Error CSI 00000019 (F) CRYPT_E_NOT_FOUND #1269556# from Windows::ServicingAPI::CCSITransaction::ICSITransaction_Commit(Flags = 38 (0x00000026), pSink = NULL, disp = 0, coldpatching = FALSE)[gle=0x80092004]
2020-06-04 08:16:04, Error CSI 0000001a (F) CRYPT_E_NOT_FOUND #1269555# 3067430 us from Windows::ServicingAPI::CCSITransaction_ICSITransaction::Commit(flags = 0x00000026, pSink = NULL, disp = 0)
[gle=0x80092004]
2020-06-04 08:16:04, Error CBS Exec: Failed to commit CSI transaction to resolve execution chain. [HRESULT = 0x80092004 - CRYPT_E_NOT_FOUND]

Any help or suggestions with things to check here would be really appreciated.

Thanks

Neal
 
Thank you for the response.

Attached is the CBS.log file. I a not sure what the upload limit is here so I didn't upload the whole folder. If you need it I can try to though. I just ran the update again and it failed but you should have the details towards the end of the log. I had to zip it as it was about 18MB unzipped.

If you do need additional files, let me know and i'll upload them.

Thanks for looking at this.

Neal
 

Attachments

FRST Registry Search
1. Click your Start button and type in cmd.
2.After you find the Command Prompt, right click on it and select Run as Administrator.
3. Copy and paste the following into the Command Prompt:

reg load HKLM\COMPONENTS C:\WINDOWS\SYSTEM32\CONFIG\COMPONENTS

4. 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.
5. Run FRST64 by Right-Clicking on the file and choosing Run as administrator.
6. Copy and paste KB4499151 into the Search box and click the Search Registry button.
7. When the scan is complete a notepad window will open with the results. Please attach this to your next reply. It is saved on your desktop named SearchReg.txt.
 
Thank you for the quick response.

Attached is the SearchReg.txt file.

Let me know if you need anything else.

Thanks

Neal
 

Attachments

Thanks.

Step#1 - 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.
6. Reboot when able and retry updates.
 

Attachments

Thank you again for the repy. Attached is the fixlog.txt file.

I am going to reboot the server now and will retry the updates. Will update shortly with the results.

Neal
 

Attachments

You are so awesome, that fix worked perfectly. I am not sure how you found the issue so quickly and were able to provide the fix but I just repatched the server and it went perfectly. I had been going through the logs for a while now and couldn't easily identify the issue so thank you so very very much for your help.

Neal
 
You must log in or register to reply here.

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

Back
Top