this is UAC issue, you can Enablelinkedconnections setting in registry to fix it:
https://docs.microsoft.com/en-us/troubleshoot/windows-client/networking/mapped-drives-not-available-from-elevated-command#detail-to-configure-the-enablelinkedconnections-registry-entry Stefan schrieb am Dienstag, 22. September 2020 um 18:12:45 UTC+2: > On Tuesday, September 22, 2020 at 12:09:57 PM UTC+2 Tobias Knauss wrote: > >> On our business computers we only have C:, but I prefer also having D: >> for my work files, so I mapped c:\d\ as DOS device "D:", as described in >> https://superuser.com/a/29076 >> >> But when executing the installer from this virtual D:, the installer >> failes with error 2755, see >> >> https://www.windowsdigitals.com/the-system-cannot-open-the-device-or-file-specified-error-2755-windows-10/ >> >> The solution is starting it from the original path in C: >> >> Other installers don't have that problem, so you might be able to solve >> it also. It's not a serious problem, but finding the root cause took some >> time. >> > > No, sorry. > msi is basically a database file. The installation is done by msiexec and > the underlying service (both come with Windows). And since the installer > service runs as the "SYSTEM" user, there's nothing I can do about that. > > -- You received this message because you are subscribed to the Google Groups "TortoiseSVN" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/tortoisesvn/2f6cd200-fba6-447f-8645-0bfcaaec6d96n%40googlegroups.com.
