Missing Drivers After Clone Disk - Windows 10
Acronis 2018 has a major bug in the latest build, when you perform a Clone Disk to the SAME hardware (eg upgrading to larger Disk) on Windows 10, various Drivers in device manager show as missing including Audio Driver, WLAN, etc.
I have performed various troubleshooting tests including:
- Using 3 different computers.
- Building new Bootable Media from different computers that i have Acronis 2018 installed.
-Downloaded the latest Bootable media from the Acronis Dashboard.
All tests Result in missing drivers.
Again i'm cloning to the exact same computer, just upgrading to a larger disk. I am also not using Universal Restore, just the standard Acronis 2018 Build.
Now here is the interesting part - Acronis 2017 Bootable media works perfect.
I will add that im a computer technician and have been using Acronis products on a daily basis for the last 7 years.
Anyway i have performed so many troubleshooting tests, i conclude that this is a bug in ATI 2018.
Pete, if you have done all this testing to reach your conclusion about ATI 2018, have you opened a Support Case with Acronis to report this and have them investigate your findings?
If not, please do so, we are just a User Forum here and cannot fix any bugs in the code.
Like Enchantech, I have no explanation for why device drivers should be missing following either a clone or a backup / restore operation, but would need more information to full understand exactly what actions are being performed in this scenario and how being done etc?
In reply to Are you using the Acronis… by truwrikodrorow…
Im using the Bootable recovery CD, to perform the Clone Disk Task.
Same process i have been using with every Acronis since 2013.
Also worth noting, today i installed Disk Director 12 and Acronis 2018 on a Brand new Out of Box Laptop. I then created new Bootable USB using the Disk Director Bootable Media Builder to see if that would work.
Unfortunately the same result with missing drivers.
Pete,
I can only advise that the media you are creating is linux based which you probably know already. The Linux based media has taken a back seat as it were because with the release of TI 2018 the move to WinPE based Recovery Media is now the default standard. This change was made to provide better driver support for the product. It is unclear how much if any further development of the Linux based media has occurred since this change.
I would advise that you create WinPE based media instead and test again. I myself, when needing to clone, do so now from within the Windows TI application which now supports LIVE disk cloning not requiring a reboot of the machine. This has worked flawlessly for me except for one caveat. In testing I found that if the target disk has an OS on the disk in some cases the TI app will request a reboot to run the clone process. To avoid this I have found that running Diskpart Clean command on the target disk prior to cloning fixes that issue.
@Pete i get the same thing! Inside TI 2018, i created a WINPE bootable media.
I cloned a Lenova all in one desktop to an external USB drive. I then tried to clone it to a same Lenova all in one, out of the box with the exact same hardware components.
After the successful clone image dump, the new machine is missing several drivers. In device manager, it was missing Audio and USB devices.
I wish i had 2017 TI to compare and see if this 2018 TI version is the buggy one. SMH...
Jeff & Pete, the only time that I have seen an issue with missing drivers has been where Acronis Universal Restore looks to have been invoked as part of a clone or recovery scenario, and this can be seen to be happening by looking at the log produced by Acronis for the clone or recovery.
If you are using the Acronis bootable Rescue Media, then the Log needs to be saved to the drive or a USB stick before you shutdown the media and restart the computer, as it is lost when doing so.
I agree with Steve here. The logs will tell the story.
I am having the exact same issue and some more issues. How do I get hold of Acronis True Image 2017?
Here are my environment details:
Lenovo Lavie Z 360 laptop with factory-installed Windows 10. It comes with a 250GB M.2 SSD (Samsung).
I am looking to upgrade to a 1TB Crucial MX500 M.2 SSD. So I have been trying to clone the existing SSD to the 1TB SSD using Crucial's recommended cloning software Acronis True Image.
I had to create a bootable USB and boot into Acronis True Image. I could not clone from within Windows 10 because Acronis would keep asking me to restart without completing the cloning.
After creating bootable USB Flash drive I was able to clone the disk successfully (or so I thought), until I realized the upgraded computer did not recognize any audio devices.
So the audio drivers have become messed up or have gone missing. If I plug the original 256GB SSD back into the laptop, and run Windows from it, audio works fine.
So I decided to redo the cloning. Now it gives me a new error "Failed to write data to the disk. Failed to write to sector '334,650,168' of hard disk '1'. Failed to write the snapshot manager volume (0x 1000D3).Unknown status (0x9). Access is denied (0xFF0)
Sunny, welcome to these User Forums.
Please see the following documents:
KB 2201: Support for OEM Versions of Acronis Products this applies to your Crucial supplied Acronis software with is an OEM version.
Forum topic: [IMPORTANT] CLONING - How NOT to do this which offers advice on how cloning should / shouldn't be approached. One key recommendation is to make a full disk & partitions backup before doing this type of operation!