501
General Software Discussion / Re: Slow Windows load even with SSD
« Last post by Shades on February 13, 2019, 09:29 PM »Are you sure nothing crept into the startup sequence of your Windows installation?
If for instance something got placed there that insists on "phoning home", but fails to do so, that something could wait till 30 seconds before it fails and allows the startup sequence to continue. That max of 30 seconds is a remnant of the TCP protocol and this is by design. Anyway, if you have more than one of those items in that sequence, that adds up quickly. There might also be software in that sequence that want to write logging or other things to it's own database, which might not be accessible at that particular moment in the startup sequence. Such things can introduce long waiting times too.
SSD's need TRIM, not a defragger. And sufficient free space in each of the partitions you or the Windows installer created on it. 10% to 20% of free space in the partition(s) of your drive keeps the drive and the file system (NTFS most likely) much "happier".
Besides, for "funsies", you should introduce a 30 second wait into the boot sequence. In your mind that feels much longer than it actually is. Same with loading a page from the internet. No matter how fast, it quickly feels slow regardless. Yet when you start a task that you know can take time, a possible extra 30 seconds doesn't seem that bad. Why perceive the same amount of time so differently while working on a computer...
You could try to boot your system in safe mode and see if that is also slow.
When that is also the case, it is most likely you'll need to dig into Windows and its event viewer to find out what kind of errors occur in that startup sequence.
If safe mode is fast, then it is most likely that one (or more) item(s) in your startup sequence is the culprit. In any case, you should have a better idea where to start looking for the actual cause.
** edit **
Ah 4wd was faster. The suggested tools in his post are very helpful in disabling items in your startup sequence.
If for instance something got placed there that insists on "phoning home", but fails to do so, that something could wait till 30 seconds before it fails and allows the startup sequence to continue. That max of 30 seconds is a remnant of the TCP protocol and this is by design. Anyway, if you have more than one of those items in that sequence, that adds up quickly. There might also be software in that sequence that want to write logging or other things to it's own database, which might not be accessible at that particular moment in the startup sequence. Such things can introduce long waiting times too.
SSD's need TRIM, not a defragger. And sufficient free space in each of the partitions you or the Windows installer created on it. 10% to 20% of free space in the partition(s) of your drive keeps the drive and the file system (NTFS most likely) much "happier".
Besides, for "funsies", you should introduce a 30 second wait into the boot sequence. In your mind that feels much longer than it actually is. Same with loading a page from the internet. No matter how fast, it quickly feels slow regardless. Yet when you start a task that you know can take time, a possible extra 30 seconds doesn't seem that bad. Why perceive the same amount of time so differently while working on a computer...
You could try to boot your system in safe mode and see if that is also slow.
When that is also the case, it is most likely you'll need to dig into Windows and its event viewer to find out what kind of errors occur in that startup sequence.
If safe mode is fast, then it is most likely that one (or more) item(s) in your startup sequence is the culprit. In any case, you should have a better idea where to start looking for the actual cause.
** edit **
Ah 4wd was faster. The suggested tools in his post are very helpful in disabling items in your startup sequence.

Recent Posts

