Windows 10: Windows 10 gets attacked with a disk repair in a multi-boot setup.

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?

:)

 

Is there a way to keep Windows 10 from altering MBR on other drives in my sytem?

If the repair you got at restart was a Disk Check, this is common for WIndows 10 in multi-boots. Only if it becomes chronic do you need to take steps to troubleshoot turning off Fast Start but not necessarily the popular Hibernate feature.
Even then it is symptomatic of other problems which need to be repaired and not caused merely by Fast Start.


I think in that you may be mistaken. The problem with Fast Startup has been known to the Linux community since Windows 8 came out. Having experienced it first hand, with catastrophic data loss on a perfectly good drive, I wouldn't suggest to anyone that
it was worth taking the risk to leave Fast Startup activated. Any drive can become defective but as you said, Disk Checks are
common in Windows 10 multi-boots. That's a fairly clear indication that the problem centers on the presence of Windows 10 in the boot mix. Further evidence implicating Fast Startup is that warm booting between OS's, which does not invoke Fast Startup
functionality, also does not generate Disk Check errors. If other problems requiring repair
were the actual cause of the Disk Check errors then those errors would continue to appear regardless of whether or not the computer is booted into a different OS. To put it another way, if
other problems caused the Disk Check errors they wouldn't suddenly stop happening altogether after Fast Startup was disabled.

 

PC shuts down during boot up and when initializing any OS Setup

'AMD Athlon 64 x2 (dual-core) 4400 CPU' system shuts down upon initializing windows 10 and
Ubuntu setups.

System DOES boot SUCCESSFULLY from a DOS 1.4MB floppy, runs Fdisk, Format, etc etc. Can view directory structures of all attached drives (Floppies, HDs and CDs/DVDs). The current drive setup is one internal floppy drive A:, zero SATA drives, and a
single IDE ATA Controller with a 98 HD as master, and a DVD-RW as slave - all three drives recognized and accessible at the DOS prompt and at boot time.

We boot a Windows 7 (64 bit) setup disk, get to the 'Blue Fish" splash, and immediately afterwards the system shuts down.

We boot a Windows 10 (64 bit) Setup disk, get to the Blue Window splash, then the small circling donut of dots appears, and just before the first installation dialog appears, the system immediately
shuts down

Ubuntu Linux (64 bit) boots successfully into the setup, we select install, system immediately shuts down.

Lastly, a windows 98 hard drive (that boots into Safe Mode properly on another motherboard) boots to the startup menu options, you select 'safe mode with (or without) networking support', gets to the last 'multi(0)disc(0)
...' entry and immediately shuts down just before the 98 splash screen.

The last 98 command is: multi(0)disk(0)rdisk(0)partition(1)\windows\system32\drivers\agp440.sys which yields the shutdown. All prior "multi(0)..." commands are successful. When we Pause the multidisc commands
just before the last command (...agp440.sys), and then press enter to continue, we get the blue screen of death:

STOP: 0x0000007b (0xf789e528, 0xc0000034, 0x00000000, 0x00000000)

Bing search using the above STOP string yielded many diagnostic 'opinions', none of which worked for THOSE submitters with this same error. Everything From: "incorrect Master on SATA / incorrect Slave on ATA" BS, 'disable/re-enable
raid array' (no RAID here), To: "reinstall everything" suggestions which all failed.

CMOS is set to defaults for maximum compatibility. Have tried many different configurations.

MotherBoard is PcChips A13G+ - Two matching 1GB DDR2 DIMMs

Keep in mind - this is NOT an operating system error - the error occurs no matter which setup or existing OS is tried. Ubuntu/Win7 dual boot is the ultimate target.

Missing somethingk simple here ... Thankx

 

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 and Windows 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.

 

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.

 

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.

 

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.

http://answers.microsoft.com/en-us/insider/forum/insider_wintp-insider_files/file-system-interoperability-in-multiple-boot/73992e8f-0810-4766-96e5-7634808fb97a