Mount Point Broken in Windows 10 Anniversary Update
Immediately after installing Windows 10 Anniversary Update, TI 2016 can no longer backup to the destination mount point.
Checking the logs, i verified that it worked fine before the update was applied.
I deleted and then recreated the mount point and then attempted to change the destination of the backup to the mount point.
TI 2016 destination browser window does not even display the mount point as being a possible backup location.
Since Im past my 30 days purchase tech support window, Im relegated to asking the community for help. Acronis doesnt feel customers reporting bugs past the intial 30 day window is worth a phone call.
Can anyone please try to verify this or suggest a fix?
Thanks in advance
I think it's simpler than that...
Windows 10 is a new install of the OS. With each install of Windows 10, Windows recreates the recovery parition - hence, changing the hard disk ID. As a result, Acronis sees the disk as a new/different one based on the disk hardware ID created by Windows after the upgrade.
In most cases, simply editing your backup task and re-selecting the source (even though it will be exactly the same as far as we see it), should get the job working again.
Hi,
I dont think TI 2016 is EOL just because 2017 shipped. 2017 doesnt offer me any features at all that I need. I suspect Acronis will stop development on 2016 but issue patches if warranted.
As to the the idea that I simply need to edit the backup task, as indicated earlier. I DID.
The problem is NOT that the source location is invalid now, its that the DESTINATION is invalid.
Even after recreating the mount point, i cannot choose it as a valid destination. The mount point is not visible in the TI destination window tree view where you see a list of all drives/folders and you are expected to choose one as the destination location.
Any ideas?
Followed upgrade instructions as suggested above.
TI 2017 installed fine.
TI 2017 does NOT recognize the mount point either.
Simple bug, pure and simple with no way of getting Acronis tech support.
Sweet!
TI 2016 destination browser window does not even display the mount point as being a possible backup location.
What is your destination. Is there anything unusual about it? Does the Windows File Explorer have any problem getting to it?
I was considering upgrading to the Win10 AU, but I may hold off depending on the outcome of this issue.
I have a dedicated backup drive mounted to D:\Backup
There is nothing special about it. File Explorer can access it fine, crashplan can too.
It worked perfectly for over a year and died the exact day that I upgraded to anniversary edition
Do have any other device you can temporarily use as a backup destination - USB flash memory or something? If so, see if TI can see it as a destination. It would be worth knowing if this is a problem with all destination devices or just your specific D: drive. If it is a problem with only your D: drive I'd suspect a driver problem. Perhaps you are getting an error that the Windows File Explorer handles (or ignores) but that Acronis is sensitive to. Is possible that, as part of the AU installation you are now using a Microsoft generic driver instead of a better driver from the disk manufacturer. What is the manufacturer and model of the drive you are using?
We're not likely to see any more version updates to 2016 - might get one more, but we'll have to wait and see.
As for mounting not working, have you tried the tibmounter patch?
Paul, please can you clarify exactly what you mean by "I have a dedicated backup drive mounted to D:\Backup" ?
If this was a physcial internal or external drive then Windows just allocates the drive letter as D: but this sounds link you are using a symbolic link here?
What is the original path for this backup drive before being mounted to D:\Backup ?
Even after recreating the mount point, i cannot choose it as a valid destination. The mount point is not visible in the TI destination window tree view where you see a list of all drives/folders and you are expected to choose one as the destination location.
Does anything show as a valid destination location?
Everything else is perfect. The mount point is simply missing.
It would really be helpful if you answered Steve's question " What is the original path for this backup drive before being mounted to D:\Backup ?", and I'd still like to know what the make and model of that drive are. (I don't know squat about Acronis, but I might be able to find something regarding Window's support of the drive. And I'd really like to do that before I instal the AU.)
This is an internal IDE drive. It was 2 years ago mounted as drive E: by default. I had to delete that mapping
Mount pointed drives do not have paths before mounting. In fact, if you did mount it normally like E: or something, diskmgr would force you to remove the drive mapping before mapping it again as a mounted volume
The volume is on drive 6. Using diskmgr, you right click on the volume and you add NTFS mount point. At that time you have to choose an empty folder on the host volume. For me, that is d:\backup.
The drive is a 6 TB WD model WD60EFRX-68MYMN1. The volume and the controller are using the same driver as before the upgrade.
Either way, bottom line is that the mount point works fine with every application EXCEPT TI 2017. PERIOD. Crashplan, Backblaze, and I even tested ShadowProtect.
When I unmount the drive and map it as E: for testing purposes, TI works properly. It simply refuses to handle mount points properly.
Can anyone suggest a scenario as why my drive model or driver version makes any difference at all? Windows thinks its fine, I think its fine, all my apps work perfect. But somehow there is this magic scenario that ONLY TI doesnt work, other than this is a simple bug?
This is an internal IDE drive.
In that case, as far as drivers go, you would need to check the driver for the IDE controler. Windows uses a generic driver, but if the controler is, for instance, an Intel chip, you need to check the web site of your motherboard manufacturer to see what driver is recommended for that chip. And if you can't find that information you should check on the Intel web site.
That is probably not your problem, but it's worth checking anyway.
It was 2 years ago mounted as drive E: by default. I had to delete that mappingMount pointed drives do not have paths before mounting. In fact, if you did mount it normally like E: or something, diskmgr would force you to remove the drive mapping before mapping it again as a mounted volume
The volume is on drive 6. Using diskmgr, you right click on the volume and you add NTFS mount point. At that time you have to choose an empty folder on the host volume. For me, that is d:\backup.
Oh! You are removing the drive letter and mounting a drive as a folder. Is that right? That's an unusual enough situation that Acronis may not have verified that they support it under Win10 AU.
The drive is a 6 TB WD model WD60EFRX-68MYMN1. The volume and the controller are using the same driver as before the upgrade.
Either way, bottom line is that the mount point works fine with every application EXCEPT TI 2017. PERIOD. Crashplan, Backblaze, and I even tested ShadowProtect.
When I unmount the drive and map it as E: for testing purposes, TI works properly. It simply refuses to handle mount points properly.
Can anyone suggest a scenario as why my drive model or driver version makes any difference at all? Windows thinks its fine, I think its fine, all my apps work perfect.
I wanted to know the make and model to make sure the AU hadn't back-leveled the driver, but, as I said ealier, the driver for the IDE controler is a more likely suspect.
But somehow there is this magic scenario that ONLY TI doesnt work, other than this is a simple bug?
I'd say that a configuration that fails only for one application running under one level of OS maintenance is probably not a simple bug, and it's going to be tough to determine whether the bug is in TI or the AU.
I just to get Acronis to access a drive mounted as a folder on a pre-AU Win 10 - version 1511, build 10586.545 - and was unsuccessful. The browse function got as far as the drive containing the mount point folder but did not show the folder. What level of Windows were you on when TI would see the mounted drive? My guess is that this isn't related to the AU.
My test may not have been very good - I used a USB flash memory stick formated NTFS.
Paul, thank you for the extra information.
I have to confess to not seeing any real benefit in removing a drive letter from an internal drive and then adding this back as a mount point, but this is your choice to make.
Have you tried adding the mount point while the IDE drive still has its assigned drive letter E:?
I tried this with one of my USB drives and can navigate the contents via the mount point in Explorer but when I tried to select the mount point as either the Source or Destination in ATIH 2017 then in the Source selection it is shown as a single 16GB file, whereas it is not shown at all in the Destination selection, except by the original drive letter for the USB stick E:.
This was on a Windows 7 32-bit system with ATIH 2017, which suggests to me that this has been the way Acronis works with mount points across various recent versions.
I will repeat the test on a Windows 10 64-bit system with ATIH 2016 and feed back the results. This will be Win 10 build 1511 as the AU has not got as far as the UK yet, not to any of my systems!
Update: I have tested this also on my Windows 10 + ATIH 2016 system and get the same results for both a 16GB USB stick and a 1TB external USB drive both mounted to folders.
ATIH source selection only sees the mounted drive as a single file (16GB / 1TB)
ATIH destination selection does not see the mount folder at all, but will show the orignal target drive if this has an assigned drive letter.
The process I am using to mount the drive is as follows:
Connect the target drive, then go into Disk Management, click on the drive and take the option for Adding / Removing drive letters. Click on mount in target NTFS folder and create folder if needed.
Viewing the mount folder in Explorer shows the contents of the mounted drive as expected.
I see the same behaviour for both ATIH 2016 and 2017 - mount point not shown as a folder for either source or target operations.
I just realized I have a similar to Paul's - similary but just opposite. He has a drive mounted as a folder; I have a folder mounted as a drive. That is, I have assigned a separate drive letter to a folder. (Yes, odd. But I have my reasons.) Acronis TI does not see that drive as either source or destination for backups. (Which is fine since I back up the entire real drive containing the folder.)
Paul has a folder that is no longer a folder - Windows has converted that folder into a pointer to a drive. I have a drive letter that does not point to a drive; it points to a folder. Acronis TI apparently does not handle either of these situations. But Paul says Acronis TI used to handle handle this.
If TI is supposed to support mounted drives and folders, perhaps it's time to submit a problem report to Acronis. (I say that assuming there is a way to do that.)