I have been having problems for about a week or so where it keeps popping up
with errors in my
c:\users\loginname\AppData\Local\Microsoft\Windows\TemporaryInternetFiles\Content.IE5\T28GTS27
folder (with the error files as stuff like msnmgr.exe, cmd.exe, and other
programs I run). It says to run chkdsk to fix it, and so I schedule a chkdsk
run (has to go on restart), but no matter what I try, I cannot get it to run.
I've checked that the dirty bit is set, I've booted to safe mode, I've run
msconfig to change it to boot into diagnostic mode, I've tried to find the
recovery mode when booting with the DVD (I can't seem to find it, since I
only have an upgrade DVD). I've tried just deleting the file, but it can't,
since it's corrupted.

I've searched many places for solutions, but nothing I have tried seems to
be able to get chkdsk to run and fix my corrupt files. Does anyone know of a
way to be able to force chkdsk to fix my files, or at least know of some
other equivalent program which can fix these files? Thanks for any help.

Are you scheduling CHKDSK /f from inside Command Prompt after opening it
with Run as Administrator?
--
Paul


"UWHabs" wrote:
[color=blue]
> I have been having problems for about a week or so where it keeps popping up
> with errors in my
> c:\users\loginname\AppData\Local\Microsoft\Windows\TemporaryInternetFiles\Content.IE5\T28GTS27
> folder (with the error files as stuff like msnmgr.exe, cmd.exe, and other
> programs I run). It says to run chkdsk to fix it, and so I schedule a chkdsk
> run (has to go on restart), but no matter what I try, I cannot get it to run.
> I've checked that the dirty bit is set, I've booted to safe mode, I've run
> msconfig to change it to boot into diagnostic mode, I've tried to find the
> recovery mode when booting with the DVD (I can't seem to find it, since I
> only have an upgrade DVD). I've tried just deleting the file, but it can't,
> since it's corrupted.
>
> I've searched many places for solutions, but nothing I have tried seems to
> be able to get chkdsk to run and fix my corrupt files. Does anyone know of a
> way to be able to force chkdsk to fix my files, or at least know of some
> other equivalent program which can fix these files? Thanks for any help.[/color]

Yeah, I've had it scheduled with both the command prompt and through
selecting it from the properties dialog box on my c: drive. Never seems to
want to run (except when using no command line options, but then it just runs
and says, "you have errors on this volume").

"PaulB" wrote:
[color=blue]
> Are you scheduling CHKDSK /f from inside Command Prompt after opening it
> with Run as Administrator?
> --
> Paul
>
>
> "UWHabs" wrote:
>[color=green]
> > I have been having problems for about a week or so where it keeps popping up
> > with errors in my
> > c:\users\loginname\AppData\Local\Microsoft\Windows\TemporaryInternetFiles\Content.IE5\T28GTS27
> > folder (with the error files as stuff like msnmgr.exe, cmd.exe, and other
> > programs I run). It says to run chkdsk to fix it, and so I schedule a chkdsk
> > run (has to go on restart), but no matter what I try, I cannot get it to run.
> > I've checked that the dirty bit is set, I've booted to safe mode, I've run
> > msconfig to change it to boot into diagnostic mode, I've tried to find the
> > recovery mode when booting with the DVD (I can't seem to find it, since I
> > only have an upgrade DVD). I've tried just deleting the file, but it can't,
> > since it's corrupted.
> >
> > I've searched many places for solutions, but nothing I have tried seems to
> > be able to get chkdsk to run and fix my corrupt files. Does anyone know of a
> > way to be able to force chkdsk to fix my files, or at least know of some
> > other equivalent program which can fix these files? Thanks for any help.[/color][/color]

Are you opening the command prompt with "Run as Administrator"?
--
Paul


