I have been testing the Consumer Preview and Release Preview and this seems to happen in both.
When dual booting 7 and 8, and booting back into Windows 7 after running Windows 8, a Chkdsk is requested 80% of the time.
Situation for this one test, 3 hard drives in GPT configuration.
SSD Windows 7 UEFI install
320 GB Windows 8 UEFI install
2 TB Data drive.
The system is setup with a parallel (independent) installs so the Windows 7 and Windows 8 drives have EFI system partitons. I boot to Windows 7 by default and select the Windows 8 Boot Manager during the Boot Device Menu to boot Windows 8.
I have been running Windows 7, without the Windows 8 drive connected, fine for some time, and Chkdsk is never required. Attaching the Windows 8 drive and booting into Windows 7 works most of the time. Booting into Windows 8 worked fine, but the Windows 7 drive (SSD) was not visible.
I booted back into Windows 7 after shutting down, and a chkdsk was requested, which I cancelled. After booting into Windows 7, the Windows 8 drive showed up fine, but when running afsutil dirty query d: command I got the following:
The file or directory is corrupted and unreadable..
The command worked fine on my Windows 7 drive and the data drive.
This has been happening for the entire time of the Windows 8 pre-releases. I normally let the chkdsk run, but once my Windows 8 User Profile was corrupted. A typical message I might see during a Chkdsk run would be:
Inserting an index entry with Id 708 into index $SDH of file 9. And messages such as this occur many times during the chkdsk.
My assumption is that there is some compatibility issue with Windows 7/Windows 8 chkdsk. If my setup is incorrect, or not allowed for some reason, please explain a way that will aleviate the chkdsk runs.
Asus P8Z77-v Pro, i7 2600k, no overclock, 8 G memory
Thanks