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.
Matthew: If you can track down the registry settings that gpedit sets for dis-allow user trusted root CAs, we could use these for Win Home users who don't have gpedit.
Thanks again for you feedback. I just posted the policy workaround to Chrome bug 838707 and the chrome-admins thread here
I know it will alway come back on when requested by other services if I just stop the service. I was just wondering if I did the changes shown in the two videos if it would affect the running of cryptsvc when it needs to.
It maybe also Chrome seems slower now after running Firefox the last two days. Maybe I was just used to the slowness of it and are only seeing it from a different perspective now using the speedier Firefox.
Gregory: AFAIK- stopping CryptSvc is always safe - it restarts on demand as needed.
In fact, just because you manually stop it, it may not stayed stopped. Sometimes other things running in the background, or other things you do on the desktop (like closing programs) will auto-start CryptSvc.
The net stop cryptsvc shortcut is a solid workaround, but you'll end up using it a lot.
Matthew: I couldn't have asked for a better 'cold jar' (I like mine creamy) than the two video clips.
Should you do this again, remember to expand the left nav panel so we can watch traversing the path.
I added text descriptions to both YouTube clips.
I used windows update today on several newly imaged win 10 1809 clients with the suggested GPO change and all is working fine. Also tested itunes, terminal services and Sophos central without any problems. I have another 30 machines to image and will report back once completed. Please be sure to thank LarryLACa if this works for you. All i have done is emulated his fix and created a few short video clips. If i get chance I will create some voice over clips showing before and after effects of implementing the workaround.
