Win 10 installed on separate hard drive changes win 7

f14tomcat said:

Glad to hear all ok! Remember that after the next build comes out, it will probably undo what you've done. Just save your REG files and re-do! Cheers!

That does make your W10TP drive inaccessible from the other drive.

The register key added in W10TP was changed on its own to show "C:" instead of "E:" drive. Not sure if that was like that yesterday after a few reboots, etc. or this morning after four updates requiring a restart??

Just remembered that no restore point was created prior to the update which I've seen it do before. Wondering if that entry changed caused that?

f14tomcat said:

Yes, W10TP would be inaccessible from other drive. If you have an ext USB drive or room to make a small partition on the HDD, you can "share" it between OS's to move files back and forth. That's the approach I took.

It will be "C:" by default on each of the OS's you are booted to, even though the drive letter will appear as something else. When on W10TP, win7 might be "E:", when on Win7 W10TP might be "F:" or something. These were the drive letters in your reg files. It's normal.

There were no restore points probably cause you had not "hidden" the drives yet, and they were deleted.

Do an image backup on both OS's and there will be restore points after.

Cheers!

Maybe I'm explaining well enough.

The entry of "E:" drive in my registry for W10 changed to "C:" entry so Windows changed the entry. I'm still retaining restore points.

Kevin said:

TechnoMage,

Lesson learned! The restore points appear still intact, Thankfully! I do backups frequently, To frequently, automatic backup ran last night at 2 am erasing the backup from last Sunday morning. I have run windows and linux in the same box for years with no problems, but never 2 windows systems. I have learned my lesson.

Wrongo in the Congo, so to speak. That's the falicy of an automated backup.... a new backup file overwrites an older backup file.
Then if there's a problem with the new backup file and it can't be restored, you're screwed!!!!!

Rule 1. Your Backup and Restore program MUST not be on your OS drive, because if that drive goes up in a puff of fire and smoke, you're screwed. How are you going to run the Restore program?

Rule 2. Your PC should not be ON at 2AM unless you're sitting there at the PC, or nearby, if it runs into trouble.

I could go on and on, with all the misconceptions about backups. I've been setting up backup schemes for individuals, businesses and corporations for over 35 years. I've seen just about everything that someone can do WRONG concerning backups.

I do my whole C: drive backup once a week, using Ghost 11.5, run from a Boot CD and my backup Image Files are stored on a separate hard drive.... a 1TB drive, with plenty of space for multiple backups. I do a massive cleanup on my C: drive before actually doing my backups, so I'm not backing up Garbage. Then I let Ghost do a verification (Check) on the backup file, to verify its integrity. (a backup file with errors in it, is NO backup at all.)

Cheers Mates!
TechnoMage

Kevin said:

I installed Windows 10 on a separate hard drive in my computer to keep from messing up my Windows 7 installation. It appears windows 10 still makes changes to windows 7 even on a separate hard drive. See attached picture. I can not correct this using the system repair disk or the original install disk because it tells me it is the wrong operating system any idea how to correct this? I tried to make a new system restore disk and it tell me the disk is for technical preview x64! even though im making it in windows 7. (See Pic) The disk windows ten was installed on was removed from my machine when I tried to make the system repair disk from the picture.
Attachment 10992

Yers, the exact same thing happened to me. If you notice on the recovery screen, the last option was to press F9 to use a different operating system. I did that, and it booted into my Old faithful win7

f14tomcat said:

0x00000000 for offline value will keep it ONLINE. 0x00000001 for offline value will make it OFFLINE.

the 0 and 1 is used to enable/disable the offline status. Sounds backwards, but it's for triggering the function.

[HKEY_LOCAL_MACHINE\SYSTEM\MountedDevices\Offline]
"\\DosDevices\\C:"=dword:00000001

will make the "C" drive appear OFFLINE. This would be the reg key used on the drive/partition of Win 10.

The "C" will be need to be changed to whatever Win 10 "sees" the Win 7 OS drive/partition to be.

And, vice-versa...... on the WIN 7 side, change the "C" to whatever Win 7 "sees" the Win 10 OS drive/partition to be.

clear as mud, right! It works.

P.S. - The reason for "Windows Seven Forum they suggest a "1" on the drive that retains the restore points "only""
is that it's the only side that is REALLY necessary, cause WIN 7 is the earlier version which Win 10 sees as incompatible
restore points. It won't hurt to do both side. It will ensure no "leaking" betwix-and-between!

I know this is a very old thread, but my problem is exactly this. Windows 7 on my old C: drive and a new installation of Windows 10 on the new 2TB E: drive.

I'm moving to a new version of accounting software package which will absolutely-positively not run under Windows 7.

After seeing the computer start chkdsk from boot power off state, or switching O/S's via the Boot Menu, I suspected their might be a file incompatibility.

I will invoke the registry changes explained on both O/S installs.

At times my chkdsk will find a bundle of re-parse errors and "delete" them one by one. Then when finished it all comes back up intact.

It's difficult to tell which O/S is invoking chkdsk as it always happens at the pre-Win boot. I have seen it pop up in the Windows 10 msg center that there are some corrupt files and chkdsk needs to run.

This was mainly a test to see how Windows 10 Pro would run on my Intel i7-2600K @3.4Ghz with only 16 GB of ram. I was pleasantly surprised. Even better after I "sterilized" all of those "toys" which I find very annoying, and can easily eat up hardware resources.

So much darn fun!