"UWHabs" wrote:
[color=blue]
> Yeah, I've had it scheduled with both the command prompt and through
> selecting it from the properties dialog box on my c: drive. Never seems to
> want to run (except when using no command line options, but then it just runs
> and says, "you have errors on this volume").
>
> "PaulB" wrote:
>[color=green]
> > Are you scheduling CHKDSK /f from inside Command Prompt after opening it
> > with Run as Administrator?
> > --
> > Paul
> >
> >
> > "UWHabs" wrote:
> >[color=darkred]
> > > I have been having problems for about a week or so where it keeps popping up
> > > with errors in my
> > > c:\users\loginname\AppData\Local\Microsoft\Windows\TemporaryInternetFiles\Content.IE5\T28GTS27
> > > folder (with the error files as stuff like msnmgr.exe, cmd.exe, and other
> > > programs I run). It says to run chkdsk to fix it, and so I schedule a chkdsk
> > > run (has to go on restart), but no matter what I try, I cannot get it to run.
> > > I've checked that the dirty bit is set, I've booted to safe mode, I've run
> > > msconfig to change it to boot into diagnostic mode, I've tried to find the
> > > recovery mode when booting with the DVD (I can't seem to find it, since I
> > > only have an upgrade DVD). I've tried just deleting the file, but it can't,
> > > since it's corrupted.
> > >
> > > I've searched many places for solutions, but nothing I have tried seems to
> > > be able to get chkdsk to run and fix my corrupt files. Does anyone know of a
> > > way to be able to force chkdsk to fix my files, or at least know of some
> > > other equivalent program which can fix these files? Thanks for any help.[/color][/color][/color]

Hi UW--

1) Are you typing the Y as in the instructions to run at next boot?
2) I'd opt for chkdsk /R because R implies (includes) chkdksk/F and in
practice they don't have to be upper case--I just did that to be clear.

CH

"UWHabs" <UWHabs@discussions.microsoft.com> wrote in message
news:068ADF3E-920E-4E7F-943C-D7C4805DEAB2@microsoft.com...[color=blue]
> Yeah, I've had it scheduled with both the command prompt and through
> selecting it from the properties dialog box on my c: drive. Never seems
> to
> want to run (except when using no command line options, but then it just
> runs
> and says, "you have errors on this volume").
>
> "PaulB" wrote:
>[color=green]
>> Are you scheduling CHKDSK /f from inside Command Prompt after opening it
>> with Run as Administrator?
>> --
>> Paul
>>
>>
>> "UWHabs" wrote:
>>[color=darkred]
>> > I have been having problems for about a week or so where it keeps
>> > popping up
>> > with errors in my
>> > c:\users\loginname\AppData\Local\Microsoft\Windows\TemporaryInternetFiles\Content.IE5\T28GTS27
>> > folder (with the error files as stuff like msnmgr.exe, cmd.exe, and
>> > other
>> > programs I run). It says to run chkdsk to fix it, and so I schedule a
>> > chkdsk
>> > run (has to go on restart), but no matter what I try, I cannot get it
>> > to run.
>> > I've checked that the dirty bit is set, I've booted to safe mode, I've
>> > run
>> > msconfig to change it to boot into diagnostic mode, I've tried to find
>> > the
>> > recovery mode when booting with the DVD (I can't seem to find it, since
>> > I
>> > only have an upgrade DVD). I've tried just deleting the file, but it
>> > can't,
>> > since it's corrupted.
>> >
>> > I've searched many places for solutions, but nothing I have tried seems
>> > to
>> > be able to get chkdsk to run and fix my corrupt files. Does anyone
>> > know of a
>> > way to be able to force chkdsk to fix my files, or at least know of
>> > some
>> > other equivalent program which can fix these files? Thanks for any
>> > help.[/color][/color][/color]

