On boot up Win xp Pro wants to run CKDSK on my "H" Drive ths happens on each bootup but nothing is r

[Accomac]

Hello,

I will try and be as succint in my description of the problem on my
machine. It is a dual boot machine, with 3 parttions, that has XP Pro
on the C: Win 7 was on the D: and the H drive is for storage of mp3
files and photographs.

In the past 2 days whenever I boot to XP, CHKDSK wants to scan the "H"
drive, it never finds anything but it scans it anyway. Originally when
the problem started it would scan the C:\ drive too but now it's only
the "H."

I have removed Win 7 to try the Win 8 and 8.1 trial versions. In using
them I was dragging files from one OS to another, maybe that was my
mistake, I don't know. I know I moved some .jpgs to the "H" from Win
8.1 and probably Win 8 too.

Today I used Acronis to install a month old image of XP that had no
troubles. Yet on boot up it STILL wants to CHKDSK the "H" partition!

So logically I am thinking that "what remained when I installed the
image of XP made in July?" Well the only things I can think of is that
the BIOS is the same, the HD is the same, and the "H" drive is the
same. I even removed Win 8.1 to no avail. So all I have is a C and H
partition and the D is unallocated

I have looked for autoruns that may be making the call to run CHKDSK
and I don't see any in MSCONFIG, Online Armor( my firewall) or in
CCleaner or WinPatrol.

Running Avast and TrendMicro and MalwareBytes show nothing.

I will say that first on the "H" drive there is an odd folder that I
DIDN'T put there and it has the name:6fa24fa22f7c6ac1f5086d482a62d59
It contains sub folders that have an MS EULA in them in various
languages and a .dll file and an .xml. Why it's there I don't know but
i cannot copy it off the drive or delete it, not even in safe mode.

No idea if the problem is really with the H drive or not but that's
what is asking to be scanned on every boot up. If I had the space I
would move all the files from the H and move them elsewhere and format
the partition again and put it all back, excluding that silly EULA
folder. No idea how it got there and the EULA that is in English is
nothing more than giving me permission to use the MS software, it
doesn't even say what it is!

I may be entirely misinsterpreting what the cause of the continual
CHKDISK on "H",so I thought maybe someone more knowledgeable than I
could help me sort it out.

Many thanks in advance!

Accomac

 

[Paul]

Hello,

I will try and be as succint in my description of the problem on my
machine. It is a dual boot machine, with 3 parttions, that has XP Pro
on the C: Win 7 was on the D: and the H drive is for storage of mp3
files and photographs.

In the past 2 days whenever I boot to XP, CHKDSK wants to scan the "H"
drive, it never finds anything but it scans it anyway. Originally when
the problem started it would scan the C:\ drive too but now it's only
the "H."

I have removed Win 7 to try the Win 8 and 8.1 trial versions. In using
them I was dragging files from one OS to another, maybe that was my
mistake, I don't know. I know I moved some .jpgs to the "H" from Win
8.1 and probably Win 8 too.

Today I used Acronis to install a month old image of XP that had no
troubles. Yet on boot up it STILL wants to CHKDSK the "H" partition!

So logically I am thinking that "what remained when I installed the
image of XP made in July?" Well the only things I can think of is that
the BIOS is the same, the HD is the same, and the "H" drive is the
same. I even removed Win 8.1 to no avail. So all I have is a C and H
partition and the D is unallocated

I have looked for autoruns that may be making the call to run CHKDSK
and I don't see any in MSCONFIG, Online Armor( my firewall) or in
CCleaner or WinPatrol.

Running Avast and TrendMicro and MalwareBytes show nothing.

I will say that first on the "H" drive there is an odd folder that I
DIDN'T put there and it has the name:6fa24fa22f7c6ac1f5086d482a62d59
It contains sub folders that have an MS EULA in them in various
languages and a .dll file and an .xml. Why it's there I don't know but
i cannot copy it off the drive or delete it, not even in safe mode.

No idea if the problem is really with the H drive or not but that's
what is asking to be scanned on every boot up. If I had the space I
would move all the files from the H and move them elsewhere and format
the partition again and put it all back, excluding that silly EULA
folder. No idea how it got there and the EULA that is in English is
nothing more than giving me permission to use the MS software, it
doesn't even say what it is!

