I just did your suggestion. I will see if it helps.
April 2018 update broke Chrome browser (Cryptographic Services bug)
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.
165 answers
Sort by: Most helpful
-
Anonymous
2019-02-05T11:25:15+00:00 -
Anonymous
2019-02-05T10:34:16+00:00 Yes! This workaround works, and I would also add the option to reinstall chrome while Cryptsvc is off and then start it this solved my problem.
-
Anonymous
2019-02-05T09:17:52+00:00 I am about to give up. Here are things I've tried.
Registry fix
Adding --proxy-server to end of the Application run command.
I just spent two days repartitioning my hard drive, formatting the drive, re-installing Windows from scratch and installing and configuring all applications.. I installed everything new and downloaded all Windows updates, including the Fall Creator Update (Windows 10 Build 1809) as well as have the latest version of Chrome. Same problem. Most times I get a timeout while going to a secure site.
Until this gets all figured out correctly between Microsoft and Google I think I will just use Firefox from now on.
-
Anonymous
2019-02-05T08:54:38+00:00 Matthew: Re:
Thanks but I have already tried this and it fails to be adequate within my domain. Firstly we use mandatory profiles which would mean editing the registry for each individual user. I have tried both scripted and manual registry of the root key with limited success. Thank you for your input though.
If you don't need User added Root CA, you might be able to use GPO to dis-allow this feature and avoid the problem CryptSvc. See my link above to Jason's GPO fix. I'd like to know if the GPO change works with mandatory profiles.
-
Anonymous
2019-02-05T07:00:29+00:00 It worked a little for me. Still taking longer than usual to load Secure sites.