When running a WiseScript .EXE on a Windows Vista machine with UAC enabled, map drives are not recognized as valid destination folders.
Steps to reproduce:
1. Open WiseScript Package Editor 2. Create a new installation using the Empty Project template 3. Add a file to the installation 4. Compile 5. Create a mapped drive on the destination machine 6. Run the .EXE 7. On the Destination Location dialog click Browse. The mapped drive does not appear in the drive list. 8. Type your mapped drive in the directory field 9. Click OK. You receive the message 'Invalid directory name specified or the removable media specified is not properly inserted.'
This appears to also be an issue on Windows XP when executing an .EXE using Run As. This is basically what UAC uses when you get prompted for elevation.
This occurs because mapped drive connections use the security context of the currently logged on user, and RunAs can't use this security context because RunAs is attempting to run programs under another user's security context. In the case of Windows Vista with UAC, even if you are an administrator most applications run as a standard user. When a task requires administrative privileges, such as installing an application, is invoked, the UAC prompt appears. When the user clicks 'Allow' to this prompt, Vista elevates the rights to full administrator access.
This issue has been fixed for Wise Installation Studio\Express 7 SP1 and Wise Package Studio 7 SP3.
Workaround: Use UNC paths instead of mapped drives
Applies To Wise Installation Studio 7.0 Wise Package Studio 7
This is machine translated content
Login to Subscribe
Please login to set up your subscription.
Didn't find the article you were looking for? Try these resources.