none
Event ID 257 CAPi2. The Cryptographic Services services failed to initialize the Catalog Database. The ESENT error was -1805 RRS feed

  • Question

  • Getting an error in the application log every time we restart Cryptographic Services:

    Event ID 257 CAPi2. The Cryptographic Services services failed to initialize the Catalog Database. The ESENT error was -1805

    I've tried following:

    1. Stopped Cyptographic service.

    2. Make a backup of c:\windows\system32\catroot2\

    3. Delete contents of c:\windows\system32\catroot2\

    4. restart Cyptographic service

    5. Error appears in application log.

    6. C:\windows\System32\catroot2\{F750E6C3-38EE-11D1-85E5-00C04FC295EE} is empty. the catdb does not get recreated.

    7. System recovery does not fix the issue.

    Consequently:

    8. Windows patches fail to install.

    9. Running any .msc, i.e. service.msc fails with a Red UAC pop-up: This app has been blocked for your protection. Publisher unknown. 

    Any insight on how to fix this would be helpful.

    Have multiple machines broken.

    All are running Windows 10 Pro 1803.

    Thursday, September 19, 2019 5:18 PM

All replies

  • Hi,

    I don’t know the specific causes,but here I provide you with four methods:

    Method 1:

    Rename your catroot2 folder->Go to the Device Manger->Select the IDE ATA/ATAPI controllers->Click on propertiers ->Update Driver->Restart your machine

    Method 2:

    Go to the Device Manger->Select the IDE ATA/ATAPI controllers->Click on propertiers ->Uninstall Device and select the option to remove the files for the driver-> Restart your machine and  on next boot Windows automatically installed the correct default Microsoft controller driver

    Method 3:

    Services > Cryptographic services > Properties >Logon (identity)

    Method 4:

     Give the identity account (usually 'network service') full permission on the C: drive.

    And here is a link that related to your condition:

    https://social.technet.microsoft.com/Forums/windows/en-US/c16cd26c-e2c4-4d7e-9032-39c7b11dab1d/cryptographic-services-fail-to-initialize-the-catalogue-database?forum=w7itprogeneral

    Hope these can help you!Good luck!


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.


    Monday, September 23, 2019 9:00 AM
  • gocomoto, I am also having the same exact issue that happened suddenly and 8 machines are affected. I have been working with Microsoft support and they have not been able to figure out anything past what is already on the internet. I have tried all the steps suggested by Microsoft and on every forum. I refuse to believe the only way to fix these machines is wipe them out and reinstall everything from scratch. Something happened to these machines and based on your post, it happened around the same time to my machines also.
    Wednesday, September 25, 2019 2:19 PM
  • Hi,

    Was your issue resolved?

    If you resolved it using our solution, please "mark it as answer" to help other community members find the helpful reply quickly.

    Best regards,

    Charlotte Tang

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Thursday, September 26, 2019 5:55 AM
  • I'm having same issue as well windows 10 1703, build 15063. Was anyone able to fix this?
    Friday, October 18, 2019 1:04 PM
  • Same problem here.  Anybody had any success?

    Sam

    Tuesday, November 5, 2019 1:10 AM
  • that does not work.
    Tuesday, December 17, 2019 12:34 AM
  • We have the exact same issue at our company. We have 20,000 machines, and 300 of our machines are affected with the exact same symptoms. It happens across different computers models and on different Windows 10 versions... 1709 / 1803 / 1909.

    The only thing we can commonly see is that PCs that have old SSD's from 2016/2015 and older, seem to be more likely to get corrupted.

    We also have a ticket open with MS and they have spent 2 months on this issue and cant so far find a fix. They recommended so far the same fixes we have all applied our selves to no avail.

    If we format and re-image the same PC that was affected with the error... That same error can come back a few weeks later. We think it might be a hardware issue causing this. So far we are advising our IT Techs to replace the SSD with a new one.... and then re-image the same machine. Since we have been adopting replacing the disk, the issue has not re-occurred on that same machine.

    I and my team have spent near on 6 months trying to find the 100% cause.. and potential software fix for this error. But we are at a loss. We think its related to the SSD and its "Garbage Collection/TRIM" schedule that can cause the corruption. Buts its all hunches with out any proof. :(
    Wednesday, April 29, 2020 9:56 AM
  • We appear to have a fix for this. Working with Microsoft they found that in our case we had too many empty GUID looking folders in the CATROOT and CATROOT2 folders. The simple fix in the end, for us, was just to delete those folders and immediately elevated programs would load with out the RED UAC prompt. And straight away Patching would work again for us. No reboot was required.

    The only two folders in CATROOT and CATROOT2 should be these:

    {127D0A1D-4EF2-11D1-8608-00C04FC295EE}
    {F750E6C3-38EE-11D1-85E5-00C04FC295EE}

    We had these Extra folders which was causing the issue:

    {00AAC56B-CD44-11D0-8CC2-00C04FC295EE}
    {573E31F8-AABA-11D0-8CCB-00C04FC295EE}
    {573E31F8-DDBA-11D0-8CCB-00C04FC295EE}
    {5555C2CD-17FB-11D1-85C4-00C04FC295EE}
    {FC451C16-AC75-11D1-B4B8-00C04FB66EA0}

    And this simple batch file fixed it for us:

    ::Start of batch::

    :: Only these two Folder should be in the CatRoot and CatRoot2 folders:

    :: {127D0A1D-4EF2-11D1-8608-00C04FC295EE}
    :: {F750E6C3-38EE-11D1-85E5-00C04FC295EE}

    :: Delete Unknown CatRoot Folders

    RD /S /Q C:\Windows\System32\CatRoot\{00AAC56B-CD44-11D0-8CC2-00C04FC295EE}
    RD /S /Q C:\Windows\System32\CatRoot\{573E31F8-AABA-11D0-8CCB-00C04FC295EE}
    RD /S /Q C:\Windows\System32\CatRoot\{573E31F8-DDBA-11D0-8CCB-00C04FC295EE}
    RD /S /Q C:\Windows\System32\CatRoot\{5555C2CD-17FB-11D1-85C4-00C04FC295EE}
    RD /S /Q C:\Windows\System32\CatRoot\{FC451C16-AC75-11D1-B4B8-00C04FB66EA0}

    :: Delete Unknown CatRoot2 Folders

    RD /S /Q C:\Windows\System32\CatRoot2\{00AAC56B-CD44-11D0-8CC2-00C04FC295EE}
    RD /S /Q C:\Windows\System32\CatRoot2\{573E31F8-AABA-11D0-8CCB-00C04FC295EE}
    RD /S /Q C:\Windows\System32\CatRoot2\{573E31F8-DDBA-11D0-8CCB-00C04FC295EE}
    RD /S /Q C:\Windows\System32\CatRoot2\{5555C2CD-17FB-11D1-85C4-00C04FC295EE}
    RD /S /Q C:\Windows\System32\CatRoot2\{FC451C16-AC75-11D1-B4B8-00C04FB66EA0}

    ::End of Batch::

    We still do not know the root cause of this issue... soon as we find out what causes the corruption, I will update here.

    Hope this helps some out there that has the same issue as us.

    Kind regards

    Allan




    • Edited by Mr--Allan Friday, May 22, 2020 11:00 AM
    Friday, May 22, 2020 10:57 AM