Skip to main content

Rescue media won't log in

Thread needs solution

I'm running Acronis 2016 on a number of PCs and back them up to a Win10 PC that acts as my backup server. I have, on a number of occasions, used the rescue media to boot into one of the machines and restore from the server backup. The problem is, that now seems to have broken.

I have one PC I need to restore and the rescue media will not log in to the Win 10 server. It boots fine and can see the server and asks for credentials, but when I enter them it says there is a connection error and to recheck the username & password. These are correct.

I can connect to the server from other PCs, browse, remote connect, etc. It is just the rescue media that gives the connection error when you enter the username and password.

I tried the rescue media on another computer I have and got the same error. Please help!

1 Users found this helpful

Glen, welcome to these public User Forums.

If your rescue media has worked previously to connect to your Windows 10 PC / server and the media itself has not been changed, then this issue is most likely caused by changes introduced by Windows 10 to improve security.

See the following webpages:

1. Disable SMB Version 1.0 in Windows 10

2. How to access files on network devices using SMBv1 on Windows 10

3. How to check SMB version on Windows 10

4. SMBv1 is not installed by default in Windows 10 version 1709, Windows Server version 1709 and later versions

One option here would be to copy your backup archive(s) to a USB drive then connect that drive to the computer you need to recover from the rescue media.

Thanks for that. Copying to USB gets me out of the immediate hole. Do I need to re-enable SMBv1 on my Win10 server to allow future connection by the rescue client? If so, what needs to be enabled? I can see:

  • SMB 1.0/CIFS Automatic Removal
  • SMB 1.0/CIFS Client
  • SMB 1.0/CIFS Server
  • SMB Direct

Which of these (or all) needs to be enabled?

Thanks again

I have followed that guide and enabled all the SMBv1 components in the add or remove windows features, but I still get a failed connection.

Glen, you may need to do a Windows restart after making such changes to make them effective.

Excellent. All works now following the reboot. Thanks for your help Steve.

Are later versions of Acronis True Image affected by this, or don't they need SMBv1? I have been considering upgrading.

The latest versions of ATI from 2018, 2019 & 2020 have started a move away from using the older Linux based rescue media that is used in ATI 2016 and now create WinPE media with files taken from your Windows Recovery Environment, so should pick up all the required drivers to support the protocols being used, i.e. SMB 2 & 3.

Glad to read that the reboot of Windows have solved the immediate issue for SMB 1 used by the ATI 2016 rescue media.