Jump to content


Photo

Cannot launch certain apps from the xoblite menu


  • Please log in to reply
7 replies to this topic

#1 thylascene

thylascene

    Newbie

  • Members
  • Pip
  • 5 posts

Posted 13 November 2020 - 06:11 PM

Trying to edit my menu.rc and a behavior I've noticed is that xoblite seems to not want to launch certain apps that are in certain protected locations like /Program Files` or /Program Files (x86) but others in those locations I can open just fine.

Things I've tried:
- Pointing to both the original locations as well as created shortcuts but to mixed results for various apps
- Taking ownership of the shortcuts that originated from these locations, which didn't fix anything

- Constantly reconfiguring & restarting, which also didn't fix anything

- Running Blackbox.exe as admin, which still didn't fix anything

Examples of apps that launch:
[exec] (Clip Studio) {C:\Apps\Shortcuts\ClipStudio.lnk} Target: "C:\Program Files\CELSYS\CLIP STUDIO 1.5\CLIP STUDIO\CLIPStudio.exe"
[exec] (Epic Games Launcher) {C:\Apps\Shortcuts\EpicGamesLauncher.lnk} Target: "C:\Program Files (x86)\Epic Games\Launcher\Portal\Binaries\Win32\EpicGamesLauncher.exe"
[exec] (Downloads) {C:\Apps\Shortcuts\IDMan.lnk} Target: "C:\Program Files (x86)\Internet Download Manager\IDMan.exe"

Apps I still have trouble launching:
[exec] (Clip Studip Paint) {C:\Apps\Shortcuts\CLIPStudioPaint.lnk} Target: "C:\Program Files\CELSYS\CLIP STUDIO 1.5\CLIP STUDIO PAINT\CLIPStudioPaint.exe" (its funny how CLIPStudio.exe was able to launch but not CLIPStudioPaint.exe)
[exec] (Unreal Engine) {C:\Apps\Shortcuts\UE4Editor.lnk} Target: "C:\Program Files\Epic Games\UE_4.24\Engine\Binaries\Win64\UE4Editor.exe"

[exec] (Precision Mouse) {C:\Apps\Shortcuts\MicrosoftMouseKeyboard.lnk} Target: "C:\Program Files\Microsoft Mouse and Keyboard Center\MouseKeyboardCenter.exe"

[exec] (Look for deleted files) {C:\Apps\Shortcuts\recuva64.lnk} Target: "C:\Program Files\Recuva\recuva64.exe"

[exec] (NVIDIA control panel) {C:\Apps\Shortcuts\nvcplui.lnk} Target: "C:\Program Files\NVIDIA Corporation\Control Panel Client\nvcplui.exe"

...and many more

What do I do to ensure that I can launch every app from the xoblite menu without fail?


  • Ahnìon and xoblite like this

#2 myke

myke

    Newbie

  • Members
  • Pip
  • 1 posts

Posted 14 November 2020 - 06:42 PM

Are you running it as the main shell or as an add-on with Explorer.exe?



#3 xoblite

xoblite

    Administrator

  • Administrator
  • 49 posts
  • LocationSweden

Posted 14 November 2020 - 07:33 PM

Hi thylascene,

 

good catch - I have only found one such .lnk menu item error myself so far, but can confirm the issue.

 

I'm not quite sure yet whether the issue is in xoblite or due to a change and/or regression in (a recent version of?) Windows 10 though (e.g. wrt WoW64, similar to this old issue), as the vast majority of my .lnk menu items seem to work just fine. The search continues... Keep me posted if you discover anything!

 

BR//KHH aka qwilk/@xoblite

 

PS. In the meanwhile, you could also try creating regular menu [exec] items pointing directly to the same .exe as the .lnk item part of a [path] would; this seems to work as it should too in my experience (if you can confirm, this would suggest the issue is related to .lnk files specifically).


  • pitkon and myke like this

#4 xoblite

xoblite

    Administrator

  • Administrator
  • 49 posts
  • LocationSweden

