Cryptographic services failure

Hello SevenForums,

I have a problem with the cryptographic services.
This service fails to start. (If I start it, it stops immediately). If I try to restart it, the the error "Cannot start the Cryptographic services-service on the local computer - Error 1067: The process terminated unexpectedly.

The eventviewer application tab is full of errors (every time Windows tries to start this service and fails).

One of the logs:

Faulting applcation name: svchost.exe_CryptSvc, version: 6.1.7600.16385, time stamp: 0x4a5bc3c1.
Faulting module name: ESENT.dll, version: 6.1.7601.17577, time stamp: 0x4d79bfba
Exception code: 0xc0000005
Fault offset: 0x0000000000006a38
Faulting process id: 0xcb0
Faulting application start time: 0x01cc64caffd5963b
Faulting application path: C:\Windows\system32\svchost.exe
Faulting module path: C:\Windows\system32\ESENT.dll
Report Id: 3d895ccf-d0be11e0-941a-00262dc388f1

Event-id number is 1000.
Can I solve this problem?

Please let me know.
Thanks.

No one with a solution??
So I have to reïnstall it from scratch?

Golden said:

Hi,

Can you try the following:

1. Click Start Orb
2. In the search box, type cmd
3. Right click on CMD in the list that appears, and then seclect 'Run as administrator'
4. In the cmd window that opens, type sfc /scannow and hit enter

Post the results here when it is done.

Regards,
Golden

Hello Golden,

Check performed.
The file CBS.log is attached (compressed in the zip file "CBS.zip").

Can you tell me which files are damaged?
I have performed the upgrade readiness tool, but only 1 file is repaired (CAT file)

Thanks!

Golden said:

Hi,

Were you prompted to reboot the PC after the scan was complete? If so, reboot the PC if you didn't. How many files were not repaired? Its probably easier to just take a screen capture of the cmd window when the scan is complete, instead of the text file.

Regards,
Golden

No reboot is requested.
So I have rebooted it by myself and I run the sfc /scannow command again.
The previous output redirected me to the log file which I have attached on the previous post. It told me only that "not all files could be repaired".

What is your advise? Run it 3 times?

I have performed the sfc 3 times, but still the same message:

-----------------------------------------------------------------------
Verification 100% completed.
Damaged files are found, but they cannot all repaired.
Details can be found in CBS.log windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log

-----------------------------------------------------------------------

How can I found out which damaged files cannot be repaired. As you have said, the CBS.log is very big.