Skip to main content

Windows 10 Update: Acronis won't recognize drive and constantly shuts down machine when running.

Thread needs solution

Not sure if this is a Windows 10 issue or Acronis, but everything has been running great and tonight Windows 10 put on an update and Acronis will not do its incremental backup to an attached 4 TB secure drive. Says I need to attach the drive but it is there, I can see the files from the previous backups through Explorer....

If anyone else sees this problem, please let me know so I don't keep struggling with it.

Cheers,

- Pete

0 Users found this helpful

Pete, perhaps an obvious question but which isn't indicated in your post above, what particular update are you referring to here?

The only current update for Windows 10 that I am aware of that was made available yesterday is the Windows 10 Insiders 17063 update.

If this is the update you are referring to, then please see: KB 60589: Acronis True Image: Windows Insider Program (beta) builds support

I haven't had time to check how Insiders 17063 works with ATI 2018 as my computer decided that it had an 'inaccessible boot device' after installing this one and I had to restore my latest Acronis backup (from yesterday) to get past the boot problem.

Pete,

Sounds like the drive letter may have changed due to the upgrade, have you checked that?

Thanks guys. I did check the drive lettering as that is a common mistake I do make (it is kind of like asking someone to check their power light before calling support - "Oh heck, your right no power!" I spent a few years as an IBM S.E. and always loved the pause and laugh that came over the phone when a large percentage of the time the customer realized it was a cabling problem. ;) Of course that was an AS/400 that just never failed, not Microsoft.

I rebooted a few times and finally got the incremental backup to recognize the drive (which I could see and access). I will see if everything goes better tonight. It is at the point of doing the next full backup. I figured I would post this up just in case someone else seems some strange behavior.

I didn't check what update it was from Microsoft, but I assumed since it was Tuesday, it was the "normal" Microsoft Tuesday patch fix for all things broken at Microsoft - and to break new things for them to fix the following Tuesday. ;)

For now, we are good to go unless someone else sees something going on, or I have issues tonight.

Thanks again guys - love the backup software. Thanks for jumping in.

- Pete

Pete, thanks for the update. 

You are showing your age a little by mentioning AS/400 which of course was rebranded to iSeries some long time ago now.  I worked in Rochester, MN on these systems on assignment in Software Support from IBM UK.  

Also the drive I am using is a 4 TB hardware-secured drive from Aegis: the Padlock DT hard drive. I had to make some manual registry changes to Windows 10 get their 2 TB drive to work, but hadn't had any problems with their 4 TB drives - (just installed them a few weeks ago) they were and will be my first suspect if I have further problems tonight. Good stuff if you don't trust the cloud security model, just something that isn't used everyday by an every day user.

Cheers,

- Pete

Steve, it will always be an AS/400 to me! I actually just wrote a book and did some research on the Future Systems project that helped produce the AS/400 for a chapter on Cary and the 70s at IBM. ;)

Have a good one.

Cheers,

- Pete

I have a similar problem on my laptop: Acronis doesn't see the attached USB hard drive although the drive letter has not changed and I can browse the drive using Windows Explorer. My laptop is also a Windows 10 machine with the latest Windows update and the latest Acronis build.

Maybe the issue is related to the problem described in KB 60612?

https://kb.acronis.com/content/60612

What works for me, and only because I do backup on demand on my laptop, is to simply click the "change destination" box on the backup screen. I don't change anything but that seems to wake up Acronis to the fact that the drive is really there.

kb 60612 gives some basic troubleshooting techniques for the situation.  The basic reason is assumed to be device detection failed in Windows.  The best way to force device detection is to disconnect the drive data cable from the computer, shutdown the computer (not a reboot), start the computer again, once you have logged on and Windows has fully started attach the device back into the computer.

Thanks for all the suggestions. As usual, the one that worked best was "don't overreact after a Microsoft update on Tuesday nights." ;) Everything has been working fine since the machine was rebooted several times. I did notice at one point that a new USB driver was loaded, but whether that was just a hitch in the update I don't know.

Anyway, next time I will wait a few days. I don't usually have so many changes in a day that it can't wait. This was an unusual day of a lot of work that I couldn't take the chance of losing and was blindsided by the Microsoft process of going to shutdown and suddenly seeing that there was an update to install. I usually backup before letting them do such nonsense.

Cheers and thanks again,

- Pete

Pete...you may want to take a look at the following thread:

https://forum.acronis.com/comment/433509#comment-433509

Apparently, a windows update can change the drive signature.