Software installation on Windows 10 64-bit system won't run - lack of permissions?

Dear Experts, I created a little software program (in Delphi) and have a few users of it. The installation package for it was created with a now defunct software called "Install-Us" (www.install-us.com, and author will no longer support it). However, it has always worked fine and has installed okay on 32-bit and 64-bit systems alike. The other day one of my users with a Windows 10 64-bit system had this problem : after successful installation, he would try to launch my software from the normal START menu program group that gets created. Only my initial splashscreen would display, and then it would "hang" there for a while before simply self-aborting (no error message). However, if I would go directly to the folder my software got installed to, and double-click the exe file there, the software launched fine! I tried making a shortcut of the main exe right there in that folder, then moving the shortcut out into the Desktop, for the ease of my user. Launching from this shortcut wouldn't work and did the same "hanging" that I described before... even if I set the properties of this shortcut to "Run as administrator".
    In my install procedure (using Install-Us), it has the facility to be able to execute some Windows commands during the installation process. Upon advice from an older question to EE a few years ago, I am running this particular command during my installation process:

icacls %Install% /grant "everyone":(OI)(CI)F

... in order to combat any "permission" problems my users might encounter with the installation (the "%install% variable is a built-in variable with the Install-Us package to signify the target installation directory). Seems to have worked fine up until this time. This Install-Us package I'm using was last updated in 2012, and has no specific facilities or settings for 64 bit systems, although it has been successful so far with my users who do use 64-bit. So I guess my question is - should this icacls command be modified in any way to reflect the peculiarities of 64-bit systems, or is it okay as is? Any thoughts on my running the exe *directly* from the installation folder would work, but a shortcut of the exe wouldn't?

Thanks!
   Shawn
shawn857Asked:
Who is Participating?
 
McKnifeCommented:
You modify only the shortcut property called "start in" of the shortcuts in (again) the personal start menu is located at
%appdata%\Microsoft\Windows\Start Menu
and the common start menu at
%programdata%\Microsoft\Windows\Start Menu

That's all. No "run as administrator".
0
 
McKnifeCommented:
Edit your shortcut and enter the program path into the "start in" line.
0
 
shawn857Author Commented:
Thanks McKnife, that's a temporary fix... but it still leaves me with the problem of why my program wouldn't start up when invoking it from the normal program group entry in the Windows START menu.

Thanks
    Shawn
0
 
McKnifeCommented:
That is a shortcut-problem, too - the personal start menu is located at
%appdata%\Microsoft\Windows\Start Menu
and the common start menu at
%programdata%\Microsoft\Windows\Start Menu
Check those shortcuts.
0
 
shawn857Author Commented:
OK thanks, I can try to log back on to my user's machine to check those when it's convenient for him. What should I be looking for? Should there be some setting set in those shortcuts to "Run as Administrator"?

Thanks
   Shawn
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.