Possible to manually "ReDeploy" to new hardware?

[Coldblackice]

Is it possible to awaken a hibernated Windows 7 image on a new SSD (image coming from a prior/different SSD)?


On SuperUser, I was told this:

"The hibernated data has dependencies upon the hardware installed at the time the hibernation occurred - there's no getting around that."


Currently, I've laid the hibernated image down onto the new SSD, properly aligned it, but am BSOD'ing when trying to resume. I wager it's stemming from the hibernation waking up to an entirely different main SSD drive.

I'm wondering if it's possible to tweak/inject the proper drivers for the new SSD into the hibernated sector-by-sector drive image, or if there's some way to un-hibernate with generic drive drivers? What about the possibility of laying this image down into a virtual machine, in the hopes of tweaking/injecting to resume the hibernation?

In either case, my primary aim is to awaken from this hibernation so I can save what was open. Worse comes to worse, I guess I'll just have to cold-boot and lose the hibernation data.

 

[/usr/home]

Should just need to clone it to the new drive. You shouldn't need any drivers for the SSD. Basic AHCI drivers should work fine.

If nothing else, boot onto the old SSD, uninstall any drivers for the SSD, shutdown. Now clone it to the new drive and boot up. Windows should install any drivers it needs.

 

[bigdogchris]

If you're just transferring the Windows install to another disk, to be used with the same motherboard, you won't need to inject drivers. Just clone the drive then expand the partition from within Windows.

If you are transferring the Windows install to another motherboard, then you would need to worry about drivers, but I think that's a horrible idea. It's even worse idea to do it while the OS is hibernated.

People say transferring Windows install between motherboards is OK to do, and I'm sure it does work once in while, but in a few years when Windows Vista and 7 start not having drivers for hardware it's going to become a big issue. That's why I say get in the habit and do it right by doing a clean install and not be lazy. As for imagine/clone software that allows you to "restore to different hardware", I've never used it before so I can't say how well it works.

The only Microsoft supported method to move an OS between computers is to use Sysprep, which strips out installed drivers and allows the OS to reinstall the hardware from internal driver stores. The problem is, just like by cloning to another computer, if Windows doesn't have the driver integrated, you're screwed. There are ways to install drivers onto a system then sysprep it without losing the drivers, but that's beyond the scope of this question or a single computer.

 

[Coldblackice]

Thanks guys.

Attempting to resume from hibernation on the new SSD gives me a BSOD of "KERNEL_DATA_INPAGE_ERROR" (7A), with an error status of 0xC000000E ("...the disk subsystem has experienced a failure").

Without having the original drive, might I have any options to try and get this to resume from hibernation successfully? Could it be a matter of injecting drivers and/or altering the drive/controller configuration tailored to the new Samsung SSD?

If that wouldn't be possible, is there any way to "extract" from a hibernation file? It was foolishness to image the drive while hibernated, I know, but I was making a dash for the airport and didn't have time to save everything down and shutdown. I hoped I might be able to awaken from the hibernated image on a new drive, as iffy as the prospect sounded at the time (it was my only option/hope).

 

[zandor]

There's a boot time option to just boot the system instead of resuming. I forget exactly how to do it but I think you just press F8 or something. I'd just try that.

 

[Coldblackice]

There's a boot time option to just boot the system instead of resuming. I forget exactly how to do it but I think you just press F8 or something. I'd just try that.

That would lose the hibernated data, though, right?

I'm trying to recover everything that was open before hibernating. Booting normally would wipe the hibernation data, I believe. If worse comes to worse, I guess that'll be my only, last-ditch option. But hoping to find some way to jury-rig a hibernation-resume on a new SSD in the meantime.

On SuperUser, I was just told:

"The hibernated data has dependencies upon the hardware installed at the time the hibernation occurred - there's no getting around that."

So maybe I'm SOL :/ And I just had the thought -- I should enable the boot-option to "Show loading", to try to see where/what driver the BSOD is stemming from.