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..

1. In my case the cryptographic service goes up to ~18% when chrome is stalling.
2. Opening Edge first does not help.
3. Pressing the windows key couple to bring up the startup menu seems to help but is very annoying.
4. I haven't try the registry fix yet.
5. This problem occurred after a clean windows install (3 weeks ago).  Did not see it before that.

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.