Sandboxie 3.76

When you browse the Web, changes occur to your computer system. Some of these might be harmful, like the unsolicited installation of malware. When you use Sandboxie to protect your browsing session, it catches all these changes just as the browser is about to apply them into your computer system. Sandboxie does record these changes on behalf of the browser, but it records them in a special isolated folder, called the sandbox. Thus, with Sandboxie, you can browse the Web securely while still keeping all your browser's functionality for active and dynamic content, such as javascript and ActiveX. All undesired side effects can be easily undone.

Thanks to thylacine for the update.

Download

Comments

thank for update, wait for new fix
Thanks for the update
uuk patch working on 32bit. Testing on 64bit.

uuk patch working on 32bit. Testing on 64bit.


Is this uuk patch need requirement turning Windows to `test mode`? [64 bit]
yes. Download from frontpage and read readme

Patch working on x64 too.
Posted Image
thanks for that :)
Thanks for the update. B)
my sys is window 8 32bit. i get same error from 3.74 to 3.76 when use keygen uuk:


SBIE1101 Sandboxie driver (SbieDrv) version 3.76 initialized
SBIE9153 Cannot start driver (SbieDrv)
SBIE9153 Cannot start driver (SbieDrv)
SBIE2331 Service start failed: [22 / 5] Access is denied.

i also can not fill up the field version - " Version unknown" and syscode show "System Code 0000000000000000"

then press activate it show "This is not a valid Activation Key. [C0000080]". any help for this?

my sys is window 8 32bit. i get same error from 3.74 to 3.76 when use keygen uuk:


SBIE1101 Sandboxie driver (SbieDrv) version 3.76 initialized
SBIE9153 Cannot start driver (SbieDrv)
SBIE9153 Cannot start driver (SbieDrv)
SBIE2331 Service start failed: [22 / 5] Access is denied.

i also can not fill up the field version - " Version unknown" and syscode show "System Code 0000000000000000"

then press activate it show "This is not a valid Activation Key. [C0000080]". any help for this?



1.Did you put version no. 3.76 instead of 3.54?Also did you copy and paste the system code by clicking ... button (instead of 0123456789ABCDEF) and change the time before clicking patch?

2.Did you enable test mode and then sign SbieDrv.sys before rebooting the system?

3.Did you do the same thing as mentioned in 1st step before clicking activate?

If you do it correctly,then Sandboxie will be activated for sure.

Follow this one:http://www.nsaneforums.com/topic/124294-sandboxie-368-final/#entry405385
i do exactly as instructions, when i click ".... " button : syscode show : System Code 0000000000000000 , thus i can not recieve any syscode to replace 0123456789ABCDEF ,about version i still can fill 3.76 instead of 3.54. as instruction pack, my sys is 32bit so i dont use dseo . i dont know why?

i do exactly as instructions, when i click ".... " button : syscode show : System Code 0000000000000000 , thus i can not recieve any syscode to replace 0123456789ABCDEF ,about version i still can fill 3.76 instead of 3.54. as instruction pack, my sys is 32bit so i dont use dseo . i dont know why?

You should follow everything in the instructions to get Sandboxie (license) working even if it is a 32 bit system.....
Would disabling test mode, after successfully activating Sandboxie, basically undo the activation? Just wondering.
Thanks For The Update.:dance2:
patch uuk still working fine on win7 x64! :wub:

Would disabling test mode, after successfully activating Sandboxie, basically undo the activation? Just wondering.

Sandboxie driver won't start and you would get errors.
Well, people Shajt is back now. Request Shajt he knows how to tackle Tzuk. :lol:. If you're not happy with uuk fix.

By the way, I have the lifetime license & thanks for the update. :showoff:

EDIT: I guess Shajt don't want ...Read Here
i just try uuk patch again , i can get syscode and version by clicking [...] but after patching and rebooting, version get unknow and syscode is 00000000000, i try copy syscode to nodepad then fill up after restart but get error when press activate button. i dont know why after rebooting system i cant get syscode?
On Windows 8 x32 You need to turn on test mode on too.
bcdedit -set loadoptions DISABLE_INTEGRITY_CHECKS
bcdedit -set TESTSIGNING ON

To turn it off again, use these commands:

bcdedit -set loadoptions ENABLE_INTEGRITY_CHECKS
bcdedit -set TESTSIGNING OFF

dseo13b.exe won't work on Windows 8

On Windows 8 x32 You need to turn on test mode on too.
bcdedit -set loadoptions DISABLE_INTEGRITY_CHECKS
bcdedit -set TESTSIGNING ON

To turn it off again, use these commands:

