Hi,
don't STOP cryptographic services . and logon with NETWORK SERVICES (username and Password)
April 2018 update broke Chrome browser (Cryptographic Services bug)
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Anonymous
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: Newest
-
Anonymous
2019-05-09T19:36:37+00:00 -
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.
-
Anonymous
2019-05-09T18:44:20+00:00 Absolutely. It causes problems with every service that somehow needs the Windows cryptographic service (I think in order to perform http requests). It can even cause freezes (like in my case) if you are running the system with an AMD processor. Microsoft should really fix the issue but for now the registry fix does the job indeed. It recreates the root folder and that's it.
-
Anonymous
2019-05-09T18:42:55+00:00 Absolutely. That's why you need to do the registry fix.
-
Anonymous
2019-05-09T18:42:23+00:00 It's not only chrome. It's basically all services that use Microsoft's cryptographic system. Firefox for example has an own cryptographic system behind it. For me not only Chrome didn't work but many launchers such as Upwork, time trackers such as Timeular etc. Also I think it has something to do with hardware, because most people who have this issue have AMD processors. What you do by erasing this in the registry is basically fixing it, because it gets recreated after reboot and then works flawlessly.