Sandboxie-Plus v1.5.0, v1.5.1, v1.5.2

Of course I have executed your mentioned "set" command before respectively inserted it into my batch file for the RAM disk. With the "query" command the status can be queried afterwards. And the status is displayed with "Enabled".

Code:

Aufgrund der oben angegebenen Einstellungen ist die Erstellung von 8dot3-Namen auf "R:" aktiviert.

 

Don't be. I was aware it was an intentional message of a new feature. Honestly it was my bad.

 

I did not intent to be snappy, sorry about that...

i have added an explenation to the github release text:

@APMichael
for me the command as shown above works, your original command was also missing the " 0" after the drive letter, an other issue may be if you are using a file system which does not support 8.3 names, in which case switch your ram disk to use NTFS, no need to say that runnign a sandbox on a non NTFS partition is also asking for trouble with installers and alike

 

I used the command you mentioned "fsutil behavior set disable8dot3 R: 0" exactly identically.

Code:

C:\WINDOWS\system32>fsutil behavior set disable8dot3 R: 0

8dot3name-Generierung wurde auf R: aktiviert.

The "query" command I used after that is only for checking which satuts the 8.3 name support has on the volume. A "0" is not needed for this "query" command.

My RAM disk is formatted with NTFS.

The batch file:

Code:

imdisk -a -s 1G -m R: -p "/fs:ntfs /q /y"
LABEL R:RAMDisk
fsutil behavior set disable8dot3 R: 0

 

mmh... strange will have to investigate that

 

On my RAMdisk drive R:

Code:

C:\Windows\system32>fsutil behavior set disable8dot3 R: 0
Successfully enabled 8dot3name generation on R:

Didn't work. SBIE2227 is still popping up.

I tested that out of curiosity only.

 

Ok, thanks in advance. Also thanks for adding the explanation to the release text.

Edit: The problem seems to be really only with the RAM disk. I just tried it with my 2nd partition of my SSD and here it works after I enabled the 8.3 name support.

Thank you for your confirmation of the problem.

 

I have found the issue with why the test failed for imdisk, will be fixed in the next build

 

I am using the last free version of Softperfect ramdisk (v3.4.8)
https://www.majorgeeks.com/files/details/softperfect_ram_disk.html
Will the upcoming fix apply to this too? Thanks.

 

yes

 

It worked with FF 105 and SBIE 5.59.2. When the FF 106 crap happened is when it quit working.

 

what is Roboform and where can i download it for testing?

 

Roboform is a password manager.
https://www.roboform.com/

There is a software compatibility entry in SBIE for it.

 

Updated to FF 106.1 and SBIE 5.60. Received error message: SBIE1307 Program cannot access the Internet due to restrictions - rf-chrome-nm-host.exe (DefaultBox). Today I updated to SBIE 5.60.1 and received the following message "The application was unable to start correctly (0xc0000005). Click OK to close the application". Any suggestions or recommendations?

 

Is it possible that you are using a third-party antivirus software that has browser, online banking or similar protection?

Please take a look at this thread:
https://www.wilderssecurity.com/threads/eis-update-do-not-allow-ff-to-run-sandboxed.448495/

 

FF 106.0.2 and Sandboxie Plus 1.5.0 running good so far.

 

This looks like another problem with FF and Roboform. If you have do have Roboform installed DavidXanatos is looking into the issue.

 

I have had Roboform installed on my computer for years and haven't noticed a problem with it but who knows? Will install Firefox 106.0.2 later, hopefully, that will resolve the problem. DavidXanatos does an outstanding job.

 

I disabled Banking and Payment protection entirely in EIS as APMichael suggested and it seems to have resolved my problem. Thanks everyone!

 

mozilla is neither nor resposible for 3rd-party programs failures, and ofc dont not care much of it. Avira or Avast at last was an exception because they failed, and on thunderbird too, again. if you have trouble with roboform, with or without sandboxie, you better ask them next time, you use a paid produkt which has to respect firefox development.

 

And they keep it enabled for other volumes or partitions as well, by default, at least I notice here on my W10 machine.

Then I realized that after enabling 8.3 names for my virtual drive (ImDisk) using the fsutil command actually works but after a computer restart, the setting is gone and gets disabled back again.

 

@Mr.X you can use the command also to enable this globally than its on for all the drivers and shoudl hance also be on for the ram disk after the reboot

 

Code:

Microsoft Windows [Version 10.0.19044.2130]
(c) Microsoft Corporation. All rights reserved.

C:\Windows\system32>fsutil 8dot3name query R:
The volume state is: 1 (8dot3 name creation is disabled).
The registry state is: 2 (Per volume setting - the default).

Based on the above settings, 8dot3 name creation is disabled on R:

C:\Windows\system32>fsutil behavior set disable8dot3 0
The registry state is now: 0 (Enable 8dot3 name creation on all volumes).

C:\Windows\system32>fsutil 8dot3name query R:
The volume state is: 1 (8dot3 name creation is disabled).
The registry state is: 0 (Enable 8dot3 name creation on all volumes).

Based on the above settings, 8dot3 name creation is enabled on R:

C:\Windows\system32>

Then after a computer reboot

Code:

Microsoft Windows [Version 10.0.19044.2130]
(c) Microsoft Corporation. All rights reserved.

C:\Windows\system32>fsutil 8dot3name query R:
The volume state is: 1 (8dot3 name creation is disabled).
The registry state is: 0 (Enable 8dot3 name creation on all volumes).

Based on the above settings, 8dot3 name creation is enabled on R:

C:\Windows\system32>

fsutil first says it is disabled then below says enabled, pff.

 

I use a browser that is not on the list of browsers, how do i add mine to it so S-boxie gets access?

 

Download: https://github.com/sandboxie-plus/Sandboxie/releases/tag/v1.5.2

Note: the installers are not signed only the driver as its a unscheduled hotfix release.


Changelog 1.5.2

Changed

• utility groups are now cleaned up automatically

Fixed

• fixed issues with SBIE2227 on virtual drives
• fixed issues on native 32-bit windows introduced with 1.5.0 #2401