bcdedit -set loadoptions ENABLE_INTEGRITY_CHECKS
bcdedit -set TESTSIGNING OFF

dseo13b.exe won't work on Windows 8

thank anuraag for useful info
I've had all kinds of problems with getting this to activate. When I finally did, I decided to write an expanded version of step 5 of the instructions so that even a baby could understand. This should solve most of your activation problems, hopefully... GOOD LUCK ;)

More info on step 5:
*After rebooting, run keygen as per step 5 above to open keygen window.
*Change Version: 3.54 to the version you installed. In this case 3.76
*Syscode: 0123456789ABCDEF ...Click on the button >>> [...] at the end of that line and a window will pop up showing you the real Syscode number.
Copy just the 16 digit alpha/numeric number you see (DO NOT copy the "System Code" word) then paste it into the Syscode: field. Be sure to delete the current 0123456789ABCDEF first before you paste it in.
*Time: Change default time 20121231 >>> (yyyymmdd) to the now date. For example: 20121217 is the date in which I installed Sandboxie and that is what I will change the date to. So change 20121231 to 20121217.
Path: Don't do anything here unless the path is incorrect. If incorrect, change it to the proper path.
*Finally, click on the 'Activate' button. Sandboxie should now be Registered and Activated.
Thanks for the info. :)

BTW, are you the same Journey from Softexia?
@ dcs18

Yep, I am.. B)

@ dcs18

Yep, I am.. B)

Ah good, it's our pleasure to have you with us - have fun, man. :cheers:
Thanks for the update
should the system remain in test mode after activation?
I get this
"Sandboxie is registered but the license should be reactivated now."
How to fix ?

should the system remain in test mode after activation?

Yes for Windows 8 x32 and upto Windows 8 x64

I get this
"Sandboxie is registered but the license should be reactivated now."
How to fix ?

Try keygen again and set time to 20201231
I am running Windows 7 32-bit. According to the readme, I do not need to run dseo13b. But according to a user here, even if one is running a 32-bit system, one should run dseo13b. So which is right?

I am running Windows 7 32-bit. According to the readme, I do not need to run dseo13b. But according to a user here, even if one is running a 32-bit system, one should run dseo13b. So which is right?

No dseo13b.exe is only for Upto windows 7 x64

I am running Windows 7 32-bit. According to the readme, I do not need to run dseo13b. But according to a user here, even if one is running a 32-bit system, one should run dseo13b. So which is right?

Continue from here:http://www.nsaneforu..._20#entry463292 You will realise...

Just follow post #21 for avoiding errors
OK.. Upon reboot, I'm getting a message that it is registered but needs to be re-activated so I conclude that neither the LnDL nor uuk patchers work anymore. We'll have to wait for either LnDL or SND to come out with a new patch seeing uuk is no longer interested in this venture.
Worked fine for me, activated for 31,790 days.....I set the date for something like 20991217. Oh and yes I have rebooted several times since.

And that's not subjective, its a fact.
@ clubhouse

You're absolutely correct. It does work. Thank you for pointing that out. My mistake was not setting the Time far ahead. I didn't know you were supposed to do that because the keygen came with confusing instructions.. That said, everyone update your instructions to this:

1. Install Sandboxie, obviously...

2. Use Keymaker (run as admin), click on Patch.

3. (Skip this step if you are using x86 architecture OS.)
Use dseo13b (run as admin), enable test mode and sign "SbieDrv.sys". Usually in (C:\Program Files\Sandboxie\)

4. Reboot

5. Use Keymaker again (run as admin), fill up the fields version and syscode by clicking on [...]
Click on Activate.

Expanded information on step 5:
*After rebooting, run keygen as per step 5 above to open keygen window.
*Change Version: 3.54 to the version you installed. In this case 3.76
*Syscode: 0123456789ABCDEF <<< Hightlight this and delete it so the field is empty...Click on the button >>> [...] at the end of that line and a window will pop up showing you the "real System Code number."
Copy just the 16 digit alpha/numeric number you see (DO NOT copy the "System Code" word) then paste it into the empty Syscode: field.
*Time: is really the date setting on a calendar whereas the word time refers to what a clock shows. uuk should have used the word Date: instead of Time. That being said,Time: Change default time in the keygen reads... 20121231 which represents year-month-day >>> (yyyymmdd) to a date way into the future, let's say 100 years. For example: Change default keygen setting from 20121231 to 21121231.
Path: Don't do anything here unless the path is incorrect. If incorrect, change it to the proper path.
*Finally, click on the 'Activate' button. Sandboxie should now be Registered and Activated. You should get a popup from the keygen saying you are registered for 36,525 something days.

6. Enjoy! ;)


