This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](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)
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..
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.
Eventually I ended screwing something up and in the end, had to start with a fresh install on my pc. Nonetheless, once updated to the most recent build, I then installed google chrome and wow, it's now wicked fast. This ongoing problem was ridiculous in itself and it's a shame that not one (Google or Microsoft) fixed the problem. If I ever have to update my PC again, I'll just make sure I uninstall Google in the meantime.
Pronwan:
At this point I personally consider the hardware connection speculative. See the main technical bug report CR838707 for the long history, beginning late 2017, just before 1803.
The problem affects both home and managed systems, at least one of the managed environments is in Germany (look for @madrian.at). In the managed environments, it sees to impact all machines, not a specific hardware subset. Because it stems from permission problems in HKCU...Root/ProtectedRoots, it's particularly hard to cleanup in managed systems because it's at the user account level.
Also, on a broken system, if you create another Windows login, not used to install Windows updates, the new account works fine. TBD if an alternate account, created before the CryptSvc problem was introduced, is still OK. I think all the examples I've seen we're for alternate logins created after the failure started. I.e. I suspect creating a new account is similar to deleting/rebuilding HKCU...Root. A new HKCU...Root (tree) is always healthy.
I've heard that Windows feature updates (1803, 1809..) are like fresh Windows installs and then the prior user accounts are re-installed. My guess is there's a problem re-installing the user account, that's used to launch the feature update.
Good luck with the hunt. Let us know what you find.
It's true the new rig is an AMD Ryzen 7 2700X with the ASUS ROG Strix motherboard. My first AMD processor since the Athlon days. No, the Windows 10 Home Edition is set to English (UK). The GPU was originally an nVidia, but because I had problems downloading drivers for it, I swapped it for a Sapphire ATI Radeon RX Vega 56 Pulse. The RAM was also swapped because one module of the Corsair Vengeance 2x8 3000MHz DDR4 was freezing the system. Instead I now have 2x8 G.Skill Trident Z 3200MHz DDR4.
The problem began when Windows Updated to 1809, before that Chrome was working fine.
I hope a true fix will be forthcoming and the next big update won't throw up the same result.
Another question, because I want to figure out what exact hardware combination causes this problem: Am I guessing right, that you are on an AMD CPU (Ryzen 5 or 7) and your Windows OS is set to German language?
Probably because there are so many issues, that are related to specific hard- or software combinations and you need to find people who had the same issue. If you explain this cryptographic / Chrome issue to a Microsoft support staff, they can't recreate it, can't figure out where it might come from beacuse it can be caused by thousands of different issues. So in the end, finding others who figured a solution for the exact same problem with a similar hardware combination ist the most efficient solution :) By the way: Do you also have an AMD CPU and GPU? Or did this issue occur on an Intel Processor?
