Can't boot - "autochk program not found - skipping autocheck" after XP SP3

I for one appreciate the pushing (harshing) that Specimen has been doing. Only by that was John to realize the exact problem.

I have the "autochk not found" problem when booting directly into Windows (Parallels launch of BootCamp partition works) and am anxiously awaiting for an official fix from John/Parallels, though I'm not sure if I can wait and might have to try some of these other suggestions.

John, any more update to this? It's been almost a week since your last post.
 
John@Parallels said:
I would like to ask all affected users to provide output from Terminal

diskutil list
Click to expand...

My trouble's fixed, but here's mine just in case it's useful.


Last login: Fri Jun 20 08:09:54 on console
Macintosh:~ <username>$ diskutil list
/dev/disk0
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *186.3 Gi disk0
1: EFI 200.0 Mi disk0s1
2: Apple_HFS Pete Macintosh HD 153.9 Gi disk0s2
3: Microsoft Basic Data Boot Camp 32.1 Gi disk0s3
/dev/disk1
#: TYPE NAME SIZE IDENTIFIER
0: Apple_partition_scheme *160.0 Gi disk1
1: Apple_partition_map 31.5 Ki disk1s1
2: Apple_HFS <username> 160.0 Gi disk1s2
Macintosh:~ <username>$
-----------------------------------

Actual username replaced with <username> notation.
My <username> appears in the disk list. The account I'm using is secured with FileVault.

Hope this helps.

Pete
 
Boot up in Boot Camp produces "autochk" error

Here's my situation:

Parallels Build 5608
MacBook Pro 2.4Ghz, 2GB Ram
OSX 10.5.3 (fully patched)
Boot Camp 2.1 (FAT 32 partition)
Windows XP SP3 (fully patched)
NO Symantec software.

Boot into Windows XP via launching Parallels - works with no issues.

System Prefs->Startup Disk->Windows XP = system restart, Windows XP splash screen, then "autochk not found". - over and over an over....

This error did not start until Build 5608 for me.

On my iMac 3.0Gz (4GB Ram), Build 5600 - same Windows XP SP3 patch level, same OSX and Boot Camp patch level - no issues in either Boot Camp or Parallels.

Two installs - one 5600 (which works) and one 5608 (which does not) - everything else the same and installed in the same manner.

Here's my diskutil info (MacBook Pro):
dev/disk0
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *149.1 Gi disk0
1: EFI 200.0 Mi disk0s1
2: Apple_HFS Macintosh HD 116.9 Gi disk0s2
3: Microsoft Basic Data WINDOWS XP 31.8 Gi disk0s3
 
My setup is almost exactly the same as rmalay

Parallels Build 5608
MacBook Pro 2.4Ghz, 4GB Ram
OSX 10.5.3 (fully patched)
Boot Camp 2.0 (NTFS partition)
Windows XP SP3 (fully patched)
NO Symantec software.

Boot into Windows XP via Parallels - works with no issues
Boot into Windows XP directly - "autochk not found" error

I first noticed this after upgrading XP to SP3 and Parallels to 5600. I rarely boot into Windows so it might have happened previously. After I noticed this problem, I upgraded to 5608 but it didn't fix anything so I came to the forums for help.

Boot Camp is still at 2.0 and I can't upgrade to 2.1 due to this bug.

Code: 
/dev/disk0
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *232.9 Gi   disk0
   1:                        EFI                         200.0 Mi   disk0s1
   2:                  Apple_HFS Isis                    211.9 Gi   disk0s2
   3:       Microsoft Basic Data .Windows                20.7 Gi    disk0s3
 
@smudge:

Boot Camp 2.1 and Parallels 3.0.5600(or 5608) was supposed to be installed before installing SP3. :/
 
Yes, we are aware about this, but most of users didn't check that requirement, and we didn't want to call this in mind, as it was seemed to be avoiding users problem.
Developers are now trying to find workaround how to resolve situation
 
How to do clean install?

I am willing to do a clean install. What is the correct order in which to install? Is it:

1. Install Boot Camp 2.1
2. Create boot camp partition
3. Install Parallels
4. Install Windows XP SP2
5. Install Windows XP SP3

Thanks
 
Unless your Mac is really recent and the OS X DVD already comes with Boot Camp 2.1, the only way (that I know of, unless Apple has released a full BC 2.1 installer and not just a patch) to have BC 2.1 is to first install Windows XP SP2 (if it's not already installed), install the Boot Camp you got from OS X DVD and then update BC to 2.1 (after you can upgrade to XP SP3).
 
Last edited by a moderator:
boot camp loop

Hi

I'm a total noob with mac, but need to support it at my work. The user that have this problem is not at the office rite now so I can't controll what versions he have of boot camp or parallels.

He doesn't use the boot camp much, but sometimes he need to boot it. He had Tiger installed and I just upgraded to Leopard. And sp3 got installed from GPO.

Problem is now that parallels work fine and boot camp goes in a endless restart loop.
Can someone point out to me what steps i need to take to get his boot camp working?
It wasn't me that sat up bootcamp and parallels so I wish not to install XP again. And if you need to know what versions i have could to point me to where I can find that information.
 
We are trying to figure out exact steps or provide executable fix, but for now:
Try to uninstall SP3 from Parallels Desktop
Try to login though Boot Camp, if you are able, install Boot Camp 2.1 update, while in Boot Camp, install SP3
If you are still unable to login through Boot Camp, perform Windows repair, install Boot Camp 2.1 update install SP3
 
Please post here if you figure out an executable fix. You might work one out before I get the macbook to my office.
 
Reinstalling Parallels worked for me

I thought I did things in the correct order, but maybe not. After I had SP3 installed, I could boot using Parallels, but I could not boot directly into Windows from power on (got autochk msg). Then I removed the Windows partition, created a new Windows partition, reinstalled XP SP2 and upgraded to SP3. Then I could boot directly into Windows, but got the pesky autochk msg when I used Parallels. Then I removed and reinstalled Parallels and everything is working fine now. I'm happy!
 
I couldn't wait any longer so I tried some of the suggestions and now it is working perfectly. Here is what I did.

Boot into Parallels and uninstalled SP3
Boot into native Windows via BootCamp
Downloaded and installed Bootcamp 2.1 Update, reboot
Installed Windows SP3 Update, reboot
Installed a few other patches/updates via Windows Update, shutdown.
Boot into OSX and started Parallels
Tried booting the Bootcamp partition but got the autochk error. Swore out loud startling the sleeping dog.
Cleared the Parallels info from the bootcamp partition via the Parallels Configuration Editor.
Started Windows in Parallels, no errors.

Just to be sure, rebooted into native Windows again. No errors.
Just to be more sure, rebooted into OSX, ran Parallels, launched Windows.

SUCCESS!

So it seems to be a problem with the Parallels info on the Bootcamp partition before SP3 and/or BootCamp 2.1. After uninstalling/reinstalling SP3/BC2.1 then removing Parallels info and letting it reinstall the info on the next install fixed the autochk error.

Hope this helps the developers and users.
 
I'm sorry. This doesn't work in my case. I followed it step by step but the problem

"can't find autochk"

with starting the boot camp partition still exists.
 
You must log in or register to reply here.
Back
Top