I may be entirely misinsterpreting what the cause of the continual
CHKDISK on "H",so I thought maybe someone more knowledgeable than I
could help me sort it out.

Many thanks in advance!

Accomac

The CHKDSK is a side effect of you multi-booting WinXP and Win8 family.

You can try this in a Windows 8 "cmd.exe" window, selecting
Run as Administrator for the cmd.exe.

powercfg /hibernate off

or you can follow this GUI recipe. I've not read this description before,
but this seems to make more sense than the theory I came up with.

http://www.pagestart.com/win8dbchkdsk121912.html

"Windows 8’s “Hybrid Boot” means that the "dirty bit" is “set” on
any additional disk drives in your computer after you have
shutdown Windows 8. Therefor the next time you boot your computer
and select Windows 7 (or XP and Vista) from the boot menu Windows
checks the status of the “dirt bit” on startup and as a result
chkdsk is automatically run to validate the integrity of each
additional disk drive and associated partitions."

HTH,
Paul

 

[Accomac]

What is drive "H:"

PS: Folder "6fa24fa22f7c6ac1f5086d482a62d5" is a remnant of a Microsoft
Update that fialed to remove the folder. If you don't have "access rights"
you will have to take Ownerhip of the folder and files below it and thenm
give your self, or a group you are a member of, full rights to delete it.

Hi David,

I shouldn't call it a drive per se it's merely a 3rd partition on the
HD. But since it appears as another drive that's what I was calling
it.The drive has only 3 partitions. C D and H.

The leftover folder has been there since November 2012 but the chkdsk
business just started yesterday or the day before. So I am dubious
that the folder is really the cause of the issue. But in an effort to
be thorough, I mentioned it. At least now I know how to remove it!

Thank you!

Accomac

 

[Accomac]

The CHKDSK is a side effect of you multi-booting WinXP and Win8 family.

You can try this in a Windows 8 "cmd.exe" window, selecting
Run as Administrator for the cmd.exe.

powercfg /hibernate off

or you can follow this GUI recipe. I've not read this description before,
but this seems to make more sense than the theory I came up with.

http://www.pagestart.com/win8dbchkdsk121912.html

"Windows 8’s “Hybrid Boot†means that the "dirty bit" is “set†on
any additional disk drives in your computer after you have
shutdown Windows 8. Therefor the next time you boot your computer
and select Windows 7 (or XP and Vista) from the boot menu Windows
checks the status of the “dirt bit†on startup and as a result
chkdsk is automatically run to validate the integrity of each
additional disk drive and associated partitions."

HTH,
Paul

Hi Paul,

I no longer even have ANY version of 7, 8 or 8.1 on my HD so I can't
really try your first suggestion. I do have an image of Win 8 that I
could potentially install on the "D" partition IE: One of 3 partitions
the C has XP on it and the D was where the various Win 7 and 8 & 8.1
resided. Right now that partition is unallocated space not even
formatted.

I agree about the hibernate setting in all versions of 8. My system
doesn't like it and when it started up there would always be an error
of some kind. I never had that trouble with 7 however, it hibernated
and slept, no matter which I chose, just fine. Sadly that's all it
seemed to do well. If it wasn't such an unpredictable thing I never
would have tried to use Win 8 or 8.1!

I haven't read the link you thoughtfully provided me and I wonder if
it tells you how to get rid of the "dirty bit". Clearly CHKDSK doesn't
find it no matter how often it runs, as it did for this session.

Oddly enough I have had the dual boot system for many months using XP
and 7 and had no ill effects. I was running Win 8 in a virtual machine
inside of 7. But then I got the brigh idea to remove 7 and install Win
8 on the partition that 7 was using. Guess that's where I went off the
rails.... <sigh> I should have stuck with the VM and ran all the
"test" versions of 8, 32 & 64 and 8.1, 32 & 64. I'd be better off I
bet!

Watch this space, I'll read your link and see what it says is the
solution to my dilemna.

Thank you!

Accomac

 

[Paul]

Hi Paul,

I no longer even have ANY version of 7, 8 or 8.1 on my HD so I can't
really try your first suggestion. I do have an image of Win 8 that I
could potentially install on the "D" partition IE: One of 3 partitions
the C has XP on it and the D was where the various Win 7 and 8 & 8.1
resided. Right now that partition is unallocated space not even
formatted.

