Win10 1803 will take 7-10 minutes to restart/shutdown just after a fresh boot, performance logs inside
I have a Dell Zbook 17 G5 laptop with nvme ssd i use for work that i am pulling my hair out to fix this issue i am having. After a fresh boot, if i restart or shutdown (possibly even just log off but i haven't test it), it will stay in the shutdown screen for 7-10 minutes before proceeding to turn off.
If i was logged in for 10 minutes already, it will turn off/reboot normally in a couple of seconds.
I've disabled all non-microsoft services, removed the anti-virus, disabled windows defender, checked if page file delete policy is disabled, etc and can't find the issue.
Last resort i found this question and answer here: How can I identify the culprit of my slow Windows shutdown?
and recorded 2 performance logs. One is "good" (quick restart since i was logged in for more than 10 minutes) and the other one is "bad" (slow restart since i rebooted as soon as i logged in).
I can't seem to find a sure cause, but i am not familiar with the analyzer enough to know what is fishy.
That's why i uploaded both logs in hopes someone can please check them out:
https://www.dropbox.com/s/76sowxabh8mndnp/windows_performance_logs.rar?dl=0
Kind regards
windows-10 performance shutdown
asked Jan 16 at 0:18
TnFTnF
36117
|
show 3 more comments
I have a Dell Zbook 17 G5 laptop with nvme ssd i use for work that i am pulling my hair out to fix this issue i am having. After a fresh boot, if i restart or shutdown (possibly even just log off but i haven't test it), it will stay in the shutdown screen for 7-10 minutes before proceeding to turn off.
If i was logged in for 10 minutes already, it will turn off/reboot normally in a couple of seconds.
I've disabled all non-microsoft services, removed the anti-virus, disabled windows defender, checked if page file delete policy is disabled, etc and can't find the issue.
Last resort i found this question and answer here: How can I identify the culprit of my slow Windows shutdown?
and recorded 2 performance logs. One is "good" (quick restart since i was logged in for more than 10 minutes) and the other one is "bad" (slow restart since i rebooted as soon as i logged in).
I can't seem to find a sure cause, but i am not familiar with the analyzer enough to know what is fishy.
That's why i uploaded both logs in hopes someone can please check them out:
https://www.dropbox.com/s/76sowxabh8mndnp/windows_performance_logs.rar?dl=0
Kind regards
windows-10 performance shutdown
asked Jan 16 at 0:18
TnFTnF
36117
Have you already tried to disable the Fast Startup function to see if that helps?
– Run5k
Jan 16 at 0:21
@Run5k - Wouldn't that make the system take longer to boot?
– Ramhound
Jan 16 at 0:31
@Ramhound, logically that should be the case. However, it also sounds like it's possible his hardware/OS configuration is having problems that could be related to similar capabilities that the Fast Startup function typically modifies. From my perspective, the principles of "troubleshooting 101" would seem to dictate that it might be wise to eliminate that possibility, since the OP apparently hasn't tried that yet. If the problem persists, it is very easy to turn back on again.
– Run5k
Jan 16 at 2:04
@Run5k Yes that is the first option i disable in any work PC, win10 junk. Also from the performance log and indicators it seems the pc doesn't do any work, it just waits:/ could be a miss-configured service if i were to guess possibly a microsoft one (since i've disabled the others)..i could update to 1809 and hope for the best but i want to stay away longer so microsoft fixes all their bugs
– TnF
Jan 16 at 2:13
Fast Startup absolutely is not "Windows 10 junk". If you have disabled the required files for Windows to boot quickly (i.e hibernation.sys, pagefile.sys, and swapfile.sys) that might explain your performance issues.
– Ramhound
Jan 16 at 2:29
|
show 3 more comments
I have a Dell Zbook 17 G5 laptop with nvme ssd i use for work that i am pulling my hair out to fix this issue i am having. After a fresh boot, if i restart or shutdown (possibly even just log off but i haven't test it), it will stay in the shutdown screen for 7-10 minutes before proceeding to turn off.
If i was logged in for 10 minutes already, it will turn off/reboot normally in a couple of seconds.
I've disabled all non-microsoft services, removed the anti-virus, disabled windows defender, checked if page file delete policy is disabled, etc and can't find the issue.
Last resort i found this question and answer here: How can I identify the culprit of my slow Windows shutdown?
and recorded 2 performance logs. One is "good" (quick restart since i was logged in for more than 10 minutes) and the other one is "bad" (slow restart since i rebooted as soon as i logged in).
I can't seem to find a sure cause, but i am not familiar with the analyzer enough to know what is fishy.
That's why i uploaded both logs in hopes someone can please check them out:
https://www.dropbox.com/s/76sowxabh8mndnp/windows_performance_logs.rar?dl=0
Kind regards
windows-10 performance shutdown
asked Jan 16 at 0:18
TnFTnF
36117
I have a Dell Zbook 17 G5 laptop with nvme ssd i use for work that i am pulling my hair out to fix this issue i am having. After a fresh boot, if i restart or shutdown (possibly even just log off but i haven't test it), it will stay in the shutdown screen for 7-10 minutes before proceeding to turn off.
If i was logged in for 10 minutes already, it will turn off/reboot normally in a couple of seconds.
I've disabled all non-microsoft services, removed the anti-virus, disabled windows defender, checked if page file delete policy is disabled, etc and can't find the issue.
Last resort i found this question and answer here: How can I identify the culprit of my slow Windows shutdown?
and recorded 2 performance logs. One is "good" (quick restart since i was logged in for more than 10 minutes) and the other one is "bad" (slow restart since i rebooted as soon as i logged in).
I can't seem to find a sure cause, but i am not familiar with the analyzer enough to know what is fishy.
That's why i uploaded both logs in hopes someone can please check them out:
https://www.dropbox.com/s/76sowxabh8mndnp/windows_performance_logs.rar?dl=0
Kind regards
windows-10 performance shutdown
windows-10 performance shutdown
asked Jan 16 at 0:18
TnFTnF
36117
asked Jan 16 at 0:18
TnFTnF
36117
asked Jan 16 at 0:18
TnFTnF
36117
asked Jan 16 at 0:18
TnFTnF
36117
asked Jan 16 at 0:18
TnFTnF
36117
36117
Have you already tried to disable the Fast Startup function to see if that helps?
– Run5k
Jan 16 at 0:21
@Run5k - Wouldn't that make the system take longer to boot?
– Ramhound
Jan 16 at 0:31
@Ramhound, logically that should be the case. However, it also sounds like it's possible his hardware/OS configuration is having problems that could be related to similar capabilities that the Fast Startup function typically modifies. From my perspective, the principles of "troubleshooting 101" would seem to dictate that it might be wise to eliminate that possibility, since the OP apparently hasn't tried that yet. If the problem persists, it is very easy to turn back on again.
– Run5k
Jan 16 at 2:04
@Run5k Yes that is the first option i disable in any work PC, win10 junk. Also from the performance log and indicators it seems the pc doesn't do any work, it just waits:/ could be a miss-configured service if i were to guess possibly a microsoft one (since i've disabled the others)..i could update to 1809 and hope for the best but i want to stay away longer so microsoft fixes all their bugs
– TnF
Jan 16 at 2:13
Fast Startup absolutely is not "Windows 10 junk". If you have disabled the required files for Windows to boot quickly (i.e hibernation.sys, pagefile.sys, and swapfile.sys) that might explain your performance issues.
– Ramhound
Jan 16 at 2:29
|
show 3 more comments
Have you already tried to disable the Fast Startup function to see if that helps?
– Run5k
Jan 16 at 0:21
@Run5k - Wouldn't that make the system take longer to boot?
– Ramhound
Jan 16 at 0:31
@Ramhound, logically that should be the case. However, it also sounds like it's possible his hardware/OS configuration is having problems that could be related to similar capabilities that the Fast Startup function typically modifies. From my perspective, the principles of "troubleshooting 101" would seem to dictate that it might be wise to eliminate that possibility, since the OP apparently hasn't tried that yet. If the problem persists, it is very easy to turn back on again.
– Run5k
Jan 16 at 2:04
@Run5k Yes that is the first option i disable in any work PC, win10 junk. Also from the performance log and indicators it seems the pc doesn't do any work, it just waits:/ could be a miss-configured service if i were to guess possibly a microsoft one (since i've disabled the others)..i could update to 1809 and hope for the best but i want to stay away longer so microsoft fixes all their bugs
– TnF
Jan 16 at 2:13
Fast Startup absolutely is not "Windows 10 junk". If you have disabled the required files for Windows to boot quickly (i.e hibernation.sys, pagefile.sys, and swapfile.sys) that might explain your performance issues.
– Ramhound
Jan 16 at 2:29
Have you already tried to disable the Fast Startup function to see if that helps?
– Run5k
Jan 16 at 0:21
Have you already tried to disable the Fast Startup function to see if that helps?
– Run5k
Jan 16 at 0:21
@Run5k - Wouldn't that make the system take longer to boot?
– Ramhound
Jan 16 at 0:31
@Run5k - Wouldn't that make the system take longer to boot?
– Ramhound
Jan 16 at 0:31
@Ramhound, logically that should be the case. However, it also sounds like it's possible his hardware/OS configuration is having problems that could be related to similar capabilities that the Fast Startup function typically modifies. From my perspective, the principles of "troubleshooting 101" would seem to dictate that it might be wise to eliminate that possibility, since the OP apparently hasn't tried that yet. If the problem persists, it is very easy to turn back on again.
– Run5k
Jan 16 at 2:04
@Ramhound, logically that should be the case. However, it also sounds like it's possible his hardware/OS configuration is having problems that could be related to similar capabilities that the Fast Startup function typically modifies. From my perspective, the principles of "troubleshooting 101" would seem to dictate that it might be wise to eliminate that possibility, since the OP apparently hasn't tried that yet. If the problem persists, it is very easy to turn back on again.
– Run5k
Jan 16 at 2:04
@Run5k Yes that is the first option i disable in any work PC, win10 junk. Also from the performance log and indicators it seems the pc doesn't do any work, it just waits:/ could be a miss-configured service if i were to guess possibly a microsoft one (since i've disabled the others)..i could update to 1809 and hope for the best but i want to stay away longer so microsoft fixes all their bugs
– TnF
Jan 16 at 2:13
@Run5k Yes that is the first option i disable in any work PC, win10 junk. Also from the performance log and indicators it seems the pc doesn't do any work, it just waits:/ could be a miss-configured service if i were to guess possibly a microsoft one (since i've disabled the others)..i could update to 1809 and hope for the best but i want to stay away longer so microsoft fixes all their bugs
– TnF
Jan 16 at 2:13
Fast Startup absolutely is not "Windows 10 junk". If you have disabled the required files for Windows to boot quickly (i.e hibernation.sys, pagefile.sys, and swapfile.sys) that might explain your performance issues.
– Ramhound
Jan 16 at 2:29
Fast Startup absolutely is not "Windows 10 junk". If you have disabled the required files for Windows to boot quickly (i.e hibernation.sys, pagefile.sys, and swapfile.sys) that might explain your performance issues.
– Ramhound
Jan 16 at 2:29
|
show 3 more comments
1 Answer
1
active
oldest
votes
Ok fixed it. So it turns out there is an issue somewhere with the GPClient if you use custom DNS servers, even though you might not be connected to them. My user account is a domain user. In my network settings i had set google dns to bypass the filtering used in the domain network. The problem with this seems the group policy client cannot access the policies set by the domain (even though in my case the policies are empty) and hangs the system until some timeout is gone.
I changed back the domain dns to automatic for my network adapter, and then updated the domain group policy by running this command:
gpupdate /force
In order for it to be successful i had to renew the dns with some command i found in the error log in the event viewer, but i would guess a restart would do the job as well. Now i need to find what setting controls this timeout which is absolutely stupid set to like 10 minutes.
answered Jan 16 at 9:21
TnFTnF
36117
found it in gpedit.msc, Computer ConfigurationAdministrative TemplatesSystemScripts , Specify maximum wait time for Group Policy scripts
– TnF
Jan 16 at 9:32
This policy setting determines how long the system waits for scripts applied by Group Policy to run. This setting limits the total time allowed for all logon, logoff, startup, and shutdown scripts applied by Group Policy to finish running. If the scripts have not finished running when the specified time expires, the system stops script processing and records an error event.
– TnF
Jan 16 at 9:34
If you enable this setting, then, in the Seconds box, you can type a number from 1 to 32,000 for the number of seconds you want the system to wait for the set of scripts to finish. To direct the system to wait until the scripts have finished, no matter how long they take, type 0. This interval is particularly important when other system tasks must wait while the scripts complete. By default, each startup script must complete before the next one runs.
– TnF
Jan 16 at 9:34
Also, you can use the ""Run logon scripts synchronously"" setting to direct the system to wait for the logon scripts to complete before loading the desktop. An excessively long interval can delay the system and inconvenience users. However, if the interval is too short, prerequisite tasks might not be done, and the system can appear to be ready prematurely. If you disable or do not configure this setting the system lets the combined set of scripts run for up to 600 seconds (10 minutes). This is the default.
– TnF
Jan 16 at 9:34
Also can confirm this is working along with custom dns no issues! You are supposedly need to set Run logon scripts synchronously policy to Disabled as well but i don't think affects this.
– TnF
Jan 16 at 9:45
add a comment |
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
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1394743%2fwin10-1803-will-take-7-10-minutes-to-restart-shutdown-just-after-a-fresh-boot-p%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Ok fixed it. So it turns out there is an issue somewhere with the GPClient if you use custom DNS servers, even though you might not be connected to them. My user account is a domain user. In my network settings i had set google dns to bypass the filtering used in the domain network. The problem with this seems the group policy client cannot access the policies set by the domain (even though in my case the policies are empty) and hangs the system until some timeout is gone.
I changed back the domain dns to automatic for my network adapter, and then updated the domain group policy by running this command:
gpupdate /force
In order for it to be successful i had to renew the dns with some command i found in the error log in the event viewer, but i would guess a restart would do the job as well. Now i need to find what setting controls this timeout which is absolutely stupid set to like 10 minutes.
answered Jan 16 at 9:21
TnFTnF
36117
found it in gpedit.msc, Computer ConfigurationAdministrative TemplatesSystemScripts , Specify maximum wait time for Group Policy scripts
– TnF
Jan 16 at 9:32
This policy setting determines how long the system waits for scripts applied by Group Policy to run. This setting limits the total time allowed for all logon, logoff, startup, and shutdown scripts applied by Group Policy to finish running. If the scripts have not finished running when the specified time expires, the system stops script processing and records an error event.
– TnF
Jan 16 at 9:34
If you enable this setting, then, in the Seconds box, you can type a number from 1 to 32,000 for the number of seconds you want the system to wait for the set of scripts to finish. To direct the system to wait until the scripts have finished, no matter how long they take, type 0. This interval is particularly important when other system tasks must wait while the scripts complete. By default, each startup script must complete before the next one runs.
– TnF
Jan 16 at 9:34
Also, you can use the ""Run logon scripts synchronously"" setting to direct the system to wait for the logon scripts to complete before loading the desktop. An excessively long interval can delay the system and inconvenience users. However, if the interval is too short, prerequisite tasks might not be done, and the system can appear to be ready prematurely. If you disable or do not configure this setting the system lets the combined set of scripts run for up to 600 seconds (10 minutes). This is the default.
– TnF
Jan 16 at 9:34
Also can confirm this is working along with custom dns no issues! You are supposedly need to set Run logon scripts synchronously policy to Disabled as well but i don't think affects this.
– TnF
Jan 16 at 9:45
add a comment |
Ok fixed it. So it turns out there is an issue somewhere with the GPClient if you use custom DNS servers, even though you might not be connected to them. My user account is a domain user. In my network settings i had set google dns to bypass the filtering used in the domain network. The problem with this seems the group policy client cannot access the policies set by the domain (even though in my case the policies are empty) and hangs the system until some timeout is gone.
I changed back the domain dns to automatic for my network adapter, and then updated the domain group policy by running this command:
gpupdate /force
In order for it to be successful i had to renew the dns with some command i found in the error log in the event viewer, but i would guess a restart would do the job as well. Now i need to find what setting controls this timeout which is absolutely stupid set to like 10 minutes.
answered Jan 16 at 9:21
TnFTnF
36117
found it in gpedit.msc, Computer ConfigurationAdministrative TemplatesSystemScripts , Specify maximum wait time for Group Policy scripts
– TnF
Jan 16 at 9:32
This policy setting determines how long the system waits for scripts applied by Group Policy to run. This setting limits the total time allowed for all logon, logoff, startup, and shutdown scripts applied by Group Policy to finish running. If the scripts have not finished running when the specified time expires, the system stops script processing and records an error event.
– TnF
Jan 16 at 9:34
If you enable this setting, then, in the Seconds box, you can type a number from 1 to 32,000 for the number of seconds you want the system to wait for the set of scripts to finish. To direct the system to wait until the scripts have finished, no matter how long they take, type 0. This interval is particularly important when other system tasks must wait while the scripts complete. By default, each startup script must complete before the next one runs.
– TnF
Jan 16 at 9:34
Also, you can use the ""Run logon scripts synchronously"" setting to direct the system to wait for the logon scripts to complete before loading the desktop. An excessively long interval can delay the system and inconvenience users. However, if the interval is too short, prerequisite tasks might not be done, and the system can appear to be ready prematurely. If you disable or do not configure this setting the system lets the combined set of scripts run for up to 600 seconds (10 minutes). This is the default.
– TnF
Jan 16 at 9:34
Also can confirm this is working along with custom dns no issues! You are supposedly need to set Run logon scripts synchronously policy to Disabled as well but i don't think affects this.
– TnF
Jan 16 at 9:45
add a comment |
Ok fixed it. So it turns out there is an issue somewhere with the GPClient if you use custom DNS servers, even though you might not be connected to them. My user account is a domain user. In my network settings i had set google dns to bypass the filtering used in the domain network. The problem with this seems the group policy client cannot access the policies set by the domain (even though in my case the policies are empty) and hangs the system until some timeout is gone.
I changed back the domain dns to automatic for my network adapter, and then updated the domain group policy by running this command:
gpupdate /force
In order for it to be successful i had to renew the dns with some command i found in the error log in the event viewer, but i would guess a restart would do the job as well. Now i need to find what setting controls this timeout which is absolutely stupid set to like 10 minutes.
answered Jan 16 at 9:21
TnFTnF
36117
Ok fixed it. So it turns out there is an issue somewhere with the GPClient if you use custom DNS servers, even though you might not be connected to them. My user account is a domain user. In my network settings i had set google dns to bypass the filtering used in the domain network. The problem with this seems the group policy client cannot access the policies set by the domain (even though in my case the policies are empty) and hangs the system until some timeout is gone.
I changed back the domain dns to automatic for my network adapter, and then updated the domain group policy by running this command:
gpupdate /force
In order for it to be successful i had to renew the dns with some command i found in the error log in the event viewer, but i would guess a restart would do the job as well. Now i need to find what setting controls this timeout which is absolutely stupid set to like 10 minutes.
answered Jan 16 at 9:21
TnFTnF
36117
answered Jan 16 at 9:21
TnFTnF
36117
answered Jan 16 at 9:21
TnFTnF
36117
answered Jan 16 at 9:21
TnFTnF
36117
36117
found it in gpedit.msc, Computer ConfigurationAdministrative TemplatesSystemScripts , Specify maximum wait time for Group Policy scripts
– TnF
Jan 16 at 9:32
This policy setting determines how long the system waits for scripts applied by Group Policy to run. This setting limits the total time allowed for all logon, logoff, startup, and shutdown scripts applied by Group Policy to finish running. If the scripts have not finished running when the specified time expires, the system stops script processing and records an error event.
– TnF
Jan 16 at 9:34
If you enable this setting, then, in the Seconds box, you can type a number from 1 to 32,000 for the number of seconds you want the system to wait for the set of scripts to finish. To direct the system to wait until the scripts have finished, no matter how long they take, type 0. This interval is particularly important when other system tasks must wait while the scripts complete. By default, each startup script must complete before the next one runs.
– TnF
Jan 16 at 9:34
Also, you can use the ""Run logon scripts synchronously"" setting to direct the system to wait for the logon scripts to complete before loading the desktop. An excessively long interval can delay the system and inconvenience users. However, if the interval is too short, prerequisite tasks might not be done, and the system can appear to be ready prematurely. If you disable or do not configure this setting the system lets the combined set of scripts run for up to 600 seconds (10 minutes). This is the default.
– TnF
Jan 16 at 9:34
Also can confirm this is working along with custom dns no issues! You are supposedly need to set Run logon scripts synchronously policy to Disabled as well but i don't think affects this.
– TnF
Jan 16 at 9:45
add a comment |
found it in gpedit.msc, Computer ConfigurationAdministrative TemplatesSystemScripts , Specify maximum wait time for Group Policy scripts
– TnF
Jan 16 at 9:32
This policy setting determines how long the system waits for scripts applied by Group Policy to run. This setting limits the total time allowed for all logon, logoff, startup, and shutdown scripts applied by Group Policy to finish running. If the scripts have not finished running when the specified time expires, the system stops script processing and records an error event.
– TnF
Jan 16 at 9:34
If you enable this setting, then, in the Seconds box, you can type a number from 1 to 32,000 for the number of seconds you want the system to wait for the set of scripts to finish. To direct the system to wait until the scripts have finished, no matter how long they take, type 0. This interval is particularly important when other system tasks must wait while the scripts complete. By default, each startup script must complete before the next one runs.
– TnF
Jan 16 at 9:34
Also, you can use the ""Run logon scripts synchronously"" setting to direct the system to wait for the logon scripts to complete before loading the desktop. An excessively long interval can delay the system and inconvenience users. However, if the interval is too short, prerequisite tasks might not be done, and the system can appear to be ready prematurely. If you disable or do not configure this setting the system lets the combined set of scripts run for up to 600 seconds (10 minutes). This is the default.
– TnF
Jan 16 at 9:34
Also can confirm this is working along with custom dns no issues! You are supposedly need to set Run logon scripts synchronously policy to Disabled as well but i don't think affects this.
– TnF
Jan 16 at 9:45
found it in gpedit.msc, Computer ConfigurationAdministrative TemplatesSystemScripts , Specify maximum wait time for Group Policy scripts
– TnF
Jan 16 at 9:32
found it in gpedit.msc, Computer ConfigurationAdministrative TemplatesSystemScripts , Specify maximum wait time for Group Policy scripts
– TnF
Jan 16 at 9:32
This policy setting determines how long the system waits for scripts applied by Group Policy to run. This setting limits the total time allowed for all logon, logoff, startup, and shutdown scripts applied by Group Policy to finish running. If the scripts have not finished running when the specified time expires, the system stops script processing and records an error event.
– TnF
Jan 16 at 9:34
This policy setting determines how long the system waits for scripts applied by Group Policy to run. This setting limits the total time allowed for all logon, logoff, startup, and shutdown scripts applied by Group Policy to finish running. If the scripts have not finished running when the specified time expires, the system stops script processing and records an error event.
– TnF
Jan 16 at 9:34
If you enable this setting, then, in the Seconds box, you can type a number from 1 to 32,000 for the number of seconds you want the system to wait for the set of scripts to finish. To direct the system to wait until the scripts have finished, no matter how long they take, type 0. This interval is particularly important when other system tasks must wait while the scripts complete. By default, each startup script must complete before the next one runs.
– TnF
Jan 16 at 9:34
If you enable this setting, then, in the Seconds box, you can type a number from 1 to 32,000 for the number of seconds you want the system to wait for the set of scripts to finish. To direct the system to wait until the scripts have finished, no matter how long they take, type 0. This interval is particularly important when other system tasks must wait while the scripts complete. By default, each startup script must complete before the next one runs.
– TnF
Jan 16 at 9:34
Also, you can use the ""Run logon scripts synchronously"" setting to direct the system to wait for the logon scripts to complete before loading the desktop. An excessively long interval can delay the system and inconvenience users. However, if the interval is too short, prerequisite tasks might not be done, and the system can appear to be ready prematurely. If you disable or do not configure this setting the system lets the combined set of scripts run for up to 600 seconds (10 minutes). This is the default.
– TnF
Jan 16 at 9:34
Also, you can use the ""Run logon scripts synchronously"" setting to direct the system to wait for the logon scripts to complete before loading the desktop. An excessively long interval can delay the system and inconvenience users. However, if the interval is too short, prerequisite tasks might not be done, and the system can appear to be ready prematurely. If you disable or do not configure this setting the system lets the combined set of scripts run for up to 600 seconds (10 minutes). This is the default.
– TnF
Jan 16 at 9:34
Also can confirm this is working along with custom dns no issues! You are supposedly need to set Run logon scripts synchronously policy to Disabled as well but i don't think affects this.
– TnF
Jan 16 at 9:45
Also can confirm this is working along with custom dns no issues! You are supposedly need to set Run logon scripts synchronously policy to Disabled as well but i don't think affects this.
– TnF
Jan 16 at 9:45
add a comment |
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.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1394743%2fwin10-1803-will-take-7-10-minutes-to-restart-shutdown-just-after-a-fresh-boot-p%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
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
Have you already tried to disable the Fast Startup function to see if that helps?
– Run5k
Jan 16 at 0:21
@Run5k - Wouldn't that make the system take longer to boot?
– Ramhound
Jan 16 at 0:31
@Ramhound, logically that should be the case. However, it also sounds like it's possible his hardware/OS configuration is having problems that could be related to similar capabilities that the Fast Startup function typically modifies. From my perspective, the principles of "troubleshooting 101" would seem to dictate that it might be wise to eliminate that possibility, since the OP apparently hasn't tried that yet. If the problem persists, it is very easy to turn back on again.
– Run5k
Jan 16 at 2:04
@Run5k Yes that is the first option i disable in any work PC, win10 junk. Also from the performance log and indicators it seems the pc doesn't do any work, it just waits:/ could be a miss-configured service if i were to guess possibly a microsoft one (since i've disabled the others)..i could update to 1809 and hope for the best but i want to stay away longer so microsoft fixes all their bugs
– TnF
Jan 16 at 2:13
Fast Startup absolutely is not "Windows 10 junk". If you have disabled the required files for Windows to boot quickly (i.e hibernation.sys, pagefile.sys, and swapfile.sys) that might explain your performance issues.
– Ramhound
Jan 16 at 2:29