Chrome messed up my “run browser sandboxed” link

Topic

New Reply

I normally use Firefox in my Windows 7 system.  I needed to install Chrome because the website I was using did not list Firefox as a supported browser.  After installing Chrome, it took over my “run browser sandboxed” shortcut.  I uninstalled Chrome, but now when I click on the link, I get an error message saying that I am trying to open an “application extension” .dll.  Choosing the “open with”, I get a list of programs to choose from.  I chose Firefox and then get the message that Windows cannot open the file “shell32.dll”.  I did this with Sandboxie 5.36.  I uninstalled this and installed version 5.49, but still have the bad file association issue.  I now use the right click link to run Firefox sandboxed, but would like to clean up the issue and use the link as intended.  Any suggestions?  Thanks

Reply | Quote

Replies

I only see 1 of the 3 attachments I submitted, here are the other 2, I hope.

Reply | Quote

Where is the link located?

What are the link properties? (Right click)

cheers, Paul

Reply | Quote

You shouldnt open DLL files with your browser. Shourcut should have *.lnk (local) or *.url (website).

I now use the right click link to run Firefox sandboxed, but would like to clean up the issue and use the link as intended.

what is “the link” file extension? I think you should be able to set this via Sandboxie or Firefox.

Dell Latitude 3420, Intel Core i7 @ 2.8 GHz, 16GB RAM, W10 22H2 Enterprise

HAL3000, AMD Athlon 200GE @ 3,4 GHz, 8GB RAM, Fedora 29

PRUSA i3 MK3S+

Reply | Quote

The link is on my desktop in my admin account and works as expected.  I deleted the link on my desktop in my user account as it had been broken by Chrome.  I placed a copy of the properly working link in My Documents so I could see it in either account.  If I try to use it in my user account I get the previously listed errors.  There was also a run web browser sandboxed link that was placed in your start menu when you install the program.  That creates the desktop icon shortcut.  Here are the properties of that shortcut.

Reply | Quote

The link is on my desktop in my admin account and works as expected.

Did you try to make your “user” account local admin?
Seems like mismatch – your admin can do it, your user account cant. It must be some installed program (Sandboxie?), that is not installed properly for “standard user”. Standard user has limited rights, so maybe he cant run the sandboxie properly? Did you think about it that way?
Try to install Sandboxie under the standars account too.

Maybe its bad idea, but your accounts are different. If it works under admin, you should be able to make it work under standard user too.

Dell Latitude 3420, Intel Core i7 @ 2.8 GHz, 16GB RAM, W10 22H2 Enterprise

HAL3000, AMD Athlon 200GE @ 3,4 GHz, 8GB RAM, Fedora 29

PRUSA i3 MK3S+

Reply | Quote

Can you run Sandboxie at all as your normal user?

Do you have access to K: from your normal user account?

cheers, Paul

Reply | Quote

I think the K: should be volume, that Sandboxie creates for a safe operations. Or?

Dell Latitude 3420, Intel Core i7 @ 2.8 GHz, 16GB RAM, W10 22H2 Enterprise

HAL3000, AMD Athlon 200GE @ 3,4 GHz, 8GB RAM, Fedora 29

PRUSA i3 MK3S+

Reply | Quote

Then you can’t start in K: if it doesn’t exist until Sandboxie runs.

cheers, Paul

1 user thanked author for this post.

doriel

Reply | Quote

I know what you mean, but I thought thats the point of sandboxing. First you run Sandboxie, then you run Firefox in it.

Dell Latitude 3420, Intel Core i7 @ 2.8 GHz, 16GB RAM, W10 22H2 Enterprise

HAL3000, AMD Athlon 200GE @ 3,4 GHz, 8GB RAM, Fedora 29

PRUSA i3 MK3S+

Reply | Quote

I have made a user account because that is supposed to be more secure than having only 1 account where you are the admin person.  I made the admin account for installing software and other admin tasks not allowed in a user account.  I rarely use the browser in the admin account so the association with chrome and sandboxie did not happen there.

Drive K is a separate partition where I install all of the non windows software that does not insist on installing to the windows drive.  I can run all of my programs as user form the K drive.  It is not a drive issue, it is something chrome did.  I only use sandboxie for the internet so any browsing is outside of the OS.

Reply | Quote

I dont know hy you get the open SHELL32.DLL dialog, if the target is START.EXE
that does not make sense to me.
Im sorry I dont know what to recommend apart of reinstalling Sandboxie and recreating your shortcut to sandboxed Firefox.

Dell Latitude 3420, Intel Core i7 @ 2.8 GHz, 16GB RAM, W10 22H2 Enterprise

HAL3000, AMD Athlon 200GE @ 3,4 GHz, 8GB RAM, Fedora 29

PRUSA i3 MK3S+

Reply | Quote

Can you post the full Target?

cheers, Paul

Reply | Quote

The full target is listed in the properties screenshot I posted on 4/8 @ 6:33AM.  I already mentioned in my 1st post that I completely uninstalled SB 5.36 including configuration and then installed version 5.49.  I get the same errors with either version of start.exe.  This all started after I installed Chrome and it took over what SB decided was the default browser.  This was with SB 5.36.  When I uninstalled Chrome, the link to run the browser sandboxed started giving me the screens pictured above instead of just launching the browser.

Reply | Quote

Can you run other things with Sandboxie?
Can you run the browser from Sandboxie by specifying the browser executable directly?

cheers, Paul

Reply | Quote

Mentioned this earlier, if I right click on the Firefox shortcut and scroll up to the run sandboxed link it works.  I do have to OK that items are place in the default sandbox.  I cannot make that a desktop shortcut.

Reply | Quote

In summary, Sandboxie is working but you can’t set/use a desktop shortcut for your default browser.

I would check the Sandboxie forums to see if this is a known issue.

cheers, Paul

Reply | Quote