Clarity has now stifled the confusion. :P
For me the activation only works with signing the driver and running Windows in Test Mode.

Disabling Test Mode makes the driver not load after reboot so for me it's not the best solution
to have Windows every time in Test Mode only to be able to use one(!) program, not worth it.

I reverted back to an easy patch&use solution from LnDL, no Test Mode required for that.
LnDL x64 patch require to enable test mode too

That said, everyone update your instructions to this:

1. Install Sandboxie, obviously...

2. Use Keymaker (run as admin), click on Patch.

3. (Skip this step if you are using x86 architecture OS.)
Use dseo13b (run as admin), enable test mode and sign "SbieDrv.sys". Usually in (C:\Program Files\Sandboxie\)

4. Reboot

5. Use Keymaker again (run as admin), fill up the fields version and syscode by clicking on [...]
Click on Activate.

Expanded information on step 5:
*After rebooting, run keygen as per step 5 above to open keygen window.
*Change Version: 3.54 to the version you installed. In this case 3.76
*Syscode: 0123456789ABCDEF <<< Hightlight this and delete it so the field is empty...Click on the button >>> [...] at the end of that line and a window will pop up showing you the "real System Code number."
Copy just the 16 digit alpha/numeric number you see (DO NOT copy the "System Code" word) then paste it into the empty Syscode: field.
*Time: is really the date setting on a calendar whereas the word time refers to what a clock shows. uuk should have used the word Date: instead of Time. That being said,Time: Change default time in the keygen reads... 20121231 which represents year-month-day >>> (yyyymmdd) to a date way into the future, let's say 100 years. For example: Change default keygen setting from 20121231 to 21121231.
Path: Don't do anything here unless the path is incorrect. If incorrect, change it to the proper path.
*Finally, click on the 'Activate' button. Sandboxie should now be Registered and Activated. You should get a popup from the keygen saying you are registered for 36,525 something days.

6. Enjoy! ;)



I followed the above instructions but after the reboot (avtivation part) I get version unknown. System code was 0000000000000000

Then I get activation code invalid

Then I tried by

1. Uninstall
2. Install
3. Before installing driver I patch it
4. reboot
5. Then sandboxie don't even want to start up.
6. Get unknown version when trying to change the version
7. When click activate, license invalid


1. Uninstall
2. Install
3. Before install the driver change it to 3.76 but it stills remain 3.54 after clicking ... > ok
4. Reboot
5. Sandboxie won't start.
6. Get unknown version when trying to activate
7. When click activate, license invalid

@Journey, did you run dseo13b.exe?
i get same problem like this [win 8], why no team as lndl,snd,.. take care of sandboxie

I followed the above instructions but after the reboot (avtivation part) I get version unknown. System code was 0000000000000000

i get same problem like this [win 8], why no team as lndl,snd,.. take care of sandboxie

I followed the above instructions but after the reboot (avtivation part) I get version unknown. System code was 0000000000000000

You are doing something wrong. It worked fine here. You are using Win8 x32?
Edit: Here is steps for Windows 8
1. Turn on test mode
bcdedit -set loadoptions DISABLE_INTEGRITY_CHECKS
bcdedit -set TESTSIGNING ON
Reboot

2. Install Sandboxie. Stop where installer do driver installation and asks to click next to install and activate system-level driver.

3. Run uuk patch as admin and hit patch.

4. Run dseo13b.exe and sign C:\Program Files\Sandboxie\SbieDrv.sys (no need to restart Windows)

5. Now back to installer and click next to do driver installation.

6. Now use keymaker, fill up the fields "version" and "syscode" by clicking on [...]. In "Time", enter the desired license expiration date in YYYYMMDD format. Click on Activate.

For me the activation only works with signing the driver and running Windows in Test Mode.

Disabling Test Mode makes the driver not load after reboot so for me it's not the best solution
to have Windows every time in Test Mode only to be able to use one(!) program, not worth it.

I reverted back to an easy patch&use solution from LnDL, no Test Mode required for that.


Agree with you! I have and will use version 3.72, unless other options are available. I use x86
@anuraag, Win7 32 bit. Do I follow the frontpage instructions or Jurney's instruction.

@anuraag, Win7 32 bit. Do I follow the frontpage instructions or Jurney's instruction.

frontpage instructions and Journey's instruction are same. Journey has only tried to explain step 5.
There is some unnecessary reboot steps present. So you can use this.

1. Install Sandboxie. Stop where installer do driver installation and asks to click next to install and activate system-level driver.
2. Run uuk patch as admin and hit patch.
3. Now back to installer and click next to do driver installation.
4. Now use keymaker, fill up the fields "version" and "syscode" by clicking on [...]. In "Time", enter the desired license expiration date in YYYYMMDD format. Click on Activate.
The syscode do I use the one provided by the keymaker or the ... one?