I agree about the hibernate setting in all versions of 8. My system
doesn't like it and when it started up there would always be an error
of some kind. I never had that trouble with 7 however, it hibernated
and slept, no matter which I chose, just fine. Sadly that's all it
seemed to do well. If it wasn't such an unpredictable thing I never
would have tried to use Win 8 or 8.1!

I haven't read the link you thoughtfully provided me and I wonder if
it tells you how to get rid of the "dirty bit". Clearly CHKDSK doesn't
find it no matter how often it runs, as it did for this session.

Oddly enough I have had the dual boot system for many months using XP
and 7 and had no ill effects. I was running Win 8 in a virtual machine
inside of 7. But then I got the brigh idea to remove 7 and install Win
8 on the partition that 7 was using. Guess that's where I went off the
rails.... <sigh> I should have stuck with the VM and ran all the
"test" versions of 8, 32 & 64 and 8.1, 32 & 64. I'd be better off I
bet!

Watch this space, I'll read your link and see what it says is the
solution to my dilemna.

Thank you!

Accomac

The "dirty" bit is cleared by CHKDSK.

I've not seen anything to suggest there is a utility
that can just make it go away. Many people have asked
for such things, due to getting stuck in a loop with
the dirty bit refusing to go away (one dirty bit per partition).

The trick is to execute CHKDSK just the right way, to
clear it on its own.

*******

There is a registry key, with room for executables to be
run before the file system is mounted. The registry key
is "BootExecute" and a typical value is "autochk". The
registry key can be modified, if for example, the OS wants
C: to be scanned by CHKDSK on the next startup (before C:
is mounted). I think more than one line of stuff to do,
can be stored in that key.

BootExecute gives a way to "schedule" a check, versus
setting the Dirty bit and having autochk catch it.
Something like that. You can cancel a scheduled check,
but I think that just modifies the contents of the
BootExecute key.

In any case, you can use Regedit, and have a look for
BootExecute.

I checked mine just now. There is room in the editing
tool, for multiple lines. But all mine has today is:

autocheck autochk *

and I'm on WinXP.

*******

You can query the current state of the Dirty bit, with fsutil.

http://technet.microsoft.com/en-us/library/cc788091.aspx

fsutil dirty query C:

Have fun,
Paul

 

[Accomac]

For XP Click Start
Click Control Panel
Click Administrative Tools
Click Computer Management

Storage
Disk Management

Volume
Right Click on The Drive
Click Properties
Click Tab Tools
Error-checking
Check Now
Check mark
Automatically fix file system errors
Start
Disk Check Complete
Click Ok
Chick Ok
Chick Ok

There it Fix

Now do a Disk Defragmenter
on too...........................

Hi Hot-Text,

Your solution worked! I never should have put the various versions of
8 directly on the HD. They should have been put in a VM on the Win 7
partition instead of blowing it out and installing the 8's right onto
the "D" partition!!

Regards,

Accomac

 

[Accomac]

The "dirty" bit is cleared by CHKDSK.

I've not seen anything to suggest there is a utility
that can just make it go away. Many people have asked
for such things, due to getting stuck in a loop with
the dirty bit refusing to go away (one dirty bit per partition).

The trick is to execute CHKDSK just the right way, to
clear it on its own.

*******

There is a registry key, with room for executables to be
run before the file system is mounted. The registry key
is "BootExecute" and a typical value is "autochk". The
registry key can be modified, if for example, the OS wants
C: to be scanned by CHKDSK on the next startup (before C:
is mounted). I think more than one line of stuff to do,
can be stored in that key.

BootExecute gives a way to "schedule" a check, versus
setting the Dirty bit and having autochk catch it.
Something like that. You can cancel a scheduled check,
but I think that just modifies the contents of the
BootExecute key.

In any case, you can use Regedit, and have a look for
BootExecute.

I checked mine just now. There is room in the editing
tool, for multiple lines. But all mine has today is:

autocheck autochk *

and I'm on WinXP.

*******

You can query the current state of the Dirty bit, with fsutil.

http://technet.microsoft.com/en-us/library/cc788091.aspx

fsutil dirty query C:

Have fun,
Paul

Hi Paul,

My dirty bit was on the H partition and I used the method posted by
Hot-Text to solve it. So far I am able to boot to XP with no CHKDSK
startup, since I told it to fix the errors.

I should have stayed with what I had previously IE: XP on the C: and
Win 7 on the D with a Vbox program running Win 8. I had no trouble
that way. It would seem that should keep any dirty bits from escaping
the VM and getting on another partition.

How the bit got on my 3rd partition that has no OS on it is a mystery
to me. A virus can't jump across a partition but yet this dirty bit
seems to have done it. <scratching head>

Thanks for the information I will save it all just in case of another
screw up. All I can say is that Acronis is worth the small cost to own
it. I can easily restore the image of the Win 7 and VM with Win 8 on
it back to the D partition and go from there!

From the RUN command I was unable to try fsutil. I entered it and ran
it but it showed nothing. I did run it AFTER I had already repaired
the bit so maybe that's why or maybe it's intended for Win 7 8 or 8.1
I dunno!

Long live XP Pro!

Win 7 64 for me has been a disappointment, I should have gotten the 32
bit version I suppose.

yes Win 8 is nice and I see some things to like about it but right now
it's not a must have item. I find I can use it easily but I am always
getting some sort of error from one version or another. But I
understand that the trial versions aren't the final ones so I hope the
errors will be fixed when the release date comes. If I have serious
workd to do I always default to XP!

Cheers,

Accomac

 

[Accomac]

The "dirty" bit is cleared by CHKDSK.

I've not seen anything to suggest there is a utility
that can just make it go away. Many people have asked
for such things, due to getting stuck in a loop with
the dirty bit refusing to go away (one dirty bit per partition).

The trick is to execute CHKDSK just the right way, to
clear it on its own.

*******

There is a registry key, with room for executables to be
run before the file system is mounted. The registry key
is "BootExecute" and a typical value is "autochk". The
registry key can be modified, if for example, the OS wants
C: to be scanned by CHKDSK on the next startup (before C:
is mounted). I think more than one line of stuff to do,
can be stored in that key.

BootExecute gives a way to "schedule" a check, versus
setting the Dirty bit and having autochk catch it.
Something like that. You can cancel a scheduled check,
but I think that just modifies the contents of the
BootExecute key.

In any case, you can use Regedit, and have a look for
BootExecute.

I checked mine just now. There is room in the editing
tool, for multiple lines. But all mine has today is:

autocheck autochk *

and I'm on WinXP.

*******

You can query the current state of the Dirty bit, with fsutil.

http://technet.microsoft.com/en-us/library/cc788091.aspx

fsutil dirty query C:

Have fun,
Paul

Hi Paul

Well I looked for giggles in my registry and found my entry for
BootExecute was autocheck autochk * aswboot.exe /Mt:3230dd07806e

Whatever that means....

I was able to stop the thing from constantly checking and rechecking
by using what Hot_Text posted and I thank him for it.

Would you remove all the extra stuff behind the autochk * ???

I intend on putting the image of Win 7 64 back on the machine with the
VM running Win 8 Enterprise.

Thanks,

Accomac

 

[Paul]

Hi Paul

Well I looked for giggles in my registry and found my entry for
BootExecute was autocheck autochk * aswboot.exe /Mt:3230dd07806e

Whatever that means....

I was able to stop the thing from constantly checking and rechecking
by using what Hot_Text posted and I thank him for it.

Would you remove all the extra stuff behind the autochk * ???

I intend on putting the image of Win 7 64 back on the machine with the
VM running Win 8 Enterprise.

Thanks,

Accomac

Don't do that, until you research where the "aswboot.exe" came from.
Looks like some software wants to take advantage of the BootExecute
key. Sometimes malware does that. If you can actually find an aswboot.exe
file, you can upload it to virustotal.com .

Aha!

Aswboot belongs to Avast Antivirus. So rather than malware, it's one
of the "good guys" who is using BootExecute for early access to the
computer.

http://www.bleepingcomputer.com/filedb/aswboot.exe-41400.html

So leave that Registry entry alone! It's a good guy (by name).

You can still upload to virustotal.com if you want.
Be by nature suspicious - "trust, but verify".

Paul