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 windows 10 staartup
Windows 10 takes about 5 minutes to start up. There are only 2
entries in the startup list: itunes helper and powerpanel personal edition. during starat up there is extremely heavy disk usate. any ideas? |
Ads |
#2
|
|||
|
|||
slow windows 10 staartup
LL Rost wrote:
Windows 10 takes about 5 minutes to start up. There are only 2 entries in the startup list: itunes helper and powerpanel personal edition. during starat up there is extremely heavy disk usate. any ideas? When was the last time you removed temporary files? Do you use CCleaner? |
#3
|
|||
|
|||
slow windows 10 staartup
LL Rost wrote:
Windows 10 takes about 5 minutes to start up. There are only 2 entries in the startup list: itunes helper and powerpanel personal edition. during starat up there is extremely heavy disk usate. any ideas? How full is the C: drive? Has it always been this slow? If not what have you changed recently? |
#4
|
|||
|
|||
slow windows 10 staartup
LL Rost wrote:
Windows 10 takes about 5 minutes to start up. There are only 2 entries in the startup list: itunes helper and powerpanel personal edition. during starat up there is extremely heavy disk usate. any ideas? ProcMon from sysinternals.com , can trace both the shutdown and the startup of the computer. And it delivers the results as two .PML files. While the system is still running, you set up ProcMon. If you select the option to do a boot trace, ProcMon at that point will place a copy of "procmon23.dll" or similar, into the system folder. The file has the hidden attribute set, to make it harder to see. In addition, the ProcMon program does not remove the DLL at any later point in time. Once ProcMon is set up, you can leave a trace running as the computer is about to shutdown. At shutdown, the running trace should be saved to a file. When the computer boots, the ProcMon program is not running. However, the procmon23.dll is working at this point in time, and collecting ETW events. If you wait a couple minutes, most of the early services should have started. Now, at the two minute mark after the screen appears after the reboot, you can run the ProcMon program again. It will "offer to save something", and that is your boot trace. Maybe you save it as "boottrace.pml" or so. At any later time, you can open boottrace.pml and examine the sequence of events. Microsoft also makes a couple of separate tracing packages. The main advantage of the tracing programs, is better graphical representations of activity. However, in most cases, you don't need "fancy", as much as you need "names". A text listing is good enough for certain kinds of failures. The main problem with the XBootMgr/XPerf or WPA, is that Services retain their disguise. You might know some SVCHOST with PID 1234 did it, but for a given boot cycle, you have no idea what's inside PID 1234 on that run. ******* To give an example of an unexpected result, when Win10 boots here, there is a ~20 second period during which there is no disk I/O, and the CPU is railed on at least one core. In the past, this has been shown to be "proportional" to the amount of RAM on the machine. Suggesting something is being done involving RAM. Things like Windows Defender can waste time, by scanning the System folder for malware. Each and every boot. It might also scan Program Files folder. The in-box CHKDSK could be running during that time. But really, if you want "half-an-answer", it's a matter of learning to use the tracing tools as best you can. I can't say I'm completely satisfied with my skill level on the topic. I still see mysteries here. That "20 second dead period" wasn't present on the first version of Windows 10. The slowness is an "improvement" and is why we wish for service packs twice a year, and tends to make a joke out of the fact I'm booting an SSD for Win10. Faster storage will not help! Whatever disease it's got, can't be fixed by hardware. Needs a clue-by-four upside the head. Paul |
#5
|
|||
|
|||
slow windows 10 staartup
On Thu, 4 Oct 2018 18:48:26 +0200, Weatherman
wrote: LL Rost wrote: Windows 10 takes about 5 minutes to start up. There are only 2 entries in the startup list: itunes helper and powerpanel personal edition. during starat up there is extremely heavy disk usate. any ideas? When was the last time you removed temporary files? Do you use CCleaner? weekly |
#6
|
|||
|
|||
slow windows 10 staartup
On Thu, 4 Oct 2018 18:13:36 -0000 (UTC), Chris
wrote: LL Rost wrote: Windows 10 takes about 5 minutes to start up. There are only 2 entries in the startup list: itunes helper and powerpanel personal edition. during starat up there is extremely heavy disk usate. any ideas? How full is the C: drive? Has it always been this slow? If not what have you changed recently? c: drive is 80% free it has not always been this slow. The internet is also running at 50% capacity for about 4 weeks. Only changes have been windows 10 updates. |
Thread Tools | |
Display Modes | Rate This Thread |
|
|