chkdsk cannot find autochk.exe in recovery console

  • Thread starter Thread starter Uwe
  • Start date Start date
U

Uwe

Hi,

a Windows XP Home Edition computer doesn't start anymore. I know that the
partition is OK, even my root directory and - with one exception - all
directories what I tried. The one exception is the \windows\system32
directory.

Because I don't have the XP CD anymore I downloaded the Setup Disks for
Floppy Boot Install
(http://www.microsoft.com/downloads/...FamilyID=E8FE6868-6E4F-471C-B455-BD5AFEE126D8),
booted into the recovery console and tried to check the drive with chkdsk.
Because
1) \windows\system32 is damaged,
2) chkdsk needs autochk.exe in order to run and
3) the setup floppies are unfortunately designed in that way that they don't
contain autochk.exe,
chkdsk fails to start and asks for an autochk.exe. (It is a harassing design
of the setup floppies!)

I looked for a second download for autochk.exe but I didn't find one. Is
there a package containing autochk.exe anywhere that can be used to be copied
onto the setup floppies so that chkdsk can work without access to
\windows\system32? I know that there are some downloads of some autochk.exe
versions in the internet but I am very cautious with using unknown versions
of system files, in this case especially for repairing the boot drive. The
danger of malfunctions is much to big. I think there should be an official
Microsoft version of autochk.exe what belongs to the chkdsk in the setup
start floppies.

Who knows of a way to prepare the setup start floppies so that I can use
chkdsk without access to autochk.exe in \windows\system32? I am not sure that
at least the chkdsk would work with the XP CD. Perhaps I will run into the
same problem. I would be so easy with setup floppies containing autochk.exe!

Thanks.
 
if you can borrow a
windows xp cd, then
you can boot up with
it and log into the
repair/recovery console.

then at the disk prompt
you can run the following
commands>:

chkdsk /f
fixboot
fixmbr

then "exit", remove cd
and try to boot normally
again.

however, because it
seems you are eluding
to the infamous error
message pertaining
to a corrupted registry
hive.

in which case you will
have to utilize the repair
console again to begin
the process of restoring
your registry.

it's a two phase process,
the first being via the
recovery console and
using a basic registry.

the second phase is
then booting up with
that basic registry and
replace it via the desktop.

http://support.microsoft.com/kb/307545



--

db·´¯`·...¸><)))º>
DatabaseBen, Retired Professional
- Systems Analyst
- Database Developer
- Accountancy
- Veteran of the Armed Forces
 
Thank you for your reply. Basically I am familiar with the procedure. I was
able to solve the start problem in the mean time with the help of NTFS4DOS
Personal by Avira
(http://www.free-av.de/de/tools/11/avira_ntfs4dos_personal.html). It is a
freeware only for personal use and no longer supported. That's why I am still
interested in a solution of the problem to get the start floppies of XP
working with chkdsk. I want to have the possibility to solve such problems
anytime on any computer with and without the XP CD. Sometimes I want to help
other people immediately (also in companies, i.e. commercially) and they
often don't have their CD's too.

NTFS4DOS has a chkdsk command what was able to start from floppy. chkdsk
found errors, corrected them after some time and I was able to start my
computer. No more hassles, problems or procedures. It was really easy. This
must also be possible with Microsoft tools! The only problem is to find a
correct autochk.exe and to integrate it onto the setup floppies. Any help is
further appreciated. I am also looking for such a possiblity for Vista. I
again and again wonder why we don't get such simple solutions from Microsoft.
In the case of boot problems it would be really easy to download a basic
setup program what allows to boot into the recovery console and what allows
to invoke chkdsk without any access on system files on a possibly damaged
hard disk!
 
glad you found a fix.

fortunately, there will
always be more than
one way to solve issues
with the o.s.

I don't always recommend
freeware, but sometimes
there are little options not
to do so.

primarily, I will always
suggest a method provided
by microsoft because we
can be assured that much
testing has been done to
ensure quality.

in respect to your floppy
method option, most people
don't have floppy drives.

however, I will look forward
to analyzing the method you
utilized and perhaps provide
your technique to others
as well.
--

db·´¯`·...¸><)))º>
DatabaseBen, Retired Professional
- Systems Analyst
- Database Developer
- Accountancy
- Veteran of the Armed Forces
 
Back
Top