I found a workaround by using a soft link from the network share to a folder on a local device, so for me personally, it's not a big issue.
I've been experiencing problems with network shares for quite some time, and one of the reasons this is an issue is a quite obscure feature in Windows that isn't that well documented. The problem is that a folder mounted for the user you are logged in as, is not mounted for the admin account you elevate to when you run something as an admin. The results are usually seemingly strange errors complaining about files and folders not existing when the user clearly sees them. The only proper solution I've found when working with systems needing access to shared folders, is to open a command prompt as admin, and then run 'net use x: \\my.network.share' to mount the share to x:. After this, the path is accessible even when running as admin.
This approach, however, is more than a bit tricky to implement in the bat-script needing the access.