Skip to main content

Must reboot for local clone

Thread needs solution

I originally posted this on Lee Turners "reboot required", stated new topic as I don't want to complicate his issue.

My problem is that cloning is my preferred  method of backup, but recently TI 2019 has been requiring a restart. Today, I attempted to clone my "C" drive SSD to the same size SSD mounted in a usb docking station,  (something I've done many times since upgrading to TI 2019). TI locks the C drive, then pops up with message that restart is required. I've cleaned the drive with disk part, no help. I with tried on unallocated drive, no help. Tried with different docking station and different target had drive, no help. I performed a repair on TI 2019, no go. I downloaded TI 2019 from my Acronis account, uninstalled TI & re-installed, still requires restart. Any suggestions? last log attached

 

Attachment Size
restart required.JPG 83.79 KB
0 Users found this helpful

Well, looks like it is my laptops version of windows, and not Acronis, causing this. It dawned on me that the problem started after the last windows insider update, vesion 18351.19h1_release.190301`_1611. I tried cloning on my wife's desktop (windows ver 1803) and it works fine. I cloned an empty drive within windows with no restart. Then used the same drive with windows installed and "re-cloned" again. All works fine.

When I have more time I will revert my laptop to an earlier (working) windows build. If that version works without needing to restart, I'll try windows ver 18351 again to confirm that it is causing my cloning issue. 

Nice find - I bet you're right.  Windows insider versions have been known to break things in 3rd party apps. In fact, in testing our MVP winpe tool, we found that the insider builds usually have broken WinRE (recovery) environments as well.  All of the WinPE we created with insider builds using the system WinRE has failed so far.

Unfortunately, Microsoft makes changes (some of them buggy) that modify the behavior or security or underlying functionality of the OS that 3rd party apps have to reconfigure to work with again.  Can't fault apps for not working in beta software that hasn't been publicly released and put into full retail production.  And when that does happen, applications that are integrated into the OS (backup software is a good example since it relies on the OS too for things like VSS snapshots) are more likely to be impacted.

Looking forward to your results of your test.  Thanks for the input!

Using insider builds of Windows can cause all sorts of (unexpected?) havoc. Like other vendors, Acronis does not support insider builds.