Chrome won't work after Windows 10 update











up vote
0
down vote

favorite












After a forced update on Windows 10 (to Version 10.0.17134.376) I can't access any site with Google Chrome.



Every time I try to visit a site it times out (ERR_TIMED_OUT).



Microsoft Edge (which suddenly appeared among my desktop icons) appears to work fine.



I've tried




  • Restarting the computer

  • Reinstalling Google Chrome

  • Running the "compatibility problems" dialog on the Chrome application


Nothing has worked.



Any ideas to what I can do?










share|improve this question




















  • 1




    When you say Edge was suddenly installed does that mean you removed it? What build were you running before you installed KB4462933, I suspect what you were actually using 1709 and due to your Windows Update settings upgraded to 1803. Have you tried to delete your Chrome user profile? Please provide all relevant information in an update to your question instead of a comment. Be sure to include the Chrome build you are using.
    – Ramhound
    Oct 26 at 18:54












  • If you syncronized your user/got backup of your favorites passwords etc. I should navigate to "%LOCALAPPDATA% , delete the folder called 'Google' . then start chrome again. this is a simple way to save time. makes things less complicated =)
    – XsiSec
    Oct 26 at 18:56

















up vote
0
down vote

favorite












After a forced update on Windows 10 (to Version 10.0.17134.376) I can't access any site with Google Chrome.



Every time I try to visit a site it times out (ERR_TIMED_OUT).



Microsoft Edge (which suddenly appeared among my desktop icons) appears to work fine.



I've tried




  • Restarting the computer

  • Reinstalling Google Chrome

  • Running the "compatibility problems" dialog on the Chrome application


Nothing has worked.



Any ideas to what I can do?










share|improve this question




















  • 1




    When you say Edge was suddenly installed does that mean you removed it? What build were you running before you installed KB4462933, I suspect what you were actually using 1709 and due to your Windows Update settings upgraded to 1803. Have you tried to delete your Chrome user profile? Please provide all relevant information in an update to your question instead of a comment. Be sure to include the Chrome build you are using.
    – Ramhound
    Oct 26 at 18:54












  • If you syncronized your user/got backup of your favorites passwords etc. I should navigate to "%LOCALAPPDATA% , delete the folder called 'Google' . then start chrome again. this is a simple way to save time. makes things less complicated =)
    – XsiSec
    Oct 26 at 18:56















up vote
0
down vote

favorite









up vote
0
down vote

favorite











After a forced update on Windows 10 (to Version 10.0.17134.376) I can't access any site with Google Chrome.



Every time I try to visit a site it times out (ERR_TIMED_OUT).



Microsoft Edge (which suddenly appeared among my desktop icons) appears to work fine.



I've tried




  • Restarting the computer

  • Reinstalling Google Chrome

  • Running the "compatibility problems" dialog on the Chrome application


Nothing has worked.



Any ideas to what I can do?










share|improve this question















After a forced update on Windows 10 (to Version 10.0.17134.376) I can't access any site with Google Chrome.



Every time I try to visit a site it times out (ERR_TIMED_OUT).



Microsoft Edge (which suddenly appeared among my desktop icons) appears to work fine.



I've tried




  • Restarting the computer

  • Reinstalling Google Chrome

  • Running the "compatibility problems" dialog on the Chrome application


Nothing has worked.



Any ideas to what I can do?







windows-10 google-chrome windows-update






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Oct 26 at 18:56

























asked Oct 26 at 18:41









Danc

113




113








  • 1




    When you say Edge was suddenly installed does that mean you removed it? What build were you running before you installed KB4462933, I suspect what you were actually using 1709 and due to your Windows Update settings upgraded to 1803. Have you tried to delete your Chrome user profile? Please provide all relevant information in an update to your question instead of a comment. Be sure to include the Chrome build you are using.
    – Ramhound
    Oct 26 at 18:54












  • If you syncronized your user/got backup of your favorites passwords etc. I should navigate to "%LOCALAPPDATA% , delete the folder called 'Google' . then start chrome again. this is a simple way to save time. makes things less complicated =)
    – XsiSec
    Oct 26 at 18:56
















  • 1




    When you say Edge was suddenly installed does that mean you removed it? What build were you running before you installed KB4462933, I suspect what you were actually using 1709 and due to your Windows Update settings upgraded to 1803. Have you tried to delete your Chrome user profile? Please provide all relevant information in an update to your question instead of a comment. Be sure to include the Chrome build you are using.
    – Ramhound
    Oct 26 at 18:54












  • If you syncronized your user/got backup of your favorites passwords etc. I should navigate to "%LOCALAPPDATA% , delete the folder called 'Google' . then start chrome again. this is a simple way to save time. makes things less complicated =)
    – XsiSec
    Oct 26 at 18:56










