Restore Windows 7 pro from a system image after HDD failure

Hallo to all,
I hope you'll be able to help me and to give me advice in right direction.
I have two Dell precision machines. I make regular backups (images) with Acronis Image.
Few days ago, on one machine HDD failed, so I put another HDD same capacity and restore windows from already made backups few months ago.
Restor process went without problems, but during the windows 7 pro 64 bit star I received 0x0000007b error. I have learned a lot about this error and I know that is usually caused by inappropriate driveres etc. This is very strange since I try to restore image on the same computer and only one component is changed and that is HDD (before seagate, now WD), both drives are Sata spo everything should be OK but it's not.
I even try to restore backup from other machine that is 100 % in working condition but received the same error. My idea was to use backup from other machine (in case my backup image of original machine is not OK), then simply change computer name and its IP addresses.

Now I have read somewhere that I probably need to do sysprep before making image.
So I have two questions>
1. Will Sysprep on my working machine remove product key and deactivate windows?
2. Sine both machines have the same HW and were delivered at the same time, is it really needed to use sysprep?

Sysprep is usually necessary when one needs to migrate OS to another hardware.

Should I try some cloning tool such as clonezilla?

Thank you

Hello ICIT2LOL,

The possibility that the computer or image is affected with virus/malware is very very low.
I have tried older backup and all end up with BSOD and 0x0000007B. I then tried with completely different HDDs and the result is the same. Then I have tried with acronis image of the second computer (fully 100% working) and the result is same. Then I begin to suspect that there is a HW problem. But I used win 7 pro installation DVD and installed windows without problems (clean install). Computer works without problems so it is not the question of HW. I inspect the differences between other fully working computer and newly installed and observed that newly installed system has reserved partition 100 MB that other computer doesn't have.
So my conclusion is that reserved partition is deleted and boot manager (BCD) is translated to C:.
This unfortunately doesn't solve my problem since there is a lot of specialized software installed which I don't know how to configure if going from scratch. Therefore with computers backup images are delivered and I also made images every few months.

My next step is going to be to try acronis restore of C,d and E partition on already installed windows system without restoring MBR and track 0. This way hopefully, windows will start and all programs will be there.

The whole situation doesn't explain at all why BSOD is showing up after restoring image of whole disk, actually it doesn't make any sense. The BSOD is so typical when HDD is moved to different computer (different MB, drivers etc.).

Another approach would be to try to use different backup / restore imaging tool such as you suggested. I would make new backup image of working computer and then applied to problematic computer.

Hallo guys and thank you for your time.

I have used today both Macriuem and Clonezilla disk clone option and in both cases I end up with BSOD.
Like I said HW is not the issue because clean install windows 7 works without problems.
The bios settings on both machines are identical.
So I investigated a little bit further and discovered how partitions are listed on 100 % working machine.
Please have a look at the attached pic. It is very interesting to see that summing sizes of all partitions are above 465 GB. It is exactly the same on non working machine.
Commands such as bootrec /rebuild all and fixmbr, fixboot didn't solve this either.
I tried of course with WIN7 installation disk to repair the startup but that didn't help.

I think the trick is with this so called extended partition.
I decided to work now with only one drive. I have removed one disk tried ACHI and ATA bio settings with repair startup but the result is the same.

Diskpart give me the same configuration, so I don't understand what's the catch.
I have no ides what confuses windows to start on the probelmatic machine.

Please note, attached is pic from list part on working machine.

All these commands executed sucessfully but that still didn't solve the problem. Very strage problem.

1. Bcdedit /export C:\BCD_Backup.
2. c:
3. cd boot.
4. Attrib bcd -s -h -r.
5. ren c:\boot\bcd bcd.old.
6. bootrec /RebuildBcd.

Hi askic

Pardon me if i said things to you may offend you, but this is a learning point, so bear with it.

Part 1 of 2. Understanding of computer knowledge.

Regarding to

Restor process went without problems, but during the windows 7 pro 64 bit star I received 0x0000007b error. I have learned a lot about this error and I know that is usually caused by inappropriate driveres etc. This is very strange since I try to restore image on the same computer and only one component is changed and that is HDD (before seagate, now WD), both drives are Sata spo everything should be OK but it's not.

Reading from the net, some are very misleading and then you concluded as the problem was the driver!

Reading from the net, you cannot and must not believe in everything people who wrote on the problem.
Knowledge in computer is also from experience, as you may not have.


Regarding to

