Inner Space launch issue

[hpavc]

I recently upgraded to a new computer, from windows 7 ent to windows 10 pro, fresh install of isboxerbundle

I have a shortcut to Innerspace.exe in shell:startup, sadly it doesn't run. All my other apps (CurseClientStartip.ccip, Wowhead_Client.lnk) run fine.

* The shortcut is run as administrator, the short cut is just 'right click' -> 'create shortcut', windows+r, shell:startup, move shortcut into shell:startup window.
* I have a the UAC set to Never notify and I am a local Administrator.
* When I click the icon in shell:startup ... perfect runs (no prompting), but nothing otherwise.
* There isn't already a innerspace running (normally I see the 'already running')

Oddly if I create a innerspace.cmd with the following contents, this works (as a shortcut or the script in the shell:startup).

cd C:\Dist\InnerSpace
C:\Dist\InnerSpace\InnerSpace.exe
Pause

I see that the internet has a lot of this related issue, but not much on why or solution ... just curious if someone knew the issue that windows 10 has. Signed code?

Thanks!

[bob]

It's not a Win10 issue. It was also present in Vista, 7, 8, 8.1.

The shell handler which starts the "shortcuts" in the Startup Folder is running as a restricted user context (regardless of the permissions of the logged in user!), so Admin required applications will fail to start. It is designed like this to prevent applications needing Admin access to start up via this method, specifically to prevent dodgy as software from gaining control of your system during the initial startup/login.

You can try adding a link to the shortcut in the following registry key instead as this will (sometimes) allow processes to start under an admin context.
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Run

The other choice will be to use the Task Scheduler trick.
http://www.sevenforums.com/tutorials/11 ... reate.html
(yes, that is the Win7 forums, but the process applies on Win10 too).

I use a slightly different method with the Task Scheduler for LGS, but it does what it is supposed to and starts my process in an admin context, without prompts, even though I have UAC enabled.

In all cases, it appears that the method to use is a bit of indirection, in that the item in the Startup group needs to run as a low privileged user, and then that starting process, in turn can call for another process to start, which can be an admin required process.

[hpavc]

Thanks, I never encountered that with win7 or 8, I'll use the batch file since that is working I guess.