I'm using it now as a shareware. Only 1 sandbox at a time. For the first launch, it displays a shareware screen.
I seems this doesn't work with the newer versions of Sandboxie? I only want to use the classic version, without all the additional features, but I'm still seeing the nag each day. Looking through the source code to see how to remove it didn't help me as I don't know enough about coding. Scanning the Sandboxie installer with VirusTotal reveals (under behavior) that it openes some registry, but I don't know what really happens and how to reset the trial to escape the nag. Any ideas?
@MS-BOSS Since Sandboxie got sold to Sophos, Sophos did integrate most features in their Security solution. Sophos then made the Code Open Source. Since then DavidXanatos maintane the project and he gives us Classic and Plus. Classic is know something i would call "Nagware" (a more liberal language would call it "Donationware") and the Subscription for Plus is more then awful. The prices are pretty intense. Back to Classic and the Nagscreen. Looking to the source code could help, but even if you kill that code you must compile it on your own. And for running Sandboxie you need a valid code signing certificate, that are not cheap. This is because of the driver that must be signed. Otherwise you would have to run Windows everytime you start it in TEST MODE. Long speak, short solution... You have to use a debugger like x64dbg to find the point, where the nagscreen gets called and this happens with a jump if not equal (JNE). The nagscreen gets called inside the executable "start.exe".
Thank you for replying jazi4641. I'm too much of a "noob" to be able to find that and crack it. What about just restarting the "trial", as in the original post? But the question is, in which registry key (or in which file on the local disk) is the installation date that's being checked...
@MS-BOSS The original post only apply for the original Sandboxie from Ronen Tzur. I don't think that this key stayed the same since over 10 years!
No, the key is not in the registry after installing the new version of Sandboxie. I tried x64dbg and watched some tutorials but it's above my head, I can't find where the nag screen happens and how to get rid of it...
You may be able to work out something with editing the code and having a GitHub CI to build it for you. I see these two discussions about the nag: - github.com/sandboxie-plus/Sandboxie/discussions/2107 - github.com/sandboxie-plus/Sandboxie/issues/2926 Another option would be to trick the check into thinking Sandboxie was installed at a later date: github.com/sandboxie-plus/Sandboxie/blob/master/SandboxiePlus/SandMan/Windows/SupportDialog.cpp A possible alternative workaround is using virtual machines and snapshots to create a clean VM, install necessary software, and take a snapshot. When needed, revert to the snapshot to use a "clean" environment. To implement this, you'll need to learn about: - Setting up and configuring virtual machines; - Taking and managing snapshots; - Using snapshots to create a "rollback" point. Educate yourself on these topics to explore this option.
Hi, thanks for the reply. I tihnk rebuilding the code would need a new MS certificate, or running Windoes in test mode, which I don't want to. And I'd like to use Sandboxie on my real Windows system, like I did for years, not in the VM. I've seen those 2 discussions before. I've even found cracks and crack guides on github, but they are all for Sandboxie Plus. I just want to use the Sandboxie classic, no fancy featurtes, only wish to remove the nag screen.