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.
Yeah, I'm with you on the frustration. It's crazy how this has been an ongoing problem for a while and the problem still persists. I thought to upgrade to 1809 and along with all the patches would fix the problem but nothing. I'm wondering if Microsoft is even watching this board.
Has Microsoft or chrome finally looked into this? I just updated to 1809 and still, the problem persists! This is crazy. I'm also noticing the font isn't as clear as firefox.
No, this is still a problem. There are several ways to make it work temporarily but the easiest one I found so far is to stop the cryptographic service and start Chrome. The cryptographic service restarts automatically but Chrome still works...for a while at least, but you have to stop the service again if you close chrome and restart it. This is a royal pain!
Has Microsoft or chrome finally looked into this? I just updated to 1809 and still, the problem persists! This is crazy. I'm also noticing the font isn't as clear as firefox.
DonChanger:
Starting regedit as Admin and updating Current_User, can update the admin's account and not the user account.
If a standard user needs to run regedit as admin, they need to navigate to their own account under HKey_Users, then do the ProtectedRoots and Root cleanup.
To see the elevation Currnet_User problem, create a 'WhoAmI' string item under Root or Credentials, then find it under HKey_Users to see which account is current.
The scripted repair has some extra steps to make sure it's updating the correct account.
In general, I believe I have confirmations that the manual regedit repair works for accounts without admin privileges. So I would be interested in trying to track down why it didn't work for your 'standard user'.
If you're an admin in an AD environment, other caveats may apply.
later, Larry
DarrelCranston:
Cool thx for info. Appreciated.
I see someone upvoted Alex's --proxy-server tip. Did --proxy-server work for you?
If it did, can you try this
close chrome, check task manager> Details to verify the background processes also stopped.
start Edge
start Chrome without the --proxy-server.
try opening some https sites in chrome, the usual ones that lockup for you
If starting edge first helps, it sounds like you have the same CryptSvc problem we're trying to fix here. If starting Edge first make no difference, you may have yet another similar problem.
Other proxy server workarounds have helped a few people, but not everyone. I'm trying confirm that you have the same core issue.
The real tell is to watch the CryptSvc CPU usage (from task manager) while Chrome is stalling. If high (>2%) then you have the CryptSvc bug. Trying to walk through task manager to find the CryptSvc svchost launcher (and it's CPU usage) requires a couple of searches and hops. Preloading Edge is easier..
TIA Larry
