Cannot load saved images after attempted (failed) W10 to W7 downgrade

[lyonkster]

First time poster here with a head scratcher (to me).

My 6 mo old Dell XPS8700 came with W7 Pro 64 bit. About two weeks ago I decided to take the plunge to W10. Upgraded without issues, and been running great for two weeks.

This weekend I decided to go back to W7 and create an image of W7 just before I upgraded (in case I decide to downgrade later, after 30 days). Turns out to have been a bad move.

Prior to downgrading, I created images of the W10 system with not one but three tools (EaseUS, Aomei, and Macrium).

I tried using the Restore W7 function in W10, which started fine but then crashed (I don't recall the error message, but it was not very clear). Subsequently the PC would not boot, I got the dreaded "Windows failed to start. A recent hardware or software change blah blah", and the repair disk option did nothing. http://answers.microsoft.com/en-us/...dware-or/8dad59b9-a08d-4cb8-8ddf-1c164b7caf65

I thought "no problem, I have the images saved". I tried to restore the W10 image using Macrium and the rescue disk. The image loaded, but when I tried to boot, I got the same exact error message.

I did the same thing with Aomei and EaseUS, and again got the exact same error messages. I simply could not boot up the PC.

After screwing with it most of the day, I found an Aomei image from 5 months ago. I was able to restore that one and the system now boots up fine. So while I need to download a bunch of programs to get back to where I was, I think (hope) that I am on the road to recovery.

What I don't get (aside from why Windows took a dump on downgrading in such an ugly way) is why none of my images are restoring correctly. I thought maybe it's a hardware problem with the SSD, but the older image did install.

What am I missing? Is it possible that the images that Aomei, Macrium, and EaseUS created while in the W10 environment cannot be reloaded in the W7 environment?

It just makes me wonder what I should do differently next time to avoid a similar disaster.

Thanks!

 

[ThrashZone]

Hi and welcome to SevenForums,
Did you share the drive with the images with both os's ?

Was this drive with the images always connected or only when you created them and tried to restore them ?

Win-10 does not play well with sharing drives
Mostly because of fast startup in win-10
Disabled it's not as bad but personally I'll never share a drive with win-10 I need for win-7.
Fast Startup - Turn On or Off in Windows 10 - Windows 10 Forums

I also disable fast start in bios.

 

[lyonkster]

Thanks for the reply! I'm not completely sure what "sharing a drive" means, but let me know if this helps - the OS drive is an SSD, and the data resides on a 1 TB HDD inside the same machine. When I made the images, I saved them on the HDD. The data HDD was always connected to the machine as a data drive. Is that what you were asking?

 

[ThrashZone]

Hi,
Yes
Win-10 imho needs it's own drives for data and system images
If all you had was win-7 system images I would of kept it totally separate and on it's own drive and disconnected when upgrading to win-10.

Either way win-10 fast start probably corrupted the images.
Many times testing win-10 I was repeatedly prompted with alerts in win-7 that the drive shared with win-10 must be initialized before use this has a very good chance to loose what ever data is on the drive
During testing all the drives I used were just transferring files from 7 to 10 so there was no real loss but was a very good wake up call for me to keep these operating system well separated
And fast start off.

 

[DavidE]

If you have a System Reserved partition that's probably where the bootloader is installed.
You would need to restore the System Reserved partition and the Windows partition when restoring. Also with Macrium v6 restoring the MBR (Master Boot Record) is optional. You should restore the MBR when restoring a different OS. With Macrium you can mount the backup image and see what partitions are in it. Probably the other backup utilities can also do this. A lot of times a Startup Repair fixes boot issues after restoring a backup image. [URL]http://www.sevenforums.com/tutorials/681-startup-repair.html[/URL]

 

[lyonkster]

Wow, I'm learning more about W10 than I ever wanted to! Thanks.

DavidE, I did try to restore both the OS and the System reserved partitions (i.e. I imaged all partitions on the SSD, and then asked for all the partitions to be restored). Maybe I screwed something up.

What does not seem to add up though is that I was able to restore an earlier image, one that I made back in September and that has been sitting on the same data drive HDD the whole time. That would seem to contradict some of the suggestions above, but perhaps if W10 ends up corrupting data/images, it does not corrupt them all uniformly, and the September image escaped unscathed.

Regardless, I think from now on I am making clones of important configurations rather than images, seems like there are fewer things that can go wrong .

 

[DavidE]

I store Macrium backup images for all OS's on the same HD and haven't had any problems with an image getting corrupted.
I have a separate Backup folder for each OS.
I haven't reverted back to Win 7 after upgrading to Win 10, so i can't comment on doing that.

I do agree the Win 10 Fast Startup can wreak havoc on a multi-boot PC, i learned that the hard way.

If you go with cloning, it uses an entire HD for the backup, so you can only keep one (the latest) clone per backup device (HD).

I share some drives/partitions for all OS's (W7, W8.1, W10) and haven't had a problem with that.
Keeping everything separate is probably safer, but i want to share my Data and Portable Programs with all OS's.
I don't want to duplicate this stuff, for each OS.

I agree, that is weird that an older image works, but not the newer ones.

 

[ThrashZone]

Hi,
Nobody has ever lost data if it's duplicated in at least 2 places
Not sharing drives insures at least to me I've done all I can to prevent data loss
Then we can get to the mechanical loss of data stuff

 

[lyonkster]

Thanks for the tips folks. Given what I learned from the responses, I now think that there is an advantage to making a clone rather than image. I understand that a clone uses up an entire HD, but I have a number of HDD's laying around collecting dust, and the reduced risk of compatibility issues seems to me to be worth it. I will also create images and incremental images on another HDD, but at least I'll have one clone that won't require any program to restore. Having wasted a full day on this nonsense, I'm once bitten twice shy.

And as I understand your replies, for future reference, I should not have used an HDD for image storage that's resident to the PC. It's better to connect an external HDD and load the image on it, then disconnect it to keep it out of harm's way. Is that the right takeaway?

 

[ThrashZone]

Hi,
Pretty much
The images are safer disconnected after verifying them.
Easiest way to disconnect them is shutting down the machine I've found.