vvlauncher, Windows 10 and mapped drives

[Iskador]

This isn't really a problem now as I've found a fix, however I just to know whether this it is going to be fixed?

The problem is with vvlauncher under Windows 10 can't see mapped drives anymore or networked folders.

I had upgraded my PC to Windows 10 (from Windows 7) and upgraded ViceVersa Pro to build to 2517.
I use vvlauncher to run a backup every hour on mapped drives from one NAS to another NAS. All worked fine under Windows 7.

on first run after upgrading to Windows 10, vvlauncher reports that source folder is not found.
When I go to "Open profile" and then to Source/target select. click on the folder icon to browse for a folder.
the Software won't show any network drives/mapped drives under This Pc or via Network.

Instead you have to put in the full UNC path in select folders. Then it works. Anyone else has this problem this is how you fix it.

[TGRMN Software]

Hi, mapped drives always had an issue since Win 7 due to UAC.
Maybe you had UAC disabled in Win 7?
Please see:

https://technet.microsoft.com/en-au/library/ee844140(v=ws.10).aspx
and
https://support.microsoft.com/en-us/kb/3035277

Also you can use UNC paths directly instead of mapped drives:
http://www.tgrmn.com/web/kb/item93.htm

thanks
_________________
--
TGRMN Software Support
http://www.tgrmn.com
http://www.compareandmerge.com