Windows 10: Restoring window backup made with acronis on SSD to a standard HDD.

Hi folks,

hope everyone is well.

I have made some backup of windows 10 that was installed on a SSD and just to make sure it would work ok, I installed the backup on a standard HDD, but getting lots of problems when I actually reach the desktop, monitor keeps flickering from black to windows all the time.

I used Acronis but also tried Macrium reflect as well to make the backup, but same thing the flicking screen when I reach the desktop after startup.

I wonder what is the problem here, the windows that I backed up on the SSD is working fine, but a little worried that if I do have to reinstall the backup to its present location on the SSD then I will get the flickering screen.

1 is it because I have windows 10 on an SSD that it wont work properly if cloned to a standard HDD?
2 Some other reason, partition size, Microsoft having inbuilt methods to prevent this or something else do you think
I would like to get to the bottom of this problem, Never really had many problems restoring backups of windows 7.

Many thanks
Joe

:)

 

boot from cloned ssd installed on cd drive

I have to assume that the cloning software you used made the SSD bootable. You can only confirm that by checking the software's documentation and confirming that you followed the procedure correctly.

I also assume that you have made a system image of the HDD. I also assume that you made a Recovery drive or a System repair disk unless you have an installation disk [which can also do the same job]. You will need this if the cloning has not worked correctly
and you need to restore your system.

The BIOS might not be capable of booting from a SSD/HDD in the CD bay. Whilst that can be a convenient location for doing the cloning, you will almost certainly need to remove the original HDD and fit the SSD
in its bay instead.

Put the old HDD in a USB enclosure so that it can be used as a storage drive but do not connect it to the computer while you are trying to get the SSD to boot. Bootable HDDs & SSDs have "signatures" that the system will look for during booting and finding
multiple signatures will confuse it & probably stop it booting at all.

If, when the SSD has proved itself, you decide to fit the old HDD in the CD bay as an onboard additional storage drive then you will need to format it first so hold off on this until you are completely confident in the SSD.

- - - - - - - - -

When I did this job last year, I used Acronis TI to "clone" to the SSD. Actually, what I did was use Acronis TI to restore a system image to the SSD. That is, in effect, cloning it but I thought that it would be a more reliable way of doing it as TI system
images are tolerant of changed hardware being found.

• I put the SSD in the CD bay to do the image restoration.
• I removed the old HDD and put the SSD in its bay.
• The SSD booted correctly.
• After a while, I reformatted the old HDD and fitted it in the CD bay as an onboard additional storage drive.

Best of luck,

Denis

 

Strange "C Missing" in Restore window

Results of testing Acronis clone and Image restore.

Boot SSD 1 – verified that there is no C Missing.

Created a second restore point for this drive.

Wipe SSD 2.

Clone SSD 1 to SSD 2 using Acronis 2016 booted from Rescue USB.

Boot from SSD 2.

C Missing exists on SSD 2

System Protection turned OFF for C System.

System Protection ON for C Missing.

Wipe SSD 2.

Image SSD1 to External backup drive using Acronis 2016 booted from Rescue USB.

Restore image from external drive to SSD2 with Acronis 2016 booted from Rescue USB.

Boot SSD2.

System Protection turned OFF for C System.

System Protection turned ON for C Missing.



My Results of testing;

Macrium clone creates C Missing folder on cloned drive.

Macrium Image restore does NOT create C Missing on imaged drive



Acronis clone creates C Missing folder on cloned drive.

Acronis image restore creates C Missing on imaged drive.



Turning Protection OFF on C Missing removes it from System Protection window.

Must turn protection on for C System.

These are my results - Others may have different results.

 

Hi,

Sounds more like a video driver problem to me. Can you try reinstalling these drivers or is the system impossible to work on ?

Cheers, *Wink