1




1




When you say Edge was suddenly installed does that mean you removed it? What build were you running before you installed KB4462933, I suspect what you were actually using 1709 and due to your Windows Update settings upgraded to 1803. Have you tried to delete your Chrome user profile? Please provide all relevant information in an update to your question instead of a comment. Be sure to include the Chrome build you are using.
– Ramhound
Oct 26 at 18:54






When you say Edge was suddenly installed does that mean you removed it? What build were you running before you installed KB4462933, I suspect what you were actually using 1709 and due to your Windows Update settings upgraded to 1803. Have you tried to delete your Chrome user profile? Please provide all relevant information in an update to your question instead of a comment. Be sure to include the Chrome build you are using.
– Ramhound
Oct 26 at 18:54














If you syncronized your user/got backup of your favorites passwords etc. I should navigate to "%LOCALAPPDATA% , delete the folder called 'Google' . then start chrome again. this is a simple way to save time. makes things less complicated =)
– XsiSec
Oct 26 at 18:56






If you syncronized your user/got backup of your favorites passwords etc. I should navigate to "%LOCALAPPDATA% , delete the folder called 'Google' . then start chrome again. this is a simple way to save time. makes things less complicated =)
– XsiSec
Oct 26 at 18:56












2 Answers
2






active

oldest

votes

















up vote
1
down vote



accepted










The problem



The problem has been discussed on Google Chrome's help forum:




The problem started with the April 2018 Win10 1803 Feature Update and can also happen with fresh Windows installs that use 1803. It is an (unknown) artifact of how Windows is installed or updated. The 1803 update can cause a core Windows identity service (CryptSvc) to loop endlessly and stall connections. -- https://productforums.google.com/forum/#!topic/chrome/s5S1uPI0kMc




Are you affected?



Try the following steps to see if you are affected by this problem:




  1. Open Task Manager

  2. Go to services

  3. Find the CryptSvc service

  4. Right click and restart the service


Can you browse sites with Google Chrome now? If so, you are affected and this is only a temporary fix.



Permanent solution



There are a lot of suggestions for solutions around (just google chrome CryptSvc fix)



The simplest fix (that worked for me) came from the Microsoft Forum.



(I have slightly altered the solution for easier understanding.)




  1. Run regedit

  2. Go to HKEY_CURRENT_USERSoftwareMicrosoftSystemCertificatesRoot

  3. Right click "ProtectedRoots" and click "Permissions"

  4. Select your user account and tick "Allow Full Control"

  5. Take a backup of Root by right clicking and click export, and save it somewhere

  6. Open Task Mananger and stop the "Cryptographic Service"

  7. Delete the SoftwareMicrosoftSystemCertificatesRoot registry entry

  8. Restart Windows