The syscode do I use the one provided by the keymaker or the ... one?

the ... one
Another question. When I change the version by clicking ... it states "version 3.76" but when I press ok, it is still 3.54. Is that normal?

Another question. When I change the version by clicking ... it states "version 3.76" but when I press ok, it is still 3.54. Is that normal?

You need to fill all things manually by clicking .... Replace 3.54 with 3.76.

1. Install Sandboxie. Stop where installer do driver installation and asks to click next to install and activate system-level driver.
2. Run uuk patch as admin and hit patch.
3. Now back to installer and click next to do driver installation.
4. Now use keymaker, fill up the fields "version" and "syscode" by clicking on [...]. In "Time", enter the desired license expiration date in YYYYMMDD format. Click on Activate.


Now, I did that still show unknown version and gave the syscode as 0000000000000000. Then sandboxie states license invalid. Uninsatll and try again (before patching the driver) and then keymaker states unknown version. Which never happen before.

Thought maybe some left behind registries. So uninstall then install and monitor insatllation with total uninstal and activate the free version and then remove it via total uninstall. But keymaker still shows unknown version when I want to patch. Even ran CCleaner afterwards to get rid of the issue still no luck.

Is it because I have 3.72 install previously and activate via the old patch? And is not a clean uninstall?
I have just tested uuk patch on Win 7 32 bit
Same Windows 8 x32 steps need to follow
see post #38
Use dseo13b.exe to enable tset mode on Win7
Don't know why 32bit also not loading unsigned driver

I myself thinks free version is enough.

LnDL x64 patch require to enable test mode too


Well, i forgot to say that i use 32bit Windows and Sandboxie v3.72, so it's clear that you have to re-sign the driver on x86 too, not only on x64, the patch will make the driver (no matter which architecture) unsigned and Sandboxie will not work with an unsigned driver, only in Test Mode, it's an self-protection of the program i think, a copy protection.
You don't have to sign the driver for x86, I don't know how uuk patch works but for x86 only checksum needs to be updated after patching. If their patcher doesn't update the checksum of the patched driver then the signer tool will.
x64 has a bigger problem, driver has to be signed there and it's not a protection from the developer, but that's how Windows x64 operates (it doesn't allow digital signatures for drivers that are not on their approved list) , so yeah ... to sum it up ... in x64 you have to enable Test mode and remain in that mode if you want the patched driver to work. There are no ways around that. What Test mode does is enabling drivers with any digital signature to load, ofc you will have watermark in the bottom right corner , there are ways to remove that but anyhow that's that :)

You don't have to sign the driver for x86, I don't know how uuk patch works but for x86 only checksum needs to be updated after patching. If their patcher doesn't update the checksum of the patched driver then the signer tool will.
x64 has a bigger problem, driver has to be signed there and it's not a protection from the developer, but that's how Windows x64 operates (it doesn't allow digital signatures for drivers that are not on their approved list) , so yeah ... to sum it up ... in x64 you have to enable Test mode and remain in that mode if you want the patched driver to work. There are no ways around that. What Test mode does is enabling drivers with any digital signature to load, ofc you will have watermark in the bottom right corner , there are ways to remove that but anyhow that's that :)

on the previous version i enabled testmode after that i removed watermark and haven't seen watermark anymore ! yesterday i installed this new version and enabled testmode again but after restarting my pc..i didn't see any watermark...maybe we need to enable testmode only one!


For me the activation only works with signing the driver and running Windows in Test Mode.

Disabling Test Mode makes the driver not load after reboot so for me it's not the best solution
to have Windows every time in Test Mode only to be able to use one(!) program, not worth it.

I reverted back to an easy patch&use solution from LnDL, no Test Mode required for that.

Agree with you! I have and will use version 3.72, unless other options are available. I use x86

+1, same here, I'm still using version 3.72 on Win7x86 with test mode disabled. :)
after times cant crack it . i decide to use free version of sandboxie, because it is enough to me

after times cant crack it . i decide to use free version of sandboxie, because it is enough to me


Same here.

after times cant crack it . i decide to use free version of sandboxie, because it is enough to me

I concur. Too much risk to take just to use 1 activated program. Unless a better 'medicine' is released, I'm sticking with the free version.

Does not work. Code in [...] does not work....

Windows 8 x64 Can you share video ?

