April 2018 update broke Chrome browser (Cryptographic Services bug)

Anonymous
2018-08-13T22:50:55+00:00

I updated to the April 2018 version of Win10 a couple months ago. It caused several issues and broke my Chrome browser completely, so I reverted back to the old version. But Microsoft forced another update on me, so I need this issue fixed somehow.

All the googling I've done says Microsoft has "fixed" this issue with the April update breaking Chrome, but I've installed all patches and they clearly haven't, not in my case. Pages simply refuse to load and time out.

I've narrowed the issue down to the "Cryptographic Services" service. If I stop the service, all of the Chrome pages instantly load and I have no issues for about an hour. It seems to be some sort of issue with certificates/SSL.

The problem is the service keeps restarting itself. I've tried setting it to "disabled," tried unchecking the service in System Configuration, nothing works. It always comes back and Chrome breaks. I'm sure there's good reason to keep it running but I'm not going to let Microsoft force me out of my favorite browser/bookmarks/extensions/etc. like this, and I can't keep stopping a service every hour just to browse the web.

So I need a solution please. And something specifically related to fixing the issue with Cryptographic Services preventing SSL on Chrome. I've done all the basic stuff like reinstalling Chrome, checking firewall settings, etc..

Windows for home | Windows 10 | Internet and connectivity

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

165 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2019-05-09T20:05:59+00:00

    Its now almost 1 year later, and i still have this problem... why wont it be fixed by normal updates?

    If you delete the registry folder, everything is fine. Basically - what it does - it creates another REG_BINARY for the Certificates value under ProtectedRoots. This change helps the cryptographic service to run smoothly. I think the error behind this is somewhere deeper in the system and depends on some hardware combination. This is for sure, because someone said, multiple office systems (probably same hardware) were affected by this. Also I had the issue (even though I reinstalled windows), while a friend of mine didn't. We have exactly the same systems except for RAM, hard drives, graphics card and USB devices. Rest is completely the same. So it might be an issue with certain combinations of RAM and processor or AMD-Processor with Windows 10 issue or, or or..Many possibilities, but for now - apparently - a simple registry fix by hand is possible. I doubt Microsoft can figure out easily where the issue exactly comes from.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  2. Anonymous
    2019-05-09T18:47:10+00:00

    The issue has been around for so long by now. They won't fix it because only a handfull of people are affected by it. What you do in the registry is, that you basically force Windows to recreate the Root folder which is for some reason f**** up. You don't erase anything permanently, you don't change anything else. It's a simple, effective and for now the only permanent solution besides manually stopping the cryptographic service. If you don't want to recreate the folder in the registry, then simply create a batch file on your desktop with this content:

    SC Stop CryptSvc

    save it as "stop.bat" and double click it after reboot and after sleep mode. This will also fix most issues such as the Chrome issue. Might not stop your system from crashing though, if you are using an AMD processor.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  3. Anonymous
    2019-05-07T00:06:32+00:00

    Had the same issue with Chrome hanging on secure connection. I typed services.msc at the admin command prompt.

    Go to Cryptographic services, right click to properties, and in the "Log on" tab, change the setting to local account. Restarted and Chrome was good as ever.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  4. Anonymous
    2019-03-21T00:28:00+00:00

    ˙ǝuıɟ buıʞɹoʍ ǝq oʇ sɯǝǝs buıɥʇʎɹǝʌǝ puɐ osןɐ ǝʇɐpdn ǝɥʇ pıp ı

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  5. Anonymous
    2019-03-20T21:28:21+00:00

    Its now almost 1 year later, and i still have this problem... why wont it be fixed by normal updates?

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments