CHKDSK Running on every boot of Win XP & Win7 in Multi-Boot System

Pleinair

Honorable
Mar 14, 2013
6
0
10,510
Hello Everyone,

My computer consists of two HDD's. Win XP is installed on the first one, while Win 7 is installed on the second HDD.
Recently I've installed Win 10 preview in a separate partition on the second HDD to try it out.
After I've checked Win 10 I booted up my system to start up Win 7 but for some reason it started performing a disk check of the partitions in my first HDD (the ones which belong to Win XP), stating that it is checking the drives consistency. The Check went fine with no issues found, after which the computer rebooted again. However, when I tried to start up Win 7 again, it started performing the same check once again! After awhile I just opted to skip the check and it started Win 7 normally with no issue after skipping the check.

Later on, I decide to boot up my Win XP to do some work there. To my surprise, the same process of disk check has started there as well with the same results (no issues found), only this time the situation was vice versa, with Win XP's pre-startup disk check performed on the partitions in my second HDD (the ones which belong to Win 7), with the exception of the partition which now belongs to Win 10 Preview. Needless to say that it doesn't find any issues either.
Just as with Win 7's disk check, XP's also starts to run every time I boot up my PC and opt to start up Win XP.
In response, I found myself similarly skipping the disk check and starting up Win XP just fine without any other issues.

Now for what I've tried so far to fix my problem, which didn't work:
First I started Command Prompt in Win XP and ran the "fsutil dirty query X:" command to see what it says about the different partitions. Apparently both the partitions which belong to Win 7 on my other HDD came out as "dirty", while the Win 10 Preview partition, as well as all the Win XP partitions on the first HDD came out as "NOT Dirty".
After that, I ran the "CHKNTFS /X X:" command for both partitions which are designated as dirty, so Windows doesn't check them on the next reboot into Win XP.
I rebooted my pc expecting that the disk check will not be performed this time, but to my surprise it promoted just the same for both partitions like any other time since this issue has started!
After I've skipped the Disk Check yet again, and booted up XP successfully, I've returned to Command Prompt and tried to perform the disk check manually for both dirty partitions with the "chkdsk /f /r x:" command.
The disk check went fine, just as it does during the startup of Windows, after which it showed that both partitions are no longer dirty. I booted up my pc and started Win XP again, and yet again the disk check was prompted for the same partitions. When I skipped and started up Win XP and opened up Command Prompt to check the partitions with the fsutil dirty query command, it showed both as dirty once more, as if I didn't do the manual check just earlier.

The next thing I tried was to open up the Registry Editor in Win XP and changing the boot execute value to "autocheck autochk * " in the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager sub tree. That didn't help either, and the disk check is prompted every boot up just the same.

I have no idea what else can I try to stop these constant disk checks from starting every boot up, and I don't wish to uninstall Windows 10 Preview just to see if it will stop them from reoccurring.
If any expert has any idea what might be the cause of these repetitive disk checks or know how to stop them from reoccurring please help me.

Thank you for your time reading this! :)
 

I think I clicked the solution button too early by mistake >_<

I'm sorry but the article clearly states that it applies solely to Win 95 & 98.
The issue I'm experiencing is in both XP and Win 7 so this isn't strictly an XP issue either.
lastly, reinstalling Win XP is out of the question for me since it stores hundreds of my programs which I use very often and in addition to that it's an OEM version which came without the original installation disk.
 
sounds like somehow having windows 10 corrupted a file to continuously to do this. Since this is just a preview and not the final product, i would remove it to test the theory out since there are still bugs in the system that can effect other drives including windows defender screwing up a few files.

Thats what i usually get with continuing chckdsk, either that, can also be a simple flash drive, i have a few flash dives that keeps wanna ckdsk each time and won't stop till i unplug it, like my parrents pc, my brothers flash drive is in and there pc will be stuck frozen showing the product pc name loading there over 5 hrs doing nothing to boot up. since u say windows 10 is connected to ur windows 7 hdd side, disconnect that drive all together and boot windows xp, after that if things turn out ok throu, dissconnect the xp drive and just have windows 7/10 hdd connected n boot windows 7, if issues do arise then i suggest trash windows 10 and get extra $50 for a 500gb or 1tb drive for that price to have w indows 10 on if u really going to use it.

10 is ok but sticking to windows xp, windows 7 and my hackintosh pc's. they need to stop going after Apple and there dam apps after the failed attempt windows crap (8).

Other suggestion to test windows 10 without the drivers n such on a physical pc, i would just run it off vmware.

ps, careful for laptops, my laptop n driver of mine of a integrated my intel wifi hotspot doesn't work, neither in windows 8/8.1.