Cohabitation issues with Windows 7 and Windows 10 on 2 different HDs

Hi,

On my computer, I have 2 Windows installed on 2 different SSD disks. One for Window7 boot and the 2nd one for Windows10 boot.
They are configured to boot with EFI.

C: is for the current Windows running, E: for the other system OS.
I have other classical HD for personnal data (ex : D:, F:, G, H: )

Here is my problem :

When I work on Windows 7 and need to reboot on Windows 10, a checkdisk is set automatically at startup and all disks are checked then repaired as if HD issues had been found.A reparation is launched to try to correct disk issues on a all system and data HDs, the actions are like :
- inserting an index entry with ID (xxx) into index $SDH of file (yyy)
- Replacing Invalid Security Id With Default Security Id

I encounter exactly the same problem, if I am working on W10 and need to reboot on W7.

Often, after checkdisk repair actions, my system SSD disk can not reboot anymore. It is exactly like W7 try to avoid W10 to boot, and vice versa.
(when it happens, I have to boot on the last working Windows, to restaure the last ISO I have for the other OS).

What is troubling is :
if I decide to always work on the same OS day after day, all works fine and never met any issues when restarting (at the condition I stay on the same Windows).

I have verifyed all the HD, they have no bad sectors.

I would need your expertise to understand that problem please. I would be glad to have an explanation because it seems very strange to me.

Is it possible that the current OS is writing automatically informations on the other System Disk ?

Maybe I can configure first each Windows to set Checkdisk to never start on the other System disk ?

Regards

Thank you for your reply, but I do not have any switch on my 2 SSD disks.
maybe could this be set directly on Windows ?

What I have decribe is it normal ? (one OS write somme data to the 2nd OS disk)

You just need to turn off hibernation and Windows 10 fast startup. From a Command Prompt with Admin privileges run the command:
powercfg -h off

Run it on both OSes. That will likely solve your problem.

I'm perplex, I don't undestand why the problem can not be resolved easilier.
I am probably not the only one to have a multi Windows boot, but I did not find anything over the net (any ressource or guide) about such a problem... as if I was the only one to encouter this problem :-(

May a solution could be to deactivate all automatic startup checkdisks ?

- - - Updated - - -

Thank you NavyLCDR, I love to read such a (potential) solution.
I hope it will help me.

I'm just curious... what hibernation and Windows 10 fast startup, have to do with my problems ? (if it is not too much technical ;-) )

You mentioned that Win 7 and Win 10 are on different drives. Did you detach (power or SATA cable) the running OS drive when installing the second OS on the other drive?

Please post a disk manager image so we can see what you have.
How to Post a Screenshot of Disk Management

cedico said:

Thank you NavyLCDR, I love to read such a (potential) solution.
I hope it will help me.

I'm just curious... what hibernation and Windows 10 fast startup, have to do with my problems ? (if it is not too much technical ;-) )

Try it. It should work. I'll explain why later, not at home right now.

@Megahertz, no, I did not try what you mentionned (I thought not necessary to do it as the 2 installs are disctinct on 2 different drives).

@NavyLCDR, since one hour, I can start my 2 OS without any problem (reboot one, then reboot the other)...
Your solution seems to be great but I don't want to be very happy too early ;-)

The problem was that Windows 10 fast startup will save status information regarding the system at shutdown in the hiberfil.sys file (same file used for Hibernation). This includes information about which files are open in the filesystems and other disk information. When you boot into Windows 7, Windows 7 will change some of that system information as it runs. So, when you return to Windows 10, it loads the system information it saved when previously shutdown and it will detect that some of that system status has changed, but the OS won't know why. This triggers the chkdsk action to attempt to determine why the system status changed since it was last saved.

Disabling and deleting hiberfil.sys using the powercfg -h off command also disables Windows 10 fast startup (because there is no place to store the system status information). This forces Windows 10 to do a "cold boot" each startup, and there is no saved system status to confuse the OS. Since you have an SSD, there is very little boot time lost by disabling Windows 10 fast startup, in fact it will save writes to your SSD.