Installer fails with error 2755 if started from a folder-mapped local drive

[Tobias Knauss]

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.

When I used a batch file with subst command, the problem appeared at many installers, because the subst is per user, and when installing we have to enter the credentials for our local admin account, but this one did not have the required subst drive, so the path simply did not exist for the admin user. But after switching to a mapped drive, every installer works from D: except yours, so far.

[Stefan]

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.

[André Ziegler]

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  

[Tobias Knauss]

André Ziegler schrieb am Freitag, 25. September 2020 um 09:23:05 UTC+2:

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  

Thanks, but we're not allowed to edit the registry (DOS mapped drive was an exception).

And I think this will not help anyway, since we're not using the elevated account, but a different account (<username>_adm) with local admin rights, but without internet access. The DOS mapped drive usually works fine for all users, and installations from EXE and MSI can be done also from mapped drive D: using normal or admin account, just this MSI installer has issues.