The "esentutl /g secedit.sdb" command is reporting Operation terminated with error -583 (JET_errSect

Hi.

In application events I'm getting messages like these:

Log Name:Application,

Source:Microsoft-Windows-CAPI2,

Event ID:257,

Level:Error,

Keywords:Classic,

User:N/A,

Description: The Cryptographic Services service failed to initialize the Catalog Database. The ESENT error was: -583.

Log Name:Application,

Source:SceCli,

Event ID:1005,

Level:Error,

Keywords:Classic,

User:N/A,

Description: Some JET database is corrupt. Run esentutl /g to check the integrity of the security database %%windir%%securityDatabasesecedit.sdb. If it is corrupt,

attempt a soft recovery first by running esentutl /r in the %%windir%%security directory. If soft recovery fails, attempt a repair with esentutl /p on %%windir%%securityDatabasesecedit.sdb. Then delete the log files in %%windir%%security. Ошибка при открытии

баз данных безопасности, таких, как %windir%securitydatabasesecedit.sdb.

But when I was tried to run commands:

esentutl /g %windir%securityDatabasesecedit.sdb

esentutl /r %windir%security

esentutl /p %windir%securityDatabasesecedit.sdb

All of them are reporting the

"Operation terminated with error -583 (JET_errSectorSizeNotSupported, The physical sector size reported by the disk subsystem, is unsupported by ESE for a specific file type.)"

error.

Question is - how to fix it?

It looks esentutl tool cannot do anything in this case because always report the same error (-583). :-(

View the thread