desktop shortcut help - Please

bjm_

New member
Hello
I want to create a desktop shortcut - red box sbox'd
Plus = Create Shortcut does not drill down to \AppData\ as far as I can find.

The path of the working desktop shortcut - unsbox'd is
Code:
C:\Users\bjmer\AppData\Local\imput\Helium\Application\chrome.exe

I've played with variations of....with No joy.
Code:
NormalFilePath="C:\Program Files\Sandboxie-Plus\Start.exe" /box:HeliumSHDP "C:\\Users\bjmer\AppData\Local\imput\Helium\Application\chrome.exe"
Code:
ReadFilePath=C:\Users\Desktop\Helium.lnk
ReadFilePath=C:\Users\bjmer\AppData\Local\imput\Helium\Application\chrome.exe

476.jpg
 
Last edited:
Code:
NormalFilePath="C:\Program Files\Sandboxie-Plus\Start.exe" /box:HeliumSHDP "C:\\Users\bjmer\AppData\Local\imput\Helium\Application\chrome.exe
Remove
Code:
NormalFilePath=
 
Code:
NormalFilePath="C:\Program Files\Sandboxie-Plus\Start.exe" /box:HeliumSHDP "C:\\Users\bjmer\AppData\Local\imput\Helium\Application\chrome.exe
Remove
Code:
NormalFilePath=
Though I tried that path?
477.jpg478.jpg
 
Last edited:
Alright try these lines:

This line goes in Target:
Code:
"C:\Program Files\Sandboxie-Plus\Start.exe" /box:HeliumSHDP "C:\Users\bjmer\AppData\Local\imput\Helium\Application\chrome.exe"
This line goes in Start in:
Code:
"C:\Users\bjmer\AppData\Local\imput\Helium\Application"
 
Alright try these lines:

This line goes in Target:
Code:
"C:\Program Files\Sandboxie-Plus\Start.exe" /box:HeliumSHDP "C:\Users\bjmer\AppData\Local\imput\Helium\Application\chrome.exe"
This line goes in Start in:
Code:
"C:\Users\bjmer\AppData\Local\imput\Helium\Application"
479.jpg
with or without quotation marks = Could not invoke program
 
Last edited:
When the sandbox is run in privacy mode, it does not give read access to the user folders, even if the user that executes the binary has access to it.

I had written on how to grant read access to folders that are normally available by using NormalFilePath.
 
When the sandbox is run in privacy mode, it does not give read access to the user folders, even if the user that executes the binary has access to it.

I had written on how to grant read access to folders that are normally available by using NormalFilePath.
Yes, I have NormalFilePath for User Date with my Edge & Chrome sbox's. I have NormalFilePath with my Helium sbox.
Helium browser gets installed with AppData. Create Shortcut does not drill down to \AppData\ ...as I can find.
Create Shortcut for Edge & Chrome was easy. Run Sandboxed & Create Shortcut for Helium red box is head scratch.
 
I always make shortcuts like these, manually.

I suggest to:
1. Go to C:\Users\bjmer\AppData\Local\imput\Helium\Application
2. Rename chrome.exe to helium.exe
3. Right-click on helium.exe
4. Send to > Desktop (create shortcut)
5. Edit "Target" field
"C:\Program Files\Sandboxie-Plus\Start.exe" /box:HeliumSHDP "C:\Users\bjmer\AppData\Local\imput\Helium\Application\helium.exe"
6. Test it
7. From there, you can make copies of it or move it wherever you want.
 
I always make shortcuts like these, manually.

I suggest to:
1. Go to C:\Users\bjmer\AppData\Local\imput\Helium\Application
2. Rename chrome.exe to helium.exe
3. Right-click on helium.exe
4. Send to > Desktop (create shortcut)
5. Edit "Target" field
"C:\Program Files\Sandboxie-Plus\Start.exe" /box:HeliumSHDP "C:\Users\bjmer\AppData\Local\imput\Helium\Application\helium.exe"
6. Test it
7. From there, you can make copies of it or move it wherever you want.
Interesting. Rename had not occured to me. But, Run Sandboxed does not work with Helium red box HeliumSHDP.


482.jpg
Edit: I'll have to change INI. Name change causes original Helium shortcut to lose it's pretty.
Edit: back to Chrome.exe
Helium browser is based on ungoogled chromium. Helium files are named "chrome".
 
Last edited:
Hello @Mr.X
Code works for my Helium orange box
Code:
Target: "C:\Program Files\Sandboxie-Plus\Start.exe" /box:HeliumSH "C:\Users\bjmer\AppData\Local\imput\Helium\Application\chrome.exe"
Start in: "C:\Users\bjmer\AppData\Local\imput\Helium\Application"
 
Last edited:
When I create a shortcut, that points to something that is not readable for the sandbox (privacy enhanced box), I get the error that the system could not find the file. When I change the settings to allow the folder to be read by the privacy enhanced box, I can use the shortcut without an error.

Edit: For me, it works, whenever if I use NormalFilePath or ReadFilePath.

