Dataloss

[MChrisp]

Hi everyone, I need your help! My Girlfriend has lost some Data for her PhD thesis... 

 

I am not even sure, if this is the write category but I suspect it is. I have in my girlfriends PC 2 SSDs and one HDD.

1. SSD = WIN10

2. SSD = WIN7

3. HDD= Backup for WIN10 via Versionhistory

 

I "installed" WIN 7 via a clone of an old HDD of a Laptop. Worked fine. I did not include WIN7 in Bootmanager of WIN10 nor the other way around. Is that necessary? I just booted WIN7 or 10 from Bios, if needed.

 

A lot of times, the PC (WIN10 or WIN7) the PC checked the drives for errors after start. This seems odd, as the drives new or not older than a view years or so.

This was so on the old Laptop, which I copied the WIN7 from. I thought, this was actually a HW issue. This also continued in the new PC, in which I build the old HDD with win7. So I naturally hurried and got a new ssd and cloned it. Worked fine, but the drive checking did not stop.

 

Now actually 4 files disappered. Three were copied from an USB-Stick in WIN7 into the WIN10 drive. They were definetly there in WIN7. Restart in WIN10, they were gone. Also another file disappeared. They also were not restorable with a recovery tool. (Not existing, so could not even try recovering it)

 

I than proceeded to restart again and acutally let the storage checking proceed (in WIN7). It restartet after that in WIN10 and 2 of the 3 lost files were there again... 3rd one still missing.

 

I naturally also used the in WIN10 included Tool for checking drives, but that said, all is fine.

 

I now included WIN7 in Bootmanager of WIN10 and did a bit of testing and I do not get this behavior anymore. But it is hard to test.

 

Has anyone an idea, what is going on? Or another tip for restoring the lost file?

[homeap5]

About checking drives - it's normal that after using win7, win10 will check drive etc. This is fine kind of different handle chkdsk and dirty bit.

 

Also - disable fast boot in win10.

[MChrisp]

8 minutes ago, homeap5 said:

About checking drives - it's normal that after using win7, win10 will check drive etc. This is fine kind of different handle chkdsk and dirty bit.

 

Also - disable fast boot in win10.

Ok, I thought that the dirty bit might be the problem. Maybe it is fixed after I included WIN7 in Bootmanager of WIN10. But at least now I know that this is an actual thing.

I will disable fast boot. But why? 

 

Thanks for the answer.

[homeap5]

Fast boot do not fully shut down computer. It's kind of hibernation. Who knows what changes you'll want to made using win7, so is best to fully boot win10 from zero imo. But it's probably not really necessary.