To do with Win 10 Shutdown behaviour which is different to Win 7 Behaviour, why and how to Fix in Win 10












0















I have a Syncing process which runs on Logoff.



In Win 7, it sat there on the logoff screen with the Force Shutdown button, but if left, it finished, no matter how long it took, and the shutdown proceeded, which meant at the end of the day I could just shutdown and go home, knowing the backups were updated with the synced work, and the computer was off.



Win 10 on the other hand, only sits on the same screen for 60 secs, and then returns to the Desktop, having also already shutdown half the small apps and services that were running, although the syncing process is still running.



So the Sync will run, but the computer is still on and logged in, although not in a good state with the other processes having been shutdown.



I have tried various values for the registry entries WaitToKillAppTimeout and HungAppTimeout even making them both 86400000 to represent 24 hours, but I can't change this behaviour.



All MS support want to do is connect and go fishing on my computer, not happening, so I have come to SuperUser as I have already found some good answers here as I migrate from Win7Pro on my HP Probook 4530s to Win10Home on my new NUC8i7BEH in the hope I might find the answer I don't seem to be able to find courtesy of Google.










share|improve this question



























    0















    I have a Syncing process which runs on Logoff.



    In Win 7, it sat there on the logoff screen with the Force Shutdown button, but if left, it finished, no matter how long it took, and the shutdown proceeded, which meant at the end of the day I could just shutdown and go home, knowing the backups were updated with the synced work, and the computer was off.



    Win 10 on the other hand, only sits on the same screen for 60 secs, and then returns to the Desktop, having also already shutdown half the small apps and services that were running, although the syncing process is still running.



    So the Sync will run, but the computer is still on and logged in, although not in a good state with the other processes having been shutdown.



    I have tried various values for the registry entries WaitToKillAppTimeout and HungAppTimeout even making them both 86400000 to represent 24 hours, but I can't change this behaviour.



    All MS support want to do is connect and go fishing on my computer, not happening, so I have come to SuperUser as I have already found some good answers here as I migrate from Win7Pro on my HP Probook 4530s to Win10Home on my new NUC8i7BEH in the hope I might find the answer I don't seem to be able to find courtesy of Google.










    share|improve this question

























      0












      0








      0








      I have a Syncing process which runs on Logoff.



      In Win 7, it sat there on the logoff screen with the Force Shutdown button, but if left, it finished, no matter how long it took, and the shutdown proceeded, which meant at the end of the day I could just shutdown and go home, knowing the backups were updated with the synced work, and the computer was off.



      Win 10 on the other hand, only sits on the same screen for 60 secs, and then returns to the Desktop, having also already shutdown half the small apps and services that were running, although the syncing process is still running.



      So the Sync will run, but the computer is still on and logged in, although not in a good state with the other processes having been shutdown.



      I have tried various values for the registry entries WaitToKillAppTimeout and HungAppTimeout even making them both 86400000 to represent 24 hours, but I can't change this behaviour.



      All MS support want to do is connect and go fishing on my computer, not happening, so I have come to SuperUser as I have already found some good answers here as I migrate from Win7Pro on my HP Probook 4530s to Win10Home on my new NUC8i7BEH in the hope I might find the answer I don't seem to be able to find courtesy of Google.










      share|improve this question














      I have a Syncing process which runs on Logoff.



      In Win 7, it sat there on the logoff screen with the Force Shutdown button, but if left, it finished, no matter how long it took, and the shutdown proceeded, which meant at the end of the day I could just shutdown and go home, knowing the backups were updated with the synced work, and the computer was off.



      Win 10 on the other hand, only sits on the same screen for 60 secs, and then returns to the Desktop, having also already shutdown half the small apps and services that were running, although the syncing process is still running.



      So the Sync will run, but the computer is still on and logged in, although not in a good state with the other processes having been shutdown.



      I have tried various values for the registry entries WaitToKillAppTimeout and HungAppTimeout even making them both 86400000 to represent 24 hours, but I can't change this behaviour.



      All MS support want to do is connect and go fishing on my computer, not happening, so I have come to SuperUser as I have already found some good answers here as I migrate from Win7Pro on my HP Probook 4530s to Win10Home on my new NUC8i7BEH in the hope I might find the answer I don't seem to be able to find courtesy of Google.







      windows shutdown






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Dec 29 '18 at 6:09









      G FrisbyG Frisby

      11




      11






















          0






          active

          oldest

          votes











          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',
          autoActivateHeartbeat: false,
          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%2f1388664%2fto-do-with-win-10-shutdown-behaviour-which-is-different-to-win-7-behaviour-why%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          0






          active

          oldest

          votes








          0






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes
















          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.




          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1388664%2fto-do-with-win-10-shutdown-behaviour-which-is-different-to-win-7-behaviour-why%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

          Terni

          A new problem with tex4ht and tikz

          Sun Ra