I have tried older backup and all end up with BSOD and 0x0000007B. I then tried with completely different HDDs and the result is the same. Then I have tried with acronis image of the second computer (fully 100% working) and the result is same. Then I begin to suspect that there is a HW problem. But I used win 7 pro installation DVD and installed windows without problems (clean install). Computer works without problems so it is not the question of HW. I inspect the differences between other fully working computer and newly installed and observed that newly installed system has reserved partition 100 MB that other computer doesn't have.

As in this your post, although you did suspect HW problem, which was your first instinct.
Then later, you suspect other issue as not HW problem.

Again here, you always jump to conclusion as to rule out HW problem.
This is where you cannot decide which is the problem that cause all these to happen.

Most users here, if not all, do not jump to conclusion too fast.
There should have a logic and step by step, in doing troubleshooting.

As in the past, i work in technical dept and reading how technical report analysis problem, in 3 steps.
1. What is the problem. This is from the customer point, not technical point.
2. Cause; how do this problem occur and why. Technically speaking, troubleshooting.
3. Remedy; how to resolve the problem.


In my conclusion on you.
You do not have enough experience and not enough knowledge and failed to do proper troubleshooting.
Hence, not many users understand about your problem &or issues.

For me, i bought/loan tons of books on computer for 3 decade, spending a lot of money investing in hardware, undergo training school, etc; to arm myself in this computer era.

This i will end here, next on your problem.


Eric.

Hi askic

Part 2 of 2

NOTICE
Do take note that there is no guarantee on successfully to totally resolve your problems.
As for expert in coming to this thread to assist you or not, it depend on them.

This is to assist you to point the correct direction for you to get resolved if we cannot continue further.
This is due to the fact that we do not know how your Dell computers are built, and by who.
It is them that you may have to approach to find out more on how they built your computers and also up to them to resolve for you or not.

Before i start here, if you want to resolve solution, you need to listen and follow some of the instruction.
Not only from me, but others expert in HW & system, may also come to assist you.

As i am not HW specialist, i will list some of my findings here, with pictures.
It is easy to understand with pictures as there is a saying, a pictures do have thousand of words.

As in my very first post #4 on the first portion (as what mjf did mentioned) is about your computers and HDD(s), which you ignore.


You need to show the disk management of your "good" computer.
As you have provided the picture on your post #7 with all available HDD(s) relating to Dell computers.


What i provide in the pictures are from my HDD(s).

Disk Management
Disk 0 is SSD 500GB Windows 7
Disk 1 is External HDD USB 3 Samsung 3TB.
Disk 2 is External HDD USB 3 Toshiba 2TB.

As in disk 1, i did use Clean command, and it end in 2TB as MBR is limited.
The other 1TB is unable to access from Disk Management, but i leave it, as already have imaged partitions.

As in disk 2, i also use Clean command, and there is no problem as it stay in the 2TB limit.

From the Disk Management, look right at the bottom, it will show you by color on the type of partition.
Logical partition (dark green) can have many partitions.


Diskpart in command The "offset" is too technical and i cannot explain.
List Disk.
Disk 0 = there is 74 GB not in use is correct as refer to disk management.

Disk 1 = 2794 GB is the 3TB HDD. It show 0 B free, that is to say it did not report on the 1TB as free.
In the Disk management on this HDD, i cannot even create that portion as a partition.
This problem is created as i use CLEAN command and it end up with only 2TB usable.
That is to say, CLEAN command can only do up to 2TB as the limit.
The 1TB is not reflected under "list part", as it is only 2TB.
Unless it is on GPT then i can fully use all 3TB storage, as under GPT is blank.

Disk 2 = I have to limit to 3 Primary partitions and 1 Logical partition.
This is the limit of the Windows system, as refer to the partition 1, 2, 3 as primary partition.
For Logical partition can have unlimited logical partitions.



Refer to this

I think the trick is with this so called extended partition.

There is nothing wrong with Extended partition, as it is known as Logical partition.
Also Extended partition can contain many logical partition, as you see in my HDD.

Window system can only have up to 4 primary partitions.
Either 4 Primary partition without any Extended partitions; or 3 Primary partition + 1 Extended partition.
Even it can be 2 Primary partitions + 2 Extended partitions, as any combination.


This is where i go no further, as i am trying to let you know that your problem is due to HDD(s) and setup.

As again, do understand what mjf is trying to inform you on first step, which you ignore.

Provide the Disk Management to see how is the setup.

It depend on whether any specialist users to assist you.


Eric.