ReadFilePath=C:\Users\bjmer\AppData\Local\imput\Helium\Application\ should work.
 
Last edited:
Edit: For me, it works, whenever if I use NormalFilePath or ReadFilePath.
Oh okay. NormalFilePath or ReadFilePath
Okay, forget shortcut for now...still have INI wrong because Run Sandboxed does not ...with my Helium red box.
483.jpg

Thanks
 
Last edited:
But, still have other code wrong because Run Sandboxed does not ...with my Helium red box

Are you able to start the process manually from the Sandboxie-Plus user interface? If that already fails, the problem is not with how the shortcut is constructed.

Do you have
Code:
ReadFilePath=C:\Users\bjmer\AppData\Local\imput\Helium\Application\
added to the sandbox? This needs to be in the Sandboxie.ini in the section of your sandbox. You can add it via the user interface, shown above in offhub's reply.
 
Are you able to start the process manually from the Sandboxie-Plus user interface? If that already fails, the problem is not with how the shortcut is constructed.

Do you have
Code:
ReadFilePath=C:\Users\bjmer\AppData\Local\imput\Helium\Application\
added to the sandbox? This needs to be in the Sandboxie.ini in the section of your sandbox. You can add it via the user interface, shown above in offhub's reply.
Hmm...no I've been trying to mirror ReadFilePath= for Helium as with my Edge & Chrome sbox's
Code:
ReadFilePath=C:\Users\Public\Desktop\Edge.lnk
ReadFilePath=C:\Users\Public\Desktop\Chrome.lnk
ReadFilePath=C:\Users\Public\Desktop\Helium.lnk
Okay...adding your code and disabling my mirror code
Code:
#ReadFilePath=C:\Users\Public\Desktop\Helium.lnk
ReadFilePath=C:\Users\bjmer\AppData\Local\imput\Helium\Application\
NormalKeyPath=HKEY_CURRENT_USER\Software\Microsoft\Accessibility\*
NormalFilePath=chrome.exe,%LocalAppData%\imput\Helium\User Data\*
Yes, I'm able to start the process manually from the Sandboxie-Plus user interface
Yes, I'm able to drill down via Create Shortcut to \AppData\

Code:
"C:\Program Files\Sandboxie-Plus\SandMan.exe" /box:HeliumSHDP C:\\Users\bjmer\AppData\Local\imput\Helium\Application\Chrome.exe
C:\\Users\bjmer\AppData\Local\imput\Helium\Application

BRILLIANT (y)
Thank You @bastik-1001

Thanks @Mr.X for pointing me to Sandboxie-Plus Forums
 
Last edited:
I don't get it, so did it work for you?
What don't you get?
Helium red box works!
Helium red box shortcut works!

btw ~ XenForo platform is great!

One of these days.
I'd like to generally grasp why a red box with holes is better than an orange box sans holes.
That's another topic for another day.
Regards w Respect
 
Last edited:
When I create a shortcut, that points to something that is not readable for the sandbox (privacy enhanced box), I get the error that the system could not find the file. When I change the settings to allow the folder to be read by the privacy enhanced box, I can use the shortcut without an error.

Edit: For me, it works, whenever if I use NormalFilePath or ReadFilePath.

ReadFilePath=C:\Users\bjmer\AppData\Local\imput\Helium\Application\ should work.
~ re-reading your message. I'm starting to appreciate Normal vs Read.
NormalFilePath: Allows read access but redirects write operations to a copy inside the sandbox, preserving your original files.
ReadFilePath: Allows read-only access to a file or folder on the host system. Any attempt by the sandboxed program to write or delete is blocked.
 
Btw. why C:\\, I've never seen that before in a shortcut but C:\
~ re-reading your message. I don't know why double backslash.
My Helium red box shortcut had C:\\. My Helium orange box shortcut has C:\.
I've since changed Helium red box C:\\ to C:\
AI wrote:
The double backslash (\\) in the file paths C:\\Users... is a common convention used in programming languages and scripts to escape the backslash character itself.
Single Backslash (\) as an Escape Character: In many programming languages (like C, C++, Python, Java, etc.) and scripting environments, the backslash character (\) is designated as a special "escape" character.
The Need for Double Backslash (\\): Since the backslash has a special function, if you want to represent a literal backslash in a string (as required for Windows file paths, which use backslashes as path separators), you must escape the backslash itself. Therefore, \\ in the code or script is interpreted as a single literal backslash character by the program.
 
I'm starting to appreciate Normal vs Read.
NormalFilePath: Allows read access but redirects write operations to a copy inside the sandbox, preserving your original files.
ReadFilePath: Allows read-only access to a file or folder on the host system. Any attempt by the sandboxed program to write or delete is blocked.

NormalFilePath is required if access to something is denied, like in a privacy enhanced box, so the path can be read again. Sandboxie applies that to binaries outside the sandbox and inside the sandbox. It restores the behavior to how Sandboxie behaves in normal boxes.
ReadFilePath does not apply to binaries inside the sandbox. (Shown in this overview.)
 
Last edited:
Back
Top