csf60 Posted June 6, 2013 Report Share Posted June 6, 2013 Hello to every reader and sorry if this is not in the correct forum section.I have Windows installed in an SSD and another HDD for storage. I noticed my boot times slow to 55 seconds when plugging the 3TB HDD up from 30 seconds with only the SSD plugged. I have boot traced both cases with the Windows SDK performance tools and when I plug the HDD, autochk.exe is responsible for the delay inside the Session Manager subsection of the boot process. It takes too long checking that HDD. I have seen in plenty of forums people with a similar problem but I have seen no solution.My questions are: What does autochk exactly do to take so long? is there any way to avoid autochk from running every startup?When I go to the Session Manager registry entry: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Managerand look in the BootExecute entry, it is at the default "autocheck autochk *". I have tried to exclude every drive from being checked by writing "autocheck autochk /k C: /k D: *". I have also tried to use the command line "chkntfs /X" to disable autochk in those drives, to no avail. The only thing that worked is completely leaving blank the BootExecute entry, but I have been told this is not advisable (why?) and Windows even restores it to the default anyway after some time, so it's not a good solution.System specs if they matter (ask for more if needed):OCZ Agility 3 120GB (only 1 partition, MBR).Seagate Barracuda 7200.14 3TB (partition table is GPT, only 1 partition).Asrock X79 Extreme4 with i7-3930k and 16GB DDR3.Corsair TX650W PSU.Windows 7 Enterprise SP1 x64 (Updated to date).Avoid telling me to (because I already did):- Check BIOS is in AHCI- Check all drivers are up to date, with Intel RST, etc.- Update to latest SSD firmware.- Try a fresh Windows install.- Try plugging the drives in different SATA ports, even mix SATA3 and 6. What I did not try is the AsMedia SATA ports, but I honestly doubt that will make a difference in autochk accessing the disk.- Using the "Fsutil dirty query" I have also checked the dirty bit flag is not set in any drive.Big thank you to anyone who helps me. Quote Link to comment Share on other sites More sharing options...
csf60 Posted June 6, 2013 Author Report Share Posted June 6, 2013 I don't know what corrupted files you are talking about, but I forgot to mention I ran CHKDSK at startup in both drives and it found no errors. Quote Link to comment Share on other sites More sharing options...
snow_lightning Posted July 28, 2014 Report Share Posted July 28, 2014 I'm having a very similiar issue. Although mine is with an SSD Raid 0 array so the 78second delay caused by this service is severly hindering my reboot times. I'll be sure to post back if I find anything! Quote Link to comment Share on other sites More sharing options...
snow_lightning Posted July 28, 2014 Report Share Posted July 28, 2014 I found this thread which has a post at the bottom linking to some microsoft articles about chkntsf and the bootexec. http://social.technet.microsoft.com/forums/windows/en-US/a0d97ca5-c486-433a-a76c-886dc58b5eca/slow-win-7-bootLooks like you forgot to add the drive letter to the command to not check the boot drive. I tried this but it wouldn't work while windows is running so the next step is to try it from the windows recovery cmd prompt. I just deleted the "autocheck autochk *" and now it boots fast. I'll see how long this lasts before I need to really try it from the recovery cmd. Quote Link to comment Share on other sites More sharing options...
Belatucadrus Posted July 28, 2014 Report Share Posted July 28, 2014 Some more reading on CHKNTFS Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.