Posted 14 November 2020 - 09:10 PM

Hi again,

 

I think I've found a workaround - the issue does indeed seem to be related to WoW64 redirection as per above, but letting Explorer execute .lnk files instead of passing them as is to the regular system ShellExecuteEx function seems to resolve the issue.

 

@thylascene, if you could please msg (or email) me your email address, I could send you an updated build with this fix included to try out and confirm back that it's indeed working? Thanks in advance!

 

BR//KHH aka qwilk/@xoblite

 

PS. For any other developers out there:

SHELLEXECUTEINFO si;
ZeroMemory(&si, sizeof(si));
si.cbSize = sizeof(SHELLEXECUTEINFO);
si.fMask = SEE_MASK_DOENVSUBST | SEE_MASK_FLAG_NO_UI;
si.hwnd = hwndOwner;
si.lpVerb = szOperation;

if (!_stricmp(&szCommand[strlen(szCommand)-4], ".lnk"))
{
	// Let Explorer execute .lnk shortcuts to (hopefully?)
	// avoid some potential WoW64 redirection related issues...
	si.lpFile = "explorer";
	si.lpParameters = szCommand;
	si.lpDirectory = NULL;
}
else
{
	// ...otherwise use ShellExecuteEx as usual...
	si.lpFile = szCommand;
	si.lpParameters = szArguments;
	si.lpDirectory = szDirectory;
}
si.nShow = nShowCmd ? nShowCmd : SW_SHOWNORMAL;

BOOL result = ShellExecuteEx(&si);

  • pitkon and Ahnìon like this

#5 Ahnìon

Ahnìon

    Newbie

  • Members
  • Pip
  • 7 posts

Posted 15 November 2020 - 07:02 PM

I have this error as well. I haven't reported it because I wanted to make sure it wasn't a local rights issue, but if others have the same one I guess it isn't.

 

I'm running Windows 10 Pro 20H2. (Build 19042.630)

 

Here are the relevant bits from the report I was fiddling with:

 

  • The error shows up in the console and log as "ERROR: Could not execute [path to shortcut]"
  • The offending shortcuts work fine in the normal Windows start menu, as well as in Explorer.
  • Launching the same applications directly via [exec] also works fine.
  • It's not consistent within a given [path] submenu directory—most shortcuts work, some don't.
  • It doesn't seem to be related to path length, nor special characters.
  • It doesn't matter where a [path] menu is located on disk.
  • Creating a new shortcut to the same application makes no difference.
  • The error only occurs for some of the applications located in C:\Program Files\ (that is, not for C:\Program Files (x86)\ nor anywhere else.)
  • Security permissions can be identical between shortcuts that work and ones that don't. The same goes for the files they point to.
  • Running xoblite elevated changes nothing.
  • Windows logs give no indications.
  • DISM and CHKDSK find nothing wrong.
  • SFC did report some duplicate ownership, but this is apparently normal, and the fix changed nothing.

  • pitkon and xoblite like this

/ paradoXymoron /


#6 xoblite

xoblite

    Administrator

  • Administrator
  • 49 posts
  • LocationSweden

Posted 16 November 2020 - 08:04 PM

@thylascene + @Ahnìon, please check your message boxes here on BB4W. Thanks!

 

BR//Karl aka qwilk/@xoblite


  • pitkon and Ahnìon like this

#7 Ahnìon

Ahnìon

    Newbie

  • Members
  • Pip
  • 7 posts

Posted 16 November 2020 - 10:50 PM

That definitely did it! Having tried nearly every item in my menu, I can find nothing that doesn't work with this test build.


  • pitkon and xoblite like this

/ paradoXymoron /


#8 thylascene

thylascene

    Newbie

  • Members
  • Pip
  • 5 posts

Posted 19 November 2020 - 10:24 PM

Can confirm that this fixed the launching of problematic shortcuts for me as well! Looking forward to future endeavors for this project!


  • pitkon and xoblite like this




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users