By Patrice_35 - 7 January 2022 8:19 PM
Hi Macrium support
I am a single customer that has a desktop PC running W10 Pro X64 21H2 with plenty of applications, 32 GB RAM, 4 SSD (2 NVME, 2 SATA), 3 disks (one with 10 partitions, 2 others single partition)
KB Omen, mouse Razer, 2 games controllers, a Nvidia FE RTX3090 as GC.
What I want to do: redeploy my system on another motherboard.
So, What is my current state:
I run W10 x64 Pro 21H2 on an Asus Maximus X hero, processor being an Intel Core i7-.9700K
My system disk is in fact a NVME SSD of 500 GB that contains many many applications and all is fully optimized;
I use also MSFS 2020 (Microsoft Flight Simulator 2020) store version which is stored in Windowsapps.
Apart this my boot is a dual boot, one for W10 and the other for Macrium rescue medium (On each boot, I have to choose what to load, by default it is w10).
My PC is custom made (desktop PC)
Now what I want to do:
I bought a new motherboard (MSI Z890 Wifi EDGE) and a core I7-12700KF processor.
You know that this processor has now a new architecture from Intel with P-Cores and E-Cores).
The MB comes with a USB key with many drivers on it. I installed this key content on my system SSD in a dedicated folder.
How do I intend to proceed:
I remove all my disks and SSD from the current configuration, I remove the MB, I install the new MB, reinstall all my disks and SSD,
enter the Bios to setup the boot process.
Then I boot the new MB and when the dual boot occurs, I start Macrium rescue software from my SSD and try to make a redeploy from this situation.
In order for Macrium find the drivers I add the folder where I stored the USB key (provided with the new MB) in the list of folders to search for drivers.
My questions/requests for clarification:
1. Is it Ok to proceed as I described it or do I need to boot from a Macrium rescue medium (USB key)? Should I remove this dual boot before making the redeploy?
2. Do you think the redeploy will be ok with such different hardware (processors are very different, the new MB has many SSD NVME slots availables with specific components to access them. The main reason I will try a redeploy is to avoid making a complete new W10 installation that will be very time consuming considering the number of apps to reinstall.
3. If the redeploy allows the system to boot OK, will it be any further problems remaining with the system after making it running ok (CTD, etc) (for this case and in general, what is your experience about this)?
4. How does the rescue medium know about the current drivers to use with a new MB? Same question regarding the correct HAL?
5. My System disk is on a NVME SSD: Will Macrium rescue be able to detect and find this system disk?
Thanks in advance for any suggestions and advices regarding my concerns.
Presently I own a Workstation version of Macrium 8.
By jphughan - 8 January 2022 2:35 AM
I would very strongly recommend that you create and test a Rescue Media USB drive rather than relying on the recovery boot menu option, just in case you have a problem that prevents the new motherboard from even booting to Windows Boot Manager in order to display that menu. I doubt that will happen, but having a flash drive is cheap insurance.
I don't think the quantity and partitioning of your storage devices will be an issue for ReDeploy, since ReDeploy is solely focused on getting Windows booting on new hardware. Other drives that don't contain Windows partitions simply aren't a factor. You might have some drive letters you'll need to customize in the ReDeployed Windows environment if the new motherboard enumerates disks differently and therefore Windows doesn't recognize them the same way (I'm not sure this will be an issue), but other than that I don't think that will be an issue.
As to drivers, here again ReDeploy is only focused on making the changes that are necessary to get Windows to start rather than locking up or blue screening. So you should NOT expect that it will take care of installing all necessary drivers for your new hardware. That's something you should plan to do in Windows AFTER ReDeploy gets it booting. It's not a bad idea to have all of those drivers available in case the ReDeploy wizard asks for anything, but you should expect to have some work to do later. And with respect to those drivers, make sure they're actual driver files, i.e. an INF file and such, as opposed to EXE installer files.
In terms of how ReDeploy "knows" which drivers to use, devices have PCI vendor and device IDs, and driver INF files specify that they are valid for various PCI vendor and device IDs. That's how ReDeploy (and for that matter Windows) knows if you're trying to load a suitable driver for whatever device needs a driver. I can't speak to the HAL question specifically, but I would imagine it would follow a similar concept where there's some way for the OS or ReDeploy to "query" the hardware.
By Patrice_35 - 8 January 2022 12:52 PM
Thank you for your clarifications.
One more question: should I remove the dual boot before making the redeploy or not?
By jphughan - 8 January 2022 3:46 PM
I don't think it makes a difference. To my knowledge ReDeploy will not be "confused" by that secondary entry for Reflect, but you can certainly do so if it makes you feel more comfortable. It's easy enough to bring back if needed, and as long as you've got USB Rescue Media in the meantime, then you don't need the menu option. However, you should really ALWAYS have USB media somewhere in order to cover unexpected failures that could break the boot menu option.
By Patrice_35 - 16 January 2022 12:50 PM
You know what:
I made my HW modifications.
After that I booted, go into Bios, make some adjustments and then let the PC boot by itself.
And what happened: Windows 10 has been able to reconfigure itself with no other intervention and now my PC i completely operational as before.
No need of Macrium to modify anything. W10 worked by itself.
By jphughan - 16 January 2022 2:57 PM
Nice! I have read from other users that Windows 10 seems to be a bit more “adaptable” than previous versions, so that may have helped. Or maybe the drivers required by those two motherboards were the same and the driver versions you already had were new enough to support the new board. Either way, glad you’re up and running!