When the computer starts, it calls autochk.exe to see if a drive is 'dirty'
(has the 'dirty bit' set) or if a scan has been scheduled. There is a
problem sometimes with autochk.exe. Try running autochk.exe in windows from
the command line (as an administrator). You will get an error, but look at
what the error says. If it says something about not running in Win32 mode,
it's probably normal. However, if the error message says "Program too big to
fit in memory," the autochk file might be corrupt, and no matter how many
times you schedule chkdsk to run, it won't if autochk is corrupt. When I
replaced the file, chkdsk worked again.
Here is the post I wrote about this:
"
Ahah!

Okay, I got the no-scan-on-startup problem fixed on my computer. Credit
definately goes to the blogger who posted on this topic. I'll add the link,
but know that the first 3/4 of the article includes some frustrated
profanity. In a nutshell the stupid autochk.exe file is corrupted somehow,
so all you do is replace it. This takes some work in Vista, but it worked
for me. My computer scanned! I believe this was the real problem because my
computer used to scan itself, but wouldn't after a while. There is a very
significant chance the problem came from a microsoft hotfix. I'll leave it
to them to figure out if that's what happened or which hotfix, etc... All I
care about is my computer scans itself without recovery console :) So here
are the steps to fix this problem in Vista... the only problem is you will
need a windows XP Install disk (I'll explain why...)

Go to C:\Windows\System32
Right click on Autochk.exe -> Properties
Click the Security tab, then click Advanced (button)
On the new window 'Advanced Security Settings for Autochk.exe' click the
'Owner' tab
Below the box labeled 'Change owner to:' click 'Edit...'
In the new window, under 'Change owner to:' select yourself (or the
Administrators group), then click OK
Close all property windows for autochk.exe, then go back to (right click)
Properties->Security
Click 'Edit...'
On the window 'Permissions for Autochk.exe' select the Administrators group,
then under 'Allow' click the 'Full Control' checkbox
Click OK and close the property windows
Ok...NOW you can rename autochk.exe to autochk_old.exe (that took a lot of
work!)

Now, I looked at Vista's installation DVD. All of the system files are
tucked nicely into 1 .wim file. This is a windows image file, and I'm not
sure how to pull the files out of it, so I just grabbed a handy XP
installation CD. The autochk.exe file is located at
(DriveLetter):\I386\AUTOCHK.EXE

Copy the AUTOCHK.EXE file from the XP installation disk to
C:\WINDOWS\SYSTEM32\AUTOCHK.EXE and you should be good to go!

I'll recontact Dell with this information, apparently other (non-Dell) users
are having this problem too.

Oh, yeah, the site where I found the solution:
"http://www.suehappycowboy.org/blog/?p=112" Thanks very very much!

dutchscout

PS As a followup, I searched online for 'how to open a wim file' in order to
get the vista 'version' AUTOCHK.EXE from the install.wim file on the install
disk. The process seems a little complicated, but there is a toolkit from
Microsoft for it. I'm probably just going to stick with the XP version until
there is a hotfix for this problem. The Microsoft toolkit for .wim files is
called the Windows Automated Installation Kit (WAIK) and is mostly for system
administrators. If you want to, though give it a try and let me know how it
goes! You might want to read this first:
[url]http://www.windowsitpro.com/Article/ArticleID/94616/94616.html[/url]
"

There are other possibilities as well. Make sure the registry entries for
autochk are correct. There is a MS Knowledge Base article on this (160963)
at
[url]http://support.microsoft.com/default.aspx/kb/160963/EN-US/[/url]
it's about using the program chkntfs which schedules disk scans and can
exclude a drive from being checked at startup.
Basically, the program modifies an entry in the registry which runs autochk.
The entry is in
HKEY_LOCAL_MACHINE\SYSTEM\CURRENTCONTROLSET\CONTROL\Session Manager
and the default value is
BootExecute:REG_MULTI_SZ:autocheck autochk *
the autocheck autochk * part is the actual value, BootExecute is the name of
the value, and REG_MULTI_SZ is the type of value it is.


Overall, I hope this helps!

dutchscout

"WBurchnall" wrote:
[color=blue]
>
> Yes, I am running the command in an administrator command prompt and
> with the /f parameter
>
>
> --
> WBurchnall
>[/color]

Thanks for the advice, but I read that post and tried it before without
success. Still doesn't work for me. Anyone have a suggestion to try?

Matt

"Dutchscout" wrote:
[color=blue]
> When the computer starts, it calls autochk.exe to see if a drive is 'dirty'
> (has the 'dirty bit' set) or if a scan has been scheduled. There is a
> problem sometimes with autochk.exe. Try running autochk.exe in windows from
> the command line (as an administrator). You will get an error, but look at
> what the error says. If it says something about not running in Win32 mode,
> it's probably normal. However, if the error message says "Program too big to
> fit in memory," the autochk file might be corrupt, and no matter how many
> times you schedule chkdsk to run, it won't if autochk is corrupt. When I
> replaced the file, chkdsk worked again.
> Here is the post I wrote about this:
> "
> Ahah!
>
> Okay, I got the no-scan-on-startup problem fixed on my computer. Credit
> definately goes to the blogger who posted on this topic. I'll add the link,
> but know that the first 3/4 of the article includes some frustrated
> profanity. In a nutshell the stupid autochk.exe file is corrupted somehow,
> so all you do is replace it. This takes some work in Vista, but it worked
> for me. My computer scanned! I believe this was the real problem because my
> computer used to scan itself, but wouldn't after a while. There is a very
> significant chance the problem came from a microsoft hotfix. I'll leave it
> to them to figure out if that's what happened or which hotfix, etc... All I
> care about is my computer scans itself without recovery console :) So here
> are the steps to fix this problem in Vista... the only problem is you will
> need a windows XP Install disk (I'll explain why...)
>
> Go to C:\Windows\System32
> Right click on Autochk.exe -> Properties
> Click the Security tab, then click Advanced (button)
> On the new window 'Advanced Security Settings for Autochk.exe' click the
> 'Owner' tab
> Below the box labeled 'Change owner to:' click 'Edit...'
> In the new window, under 'Change owner to:' select yourself (or the
> Administrators group), then click OK
> Close all property windows for autochk.exe, then go back to (right click)
> Properties->Security
> Click 'Edit...'
> On the window 'Permissions for Autochk.exe' select the Administrators group,
> then under 'Allow' click the 'Full Control' checkbox
> Click OK and close the property windows
> Ok...NOW you can rename autochk.exe to autochk_old.exe (that took a lot of
> work!)
>
> Now, I looked at Vista's installation DVD. All of the system files are
> tucked nicely into 1 .wim file. This is a windows image file, and I'm not
> sure how to pull the files out of it, so I just grabbed a handy XP
> installation CD. The autochk.exe file is located at
> (DriveLetter):\I386\AUTOCHK.EXE
>
> Copy the AUTOCHK.EXE file from the XP installation disk to
> C:\WINDOWS\SYSTEM32\AUTOCHK.EXE and you should be good to go!
>
> I'll recontact Dell with this information, apparently other (non-Dell) users
> are having this problem too.
>
> Oh, yeah, the site where I found the solution:
> "http://www.suehappycowboy.org/blog/?p=112" Thanks very very much!
>
> dutchscout
>
> PS As a followup, I searched online for 'how to open a wim file' in order to
> get the vista 'version' AUTOCHK.EXE from the install.wim file on the install
> disk. The process seems a little complicated, but there is a toolkit from
> Microsoft for it. I'm probably just going to stick with the XP version until
> there is a hotfix for this problem. The Microsoft toolkit for .wim files is
> called the Windows Automated Installation Kit (WAIK) and is mostly for system
> administrators. If you want to, though give it a try and let me know how it
> goes! You might want to read this first:
> [url]http://www.windowsitpro.com/Article/ArticleID/94616/94616.html[/url]
> "
>
> There are other possibilities as well. Make sure the registry entries for
> autochk are correct. There is a MS Knowledge Base article on this (160963)
> at
> [url]http://support.microsoft.com/default.aspx/kb/160963/EN-US/[/url]
> it's about using the program chkntfs which schedules disk scans and can
> exclude a drive from being checked at startup.
> Basically, the program modifies an entry in the registry which runs autochk.
> The entry is in
> HKEY_LOCAL_MACHINE\SYSTEM\CURRENTCONTROLSET\CONTROL\Session Manager
> and the default value is
> BootExecute:REG_MULTI_SZ:autocheck autochk *
> the autocheck autochk * part is the actual value, BootExecute is the name of
> the value, and REG_MULTI_SZ is the type of value it is.
>
>
> Overall, I hope this helps!
>
> dutchscout
>
> "WBurchnall" wrote:
>[color=green]
> >
> > Yes, I am running the command in an administrator command prompt and
> > with the /f parameter
> >
> >
> > --
> > WBurchnall
> >[/color][/color]

My computer was unable to do error checking (chkdsk) and errors began to
accumulate. System restore did not go back far enough to restore this
function. System File Check identified a corrupt system file "autochk.exe"
that sfc was unable to repair. Instead of doing a clean install, I was able
to do an Upgrade Install that preserved my programs, devices, settings, etc.
(see John Barnett Windows MVP).

I wanted to replace my corrupt system file with a good one from the Vista
Install DVD without having to do a complete install, but was unable to do
this until now. From multiple sources including contributors on Vista
Communities, Windows IT Pro, How-To Geek, and Vistax64 Forum, I have put
together a tutorial on how to access files from your Vista Install DVD that
you can use to replace corrupt files in your OS. See the link below:

[url]http://www.vistax64.com/tutorials/86959-access-vista-install-dvd-files.html[/url]

System File Check will identify corrupt system files that it can't repair
(see CBS.log). You can replace your corrupt files with good copies from the
Vista Install DVD. Many thanks to those who contributed to this solution.


"brink" wrote:
[color=blue]
>
> UWHabs;331634 Wrote:[color=green]
> > I have been having problems for about a week or so where it keeps
> > popping up
> > with errors in my
> > c:\users\loginname\AppData\Local\Microsoft\Windows\TemporaryInternetFiles\Content.IE5\T28GTS27
> > folder (with the error files as stuff like msnmgr.exe, cmd.exe, and
> > other
> > programs I run). It says to run chkdsk to fix it, and so I schedule a
> > chkdsk
> > run (has to go on restart), but no matter what I try, I cannot get it
> > to run.
> > I've checked that the dirty bit is set, I've booted to safe mode, I've
> > run
> > msconfig to change it to boot into diagnostic mode, I've tried to find
> > the
> > recovery mode when booting with the DVD (I can't seem to find it, since
> > I
> > only have an upgrade DVD). I've tried just deleting the file, but it
> > can't,
> > since it's corrupted.
> >
> > I've searched many places for solutions, but nothing I have tried seems
> > to
> > be able to get chkdsk to run and fix my corrupt files. Does anyone know
> > of a
> > way to be able to force chkdsk to fix my files, or at least know of
> > some
> > other equivalent program which can fix these files? Thanks for any
> > help.[/color]
>
> Hi UWHabs,
>
> I don't know if you tried this method, but it's work a look and try.
> Go to this link for full details:
>
> '_http://www.vistax64.com/tricks-n-tips/67612-checkdisk.html?ltr=C_'
> ([url]http://www.vistax64.com/tricks-n-tips/67612-checkdisk.html?ltr=C[/url])
>
> Hope this helps,
> Shawn
>
>
> --
> brink
>
> "Practice makes perfect, then you reinstall"
> '_www.Vistax64.com_' ([url]http://www.vistax64.com/www.Vistax64.com[/url])
> Please post feedback to help others
>[/color]