Installer gives "Invalid Drive" error when installing Payment Terminal in a networked environment – Verosa

Problem

When installing the Payment Terminal on a device/user profile which uses network drives, it's possible that an "Invalid Drive X:\" error will pop up during installation (where X:\ is the drive letter of a networked drive). This tends to occur if the user's shell folders have been redirected to a network drive (either the drive in the error, or another network drive).

Explanation

This information is intended for IT professionals. If you're not an IT professional, feel free to forward this information to your IT team for a more complete resolution.

This issue generally occurs if the network shares are mapped for the user on the system, but are not mapped for the built-in Administrator user (which the installer is run as after using UAC). If a shell folder, temp folder, installer folder, or other folder used by the installer is on one of the aforementioned mounted network drives, the installer will pop the error mentioned, and stop the install process.

This issue generally does not occur if the shell folders are redirected to UNCs - as the path is still accessible under the Administrator user (using cached credentials from the currently signed-in user). The issue itself centers around the lack of the mounted network drives, which this guide focuses on fixing.

Solution

Open a Command Prompt window.

Open the Start menu by pressing the Windows key, type cmd, and pressing Enter.

Make sure you've launched a standard Command Prompt - the window title should not have Administrator in it.

Get a list of mounted network shares.

In the Command Prompt dialog, enter the command net use, and press Enter. You'll be given a list of mounted network shares, including the Local path (the drive letter/folder the network share was mounted to), and the Remote path (the UNC/network path to the network share).

Open an elevated Command Prompt window.

Open the Start Menu, type cmd, make sure that Command Prompt is highlighted, and press Ctrl-Alt-Enter.

Make sure you've launched an elevated Command Prompt - the window title should have Administrator in it.

Get a list of mounted network shares (from the Administrator user context).

In the elevated Command Prompt, enter net use, and press Enter. You'll be presented with a list of current/previously mounted network shares.

Mount any missing network shares.

Compare both the non-elevated and elevated Command Prompt windows. If any of the entries in the non-elevated window are missing from the elevated window, add them using the following command: net use X: \\server\share, where X: is the contents of the Local column (drive that the network share was mounted as), and \\server\share is the contents of the Remote column (path to the network share).

Start the installer again.

Relaunch the PTSetup.exe file to restart the software. Be sure to allow UAC to elevate the program.

If the issue persists, it may be necessary to launch the installer from the elevated Command Prompt window (depending on system settings). Locate the installer in File Explorer, hold the Shift button, right-click on the file, and click Copy as path. Then, paste that path in to the elevated Command Prompt window, and press Enter.