• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 768
  • Last Modified:

Cryptographic Services not there

Long story short, i'm trying to fix error code 0x80240020 concerning Windows Update on a Windows 2000 Professional SP4 installation.

Updates are found and are downloaded, but all of them immediately fail as soon as Windows Update tries to install them. I've spent quite a lot of time on this and basically I've found that I'm missing some winlogon\notify keys in the registry.

I won't be able to test this theory until tomorrow when I can get my hands back on the computer. However, I noticed that the Cryptographic Services service is not even there in services.msc. Should it be there in a windows 2000 installation?

Also, updates manually installed are no problem and fully install. The above question is really what I'm concerned about right now. How can I get it installed if it needs to be/should be there?
3 Solutions
Not as far as I am aware it shouldn't. I have also looked on some Win 2k Installations we have here and I can see it present on them. If I am not mistaken it is from XP that it is present.

I am assuming that you have seen this article but I will post it here anyway


Windowsupdates sometimes don't work if you don't have the client for microsoft networks installed for your nic.
Win 2000 doesn't show the cryptographic service in the Services control panel, but it still exists.
I myself am trying to find out how to start and stop and debug it in w2k.

I have had simular windows update problems, and got a little further by exporting Certificates from another computer and importing them into the problem pc.

still not perfect though..
tvaccAuthor Commented:
I figured it out, but still gave some points. Basically (for anyone else who has this problem), go to the KB Article (I had been over that many times before) and look were it instructs you to add/verify the SansLogn registry keys in Notify.

I had added the correct ones, but it still didn't work for me. I had no Notify at all, but I DID have a Notify_Disabled. I, of course after backing up the registry, renamed Notify_Disabled to Notify and whatda know...it works.

Also, yes, you need client for microsoft networks installed for some reason, but this wasn't my problem.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Cloud Class® Course: CompTIA Cloud+

The CompTIA Cloud+ Basic training course will teach you about cloud concepts and models, data storage, networking, and network infrastructure.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now