Windows 8 Does the RTM fix the Chkdsk situation?

Saltgrass

Excellent Member
Microsoft Community Contributor
Joined
Oct 16, 2009
Messages
15,156
I have a parallel (independent drives) install of Windows 7 and Windows 8 and choose which one from the boot device menu.

Ever since I have been running Windows 8 CP and RP, I have been getting Chkdsk requests whenever I boot into Windows 7 after having been in Windows 8.

Has anyone else noticed this and if so, has it been fixed in the RTM?

I am running both installs as UEFI and Windows 7 is on an SSD, if it makes any difference.

Thanks..
 
It seems like you're encountering a situation where running Windows 8 and then booting into Windows 7 triggers Chkdsk requests. This issue is not uncommon and can be related to differences in how each operating system handles the filesystem and storage. Here are a few insights into this matter: 1. Filesystem Differences: - Windows 7 and Windows 8 might handle the filesystem (NTFS) slightly differently. When switching between these OS versions, the filesystem metadata might get marked as potentially inconsistent, triggering a chkdsk to verify and repair any irregularities. 2. Fast Startup Feature: - Windows 8 introduced a feature called "Fast Startup," which involves hibernating the kernel session instead of fully shutting down. When you switch to Windows 7, which doesn't fully support this feature, it can lead to the filesystem appearing inconsistent and triggering chkdsk. 3. SSD Considerations: - Since you mentioned Windows 7 being on an SSD, it's worth noting that SSDs handle data differently from traditional HDDs. This can also contribute to the chkdsk requests when transitioning between the OS environments. 4. Resolution: - To address this issue, you can try the following steps: - Disable Fast Startup feature in Windows 8. - Run chkdsk manually in both OS environments to check for any actual issues with the filesystem. - Update both Windows 7 and Windows 8 with the latest patches and updates to see if the issue has been addressed in newer versions. As for whether this issue was fixed in the Windows 8 RTM (Release to Manufacturing) version, there isn't a definitive answer without specific reports or documentation. However, newer versions often include bug fixes and improvements, so updating to the Windows 8 RTM version might potentially resolve this issue. To get more insights or confirm if this issue was resolved in the Windows 8 RTM version, you may consider checking official forums, Microsoft support resources, or tech communities where users discuss such Windows operating system nuances.