share|improve this answer




























    up vote
    0
    down vote













    I have fix it with our environment, we are using Windows 10 Eng 64bit Enterprise 1803 or 1809 clients and Windows 2016 server AD with mandatory login profile, Chrome is V70 64bit default profile is roaming also and getting this problem of Chrome not going on the internet and it take a long time to show web pages. What I did do was change the Crypto services logon from Network services to local system account and allow services to interact with desktop land added domain users to the Cryto services to start/stop.



    It seems to work OK now, let me know if it works for you. I did it with GPO.






    share|improve this answer





















      Your Answer








      StackExchange.ready(function() {
      var channelOptions = {
      tags: "".split(" "),
      id: "3"
      };
      initTagRenderer("".split(" "), "".split(" "), channelOptions);

      StackExchange.using("externalEditor", function() {
      // Have to fire editor after snippets, if snippets enabled
      if (StackExchange.settings.snippets.snippetsEnabled) {
      StackExchange.using("snippets", function() {
      createEditor();
      });
      }
      else {
      createEditor();
      }
      });

      function createEditor() {
      StackExchange.prepareEditor({
      heartbeatType: 'answer',
      convertImagesToLinks: true,
      noModals: true,
      showLowRepImageUploadWarning: true,
      reputationToPostImages: 10,
      bindNavPrevention: true,
      postfix: "",
      imageUploader: {
      brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
      contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
      allowUrls: true
      },
      onDemand: true,
      discardSelector: ".discard-answer"
      ,immediatelyShowMarkdownHelp:true
      });


      }
      });














      draft saved

      draft discarded


















      StackExchange.ready(
      function () {
      StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1370326%2fchrome-wont-work-after-windows-10-update%23new-answer', 'question_page');
      }
      );

      Post as a guest















      Required, but never shown

























      2 Answers
      2






      active

      oldest

      votes








      2 Answers
      2






      active

      oldest

      votes









      active

      oldest

      votes






      active

      oldest

      votes








      up vote
      1
      down vote



      accepted










      The problem



      The problem has been discussed on Google Chrome's help forum:




      The problem started with the April 2018 Win10 1803 Feature Update and can also happen with fresh Windows installs that use 1803. It is an (unknown) artifact of how Windows is installed or updated. The 1803 update can cause a core Windows identity service (CryptSvc) to loop endlessly and stall connections. -- https://productforums.google.com/forum/#!topic/chrome/s5S1uPI0kMc




      Are you affected?



      Try the following steps to see if you are affected by this problem:




      1. Open Task Manager

      2. Go to services

      3. Find the CryptSvc service

      4. Right click and restart the service


      Can you browse sites with Google Chrome now? If so, you are affected and this is only a temporary fix.



      Permanent solution



      There are a lot of suggestions for solutions around (just google chrome CryptSvc fix)



      The simplest fix (that worked for me) came from the Microsoft Forum.



      (I have slightly altered the solution for easier understanding.)




      1. Run regedit

      2. Go to HKEY_CURRENT_USERSoftwareMicrosoftSystemCertificatesRoot

      3. Right click "ProtectedRoots" and click "Permissions"

      4. Select your user account and tick "Allow Full Control"

      5. Take a backup of Root by right clicking and click export, and save it somewhere

      6. Open Task Mananger and stop the "Cryptographic Service"

      7. Delete the SoftwareMicrosoftSystemCertificatesRoot registry entry

      8. Restart Windows






      share|improve this answer

























        up vote
        1
        down vote



        accepted










        The problem



        The problem has been discussed on Google Chrome's help forum:




        The problem started with the April 2018 Win10 1803 Feature Update and can also happen with fresh Windows installs that use 1803. It is an (unknown) artifact of how Windows is installed or updated. The 1803 update can cause a core Windows identity service (CryptSvc) to loop endlessly and stall connections. -- https://productforums.google.com/forum/#!topic/chrome/s5S1uPI0kMc




        Are you affected?



        Try the following steps to see if you are affected by this problem:




        1. Open Task Manager

        2. Go to services

        3. Find the CryptSvc service

        4. Right click and restart the service


        Can you browse sites with Google Chrome now? If so, you are affected and this is only a temporary fix.



        Permanent solution



        There are a lot of suggestions for solutions around (just google chrome CryptSvc fix)



        The simplest fix (that worked for me) came from the Microsoft Forum.



        (I have slightly altered the solution for easier understanding.)




        1. Run regedit

        2. Go to HKEY_CURRENT_USERSoftwareMicrosoftSystemCertificatesRoot

        3. Right click "ProtectedRoots" and click "Permissions"

        4. Select your user account and tick "Allow Full Control"

        5. Take a backup of Root by right clicking and click export, and save it somewhere

        6. Open Task Mananger and stop the "Cryptographic Service"

        7. Delete the SoftwareMicrosoftSystemCertificatesRoot registry entry

        8. Restart Windows






        share|improve this answer























          up vote
          1
          down vote



          accepted







          up vote
          1
          down vote



          accepted






          The problem



          The problem has been discussed on Google Chrome's help forum:




          The problem started with the April 2018 Win10 1803 Feature Update and can also happen with fresh Windows installs that use 1803. It is an (unknown) artifact of how Windows is installed or updated. The 1803 update can cause a core Windows identity service (CryptSvc) to loop endlessly and stall connections. -- https://productforums.google.com/forum/#!topic/chrome/s5S1uPI0kMc




          Are you affected?



          Try the following steps to see if you are affected by this problem:




          1. Open Task Manager

          2. Go to services

          3. Find the CryptSvc service

          4. Right click and restart the service


          Can you browse sites with Google Chrome now? If so, you are affected and this is only a temporary fix.



          Permanent solution



          There are a lot of suggestions for solutions around (just google chrome CryptSvc fix)



          The simplest fix (that worked for me) came from the Microsoft Forum.



          (I have slightly altered the solution for easier understanding.)




          1. Run regedit

          2. Go to HKEY_CURRENT_USERSoftwareMicrosoftSystemCertificatesRoot

          3. Right click "ProtectedRoots" and click "Permissions"

          4. Select your user account and tick "Allow Full Control"

          5. Take a backup of Root by right clicking and click export, and save it somewhere

          6. Open Task Mananger and stop the "Cryptographic Service"

          7. Delete the SoftwareMicrosoftSystemCertificatesRoot registry entry

          8. Restart Windows






          share|improve this answer












          The problem



          The problem has been discussed on Google Chrome's help forum:




          The problem started with the April 2018 Win10 1803 Feature Update and can also happen with fresh Windows installs that use 1803. It is an (unknown) artifact of how Windows is installed or updated. The 1803 update can cause a core Windows identity service (CryptSvc) to loop endlessly and stall connections. -- https://productforums.google.com/forum/#!topic/chrome/s5S1uPI0kMc




          Are you affected?



          Try the following steps to see if you are affected by this problem:




          1. Open Task Manager

          2. Go to services

          3. Find the CryptSvc service

          4. Right click and restart the service


          Can you browse sites with Google Chrome now? If so, you are affected and this is only a temporary fix.



          Permanent solution



          There are a lot of suggestions for solutions around (just google chrome CryptSvc fix)



          The simplest fix (that worked for me) came from the Microsoft Forum.



          (I have slightly altered the solution for easier understanding.)




          1. Run regedit

          2. Go to HKEY_CURRENT_USERSoftwareMicrosoftSystemCertificatesRoot

          3. Right click "ProtectedRoots" and click "Permissions"

          4. Select your user account and tick "Allow Full Control"

          5. Take a backup of Root by right clicking and click export, and save it somewhere

          6. Open Task Mananger and stop the "Cryptographic Service"

          7. Delete the SoftwareMicrosoftSystemCertificatesRoot registry entry

          8. Restart Windows







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Oct 26 at 19:30









          Danc

          113




          113
























              up vote
              0
              down vote













              I have fix it with our environment, we are using Windows 10 Eng 64bit Enterprise 1803 or 1809 clients and Windows 2016 server AD with mandatory login profile, Chrome is V70 64bit default profile is roaming also and getting this problem of Chrome not going on the internet and it take a long time to show web pages. What I did do was change the Crypto services logon from Network services to local system account and allow services to interact with desktop land added domain users to the Cryto services to start/stop.



              It seems to work OK now, let me know if it works for you. I did it with GPO.






              share|improve this answer

























                up vote
                0
                down vote













                I have fix it with our environment, we are using Windows 10 Eng 64bit Enterprise 1803 or 1809 clients and Windows 2016 server AD with mandatory login profile, Chrome is V70 64bit default profile is roaming also and getting this problem of Chrome not going on the internet and it take a long time to show web pages. What I did do was change the Crypto services logon from Network services to local system account and allow services to interact with desktop land added domain users to the Cryto services to start/stop.



                It seems to work OK now, let me know if it works for you. I did it with GPO.






                share|improve this answer























                  up vote
                  0
                  down vote










                  up vote
                  0
                  down vote









                  I have fix it with our environment, we are using Windows 10 Eng 64bit Enterprise 1803 or 1809 clients and Windows 2016 server AD with mandatory login profile, Chrome is V70 64bit default profile is roaming also and getting this problem of Chrome not going on the internet and it take a long time to show web pages. What I did do was change the Crypto services logon from Network services to local system account and allow services to interact with desktop land added domain users to the Cryto services to start/stop.



                  It seems to work OK now, let me know if it works for you. I did it with GPO.






                  share|improve this answer












                  I have fix it with our environment, we are using Windows 10 Eng 64bit Enterprise 1803 or 1809 clients and Windows 2016 server AD with mandatory login profile, Chrome is V70 64bit default profile is roaming also and getting this problem of Chrome not going on the internet and it take a long time to show web pages. What I did do was change the Crypto services logon from Network services to local system account and allow services to interact with desktop land added domain users to the Cryto services to start/stop.



                  It seems to work OK now, let me know if it works for you. I did it with GPO.







                  share|improve this answer












                  share|improve this answer



                  share|improve this answer










                  answered Nov 20 at 2:47









                  user965365

                  1




                  1






























                      draft saved

                      draft discarded




















































                      Thanks for contributing an answer to Super User!


                      • Please be sure to answer the question. Provide details and share your research!

                      But avoid



                      • Asking for help, clarification, or responding to other answers.

                      • Making statements based on opinion; back them up with references or personal experience.


                      To learn more, see our tips on writing great answers.





                      Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


                      Please pay close attention to the following guidance:


                      • Please be sure to answer the question. Provide details and share your research!

                      But avoid



                      • Asking for help, clarification, or responding to other answers.

                      • Making statements based on opinion; back them up with references or personal experience.


                      To learn more, see our tips on writing great answers.




                      draft saved


                      draft discarded














                      StackExchange.ready(
                      function () {
                      StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1370326%2fchrome-wont-work-after-windows-10-update%23new-answer', 'question_page');
                      }
                      );

                      Post as a guest















                      Required, but never shown





















































                      Required, but never shown














                      Required, but never shown












                      Required, but never shown







                      Required, but never shown

































                      Required, but never shown














                      Required, but never shown












                      Required, but never shown







                      Required, but never shown







                      Popular posts from this blog

                      AnyDesk - Fatal Program Failure

                      How to calibrate 16:9 built-in touch-screen to a 4:3 resolution?

                      QoS: MAC-Priority for clients behind a repeater