Has anyone got this working on Windows 8 x64? I've tried everything I can find in here but the uuk patcher always complains saying "Make sure the drive has been patched.", followed by "This is not a valid activation key.", regardless of how often I try to patch it and sign the driver with dseo while in test mode.

 

EDIT: Found the problem, basically just have to run everything (Patcher, dseo, etc.) as an administrator.

Hi !

I've got the same problem, after patch and use dseo, and after reboot sb isn't work so I can't activate...

 

SBIE9153 Ne peut démarrer le pilote (SbieDrv)
SBIE9153 Ne peut démarrer le pilote (SbieDrv)
SBIE1101 Driver Sandboxie (SbieDrv) version 3.76 initialisé
SBIE9153 Ne peut démarrer le pilote (SbieDrv)
SBIE9153 Ne peut démarrer le pilote (SbieDrv)

 

and I have "version unknown" and sys code 0000000000

 

 

How is possible to "stop" where installer do driver installation and asks to click next to install and activate system-level driver ?

When I install sb, it stop alone just before driver installation and, at this moment, I can't use keygen until the installation isn't completed...

 

Is anyone can hepl me please ?

 

(Windows 7 x64)

People the instructions in post #33 work perfectly.

Keep in mind when doing step 3 you need to do 2 things

 

1. click enable test mode, Next

2. singn a system file, Next     , use this address for windows 7  "C:\Program Files\Sandboxie\SbieDrv.sys"  then click ok

 

Now restart.

 

The keygen

replace 3.54 with 3.76...................replace the systems code with the one found under [..].........Replace the time with     "21121231"

 

Click activate ..

 

The keygen has issues with all the replacing parts. It should be more straight forward and user friendly.   But it works 100%

Hello, I tried a million time to install Sandboxie following your step, but I didn't work. Then I try by my own way, and it work. So i want to share with you who cant install it yet

 

1- Install Sandboxie. Close it on taskbar
2- Use Keygen, fill up the fields version and syscode by clicking on ... then apply patch. Dont do anything with the Time

3. REBOOT
4- Close Sandboxie on Taskbar

5 - Use dseo13b (run as admin), enable test mode and sign a system file: C:\Program Files\Sandboxie\SbieDrv.sys
6- Reboot.

7- Close Sandboxie on Taskbar
8- Use Keygen again, fill upthe fields. Fill the Time to 20991231
Done.

Hello, I tried a million time to install Sandboxie following your step, but I didn't work. Then I try by my own way, and it work. So i want to share with you who cant install it yet

 

1- Install Sandboxie. Close it on taskbar
2- Use Keygen, fill up the fields version and syscode by clicking on ... then apply patch. Dont do anything with the Time

3. REBOOT
4- Close Sandboxie on Taskbar

5 - Use dseo13b (run as admin), enable test mode and sign a system file: C:\Program Files\Sandboxie\SbieDrv.sys
6- Reboot.

7- Close Sandboxie on Taskbar
8- Use Keygen again, fill upthe fields. Fill the Time to 20991231
Done.

it's still old method, but working on some machine, not on some others

Hello, I tried a million time to install Sandboxie following your step, but I didn't work. Then I try by my own way, and it work. So i want to share with you who cant install it yet

 

1- Install Sandboxie. Close it on taskbar
2- Use Keygen, fill up the fields version and syscode by clicking on ... then apply patch. Dont do anything with the Time

3. REBOOT
4- Close Sandboxie on Taskbar

5 - Use dseo13b (run as admin), enable test mode and sign a system file: C:\Program Files\Sandboxie\SbieDrv.sys
6- Reboot.

7- Close Sandboxie on Taskbar
8- Use Keygen again, fill upthe fields. Fill the Time to 20991231
Done.

Tested ... these steps worked for Win7 x86.

 

Just don't understand why 32-bit OS needs to be in test mode as well ?

Otherwise, the syscode is detected as 16 zeros and cannot be activated.

Hello, I tried a million time to install Sandboxie following your step, but I didn't work. Then I try by my own way, and it work. So i want to share with you who cant install it yet

 

1- Install Sandboxie. Close it on taskbar
2- Use Keygen, fill up the fields version and syscode by clicking on ... then apply patch. Dont do anything with the Time

3. REBOOT
4- Close Sandboxie on Taskbar

5 - Use dseo13b (run as admin), enable test mode and sign a system file: C:\Program Files\Sandboxie\SbieDrv.sys
6- Reboot.

7- Close Sandboxie on Taskbar
8- Use Keygen again, fill upthe fields. Fill the Time to 20991231
Done.

Yes!! tested.. :) 

works perfectly even with Sandboxie 4.04 latest in Windows 8 x86.. :yes:

Thanks a lot..

:cheers:

 

13557641.jpg