If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Rate Thread | Display Modes |
#1
|
|||
|
|||
slow restarting
When I select restart it takes 4-5 minutes to get back to the desktop. I
have no items in startup via the registry or startup items in the startup folder(s). I'm on a i7 8 cores and 32 gigs of ram and a 500 gig ssd drive and no issues with the drive having fragmentation. thnx for any tips/help |
Ads |
#2
|
|||
|
|||
slow restarting
Black Baptist wrote:
When I select restart it takes 4-5 minutes to get back to the desktop. I have no items in startup via the registry or startup items in the startup folder(s). I'm on a i7 8 cores and 32 gigs of ram and a 500 gig ssd drive and no issues with the drive having fragmentation. https://www.digitalcitizen.life/4-wa...ode-windows-10 Then time how long to boot in safe mode to the desktop. |
#3
|
|||
|
|||
slow restarting
"Black Baptist" wrote
| When I select restart it takes 4-5 minutes to get back to the desktop. https://docs.microsoft.com/en-us/sys...loads/autoruns Autoruns. The only good way to manage startup programs, services, etc. While you're there, you might want to check out: https://docs.microsoft.com/en-us/sys...als/downloads/ There are lots of useful things there. Especially Process Monitor and Process Explorer. The first lets you see what's happening on disk and in the Registry, in real time. The second is similar to task manager, but does a much better job of telling you what's running, what dependent files are loaded, etc. It's a good idea to keep copies of the tools from Sysinternals. Probably one of these days Microsoft will just remove them from online, as they do with so many things. The tools were written by one Mark Russinovich who now works for MS but originally wrote these tools and worked as an instructor at tech workshops. He's pretty much as expert as anyone gets. I still use Regmon and Filemon instead of Procmon, which incorporates both. But Procmon is slow. When you decide to freeze the output, *it* freezes for up to a minute, claiming that it's working on "disconnecting". Filemon and Regmon have no such problems, but they're no longer available. |
#4
|
|||
|
|||
slow restarting
"Mayayana" wrote in news5aj7l$t5m$1@dont-
email.me: "Black Baptist" wrote | When I select restart it takes 4-5 minutes to get back to the desktop. https://docs.microsoft.com/en-us/sys...loads/autoruns Autoruns. The only good way to manage startup programs, services, etc. While you're there, you might want to check out: https://docs.microsoft.com/en-us/sys...als/downloads/ There are lots of useful things there. Especially Process Monitor and Process Explorer. The first lets you see what's happening on disk and in the Registry, in real time. The second is similar to task manager, but does a much better job of telling you what's running, what dependent files are loaded, etc. It's a good idea to keep copies of the tools from Sysinternals. Probably one of these days Microsoft will just remove them from online, as they do with so many things. The tools were written by one Mark Russinovich who now works for MS but originally wrote these tools and worked as an instructor at tech workshops. He's pretty much as expert as anyone gets. I still use Regmon and Filemon instead of Procmon, which incorporates both. But Procmon is slow. When you decide to freeze the output, *it* freezes for up to a minute, claiming that it's working on "disconnecting". Filemon and Regmon have no such problems, but they're no longer available. Yea I've been using sysinternals apps for quite some time and they were no help in trouble shooting the long restarting problem. |
#5
|
|||
|
|||
slow restarting
VanguardLH wrote:
Black Baptist wrote: When I select restart it takes 4-5 minutes to get back to the desktop. I have no items in startup via the registry or startup items in the startup folder(s). I'm on a i7 8 cores and 32 gigs of ram and a 500 gig ssd drive and no issues with the drive having fragmentation. https://www.digitalcitizen.life/4-wa...ode-windows-10 Then time how long to boot in safe mode to the desktop. In addition, there are tools to profile the boot process, like: https://helgeklein.com/blog/2013/07/...rder-analyzer/ https://docs.microsoft.com/en-us/win...mance-analyzer Did you disable Windows 10's Fast Startup option? That sacrifices shutdown time (to record state) to make startup faster. https://lifehacker.com/enable-this-s...ter-1743697169 In your reply to Mayayana, you said you already know or tried various SysInternals' tools. Did you ever try ProcMon's boot logging? https://www.msigeek.com/6231/how-to-...s-monitor-tool http://woshub.com/using-process-moni...boot-problems/ |
#6
|
|||
|
|||
slow restarting
Black Baptist wrote:
"Mayayana" wrote in news5aj7l$t5m$1@dont- email.me: "Black Baptist" wrote | When I select restart it takes 4-5 minutes to get back to the desktop. https://docs.microsoft.com/en-us/sys...loads/autoruns Autoruns. The only good way to manage startup programs, services, etc. While you're there, you might want to check out: https://docs.microsoft.com/en-us/sys...als/downloads/ There are lots of useful things there. Especially Process Monitor and Process Explorer. The first lets you see what's happening on disk and in the Registry, in real time. The second is similar to task manager, but does a much better job of telling you what's running, what dependent files are loaded, etc. It's a good idea to keep copies of the tools from Sysinternals. Probably one of these days Microsoft will just remove them from online, as they do with so many things. The tools were written by one Mark Russinovich who now works for MS but originally wrote these tools and worked as an instructor at tech workshops. He's pretty much as expert as anyone gets. I still use Regmon and Filemon instead of Procmon, which incorporates both. But Procmon is slow. When you decide to freeze the output, *it* freezes for up to a minute, claiming that it's working on "disconnecting". Filemon and Regmon have no such problems, but they're no longer available. Yea I've been using sysinternals apps for quite some time and they were no help in trouble shooting the long restarting problem. You can use xbootmgr and xperf or xbootmgr and wpa to trace startup. Here, I compare two recent OS versions. For some reason, the one with the later patches is slower. The SSD one is slower to start than the one with a regular HDD hard drive. https://s9.postimg.org/dmso6bea7/xbootmgr_and_wpa.gif You can get a WADK kit from here. https://developer.microsoft.com/en-u...deployment-kit The thing it downloads is a stub loader. If you check the properties of the downloaded stub loader, it says what release it is. This might have been my 16299 one. http://download.microsoft.com/downlo...k/adksetup.exe Now, the whole WADK is 4GB if you download the whole thing. But the Windows Performance Toolkit is only 150MB, and is a single tick box in the stub downloader dialog box. It doesn't take too long to download the CAB and friends for that. You don't need the rest of it, for the time being. Once installed, you'll have a new folder in your Program Files for Windows Kits, and a folder below that which says "10". Somewhere down there, is xbootmgr.exe . Open an Administrator command prompt. Create a folder to dump the output. You'll need up to around 1GB of storage space. I use C:\TEMP in my examples. I made my C:\TEMP from my regular account, to make it easier to access later. cd /d C:\Program Files (x86)\Windows Kits\10 ... === CD to where xbootmgr is xbootmgr -trace boot -traceFlags BASE+CSWITCH+DRIVERS+POWER -resultPath C:\TEMP The *instant* you issue the xbootmgr call, the system will reboot. You have about five seconds warning or so. The computer will reboot, and a trace file gets dumped into C:\TEMP. For up to two minutes after reboot, there will be a dialog on the screen, telling you it's still capturing the trace. If you're bored, you can truncate the trace. Or, let it run to completion. I let my two go to completion. Then, you navigate to C:\TEMP. Right click the .etl file (the only really big file), and the open options include the new wpa.exe you have installed. Then after the file is parsed, you get graphs to look at. They're not useful graphs, but those are your diagnostic info. In my case, I can't believe that SMSS is holding up the computer, but what I notice is a "dead time" during which the LED on the SATA port stops flashing, and the CPU is probably railed doing something. I thought in my case, it might be the initialization of my RAMDisk, but I doubt that's it. Because the 16299.98 boot sequence is faster for no apparent reason. Paul |
#7
|
|||
|
|||
slow restarting
Black Baptist wrote in
: "Mayayana" wrote in news5aj7l$t5m$1@dont- email.me: "Black Baptist" wrote | When I select restart it takes 4-5 minutes to get back to the | desktop. https://docs.microsoft.com/en-us/sys...loads/autoruns Autoruns. The only good way to manage startup programs, services, etc. While you're there, you might want to check out: https://docs.microsoft.com/en-us/sys...als/downloads/ There are lots of useful things there. Especially Process Monitor and Process Explorer. The first lets you see what's happening on disk and in the Registry, in real time. The second is similar to task manager, but does a much better job of telling you what's running, what dependent files are loaded, etc. It's a good idea to keep copies of the tools from Sysinternals. Probably one of these days Microsoft will just remove them from online, as they do with so many things. The tools were written by one Mark Russinovich who now works for MS but originally wrote these tools and worked as an instructor at tech workshops. He's pretty much as expert as anyone gets. I still use Regmon and Filemon instead of Procmon, which incorporates both. But Procmon is slow. When you decide to freeze the output, *it* freezes for up to a minute, claiming that it's working on "disconnecting". Filemon and Regmon have no such problems, but they're no longer available. Yea I've been using sysinternals apps for quite some time and they were no help in trouble shooting the long restarting problem. I solved it my option to clear the pagefile was set to 1 in the registry. |
#8
|
|||
|
|||
slow restarting
Black Baptist wrote:
Black Baptist wrote in : "Mayayana" wrote in news5aj7l$t5m$1@dont- email.me: "Black Baptist" wrote | When I select restart it takes 4-5 minutes to get back to the | desktop. https://docs.microsoft.com/en-us/sys...loads/autoruns Autoruns. The only good way to manage startup programs, services, etc. While you're there, you might want to check out: https://docs.microsoft.com/en-us/sys...als/downloads/ There are lots of useful things there. Especially Process Monitor and Process Explorer. The first lets you see what's happening on disk and in the Registry, in real time. The second is similar to task manager, but does a much better job of telling you what's running, what dependent files are loaded, etc. It's a good idea to keep copies of the tools from Sysinternals. Probably one of these days Microsoft will just remove them from online, as they do with so many things. The tools were written by one Mark Russinovich who now works for MS but originally wrote these tools and worked as an instructor at tech workshops. He's pretty much as expert as anyone gets. I still use Regmon and Filemon instead of Procmon, which incorporates both. But Procmon is slow. When you decide to freeze the output, *it* freezes for up to a minute, claiming that it's working on "disconnecting". Filemon and Regmon have no such problems, but they're no longer available. Yea I've been using sysinternals apps for quite some time and they were no help in trouble shooting the long restarting problem. I solved it my option to clear the pagefile was set to 1 in the registry. You could crank down the size of the pagefile. About 512MB is as small as I'd go. My "standard" value here on all Windows installs is 1GB. I also set the pagefile to a fixed size, rather than let the system manage it. It shouldn't take long to clean a 1GB pagefile. Paul |
Thread Tools | |
Display Modes | Rate This Thread |
|
|