Before installing Win 10 preview onto an HDD I disconnect the other bootable drives lest they be molested by the Windows 10 install process. After installing the preview and updating everything I shutdown the PC and re-attach the other HDDs. My default boot drive has Windows 8.1 on it, and I get to the Preview using the BIOS boot menu. That's the setup I like. The problem is at some point while booting to Win 7 or win 8.1 the OS detects the drive with the Windows 10 Preview and starts a disk repair on it. Windows 10 never survives. Files get lost, system errors pop up, and the OS get left in an unrecoverable state. Not only that, the OS that launched the disk repair can corrupt itself leaving both OSes unbootable. What would cause this?
I don't know but had a similar situation. I did as you did and unplugged my windows 8.1 drive. Installed 10 to a second drive and then plugged the 8.1 drive back in. As soon as I tried to boot up to 8.1 it did a repair on that install. Every thing worked after that and it didn't do it again after. There was nothing wrong with my 8.1 install, not as far as I know, I was using it everyday. I've since ditched the dual boot and I am in no hurry to try it again.
If this disk repair is a feature of Windows boot process, search on how you can disable it. Alternatively, you can try to completely shutdown Windows 10 , then leave it to complete the repair. My mind is going to "Fast Boot" mode (Hibernate/Shutdown) and it gets corrupted everytime it tries to check and fix the drive.
I have hibernation disabled from the command prompt, Windows 8.1 and 10. it's one of the first things I do on a clean install.
Once auto repair starts on windows 10 it's pretty much corrupted. I had installed Windows 10 on another PC weeks ago. The auto repair inevitably returned and I left it to complete. As a result both Windows 10 andWindows 7 were made unrecoverable. Next time I'll try disabling "Fast boot" on the Windows 10 install if you think that is the reason why it gets attacked with a disk repair when booting up another OS.If this disk repair is a feature of Windows boot process, search on how you can disable it. Alternatively, you can try to completely shutdown Windows 10 , then leave it to complete the repair. My mind is going to "Fast Boot" mode (Hibernate/Shutdown) and it gets corrupted everytime it tries to check and fix the drive.
I'm dual bootng Windows 8.1.1 and Windows 10 without any problems. I have each OS on separate drives. I turned off fast start in Win 8 and Win 10. I also hid the OS drives from each other with the reg hack that was posted here. Windows 8 is hidden from Windows 10 and Windows 10 is hidden from Windows 8.
I have been dual booting each Windows 10 build with my 8.1, never received a problem. (knocking on the fake wooden desk). I have both OS's installed on separate SSD's, maybe that is my saving grace. I have tried using various builds as my main OS, but always revert back to 8.1. Simply more stable for me. I prefer Windows 7, but Windows 8 has some fixes for my AMD CPU, an 8 core 8150.
Cheers,
Ray,
The Old Marine
Semper Fi
I'm thinking this might be the reason not of the "repair attack" itself, but for the corruption during the repair. If it completes once without problems, probably it will never bother you again with this repair. When a disk is in hibernate state, it's somewhat inaccessible. You can read but not write in this disk. Because of that, my first thought was the "Fast Boot" feature could cause such problems.Next time I'll try disabling "Fast boot" on the Windows 10 install if you think that is the reason why it gets attacked with a disk repair when booting up another OS.
I was encountering much the same problems -- until I disabled FastStartup on BOTH Win8.1 and Win10. Since then, I've not run into any forced CHKDSKs not any filesystem corruption problems. Also, be sure to choose ShutDown when switching OSs. IF you choose Restart (as I as doing), FastStartup kicks in again and the problems resume.Once auto repair starts on windows 10 it's pretty much corrupted
I've stumbled across a very interesting thread as to why this happens. It looks like there's a slight compatibility issue between NTFS on Windows 10 preview and older versions of Windows. When another volume is accessed from within Windows 10 preview, or vice versa, that volume is marked 'dirty'. So you can imagine what will go wrong if you boot to the same OS twice in a row. It's will try to 'fix' that other volume, and my 'fix' I mean corrupt.
