Windows 10: Macrium - Setup Macrium Rescue to boot from an Internal SSD

Hey Guys

I was a poster on the SevenForums, but it appears that usernames and logins don't transfer from there? Anyhow ive registered a new account here to post my (hopefully simple) query:

Ive just followed Brinks amazing Clean Install W10 without having to upgrade guide and it went flawlessly. I'm now in 10 and have been installing drivers, updates and AV/Malware scans and setup. All done - ready to make a post install image using Macrium (which I have also used before on 7)

I was intrigued with this guide though: https://www.tenforums.com/general-dis...sb-hd-ssd.html

I have followed all the steps (I believe successfully) and now have a separate SSD (not my OS SSD) with an Active Primary partition of 512mb. Ive copied the ISO which macrium created for the Rescue disc to it etc.

I then tried to get into the boot menu he shows in the guide and that's where Ive come unstuck. I have literally no idea how to boot from this rescue disc on my other SSD. I'm not even sure copying the ISO to it makes it a rescue environment I can boot from.

Happy to answer any questions or post screen snips of whats going on.

Any help greatly appreciated

thanks
Matt

:)

 

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.

 

Windows Boot Sector corrupted

Does your HDD installation still work? If so then this would be the correct procedure to follow:

• Use Macrium Reflect (or a similar tool) to create an image of your installation.
• Disconnect the HDD, connect the SSD.
• Boot the machine with the Macrium Reflect bootable rescue flash disk.
• Restore the image to the SSD.

In general: When restoring images you must make sure at the first reboot to connect the new disk only. If both disks are connected then you risk ruining both installations.

 

It was my post. You have to copy the content of the ISO, not the ISO

 

Hey Topgundcp

Thanks for your quick response. whilst I was waiting for a reply I realised my error and was just figuring out how to mount the iso which macrium had created.

Long story short, ive now moved the .iso to another drive, mounted it there and then copied the mounted contents to my M drive (Active, Primary) and then deleted the drive letter.

I just did a successful boot from it using W10 UEFI bootloader interface (I really have no idea what its called....I got to it via settings > update & security >recovery > advanced startup

In there I stumbled upon launching a UFEI rescue and a few seconds later I was in the macrium environment.

Sounds OK to you? Seemed OK to me

Many thanks Matt

 

You should not have to do this even though it works but what if your PC became unbootable ?
You can boot it via the Boot Menu, just select the item from the list pointed to the SSD where you have the rescue copied to.

 

That's a very good point. I do need to be able to boot from that SSD when/if W10 is unbootable.

This is where I am struggling. I honestly do not know how to get into the boot menu from a cold boot? It takes W10 6 seconds go from me pressing the power button to being asked for a login. Hitting Del will get me into bios, but I don't know how to get to the boot menu which you show in the final picture of your guide.

For what its worth I'm using an asus motherboard (Maximus Ranger VII). Sorry for coming across so ignorant of this probably simple thing.

 

You need to look in the Manual for your MB to find out which key or function key to display the boot menu. Each manufacturer set it up differently. I use MSI Mother board and DEL key will get into BIOS, F11 will display the boot menu.

 

Many thanks top gun.
Found its the f8 key, but I had to add a 2 sec delay into the boot through bios to get f8 to register. It barely registered hammering del just to get to bios it boots to quick in uefi mode.

F8 got me to the menu and there I can choose to boot from the ssd with the macrium rescue environment.

Really appreciate your help
Matt

 

Great. Glad you got it sorted.
It's a nice feature that you can delay the POST for 2 seconds, gives you time to access the BIOS/Boot Menu.

 

My asus board allows you to delay post (after bios logo) for between 0 and 10 seconds.

The temptation is obviously for a rapid boot, and it's been set to 0 under Windows 7 for 2 years, non uefi, and I could always get in.

0 secs under w10 with full uefi disk structure and the windows logo appears 1 second in after I hit power lol.

 

OK. Now that you have everything set. From Admin command, run:

• Dism /Online /Cleanup-Image /StartComponentCleanup
• %SystemRoot%\System32\Cmd.exe /c Cleanmgr /sageset:65535 & Cleanmgr /sagerun:65535
  Put a check mark on everything except "Setup Log Files"
• Win+X->Program and Features then turn on Net Framework right away.
• Boot up Macrium and make your 1st backup.

 

Whoa. That is totally over my head. I can follow the instructions, but I would like to know what the purpose of those various commands are, as I don't like to do things blindly.

Cheers
Matt

 

• Cleans up WinSxS folder securely to reduce the component store size. In addition, this command should be run after every major Windows Updates.
• Cleanup all temp files/set up files/Windows Updates etc....
• Some Applications written with Dot Net and won't run without Net Framework. Better to add this feature to avoid conflict and unable to add the feature later on.
  For example: Showkey - Windows 10 Forums
  developed by @Superfly

 

Hey Topgun

Just wanted to report back that I ran all those commands successfully last night without issue.

The first command (reduce component size) took about 5 mins to run. I thought it was broken but it was steadily making progress. That was on an SSD with a 4790k quad core!

After I did those commands I ran my AV and spyware checks one last time and then imaged. Many thanks.

A question: is there any difference or issue with imaging from within the OS vs imaging from the recovery environment?