Share via

Why is Autocheck.exe taking 3+ minutes at startup

Anonymous
2015-06-10T23:00:09+00:00

Hi;

I recently set up a new build (specs at the end), and after installing all of the win 7 updates that were available, I started having a recurring problem of sloooooooooow startup.  I seem to have two options now, and neither of them are ideal, which is why I am posting here.

1.  I can reboot and wait the 3-4 minutes, and when windows starts, all seems fine

2.  I can remove autocheck autochk * from the BootExecute registry entry and then it boots fine, but then windows is locked for 3 minutes or so after logon. Nothing responds.  After that it runs fine.

In investigating this situation, I first blamed SMSSinit, but I later discovered that this routine is more of a chaperone for the other processes that are running prior to Winlogon taking over the chaperone duties.  Using MS SDK, I have found that it is Autochck.exe that is the culprit, taking 200-220 seconds on each boot.  I have done the following (and more) to address this issue:

1.  Checked all drives for dirty bits - none found

2.  Ran check disk on all connected drives - no errors found

3.  Disabled Checkdisk in "task manager"

4.  Disabled Checkdisk in registry (when I do this, I get scenario 2 from above)

5.  Restarted the computer in every way I can imagine

6.  Tried a windows repair with my UEFI stick (no love - says it found no issues)

7.  Tried reverting to an earlier restore point (I only had one and it did not solve)

8.  Removed all windows updates I had done (and all Win updates are set to manual only)

9.  Grabbed autochk.exe from another install and put it in the Windows/system32 folder (after taking proper ownership of both) with a new name autochk_safe.exe and pointed registry BootExecute entry to that checkdisk application (thought that was a clever try that I found at another forum)

10.  Ran sfc /scannow - no problems found

11.  Set the BootExecute registry entry to " autocheck autochk /k:C /k:G /k:M /k:R /k:S * ".  I tried this (which should skip autocheck at startup for drives C, G, M, R and S) but it changed nothing.  And that is a disable of all the drives in the system.

If anyone knows what steps I can take here to stop this extended autocheck and not suffer other consequences, it sure would be appreciated.  And yes, I know I can do a full wipe and reinstall, but that should not be necessary as something is causing this and it should be identifiable and resolvable IMO.

Cheers~

C

Build Specs:

Windows 7 Pro 64 bit SP1 (all critical updates installed until I removed them in an attempt to resolve this issue)

ASUS X99 Sabertooth Mobo

i7-5820k CPU

M.2 SM951 Samsung 256GB (Main drive)

Corsair ForceGT 128GB SSD (secondary drive and scratch disk when running on main)

4TB WD Red

4x4TB WD Red in RAID5 configuration (fully initialized and running quite well)

Crucial RAM - 2 x 8GB - 2133Mhz

FireGL Pro V8700 GPU (the elder in this system from 2010)

EVGA Supernova 1000 G2 PSU

Windows for home | Previous Windows versions | Windows update

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments
Answer accepted by question author
  1. Anonymous
    2015-06-15T10:35:45+00:00

    At that stage of the installation the setup program hasn't yet copied any files or written a basic setup registry.  You can see the disk because the drivers are loaded into memory to allow the setup program to see the disks, at that point you had not even yet told the setup program where to install Windows, how would it have known where to put the files?

    This may be helpful:

    SysInternals LoadOrder v1.0

    (Works on Windows 7)

    John

    0 comments No comments

14 additional answers

Sort by: Most helpful
  1. Anonymous
    2015-06-13T01:45:11+00:00

    Thanks for the reply John.  I will give that a try.  I can't get past the idea that there is a startup call for this (other than the registry BootExecute) that gives this some parameters and that is what should be adjusted to get rid of this problem. 

    Does anyone know of a way to trace what exactly Autocheck is doing at any given time (i.e. scanning D:\ or sitting idle waiting for command)?  If I could see this kind of detail, maybe I could find a solution that does not disable this feature but instead, allows it to perform correctly.

    Thanks

    C

    0 comments No comments
  2. Anonymous
    2015-06-11T12:48:27+00:00

    You can replace the Autochk.exe file with a nonexecutable file also called Autochk.exe in order to bypass the Autochk process, not something I really recommend but as long as Windows can boot you can always run chkdsk on dismounted data volumes, you just won't be able to correct any errors on the Windows volume.  I've not tried this on Windows 7 and I'm not sure how well Windows File Protection (WFP) will take this attempt to change the file in question.

    John

    0 comments No comments
  3. Anonymous
    2015-06-11T00:26:24+00:00

    Hi John;

    Thanks for the quick reply.  I went through every BIOS field and did not see computrace anywhere.  With a little research, it looks like that feature is for laptops mostly to use in conjunction with LoJack for theft tracing.  This box is a desktop. I do not see this setting.

    BTW, I am running BIOS 1702 on this board which is the most up to date BIOS from ASUS for the X99 Sabertooth mobo.

    Cheers~

    C

    0 comments No comments
  4. Anonymous
    2015-06-10T23:27:57+00:00

    Possibly caused by Computrace, is this enabled in the firmware (BIOS/UEFI)?

    John

    0 comments No comments