Jump to content

Sandboxie 4.14


jalaffa

Recommended Posts

Quick question regarding the UUK patcher:

The instructions stays:

9. Run keygen (as administrator)

- Version -> Click "..." and paste (example: 4.14)
- Syscode -> Click "..." and paste code
- Time -> Change to 21121231

Why 21121231? Why not the current date or any other date? What is special about that date?

Link to comment
Share on other sites


  • Replies 110
  • Views 17.2k
  • Created
  • Last Reply

Allow me to announce this update :

Combined 32/64 installer:

http://www.sandboxie.com/SandboxieInstall-415-11.exe

Separate:

http://www.sandboxie.com/SandboxieInstall32-415-11.exe

http://www.sandboxie.com/SandboxieInstall64-415-11.exe

Fixes in 4.15.11

The only change in this beta is to diagnose these 2 error messages:

SBIE2205 Service Not Implemented: LoadedModules

SBIE2205 Service Not Implemented: NtCreateProcessEx (xxxx)

I added an error code to the LoadedModules error. I believe the NtCreateProcessEx error is masking the real problem, which is a crash in the sandboxed application. So I removed it.

Now whatever application is crashing should reveal itself and we can diagnose the problem.

Link to comment
Share on other sites


  • 2 weeks later...

Combined 32/64 installer:
http://www.sandboxie.com/SandboxieInstall-415-12.exe

Separate:
http://www.sandboxie.com/SandboxieInstall32-415-12.exe
http://www.sandboxie.com/SandboxieInstall64-415-12.exe

Fixes in 4.15.12

1) KB3031432 in Win 8-64 causes Chrome-64 to crash.
2) Sbie now detects when a sandboxed application starts WerFault.exe because it has crashed, and gives WerFault plenty of time to create a crash DMP file.

WerFault has a couple of flaws. It doesn't create the crash DMP until the user presses OK on the crash popup dialog box. If the user does not respond quickly, the crashed application will exit memory and the DMP cannot be created. So now Sbie disables the WerFault dialog box and issues its own SBIE2224 "Sandboxed program has crashed". WerFault also must be given enough time to do various Internet activities before the application exits.

Link to comment
Share on other sites


I run Windows 8.1 x64 and SB 4.15.12, i can't get internet connection when i run Maxthon or IE sandboxed (chrome works perfect now)

Anyone else have that problem?

Link to comment
Share on other sites


  • 2 weeks later...

Why 21121231? Why not the current date or any other date? What is special about that date?

it's the date when the license would expire.

Link to comment
Share on other sites


  • 4 weeks later...
  • 6 months later...

Just registered to say persevere!

I upgraded to 4.18 because I upgrade Chrome and had to to get web sandboxing back.

After scouring, I kept coming back here. I found lots of links, but they all point to the same kit - dseo and the uuk tool.

It was only after following the exact instructions laid out in sHaRewbb_sndboxie418 22Mb RAR under Windows 7.txt

Instructions by sHaRewbb.com ( Do not leech )
Activate Sandboxie 4.18 on Windows 7 x86/x64 (Tested)
Then reboot the PC and Windows will be loaded in Test Mode
1. Install Sandboxie
2. Run the file "keygen_by_uuk.exe" (As Administrator)
3. Specify the folder in which you installed Sandboxie (field "Path")
4. Click the "Patch"
5. If you have a 64-bit operating system, do the following (all actions should be run as an administrator):
- Run dseo13b.exe (As Administrator) Click "Sign a System File" and
paste the following text in the input box: C:\Program Files\Sandboxie\SbieDrv.sys
- Also use dseo13b (run as admin) to enable test mode
6. Reboot the system
7. Run the file "keygen_by_uuk.exe" again (As Administrator)
- Specify the folder in which you installed Sandboxie (field "Path")
- Change the version 3.54 to 4.18
- Change syscode: Click "..." button, Sandboxie License Manager will appear.
Copy your System Code & paste it in Syscode box
- Change the duration of activation (ex, 20200220).
- Press 'Activate'
8. Reboot
9. In the corner of the left will be lifted up, "Test mode"
You can use dseo13b.exe to remove it
will try with v5.04, but don't think it's likely it'll still work...
Link to comment
Share on other sites


Archived

This topic is now archived and is closed to further replies.

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...