Windows 10: Forced checkdisk after switching between OSs in dual boot

I remember reading a solution to this issue, but can't find it anymore, perhaps someone can let me know.

I have Windows 10 installed on a separate drive in a machine that otherwise runs Windows 7. When I was installing 10, I had all other hard drives disconnected, so in order to boot into 10 I have to select the boot drive in BIOS, otherwise the system boots to 7.

The problem is (appeared after one of the recent updates, but I'm not sure whether it's relevant) that if I want to boot to 7 after using 10 (i.e. reboot the machine and follow the default), sometimes Windows 7 wants to check my hard drives for errors. I have a lot of drives, so that procedure takes a while. Can anyone tell me how to get rid of it? I know, I can press any key to stop checkdisk, but first of all I would have to do it for each drive and then next time I boot the machine it will want to check the disks again.

:)

 

Windows 10 0xc000000f

Pressing F9 worked for me. It seems windows is between OSs - doesn't have the boot record for the previous OS and cannot find the new boot record. F9 booted back in to windows, completed the update and all is well after that.

 

How to remove dual boot on Windows 10?

Original title: Remove dual boot

I have a two OSs (dual boot) on my PC. Each is windows 10. One upgraded from windows 8.1 and the second was upgraded from windows 7.

I want to remove one of them. How can I do it in a safe way?

 

Something like disable hibernate Hibernate - Enable or Disable - Windows 7 Help Forums

 

If you have fast startup turned on try turning it off and see if that helps.

 

Do NOT get rid of it! If the filesystem is corrupt enough that CHKDSK is being forced on restart, there are other problems at play. Disabling that will only damage the filesystem more.

I'm running Win8.1 on one SSD and Win10TP on a second SSD, and every other day or so, I get a forced CHKDSK of the Win 10TP drive when I boot into Win8.1.

Yes, it's a pain, but if you ignore it or suppress it, eventually, the OS will no longer boot -- I know, I had this happen to me.

 

I do have this issue but I don't bother with it. I just keep cancelling it. I have 4 hard drives but it detects all the partitions so I just cancel everything. No big deal. I hope it will go away on later builds.

 

I had this problem when I was dual booting Win 7 and the beta versions of Win 8. CHKDSK would run when I went from Win 8 to Win 7. I just let CHKDSK do it's thing. It stopped when I stopped dual booting and switched to Win 8.

 

If you are copying files back/forth between W7 and W10 or even W8.1 might be your problem. It's been mentioned in the Technet about possible NFTS incompatibilities between different OSs. I stopped doing so and used a USB flash drive as a go between. I think 9926 with updates is better than 9879. I've just went back to passing MS Outlook PST files yesterday and didn't get any CHKDSK yet. That's the only files that I've tried so far.

I actually pasted a corrupt PST file to W7 and lost a months worth of saved email.

 

happens to me as well ,2 drives ,one ssd with win8.1 and one hdd with win10 9926.

 

I'm not sure what you mean by copying between W7 and W10. My setup is such that I have OSs on separate drives (two SSDs for two OSs) and then all data are on other drives. I never use the My Documents and other automatically generated folders. Do you mean that different OSs would read the NTFS tables on some data drives differently?

 

NTFS/W7 might not be the same as W10/NTFS.

I use Paragon HDM15S for back ups. I was trying to recover my MS Outlook PST files. I wasn't trying to pull them from a W7 back up but from W10 build 9879 to the build 9926 and it came up with a "file architecture" mismatch. I then really messed up I tried to send them to my W7 drive. It booted up to a blue screen only saying one thing, non registered copy of W7. I used a restore point to recover the W7 OS. Later I was able to pull the files if sent to a USB flash drive that was formatted NTFS "only". I've done this many times with W7 and never ran into this. This tells me that the NTFS file structure wasn't/isn't the same in W10 but recent updates "may" have corrected some but "maybe" not all issues.

 

Evidently, this IS a problem -- as I mentioned it some time ago, since I "share" a data partition between Win8.1 and Win10, and was noticing that when I downloaded something in Win8.1 to the shared volume, when I later booted into Win10, the file was not there.

I've had to resort to copying to USB to do the file "transfers", as well.

I guess it's good to know, now, that it's not just my system that is having this problem.

 

I discovered this during another thread I started and was going to mention it but the whole thread got deleted.

OT a bit: Are you retaining your restore points in W10? The default "might" be set to OFF but I lose mine as soon as I boot into W7.

 

Evidently, this IS a problem -- as I mentioned it some time ago, since I "share" a data partition between Win8.1 and Win10, and was noticing that when I downloaded something in Win8.1 to the shared volume, when I later booted into Win10, the file was not there.

I've had to resort to copying to USB to do the file "transfers", as well.

I guess it's good to know, now, that it's not just my system that is having this problem. I never experienced that issue. My data drives are available to both W7 and W10 and there is never a problem of finding files in either OS. The only reminder of which OS was used to download or create a given file is in the file "owner" - the username from another OS is of course not recognized and in the ownership column in file explorer you just see a long alphanumeric.

However, when switching between OSs sometimes the checkdisk is triggered. This is very annoying since it takes a long time to go through all the drives in my system. Once again, this issue has come up already during W8 testing and there was a useful solution, but I can't find the relevant thread in either eightforums or sevenforums. My solution was to install the second OS with all other drives unplugged and it worked for a while, but somehow with the latest build of W10 this does not work anymore, suggesting that this was not a solution in the first place.