I'm dual booting Windows 7 & 10, and when boot up Windows 7, and then back into Windows 10, the Windows 10 restore points have been deleted. I tried the fix here but it didn't work. The restore points are still being deleted. Anybody else having problems with this (maybe maybe dual booting with Windows 8 with the same problem)? If so, is there a fix for this? I've searched the web and haven't found one yet. Thanks in advance for any replies.
Hi there
probably part of the problem is caused by the same system recovery partitions being used by both W10 and W7.
IMO the best way to dual boot is to have two separate partitions for the OS'es - including the extra system / recovery partitions and before booting EITHER OS is to HIDE the other OS and its partitions. There used to be a program called Easyboot or something like that - but I haven't dual booted for years now.
If the OS is totally on a separate HDD you could disable that HDD possibly in the BIOS before booting the second OS. Depends though on your BIOS.
Unless you REALLY HAVE to dual boot - why not consider using a VM (Virtual Machine) for your second OS. VM's these days can handle most graphics and hardware so if it's mainly legacy stuff you want to run (Old OS) or test a new OS (W10) a VM should be fine.
A VM won't always be appropriate (serious gamers) etc but I'm sure in over 90% of cases where people are Dual booting a VM would work just as well.
Cheers
jimbo
I really don't want to do a VM. Performance isn't not as good as a native machine installation, plus Windows 10 is so new that VirtualBox hasn't worked out all the bugs yet, either as Windows 10 host or guest. VirtualBox is my preferred VM manager. I've tried the Windows 10 Tech Preview as a guest in VirtualBox using my Windows 7 installation as the host. I didn't like the experience. Not as good as a native installation. Plus I'm experimenting with my native Windows 10 installation to see if I like it good enough to eventually remove my Windows 7 installation. I was just wondering if anybody had found a fix for the deletion of restore points. Not many people dual boot so finding people with the same problem is rare I guess. Thanks for the reply and advice. I really appreciate it.
Best Regards,
Tom
This has been a problem with Dual booting since Windows 7/8 I believe. To the best of my knowledge there is no good solution other than separate partitions as has already been recommended.
How about another option instead of Virtualbox? Install Windows 10 and run Windows 7 under Hyper-V? Not knowing what your exact issue is with performance (are you running video games for instance) it is impossible to come up with better solutions.
Or Upgrade Windows 7 to Windows 10. You have 30 days to revert back to Windows 7 if you find you don't want to stay with Windows 10. If that isn't enough time to make a decision, then I'm not sure how to help.
I'm frankly not sure where a dual boot system would benefit me anymore with VM's being so easy to work with.
You didn't happen to clone the Windows 7 and then convert it to 10 did you? Windows can get mixed up on the identity of the drive for shadow copies when you do that IME.I'm dual booting Windows 7 & 10, and when boot up Windows 7, and then back into Windows 10, the Windows 10 restore points have been deleted. I tried the fix here but it didn't work. The restore points are still being deleted. Anybody else having problems with this (maybe maybe dual booting with Windows 8 with the same problem)? If so, is there a fix for this? I've searched the web and haven't found one yet. Thanks in advance for any replies.
Yes that's what I did. I cloned Windows 7 and upgraded it to Windows 10. That explains a lot. Thanks for the info. I thought that was the easiest way to try Windows 10 with a native installation. I guess until I remove my Windows 7 installation (which I'll probably do soon) I'll just create new restore points in Windows 10 every time I boot into it. I find myself primarily in Windows 10 now all the time anyway now (I want to thoroughly use it to see if I'll stick with it). Again, thanks for the info.
