Skip to main content

Unable to clone a disk (SSD M.2) or create a working rescue media

Thread solved

I've been trying to make a clone of my drive (Windows 10 - 22H2, Build - 19045.3803), but when it comes time to restart the system, I just boot back into windows. It makes to attempt to continue the cloning process.

I tried making a work around by creating a rescue USB media, but both simple and advanced versions failed, bring up the error concerning

ntoskrnl.exe

Error Code: 0xc000a004

stating it's either missing or corrupted.

 

if you can help to fix this issue it would be great.

Thanks

0 Users found this helpful

Mohammed, when you attempt to clone a drive from within Windows and it does a restart, then this is into a Linux based recovery environment which has a number of known limitations, including support for NVMe M.2 SSD's, RAID and BitLocker encryption.

For this reason, it is recommended that you should use Windows PE based rescue media using either the Simple method using the Windows Recovery Environment files, or else Advanced which others more control for adding any required device drivers.

When using WinPE rescue media it is very important that you boot from that media using the same boot mode as your Windows 10 OS normally uses.  For modern systems this is normally in UEFI BIOS boot mode, and for older systems it is Legacy boot mode.  You can check the mode used from within Windows by running the command: msinfo32 then looking in the right panel it produces at the BIOS mode setting.

I suspect that the error with ntoskrnl.exe may be caused by using the wrong BIOS boot mode.

One other thought, the USB rescue media should not be larger than 32GB in size and not smaller than 2GB.

See KB 65508: Acronis True Image 2021: how to create bootable media and KB 59877: Acronis True Image: how to distinguish between UEFI and Legacy BIOS boot modes of Acronis Bootable Media

See forum topic: Steve migrate NVMe SSD where I have documented (with images) the process that I have used multiple times for my own laptops using Backup & Recovery. 

As you suggested

I created another Rescue Media with a 32GB USB

and used simple to create it

unfortunately the same pop up when I attempted to boot from it.

The error screen isn't coming from the Acronis rescue media - it is from Windows itself, almost as if it hasn't detected the Acronis media as being bootable.

You should be seeing displays as shown in KB 59877: Acronis True Image: how to distinguish between UEFI and Legacy BIOS boot modes of Acronis Bootable Media

What actual version of Acronis are you using here?  ACPHO or ATI 2021 ?

What type of PC is this?  Desktop / Tower PC or a Laptop / Notebook ?

Have you tried doing a full shutdown of Windows by holding down a Shift key while clicking on Shutdown, then trying to boot from the rescue media?

There is an issue with WinRE in Windows 10. WinRE is faulty and can't boot after some of the recent Windows Updates. The error message is exactly what you are showing. If you have access to a Windows 11 computer with ACPHO installed, you can make the Simple recovery media and it will work on your Windows 10 computer.

Another alternative is to download and install the Windows ADK and WinPE add-on on your Windows 10 computer. Then use the Advanced method and select installed ADK to make the media.

You can read about the problem on the Macrium forum. https://forum.macrium.com/73641/Blue-Screen-on-RE-Rescue-Media

 

A little more on this...

I had the exact same issue last October and just found my email to Mustang about it.

I discovered that there was a Service Stack Update made to WinRE in September. My solution at the time was to recover WinRE to a prior version from an earlier disk backup.  I did this by

1. Run reagentc /disable
2. copy the older good winre.wim to C:\Windows\System32\Recovery to replace the bad one
3. run reagentc /enable.

All was good after that. When I later installed the October second Tuesday Windows Update, it made a Service Stack Update which was good.

From Microsoft Update Release Notes for September 12 Update

Windows 10 servicing stack update - 19044.3385 and 19045.3385

This update makes quality improvements to the servicing stack, which is the component that installs Windows updates. Servicing stack updates (SSU) ensure that you have a robust and reliable servicing stack so that your devices can receive and install Microsoft updates.

From the October 10 Update

Windows 10 servicing stack update - 19044.3562 and 19045.3562

This update makes quality improvements to the servicing stack, which is the component that installs Windows updates. Servicing stack updates (SSU) ensure that you have a robust and reliable servicing stack so that your devices can receive and install Microsoft updates.

I actually see both of these in my WinRE.wim now so I don't know if .3385 got put back after the October update. In your case, I'm wondering why the October update may not have fixed the September update.

Can you determine the last modification date/time for your WinRE.wim?

Thanks to Mustang's advice

After creating the Advanced Rescue Media use the ADK & WinPE Add-on

I was able to finally book into the Acronis Rescue Media and clone my M.2 drive.