thank you!! together we can windows get to work properly!!!!!
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-05-13T01:24:38+00:00 -
Anonymous
2019-05-13T01:21:50+00:00 thank you
-
Anonymous
2019-05-13T01:19:03+00:00 thank you
windows creates lots of bugs , for example in component services and this one in cryptographic services ! the community soves these problems mostly ! microsoft almost never knows the right answers. they always advise a clean boot , or scannow , or restore health or whatever . these solutions almost never work!! strange indeed!
-
Anonymous
2019-05-12T21:39:51+00:00 That's interesting. My processor is an AMD.
-
Anonymous
2019-05-12T19:07:19+00:00 I Have a AMD CPU and NVIDIA GPU on the PC who had this problem.
my Other PC has an INTEL Processor and exactly the same windows version.this issue didn't occur on this PC, indeed