Some new troubles with the MVP WinPE recovery media
Last month I was dealing with an issue of not being able to access my Synology NAS with the recovery media. After lots of testing with Bobbo to get the right configuration, I created an MVP recovery media under Windows 1803 with the ADK for version 1803 and ATI 2018. I also used the command net use \\NasBox\Acronis /user:<Unserid> <Password> to get access to the NAS.I was successfully able to make my backups.
Well, today I tried to run the same thing and I was getting weird errors. First, as soon as I selected a back name, I was getting an Acronis error message saying:
You have selected a remote resource and have not
specified credentials for it. Do you want to continue?
In the case when the credentials are really required then the task may fail.
Note: in order to specify a user name/password for this resource select it and click the
Authentication settings button on the toolbar.
When I go to the Authentication settings, it works just fine to access the NAS. Also, I am able to see the NAS, navigate through its folders and even create a new folder.
In some cases I tried to move on and nothing would happen for a minute or so and then it would fail. The log had the following messages:
Operation "My Disk Drives Backup" started.
Please close the application that may currently use the file: ...
Cannot open the backup.
Access to the file is denied.
Access to the file is denied.
A specified logon session does not exist.It may already have been terminated.
Backup operation failed.
In subsequent tests, I after booting the recovery media I use the net command, but to assign a drive letter. I could then see the drive letter in Acronis and also had no problems in navigating around the NAS drive. But I still got the specified credential error box. So I answered Yes to continue and the backup seemed to work. But after it completed I was seeing the following in the log file:
"Pending operation 173 started: 'Creating partition image'."
"Volume Tracker has failed to open session '\Device\HarddiskVolume3' for volume '\\?\Volume{49983a45-ec83-4ece-ad26-745753334f7f}\'."
"Pending operation 173 started: 'Creating partition image'."
"Volume Tracker has failed to open session '\Device\HarddiskVolume4' for volume '\\?\Volume{97e16b3d-7e26-4d96-90af-d48b3c983c0e}\'."
"Writing full version to file: C_full_b1_s1_v1.tib"
"Pending operation 173 started: 'Creating partition image'."
"Volume Tracker has failed to open session '\Device\HarddiskVolume6' for volume 'D:'."
"Pending operation 173 started: 'Creating partition image'.
"Volume Tracker has failed to open session '\Device\HarddiskVolume7' for volume '\\?\Volume{28635cbb-3d24-4f12-baca-95e152c487f2}\'."
"Pending operation 173 started: 'Creating partition image'."
"The following backups have been successfully created:<endl/>"O:\Zomo (Z270M)\Recovery\Windows 1809 Build 437\C_full_b1_s1_v1.tib""
"Backup operation succeeded."
(The full log file is attached).
By the way, after creating the backup and rebooting back to Windows 10, I ran an ATI validation on the file and it passed. Looking at the size of the file and the contents, it looks like the backup itself is all OK.
So, why am I seeing these errors where it worked perfectly last month. Well, the one thing that changed is that I upgraded my PC from Windows 1803 to Window 1809. So, I am thinking that maybe the credential issues were not in reference to the NAS destination but perhaps my C: drive source. Does that make sense?
Is it imperative to rebuild a new Rescue Media after a change in the base OS? I would not have thought so, but maybe? I think I first need to update the ADK from 1803 to 1809 version.
Bobbo, what do you think?
Hi BrunoC,
Your upgrade to Windows 1809 is at route of your issue I am confident. With the release of 1809 MS has made further changes to the SMB 1 Protocol.
My advice would be to add the domain name in place of the username in your net use command as shown in the example below:
net use \\NasBox\Acronis /user:workgroup/<Unserid> <Password>
The above will authenticate you the user at the Domain level and not the user level. This in turn should resolve all the errors you are seeing.
Once you boot the MVP media close down the True Image application, open the command prompt and run the net use command above. Then open True Image and see how it behaves afterwards.
One other recent change to my system was to update the Samsung NVMe Controller from version 3.0 to 3.1. Could that have any effect? Would I need to add this driver to the MVP media? I never added the last one on the prior media.
Your Samsung Controller driver does not need updating as it has no effect in drive detection.
If the net use command I suggested does not help then substitute the hostname in the command with that of your Primary network IP address. Example: 162.168.0.1
Enchantech, there was no change. I am not having any trouble accessing the NAS so I'm not convinced that error message is directly related to the NAS.
I am more concerned that for each source disk partition, I am getting logged
Volume Tracker has failed to open session '\Device\HarddiskVolu<n>' for volume ...
followed by a message
The specified module could not be found.
This occurs whether I'm backing up the C: SSD or the D: WD drive.
Apparently the backups are good. But what is curious is that I get errors on both Rescue Media... one created under Windows 1803 with the 1803 ADK, and now with Windows 1809 and the 1809 ADK. But the 1803 version did not have these error when I ran it before updating windows to 1809. So I'm curious... is there something on the C: and D: drives that used to be there but has been eliminated with the Windows update... something that Volume Tracker is looking for? And what exactly does Volume Tracker do, especially when doing a Full backup where changes are not tracked.
I'm not certain but I think Volume Tracker is a tool that tracks Volumes via the UUID of the drives. I have heard that this UUID number can change as a result of Windows version upgrades so this could be in play here I suppose.
I think opening a Support case on this would be appropriate as this is a totally new development with the Recovery media to be best of my knowledge.
I'd thought about something on this front, but then creating a whole new rescue drive would leave me to wonder where in the world an old UUID may have come from. Is there something in the database on ATI on the PC that gets put into the rescue drive?
And why is it that I could use a rescue drive created on a different computer and it would not generate such errors.
I just tried two other Rescue Media drives, created with Bobbos help to try out ATI2019 with the ADK 1803, and to try ATI 2018 with the ADK 1809. Both of them are now showing these new issues whereas they worked before I updated to Windows 1809.
One more piece of information.
I ran the rescue media to backup my C: drive to the D: drive. I did not get the superfluous unspecified credentials message since I wasn't backing up to the NAS. So I guess I now that that is definitely related. But all the Volume Tracker warnings in the log are still there. So, two separate things work differently as a result of updating to Windows 10 Version 1809.
And running backups from the Windows UI shows no issues.
Well, I do not have any definitive answers for what you are seeing. I can say that 1809 introduced some new wrinkles that have yet to be resolved in a few areas not the least of which is networking. If you search the Web you will see many having issue with device discovery (devices not showing up in Explorer), mapped network drives disconnecting and not being able to reconnect, file associations being lost, even BSOD and sound problems.
Seems that the user is left to sort things out for themselves with some of these problems. As to if these issues are related to True Image media I can only say that I have not seen them on any of my machines but that does not mean they are only present for you either.
Submit a support request and see what happens, maybe it can be sorted for you.
I just ran a test by using the WinRE Acronis built Rescue Media that I created in March. I am not getting the Volume Tracker errors on that version.
If that is the case then I would say that the disk UUID has not changed since then even though you have upgraded to 1809 since that time.
I have noticed on occasion that I might get these errors with Volume Tracker but I always discounted them as the task always completed successfully. Your log shows that to be true for you as well.
I believe that I have only seen such errors in the Windows installed app and to the best of my recollection I do not remember having seen them in the Recovery Media.
I can only say that if you want an answer about these errors you need to open a support ticket.
I believe that I have only seen such errors in the Windows installed app and to the best of my recollection I do not remember having seen them in the Recovery Media.
I have been using the same Acronis UEFI Recovery Media image for about 18 months and added a synology drive about 6 months ago. It HAS been working fine til about 2 weeks ago, now everytime I tried to log in to the synology drive it says "you have selected a remote resource and have not specified creditials for it....." and that's happening AFTER I correctly logged into the nas drive with my credentials, and I've selected the folder/file.
Any ideas? anyone?