Computer Hope
Microsoft => Microsoft Windows => Windows Vista and 7 => Topic started by: Geek-9pm on July 09, 2018, 10:37:32 PM
-
The topic title is fro this:noot thing with
http://www.tomshardware.com/forum/id-3386873/windows-dual-boot-issue-chkdsk.html
The problem i have is that every time i boot Windows the CHKDSK utility keeps running on my D drive (the SSD with Windows 10) - so far i've cancelled this every time however i suspect it will catch me out sooner or later and i'll be back into the crash loop situation again. Is there any way i can resolve this as i do not want to give up either version of Windows as i have games that only run on Win 10 and other games that run better on Win 7 (plus i like the interface of Win 7).
Me too! :'(
Apparently this is not an isolated thing nor is it about hardware. There is some kind of problem with doing dual boot with windows 10 and another Windows .
From Microsoft:
https://answers.microsoft.com/en-us/insider/forum/insider_wintp-insider_perf-insiderplat_pc/chkdsk-problem-in-windows-7-after-parallel-install/c7bb1c5c-18f8-45da-8689-3d47952ca5d6
Unfortunately windows 10 has the bad idea to turn on fast startup by default and this corrupts external drives attached when you reboot as well as other operating systems in a dual boot system.
You need to boot into windows 10 and turn fast startup off.
Click start, Control Panel, Power Options ...
My question is this: Have you also found this issue when doing a dual-boot?
If so, what is the best solution?
-
just curious, why dual boot and have all these issues when you can just setup a virtual machine within Win10 using the inbuilt Hyper-V?
-
Mark, to date I have never done virtual machine. It look s to hard to me.
I have been using dual-boot for maybe 15 years and only recently have I had the odd thing with check disk on boor. I seems to be a flaw in recent versions of Windows 10.
Is there an easy way to implement a VM in Windows 10? :)
-
It can only be implemented with Pro, Enterprise or Education versions of Win 10. If you have Home your out of luck.
-
It can only be implemented with Pro, Enterprise or Education versions of Win 10. If you have Home your out of luck.
Oh No! I got the home version! :'(
-
Doing more research, this is an old issue and has never been fixed. I been fixed in the sense that the problem is corrected in such a way as to not compromise the integrity of either OS in a dual boot system.
Some posts elsewhere state when you shut down Windows 10, the partition is put into a a state the other OS sees as as unreliable. So the check disk program starts and finds not real errors. In at least one forum somebody said this is harmful.
I have gone through a long lit of forum this claim to have the answer tony to find they don't have the answer. These posts start soon after Windows 10 was introduced. If there really was a fix, surely Microsoft would have documented it for the benefit of Windows 7 users.
But I am still open to suggestions. My best guess is to disable the check disk program in Windows 7. I am not sure how to do that :-\
-
Do you have "Fast Boot" disabled in Windows 10? If not then When WIndows 10 is shut down it's more like hibernation; which means some file system structures might be affected and detected as incorrect when booting into another version of Windows.
Additionally Windows 8 and later changed the NTFS Log format for Metadata. Windows 7 only supports version 1.1 of the CLFS but the new version is 2.1. Windows 10 sees "bad' entries as per CLFS 2.1 and Windows 7 see's "bad" entries as per CLFS 1.1.
-
Thanks.
I was unaware the NTFS had been altered. That makes sense and would ex-plain why good disks are being checked.
So if I want tohare data between two OS, maybe I shooed use a fat32 drive?
-
autocheck is being run because a dirty bit has been identified on the drive / partition in question. Unfortunately, autocheck does not run with the /r switch - it only checks the drive, it doesn't repair it. Assuming "D" Drive is the partition or drive being checked, what you need to do is open a command prompt within Windows and type: chkdsk d: /r (and then press enter). As long as it isn't your system partition, checkdisk will run. It may tell you the drive needs to be unmounted. Just say "yes". If it IS the system partition, you will be asked if you want to run checkdisk on the next boot. Say "yes" and reboot. Checkdisk will run and attempt to repair the problem. Hopefully it will be fine after that.
-
You should have the OS's installed to seperate HDD's as suggested months ago...
-
You should have the OS's installed to seperate HDD's as suggested months ago...
Yes, I have also tried that. Had to find where the third SATA port was on the motherboard. The BIOS calls it SATA 5and I have no idea where the others are.
It only works if the drives and not 'see' each other. If bother drives are enable in the BIOS, then Windows 10 will decide to mess with everything it can find.
I have now turned off the fast boot thing in Windows 10 and today it seems to fix the problem. I am going to try several re boots and switch between systems just to see. As I write this I am in Windows 10.
-
Disable Fast Boot is hard to find. :'(
https://answers.microsoft.com/en-us/windows/forum/windows8_1-performance/fast-startup-how-to-disable-if-its-causing/f9a4a2d0-104d-42dc-9946-4a2e13c0a348
The above is the latest,I think, explanation from Microsoft.
In this article we're going to discuss how to disable Fast Startup. Why? In many systems it is known to cause issues with shutting down, restarting, etc. For example, on my system after I would shut down my system, it wouldn't fully shut down and would remain in a hibernation state instead. After I went ahead and disabled Fast Startup, I was able to successfully shut down.
Other posts elsewhere say it disturbs Windows 7 and then Windows 7 wants to check some or all partitions of visible Hard Drives. Even Microsoft said that somewhere.
I am still at work on this. :(