Build 0.98.5 of Major Privacy now allows to script not only access rules but also program rules and enclaves. The script can log output to the built in log. The scripts are executed by the agent during a callback from the kernel. When the agent is not available the default rule action will be performed, so the rule should be set to most restrictive and the script used to implement advanced custom exceptions.
MajorPrivacyâs latest release focuses squarely on reliability, recoverability and responsiveness while adding a number of usability improvements and important security refinements. The Kernel Isolator driver now includes robust failsafe logic so that a configuration error can no longer easily leave a system unusable: the driver detects when Windows was started in Safe Mode and will refrain from enforcing rules so the system can be recovered, it counts unsuccessful boot attempts and will automatically load the last known good rule set after three failed boots, and after five failed boots it will refuse to load any rule set at all. These measures are intended to make misconfigurations much easier to recover from without manual driver intervention.
On the user interface side we added several features to make inspection and interaction faster and less error prone. Most views now include a Hold & Refresh button, there is an option to flatten the program view, and a new program-item-missing event helps detect and respond to removed or moved binaries. The traffic view now provides a menu action to block domains in the DNS filter or to block programs directly in the firewall. You can choose to hide default Windows firewall rules and to hide default Windows libraries in the module load view, and we restored missing first-start wizard pages while adding more UI configuration options. An online updater has been added to simplify future updates, and there is a new option to prevent the system from entering hibernation when protected secure volumes are mounted.
Under the hood the GUI is now multithreaded, which significantly improves responsiveness and reduces UI stalls, and we improved the image-checking mechanism and the status page. The user-controlled Code Integrity verification mechanism has been redesigned: user-trusted hashes and certificates are now stored in the registry alongside the protected configuration instead of in C:ProgramDataXanasoftMajorPrivacysig_db files. Important caution: the new code does not automatically import old signatures, so you will need to re-authorize your files after upgrading. We also improved log cleanup handling and UI performance around execution records.
This release fixes a number of stability and correctness issues: the BSOD related to remote file systems has been resolved; the translation list not being populated is fixed; accepting firewall rule changes from the summary page now works reliably; the hardlinked program running outside the enclave issue (#49) is addressed; an open handle resource leak was closed; a bug in the thread pool was fixed; many minor UI glitches were corrected; repeated Exec notifications caused by UPX-compressed files (#76) no longer occur; image signature verification and host name update issues were repaired; cases where image protection was incorrectly applied to non-protected processes were fixed; and the notification window bug was resolved.
Please note the signature storage change when you upgrade: because trusted signatures and certificates are now kept in the registry, you must re-authorize any files you previously trusted from the old sig_db files.
Download: https://github.com/xanasoft/MajorPrivacy/releases/tag/v0.98.4
Since my website is WordPress-based, and this is blogging software at heart, I thought I'd start a blog. I'm a very introverted person, but I also have a lot of thoughts and ideas I think are worth sharing with the rest of humanity.
I'll start with something controversial: a rant on why I think Linux is not even close to being a viable replacement for Windows (in most cases).
Now that Windows 10 support is coming to an end for most consumers (for corporate users it's different due to 3 years of promised ESU), and Windows 11 has very high hardware requirements, many people are contemplating: what now?
Buy Windows 11 compatible hardware? A waste of money and a waste of global resources.
Install Windows 11 on officially unsupported hardware? Works great. I myself run it on a few 2013-era Dual Xeon V2 systems; a high-end CPU from that age with plenty of RAM and an SSD is still pretty fast for most use cases. To make a point: only a Zen 4 Ryzen or later CPU is at least 2x faster in single-threaded use cases than an old Ivy Bridge Xeon. All the older CPUs still officially supported by Windows 11 are not even 2x as fast as decade-old hardware. And what's not at least a more-than-2x improvement is not a worthy upgrade.
The official reason for Windows 11 not supporting even Zen 1 is the lack of CPU extensions required for good performance when using VBS (Virtualization-Based Security). Nice to have, but for no reasonable consumer a must-have. In fact, it is incompatible with some up-to-date 3rd party virtualization software one may still want to use. But Microsoft may at any point make VBS mandatory, or decide to use some less important instruction set extension (like AVX) that is supported by newer CPUs but not by great, still-working decade-old systems - like what already happened with requiring SSE4.2 in 24H2 and later.
So, what else? Running Windows 10 without security updates is not a recommended option, and obtaining a version of Windows 10 that would have support until at least 2031 is, let's say it this way, license-wise challenging.
A fourth solution is now being advocated on the internet, and its proponents see a great opportunity on the horizon: switching to Linux. It's entirely free (like in freedom), it often doesn't cost any money (like in free beer), and it doesn't monetize its users - not even the non-paying ones. Moreover, it still supports hardware from the dawn of the century. So, is that a viable option? For some, sure. But to be honest, these are the people who would have been better off with a Chromebook to begin with, instead of getting a full-blown universal personal computer. For Windows power users, no - it is not.
Linux fails as a Windows replacement in many ways. On one hand, it's about its design policies, its GUI (or lack thereof). On the other, it simply fails because WINE is unable to run most Win32 applications. And while there are many other smaller shortcomings, those are all immaterial - Windows has plenty of its own small issues as well.
Let's start with the second point first - it's simpler and more straightforward. Not every Windows program has an open-source Linux alternative, not even a decent one. Often, proponents of switching to Linux will claim there are alternatives and it's only about âgetting used to something new.â They try to put the blame on the users: a.) not putting in enough effort to find the alternatives, and b.) not spending enough time learning how to use them.
There are two things to be said about this: First: It is simply not true. For example, GIMP is not a real alternative to Photoshop. Claiming otherwise is like saying MS Paint is an alternative to Paint.NET. Yes, kind of, but only in the way a Ford Model T is an alternative to a modern car - they will both bring you from A to B, but it's everything but the same. Second: More importantly, even if there were feature-equivalent alternatives to every Windows application, the burden of relearning a quarter century (or more) of muscle memory and know-how is, bluntly said, a debilitating handicap. It's like trying to get your life back after a stroke. Even if it's possible, it's an almost insurmountable effort that should not be casually demanded of anyone.
And the reality is: most Linux software that would qualify as an alternative has fewer features and a less polished GUI. So even if one found alternatives and learned to use them, one would still feel handicapped compared to life before the Linux.
In computing, software compatibility is everything. Short of creating a completely new product category and being one of the first movers, no company has ever managed to enter the market without compatibility with existing software.
My favorite example is Windows Phone. It was, all in all, a great smartphone operating system. But it lacked one crucial thing - the one reason, in my opinion, for its failure: it did not run Android (or iOS) apps. That's it, full stop. Enough said. That's why it failed. Many others failed for the same reason - Windows RT (the Windows that couldn't run Win32 apps), and so on.
In the past, companies understood this. The C128 came with an entire C64 subsystem and secondary CPU for full compatibility with C64 software, because no matter how much better a C128 could be, if it could not run existing software, it would have been garbage.
Apple knew that as well. Whenever they broke everything and made life hell for developers, they still made sure old existing software could run on the new Macs - even across two major CPU architecture changes. Users did not experience interruptions. Because in computing, the only thing that matters in the end is: does your new system run your old software? Everything else - 4x the clock speed, 8x the RAM - is just nice to have, not mandatory.
The only example in this century of a new OS establishing itself was iOS/Android. They were first movers in a new market segment where almost no software existed before, a little bit Symbian and a few Windows CE/PocketPC's all targeting business users only was all there was. Microsoft already came too late to the party with Windows Phone.
In light of this, thinking Linux could succeed without a working WINE was always self-deception. The only way Linux could win the desktop in the long run would be if major countries worldwide outlawed Windows in schools and mandated Linux as children's first contact with IT. Even then, it would take 20 - 40 years.
And after many painful lessons, even Microsoft learned this. Windows on ARM has one feature that makes it useful: it can run almost all x86/x64 software. Sure, it does it via emulation, but almost flawlessly. That's why this time ARM can finally compete with x86/x64. Whether ARM is better than CISC may or may not be true - but it doesn't matter. It never mattered.
Let's set that aside. There are workarounds - for example, running Windows VMs. If one's goal is enhanced privacy and independence, running a bunch of compartmentalized, stripped-down Windows VMs on a Linux host for the required Windows software is a workable solution. In fact, I myself, while still using Windows as the host OS, run larger software packages in Windows VMs for compartmentalization: to make them portable when I upgrade or switch devices, and to be able to reinstall the host OS without disturbing my workflows.
So, let's focus next on the standalone issues of Linux.
Linux is a CLI-first operating system. Most Unixes are, but not all. This is a problem. Everything UI on Linux feels like an afterthought. Yes, today you can install and use most Linux distributions without touching the CLI or config files, but this won't satisfy anyone beyond basic users.
Using a Linux GUI feels like using a Mac - and just to be clear, that is NOT a compliment. Quite the opposite. And if that weren't enough, on Macs most things usually just work. If they don't, forget about them - you won't get them to work as a mere mortal. Stay inside the lines Apple drew for you. On Linux, many things simply don't work at all.
What I personally find most frustrating is that since Windows 8, Microsoft has been moving Windows more and more towards a Mac OS - like experience, which means nothing good.
I realize this sounds very subjective - I grew up with DOS and Windows. But I assure you, dear reader, there are concrete advantages in how classic Windows was designed that make it superior to any other mainstream operating system currently available. I will outline those advantages in the next paragraphs - advantages Microsoft is actively destroying in their latest Windows versions.
At the core, it's about why GUI-first is generally better than a CLI approach. Not all humans have the same cognitive abilities. That applies to many fields, but here the relevant attribute is memory.
Some people have very good procedural and semantic memory. They can easily use a CLI, edit uncommented config files, and so on. However, this type of memory is not common. What most people are great at is associative memory - which makes sense, because that's the type of memory animals need the most in the wilderness.
A GUI can be navigated with associative memory. One doesn't need to remember what the tool is called, what arguments it takes, and how to mix the parameters. Just looking at the GUI reveals these directly. Or at least, to a somewhat experienced user, it becomes immediately apparent where to look for more options if the ones wanted are not yet visible.
So, it helps one to remember how to use it - something a CLI does not do. But a GUI is even better: one often doesn't even need to know how to use it beforehand. Just by seeing the offered options with a basic abstract understanding of computing, one can often deduce how to use it. As a side effect, it also makes new features and options apparent during normal usage.
This may sound like GUIs are for the cognitively inferior. But is that bad? Don't we want to empower as many people as possible to be capable and powerful computer users, regardless of their natural strengths?
A personal example: I grew up using VMware. When I needed to use Hyper-V or VirtualBox, I could do it - not to the same level I knew VMware, but to a solid 80%, simply by looking at the GUI and abstracting the knowledge I had about virtualization.
When I had to use KVM on Linux, I was like a caveman in front of a Ford Model T. After ChatGPT explained step by step how to configure it, I could operate it - to the extent it was explained, as long as I had my cheat sheet with the written-down commands. And yes, one can even teach an orangutan to drive a golf cart.
But whenever I needed to change a new option - an option I knew from GUI-based tools should exist - I couldn't. Not without asking AI or googling it. Sure, I could have read (or Ctrl+F'd) through the hundreds of manual pages and documentation. I know I could do so much more with KVM than with VMware Workstation - PCIe passthrough, GPU virtualization, etc. - but I can't, not without investing far more time than I want to spend on it.
A well-designed GUI makes reading the documentation for most common tasks obsolete. Isn't that an incredibly great thing?
So no, GUIs are not just a crutch for the cognitively inferior - they are powerful mechanisms that let the best and brightest focus their limited time on the important things. Understanding how computing works is important, but explicit knowledge of how tool X, Y, or Z works is not. It's useful when you have the tool, but useless elsewhere. That's why all cars have their control elements mostly in the same places and working similarly.
Could CLIs be standardized to follow the same patterns across different tools? Probably - but in reality, no one ever bothered.
Without the self-revealing property of a GUI, any CLI tool is at first a book closed with seven seals.
The core issue with Linux, macOS, and modern Windows GUIs is that they only offer you the absolute basics. If you have any non-trivial requirements, they fail in their own way. Linux sends you to the CLI. macOS tells you âThis is not something Apple wants you to do.â Modern Windows sends you to the vestiges of the classic Control Panel.
The classic Windows GUI design, which offered tools not only for the computer illiterate but also for advanced power users, was great. It offered a simple pathway of many minor steps for beginners to become power users - without forcing them to jump over large hurdles like memorizing documentation.
To hammer the point home:
On a CLI-based system, you need to learn how things work and how to operate the tools.
On a GUI-based system, you need to learn how things work - but can then use any tool without first learning its operation first.
Another example: if you know how to use an image backup tool like Acronis True Image, you can almost as easily operate competing products like Macrium Reflect or Ashampoo Backup. They're not the same, but if you understand the underlying mechanics, they're all similar enough.
On Linux, if you know how to use dd, that won't help you at all with Clonezilla - and that's very frustrating.
Are GUIs always superior? No, of course not. There are use cases where a CLI is better - for example, when you need to recreate setups with only a script, or when you have complex toolchains with many interdependencies. Recreating those with a GUI is a chore. But such advantages are not an argument against GUIs - just for software offering both.
Unfortunately, most developers seem to follow the policy that âif you have a full CLI, you can get by with a limited, dumbed-down GUI.â And this is simply wrong. It makes life for aspiring power users so much harder.
In my eyes, whoever doesn't provide a proper, full GUI for their software wants computing to remain a kind of dark magic - something only for the initiated few who can afford to spend 10,000 hours mastering the relevant CLI tools.
A proper GUI is inclusive - and of great use to everyone - isn't that the zeitgeist of our age, not to exclude anyone because of their individual shortcomings?
And frankly, Linux is right now (as of 2025) deprecating X in favor of Wayland, which is universally criticized for its inadequate and/or missing accessibility features, effectively excluding the visually impaired from computing for the sake of having a more secure and technically elegant solution. But what good is security if it makes it impossible, or barely possible, to keep using computers?
I personally miss many things in Linux, but listing all of them here would not be the point of this text (I may dedicate a follow up post to my own experiences with trying (more than once) to move to Linux); for everyone, different missing things will be most important...
So, let's instead focus on other Linux design policies which make it a real PITA for the casual user. Linux is extremely fragmented. A myriad of distributions may look like choice and freedom, but in practice it's a nightmare of spotty compatibility and functionality. Fragmentation does not need to be a bad thing, as Android shows: every vendor has their own flavour, but all apps work on all Android devices if they are new enough. With Linux, that is not the case. Even though the glibc ABI itself is technically kept stable, in practice different distributions ship different library versions and dependencies, meaning that a binary built for one often won't run on another. So basically, no developer can provide an application that would âjust workâ on Linux, short of packaging their own complete user space with it. In fact, some do: solutions like Flatpak, Snap, or AppImage provide all the libraries needed and only rely on the kernel ABI, which - unlike user-space packaging - does not change.
Call it my small personal conspiracy theory, but that can't be due to ignorance or incompetence; it must be on purpose, to make closed-source development, if not impossible, then at least highly impractical. I personally like open source, but trying to enforce it as the only acceptable norm from the position of an underdog is outright stupid. An OS family that deliberately shows the middle finger to all commercial software vendors should not complain about there being little to no commercial software for it. But complain its users do: for many people, a major hindrance on the way away from Windows is that they can't find workable alternatives to the tools they rely upon, which only run on Windows.
If Linux ever wants to be a serious OS, it must cater not just to the FLOSS crowd but at least avoid making the life of closed-source developers deliberately hard. Do it like Android: ensure that any app compiled for Linux ten years ago will run on any modern distribution. It's not as if nobody thought of this before - there was even the Linux Standard Base (LSB), which tried to be exactly that kind of unified baseline, but it fizzled out because distributions didn't want to tie themselves to long-term compatibility. Still, the need has only grown. It's time for a Great Unified User Space (let's call it GUUS for short).
There are many other things I haven't touched here in deep, like hardware support, driver compatibility, Gaming, Ecosystem Lock-in, Cloud Services integration and much more. To just share a few thoughts on that, In the past windows had the best hardware support even for the oldest of hardware, but this is often no longer true, if you have e.g. a printer from the year 2000 you'll probably get it to run on Linux but will fail on windows. Gaming is improving in great leaps thanks to valve, and Ecosystem Lock-in / Cloud Services well some people don't want any of that and the fact it may not work on Linux is not a bug but a feature.
To summarize, these are the three main issues in my view: the lack of proper GUIs, the lack of long-term compatibility, and the lack of a reliable Win32 compatibility layer. Together, they turn Linux into a very peculiar product - a bi-modal operating system. On one end of the spectrum, if it happens to run on a given piece of hardware, it can serve the computer illiterate surprisingly well. A simple desktop with Firefox, LibreOffice, and a few basic apps works fine for web browsing, email, and light office use. As long as nothing breaks, these users never touch the CLI and may even believe Linux is âeasy.â
On the other end of the spectrum are the console-loving geeks. These are the people who enjoy spending countless hours tweaking config files, chasing obscure dependencies, and building up vast collections of specialized knowledge. They treat their operating system like a puzzle box, a place to prove their cleverness and mastery of arcane tools. For them, the constant change, the rough edges, and even the breakage are part of the fun. But this knowledge rarely transfers beyond Linux itself - it's neither broadly generalizable nor guaranteed to remain valid long-term. What works today might be obsolete in the next kernel, the next distribution release, or the next wave of half-finished packaging solutions.
And in between those two extremes lie the majority of users - the people who want to be productive, to install software and use it, to get their work done without friction or ritual. For them, Linux consistently fails. It neither offers the turnkey reliability of Windows nor the polished consistency of macOS. Unless you are content with bare-minimum use or willing to dedicate yourself fully to the Linux way of life, it leaves you stranded.
To put it bluntly: as long as it takes less work and hassle to strip down whatever version of Windows is current - removing the bloat, disabling the nags, and cutting off its endless communication with the mothership - than it does to get all essential workflows running smoothly on Linux, Windows will remain the only viable option for many. No matter how bad Windows becomes in the coming years, it will still be easier to tame than to replace. That's the sad irony: Microsoft can keep making Windows worse, and yet it will remain the path of least resistance, because Linux still hasn't solved the fundamentals.
You can discuss this article on our forum: https://forum.xanasoft.com/forums/forum-discussion.28/
FYI: I let ChatGPT correct the gramatics and ortography of the above text and help me draft the final words.
This release of MajorPrivacy introduces several important improvements, bug fixes, and optimizations. The resource access rules engine has been enhanced to include the user as an additional parameter, enabling finer-grained access control. CPU usage has been reduced in both the user interface and background service, improving overall performance. The ImBox feature has been updated to avoid modifying container file timestamps when accessing secure encrypted volumes. Firewall rule handling has been improved for Store Apps on Windows 23H2 and later versions, increasing compatibility and reliability.
A critical issue has been resolved in ImBox.exe that affects the mounting of older encrypted volumes; users should use a previous build to recover data and then recreate the volumes using this or a later version. Additionally, several interface and functionality bugs have been addressed: translations now load correctly, the Data Editorâs tree view now functions properly across multiple .dat files, and the Execution Monitor displays entries as expected when a time filter is applied. The âAdd to Groupâ menu now correctly lists all available groups, and folder creation is no longer incorrectly permitted under Directory Listing and Read-only actions.
Download: https://github.com/xanasoft/MajorPrivacy/releases/tag/v0.98.3
The final release of Sandboxie-Plus version 1.16.2 / 5.71.2 consolidates and builds upon the significant advancements introduced in the recent pre-releases, delivering a more secure, compatible, and modernized sandboxing experience.
This version marks a major step forward in platform modernization. The underlying codebase has been updated to the MSVC 2022 toolset, while the user interface has migrated from Qt 5 to Qt 6. These changes provide better performance, improved security, and access to newer development features. However, they also necessitate the discontinuation of support for Windows 7 and 32-bit systems. Depending on user interest, an Extended Support Release (ESR) for older systems may be considered.
The update further refines usability and functionality. A new INI key validation feature, complete with per-key tooltips, has been integrated into the INI section editor, making advanced configuration safer and more accessible. SandMan now also supports an optional Windows 11-style visual theme, enhancing UI consistency on modern systems.
A major new feature allows administrators to redirect all files marked with the "Mark of the Web" into a designated sandbox, improving security by isolating potentially unsafe downloads. Forced process rules now support wildcards, and virtual sandboxes can be created without being written into the main configuration file, ideal for temporary or dynamically managed setups.
Under the hood, the DNS filter logic has been hardened to prevent unresolved domains from bypassing filtering, addressing a potential security flaw.
Additional improvements to system object handling now cover EventPair, KeyedEvent, and Timer types, enhancing compatibility with more applications.
The UAC subsystem can now invoke Sandboxie's own prompt, capable of simulating administrative rights without actual elevation, for more secure testing scenarios.
This release also addresses a range of bugs. Issues with incomplete shortcut paths, broken network adapter isolation, misinterpreted backslash-prefixed file paths, and language mismatches during installation have been resolved. The UAC prompt layout has been visually refined, and a long-standing fullscreen issue with Firefoxâs taskbar behavior has been fixed. Moreover, Firefox compatibility has been improved for both stable and Nightly builds, resolving recent hook-related failures. An important security issue involving sandbox key leaks during encrypted volume password changes has also been mitigated by backporting hardened logic from MajorPrivacy.
Together, these changes offer a more future-proof, stable, and secure experience for Sandboxie-Plus users.
For a full list of changes please review the change log.
Download: https://github.com/sandboxie-plus/Sandboxie/releases/tag/v1.16.2
MajorPrivacy version 0.98.2 introduces several powerful new features and critical stability improvements. This release adds a mechanism for detecting and restoring changes to Windows Firewall rules, helping users maintain consistent privacy configurations even when rules are modified externally. One of the major highlights is the introduction of a JavaScript engine that enables users to define advanced scripted rules, laying the groundwork for highly customizable privacy logicâthough much of the scripting API is still under development and will be expanded in upcoming releases.
A new summary page has been added, offering users a centralized view of their systemâs privacy status. This page includes information about detected privacy issues, recent relevant events, and a comprehensive activity log. The notification system has also been refined for better usability and visual clarity.
Under the hood, the project has been updated to the latest development toolchain, now using Visual Studio 2022 and Qt 6. Several important bugs have been resolved, including a blue screen issue related to the driver, problems with signature database management, and missing descriptions for tweaks in the user interface. Additionally, issues with loading volume rules have been addressed to improve overall reliability.
Download: https://github.com/xanasoft/MajorPrivacy/releases/tag/v0.98.2
The new release updates TaskExplorer to the latest PHlib and VS2022 toolset.
updated PHlib to version 3.2.25180.1655
switched to VS2022 toolset
updated Qt to 5.15.16
Download: https://github.com/DavidXanatos/TaskExplorer/releases/tag/v1.6.5
The 0.98.1 release of MajorPrivacy introduces significant enhancements and a number of critical fixes aimed at improving usability, localization, and system integration. A major new feature is the introduction of full translation support, allowing the application interface and tweaks to be localized into multiple languages. Initial translations include AI-assisted German and Polish versions, a community-contributed Turkish translation, and Simplified Chinese. Users interested in contributing translations or adding new languages are encouraged to participate via the forum.
This version also improves compatibility and deployment by bundling the Microsoft Visual C++ Redistributable with the installer, which is required for the ImDisk user interface.
Several important bugs have been resolved. The installer now correctly removes the driver during uninstallation. Tweak definitions have been cleaned up for better consistency. A number of networking issues were addressed, including failures related to network shares and incorrect handling of mapped drive letters. It is now required to use full UNC paths for defining rules involving shared resources. Additionally, configuration persistence issues on system shutdown have been fixed, as well as problems affecting protected folder visibility and rule precedence involving enclave conditions.
Finally, the underlying driver code has been refactored, laying the groundwork for better maintainability and future enhancements.
Download: https://github.com/xanasoft/MajorPrivacy/releases/tag/v0.98.1
This release introduces several important improvements to Sandboxie-Plus, further enhancing compatibility, usability, and control for advanced users. A new option has been added to copy the Hardware ID directly from the support page for convenience. More significantly, a powerful new feature allows administrators to automatically redirect all files marked with "Mark of the Web" into a specified sandbox using the MarkOfTheWebBox=BoxName setting. Wildcard support has also been introduced for forced process rules, and a new option now allows for the creation of virtual sandboxes that do not require persistence in the main configuration file.
The Trace Log page now properly adapts text scaling in the 'Type' dropdown, ensuring clarity on high-DPI displays. Several system object types, such as EventPair, KeyedEvent, and Timer, have received improved virtualization and filtering support. A new UAC handling option (UseSandboxieUAC=y) enables Sandboxieâs own prompt, which includes the ability to simulate administrator rights without actually elevating privileges.
Under the hood, the DNS Filter logic has been refactored to address issues where domains that did not resolve could bypass filteringâthis resolves potential security leaks and improves consistency. Support for compiler security features like /GS and /CETCOMPAT has been expanded to more components, and INI configuration handling has been modernized to allow importing sandbox configurations from external files and support for virtual config sections within the driver.
Finally, a number of bugs have been resolved, including a persistent taskbar issue in Firefox when entering fullscreen mode, glitches in content deletion UI, unexpected Sandboxie Plus shutdowns, and context menu execution behavior on Windows 11. Display issues and inconsistencies in the Move Sandbox menu have also been addressed, offering a more stable and refined user experience overall.
For a full list of changes please review the change log.
Download: https://github.com/sandboxie-plus/Sandboxie/releases/tag/v1.16.0
This update marks a major step forward in functionality, security, and usability for MajorPrivacy. With version 0.98.0, we're introducing an installer to simplify setup and deployment. Core security enhancements include token integrity level elevation for enclave processes, significantly improving User Interface Privilege Isolation (UIPI), and new driver unload protection to guard against tampering. Secure desktop prompting has been implemented, requiring explicit user approval before Core components can be shut down, reinforcing trusted control over critical operations.
The AccessTree now includes a convenient "Copy Path" feature, and the tweak management interface has been upgraded with the ability to approve or restore tweaks directly within the view. A range of new privacy and security tweaks are now available, including resource access restrictions, execution control, and finely tuned firewall rule adjustments.
In terms of usability improvements, the tweaks view has been refined, and tweak status is now persistently saved to disk, ensuring settings survive reboots or restarts. Weâve also resolved a critical stability issue that could cause a BSOD when the agent crashed during process startup inside an enclave.
This release lays important groundwork for the upcoming 1.0 milestone by tightening system integrity and enhancing user control without compromising performance or clarity.
Download: https://github.com/xanasoft/MajorPrivacy/releases/tag/v0.98.0
fixed failure to update dyndata
fixed crash when dyndata update failed
Download: https://github.com/DavidXanatos/TaskExplorer/releases/tag/v1.6.4
improved berformance with very big processes
updated dyndata for latest windows
fixed issue with stack traces introduced 1.6.1
fixed issue with run as Trusted Installer or as this user
Download: https://github.com/DavidXanatos/TaskExplorer/releases/tag/v1.6.3
Sandboxie Plus version 1.15.12 / 5.70.12 introduces a range of enhancements, fixes, and usability improvements. This release adds Indonesian language support to the Plus UI, a new template for the WeType Input Method Editor (IME), and support for proxy configuration using host names instead of raw IPs by resolving them at WSA_Startup. Sandboxie can now bind to network adapters rather than specific IP addresses, providing more flexibility in networking setups. Additionally, support for the %ProgramFiles(x86)% environment variable has been introduced, along with a new TemplateDefaultFolders entry to define standard paths in privacy-enhanced boxes.
Several changes improve usability and performance. The "Move Sandbox" list sorting behavior has been refined, and personal details like name and hardware ID in the Support tab are now hidden by default. An experimental alternative proxy relay implementation has also been added, shifting from socket modification to relay threads.
Numerous issues have been addressed. These include the BoxAlias not appearing in the "run in box" dialog, UI inconsistencies after using Ctrl+F, and persistent high I/O usage by SbieCtrl.exe and SandMan.exe. Registry access functions were hardened with additional checks, and problems with Tencent TIM, MSI installer behavior, and oversized Sandboxie.ini files have been resolved. Other fixes address UI glitches, translation inconsistencies, drag-and-drop issues, and crashes related to SbieDll.dll. Compatibility problems with PingInfoView and a loop condition in CollectProducts() have also been fixed.
For a full list of changes please review the change log.
Download: https://github.com/sandboxie-plus/Sandboxie/releases/tag/v1.15.12
May Insider Download (for great patreons and above only): https://github.com/DavidXanatos/Sandboxie-Next/releases/tag/May-01-2025
This release of MajorPrivacy introduces several powerful new features and important improvements. A DNS filter server has been added, enabling more granular control over DNS traffic. Users can now define Windows Firewall rule templates with wildcard-enabled paths, significantly streamlining rule creation. The ingress view includes a new operation filter, and program items in the UI now display memory usage for log and trace data, with a total memory usage indicator for services. We've also introduced trace presets per process and added an option to enable debugging of processes running in enclaves. For easier navigation, a new "expand/collapse all" button has been added to the program tree.
Path rule handling has been reworked with a more flexible mechanism supporting DOS-style patterns, with plans for a future rule import system. The firewall popup now ignores incoming connection attempts to avoid unnecessary prompts. Internally, the project structure, framework, and variant implementation have been refactored and cleaned up, resulting in a more stable and maintainable codebase. Log and trace data are now managed using dedicated memory pools per program, improving performance and reliability.
This version also resolves a deadlock issue during program list cleanup and a crash that could occur when stopping the service while the UI remained open.
Download: https://github.com/xanasoft/MajorPrivacy/releases/tag/v0.97.2
A new Sandboxie-Plus Insider build based on 1.15.11 is available for Great Patreon's and above: https://github.com/DavidXanatos/Sandboxie-Next/releases/tag/April-04-2025 as well as to all holders of DEVELOPER type supporter certificates.
Exclusive Insider Features
The Insider builds introduce several powerful enhancements designed to improve security, usability, and customization in Sandboxie-Plus:
Isolated Desktops â Run applications in their own fully isolated Windows desktop environment, separate from the default user desktop.
Isolated Clipboard â Each sandbox can have its own independent clipboard, fully isolated from the host system, with options for read-only or write-only integration.
Portable Sandboxes â Use sandboxes configured in independent .ini files, enabling fully self-contained and portable sandbox setups.
Urgend bugfix: fixed issue with SboxHostDll.dll failing to be injected into OfficeClickToRun.exe
Download: https://github.com/sandboxie-plus/Sandboxie/releases/tag/v1.15.11
This release primarily addresses critical compatibility issues with Firefox, ensuring that version 137.0 and later now runs correctly within Sandboxie Plus without generating SBIE2328 notifications. This fix restores proper functionality for Firefox users, resolving a major disruption introduced in the previous version.
In addition to the Firefox fix, this update introduces a new configuration option, BindAdapterIP, which allows users to bind sandboxed applications to a specific host IP address. This can be defined globally or per process via the INI file, offering greater control over network behavior within the sandbox. Itâs important to note that the specified IP must be bound to a local network interface, or connections will fail.
Several additional issues have been resolved, including problems affecting Thunderbird. Memory leaks related to process command line retrieval have been addressed, and missing components like SbieShellExt.dll have been restored.
For a full list of changes please review the change log.
Download: https://github.com/sandboxie-plus/Sandboxie/releases/tag/v1.15.10
I have updated the code at https://xanasoft.com/get-supporter-certificate/ it now should use the OPTIONS field, and DAYS field for new patreons.
Also there is a new Patreon tier: Advanced located between the Regular and Great.
Sandboxie Plus 1.15.9 delivers a robust update centered on security, stability, and compatibilityâparticularly for users of modern web browsers and those prioritizing privacy and sandbox integrity.
A key highlight is the improved compatibility with Firefox 137 Nightly and later, resolving previous hooking issues that caused instability or functional limitations. Firefox now runs smoothly within sandboxed environments once again.
Security enhancements are another major focus. This release addresses a potential IP leakage vulnerability affecting dual-stack IPv4/IPv6 setups when only one proxy type was configured. Connections now fail gracefully if no proxy is set for the relevant IP type, effectively preventing unintentional bypasses and preserving user anonymityâa critical improvement for users relying on VPNs or proxies.
Additionally, a serious local privilege escalation vulnerability tied to the HostenjectDll mechanism has been patched, thanks to responsible disclosure. This fix strengthens Sandboxie's role as a secure execution layer.
For advanced users, a new debug option OpenAllSysCalls=y has been added, allowing unrestricted system call access for testing purposes. However, due to its permissive nature, it should be used with caution.
Among the usability improvements, users can now duplicate sandboxes and their contents directly from the UI, streamlining environment management. The update also introduces a new developer certificate type that disables user-mode component verification for advanced use cases. This node-locked certificate is available at no additional cost to existing Contributor or Eternal/Huge certificate holders upon request.
Overall, version 1.15.9 brings a thoughtful balance of new features, critical fixes, and user-focused enhancements, reinforcing Sandboxie Plus as a powerful tool for secure application isolation.
For a full list of changes please review the change log.
Download: https://github.com/sandboxie-plus/Sandboxie/releases/tag/v1.15.9
Version 0.97.1 of MajorPrivacy introduces several new features, improvements, and fixes, enhancing both functionality and reliability. This update continues to refine the toolâs ability to manage privacy, security, and process control in modern Windows environments.
In this release, an optional user password cache is now available, allowing users to store credentials locally if desired, to simplify certain interactions. The tray menu has also been expanded, providing more convenient access to frequently used functions directly from the system tray. To improve visibility into network activity, additional filters have been added to the network views, giving users more granular control over what data is displayed.
Several significant changes have also been made to enhance usability and functionality. Signature verification has been reworked and improved. The Ingress record has been moved to its own dedicated file, separating it from other logs for better organization. Along with this, file naming conventions have been revised: AccessLog.dat has been renamed to AccessRecord.dat and TrafficLog.dat is now called TrafficRecord.dat. Since MajorPrivacy is still in beta, the old files will not be automatically migrated or cleaned up, so users are encouraged to manually delete them from C:ProgramDataXanasoftMajorPrivacy if they are no longer needed.
Another important change is that, by default, no records (Traffic, Execution, Ingress, Access) are stored to disk anymore. This change reflects a stronger focus on privacy by default, ensuring that only users who explicitly choose to enable logging will have data written to disk. Furthermore, the services configuration file has been renamed to PrivacyAgent.ini to better align with the serviceâs role. Finally, popup notifications have been cleaned up to avoid showing redundant entries, improving readability and reducing noise in high-activity environments.
This release also addresses several critical bugs and compatibility issues. An incompatibility between ZwLockRegistryKey usage and HVCI (Hypervisor Code Integrity) has been resolved, ensuring MajorPrivacy works correctly on systems with HVCI enabled. Multiple UI crashes related to process protection and DLL loading have been fixed, significantly improving stability. Lastly, a crash occurring when setting the firewall filtering mode has been corrected, ensuring smoother configuration changes.
With these additions, improvements, and fixes, MajorPrivacy 0.97.1 offers a more robust and reliable experience, particularly for users working with advanced security configurations and detailed process monitoring needs.
Download: https://github.com/xanasoft/MajorPrivacy/releases/tag/v0.97.1
Download: https://github.com/DavidXanatos/TaskExplorer/releases/tag/v1.6.2
added driver DynData updater, on start when the current DynData is not compatible with the windows kernel TE will offer an option to update the DynData
Note: the updater extracts the DynData from regular SystemInformer canary update packages.
added preparations (not enebled) to use the old driver on windows 7
moved translations to translations.7z
incompatybility witn windows 7 introduced in 1.16.1
fixed crash in module search window
fixed performance issue with codepage detection
In this update, several improvements and fixes have been introduced to enhance the stability and functionality of Sandboxie Plus.
A new capability has been added to the service, allowing it to log monitor events, providing users with additional insights and diagnostics.
The Notepad++ template has been updated to ensure compatibility with Sandboxie Classic, improving usability for users of the legacy version. Additionally, MiscHelpers.dll has been updated with enhancements to the finder, contributing to improved performance and reliability.
Several issues have been resolved in this release. Obsolete entries in the Sandboxie Plus installer have been removed, ensuring a cleaner installation process. An issue where pinned shortcuts created via the 'Run from Start Menu' option were non-functional has been fixed, addressing reported concerns (#4502). A potential Blue Screen of Death (BSoD) issue with the driver under low-resource conditions has been resolved, improving overall system stability.
Further refinements include fixing a crash occurring in NsiAllocateAndGetTable, thanks to a report from tzf-omkey (#4511). Additionally, two memory leaks have been addressed: one occurring when a sandboxed process received a device change notification, and another affecting the NtQueryDirectoryFile hook, which previously manifested in privacy-enhanced sandboxes (#4509).
This update ensures a more robust and efficient experience for Sandboxie Plus users. As always, feedback and reports from the community are invaluable in maintaining and improving the software.
For a full list of changes please review the change log.
Download: https://github.com/sandboxie-plus/Sandboxie/releases/tag/v1.15.7
Download: https://github.com/DavidXanatos/TaskExplorer/releases/tag/v1.6.1
added ARM64 driver
added translations
updated code to be qt6 comaptible
greately improved dark mode
improved driver statis information on startup
updated MiscHelpers.dll, improved finder
fixed Closing System Info closes also the TaskExplorer #34
fixed handle leak in thread stack panel
fixed bad performance on windows 10
fixed issue where two instances were started when "Skip UAC" was enabled
This insider build is a bit more experimental them usual, it contains 2 new features: Sandboxed clipboard & better clipboard isolation, as well as portable boxes, see github screenshots for details.
Download for Great Patreons and above : https://github.com/DavidXanatos/Sandboxie-Next/releases/tag/Feb-20-2025
This update introduces improvements to stability, compatibility, and debugging tools, addressing several reported issues affecting various applications and sandbox configurations.
This release also includes a rework of CreateDesktop handling, which addresses various issues encountered with browsers and browser-based applications when running within Sandboxie. These changes should result in improved stability and functionality for affected software. Furthermore, a missing hook for NtQueryInformationByName has been implemented to enhance overall system compatibility.
Several bugs have been resolved in this update. An issue where the Sandboxie Plus data folder was not functioning correctly after updating to version 1.15.5 has been fixed. Additionally, crashes affecting Adobe Acrobat Reader when used within an Application Compartment box have been resolved.
Compatibility issues with Viber have also been fixed, ensuring that the software no longer crashes upon launch within Sandboxie. Users of qutebrowser will benefit from a fix that now allows the browser to run properly in a sandboxed environment. A problem preventing applications from launching when ApiTrace was enabled in version 1.15.5 has also been resolved. Lastly, a critical fix has been implemented to prevent blue screen errors (BSoD) when using OpenWndStation=y on Windows 10 with applications that call CreateDesktopW/A.
This release provides key stability and usability improvements for Sandboxie Plus, ensuring better compatibility across a range of applications.
For a full list of changes please review the change log: https://github.com/sandboxie-plus/Sandboxie/blob/master/CHANGELOG.md#1156--5706---2025-01-3
Download: https://github.com/sandboxie-plus/Sandboxie/releases/tag/v1.15.6
https://github.com/DavidXanatos/Sandboxie-Next/releases/tag/Feb-02-2025
this link works only for patreons on the Great tier and above.
This release introduces several important fixes to enhance functionality and improve user experience.
A new debugging feature has been added with the inclusion of the HookTrace=y setting, which provides enhanced debugging capabilities for API hooking.
The Sandboxie-Plus data folder has been relocated from C:Users[User]AppDataLocalSandboxie-Plus to C:Users[User]AppDataLocalXanasoftSandboxie-Plus. This change is automatic for users upgrading to this version, but those downgrading to an older version will need to move the folder back manually. Additionally, some options in the box context menu have been re-ordered for improved usability.
This update resolves several critical issues and enhances overall stability. The crash triggered by selecting "Run as Administrator" in the non-advanced view has been fixed, along with a crash caused by missing IP definitions in DNS filtering (#3600, #4475).
Compatibility with ARM64 systems has been significantly improved, addressing issues such as x64 executables failing to run on Windows 11 ARM64 (#4422, #4415) and resolving compatibility MSEdge and explorer problems with Windows 10 ARM64.
Several user experience issues have also been addressed. These include process self-termination failures, infinite loops when Gui_ConnectConsole waited for SbieSvc.exe to quit (#4462), and missing program icons when paths with spaces were specified in the RunCommand setting (#4416). Additional fixes include template scanning reliability (#4401) and the proper display of credential dialogs for RDP connections in encrypted boxes (#4389).
This update aims to provide a smoother, more reliable experience across supported platforms, particularly for users on ARM64 systems.
For a full list of changes please review the change log.
Download: https://github.com/DavidXanatos/TaskExplorer/releases/tag/v1.6.0
This update introduces significant enhancements, bringing the tool in line with modern requirements by incorporating many previously missing features from SystemInformer. Most notably, this release marks the first version with a fully signed driver, making TaskExplorer ready for professional production use.
Key improvements include expanded security options and enhanced process control features like freezing processes and adjusting efficiency modes. Several panels, including memory, services, modules, and threads, now provide additional columns and insights, while menus have been reorganized for better usability. The config folder has also been relocated to C:Users[User]AppDataLocalXanasoftTaskExplorer for improved integration with other Xanasoft Tools.
Numerous bugs have been resolved, and PHlib has been updated to version 3.2.25011 to ensure stability and compatibility. For a complete list of changes, please refer to the full changelog.
Download (x86 & x64): https://github.com/DavidXanatos/TaskExplorer/releases/download/v1.6.0/TaskExplorer-v1.6.0.exe
This release brings substantial new functionality, user interface enhancements, and critical fixes to improve usability and performance. Users will notice numerous quality-of-life improvements and expanded capabilities for managing secure environments and configurations.
A significant addition in this version is the ability to manage Secure Volumes and Protected Folders more effectively. Users can now add folders directly to the Secure Volumes view for improved organization and rename Secure Volumes or Protected Folders as needed. These features enhance flexibility and streamline folder security workflows.
Several new options have been introduced to improve control and customization. Users can now enable temporary rules, disable trace and access logging, and configure trace/access log limits to suit their specific requirements. Additionally, the tweak info panel offers detailed insights, and centralized signature database management has been implemented. A new signature folder located at C:ProgramDataXanasoftMajorPrivacysig_db allows for user signature creation without altering third-party application directories. Importantly, a signature file in the application folder retains precedence for compatibility purposes.
Rule management has been enriched with several upgrades. The rule creation dialog now includes an auto-name generation feature, a dedicated program picker, and the ability to create process audit rules. These rules monitor processes as though protected but without applying actual protections. Signing capabilities have also been extended, allowing users to sign certificates in addition to files directly from the library view.
The user interface sees significant enhancements, including icons for main panel tabs and the enclave view, along with a new process view-based side panel in the enclave view. Color coding have been added to improve visibility and ease of use across trace, rule, and other views. Access mask columns are now human-readable, and a signature database viewer has been introduced for detailed examination of signatures.
Several critical changes were made to the underlying architecture. Internal path handling has been reworked; as a result, previous versionsâ .dat files are incompatible and will be discarded. Signature files have been renamed to .mpsig, with the format enhanced for future-proofing. Old .sig files are no longer supported. These changes, along with streamlined APIs, ensure better performance and scalability.
Finally, this update resolves several issues. Problems with saving rules in the driver and inconsistencies with tweaks have been addressed, improving reliability and overall system behavior.
This update marks a major step forward in usability, flexibility, and security, and we thank our users for their continued feedback and support.
Download: https://github.com/xanasoft/MajorPrivacy/releases/tag/v0.97.0
This release introduces several significant enhancements and fixes. It includes new features such as an automated cleanup of access and trace logs with a default retention time of 14 days, detection of missing program files in the program tree, and the ability to create custom user-defined program groups. Users can now clear individual trace logs, and clear the ignore list. A secure volume-specific access panel has been added alongside new tools like the Mount Manager Viewer and improved options in the Program Editor Window, including a browse button and icon picker.
Major changes include a complete overhaul of the access tree with a dynamic implementation better suited to user needs, reworking of NT to DOS path resolution, and enhancements to the program tree's column display capabilities. Additionally, and the maintenance menu and program item deletion process have been refined.
Notable fixes address issues such as driver loading conflicts, consistency problems in CTreeItemModel, a crash in CTraceModel, and performance improvements in the *.dat viewer. The update also resolves issues related to service binary path changes and missing patterns for installed Win32 programs.
Download: https://github.com/xanasoft/MajorPrivacy/releases/download/v0.96.2/MajorPrivacy-v0.95.2-BETA.zip
Added
added access tree cleanup, removed all entries refering not longer or never existing reosurces
added option to clear individual trace logs of program items
added option to ignore invalid resource accessa tempts (bad path syntax, etc)
last network activity values are now saved to the programs.dat
program item column counting all accessed files for any program item
added autoamted Access log and trace log cleanup, default retention time is 14 days
added detection of missing program files thay are indicated in gray in the program tree
added clean up option to remove missing program items
added custom user defined program groups
added option to clear teh ignore list
added option to run privacy agent as service
added mount manager viewer
added browse button to program editor window
added icon picker to program editor window
added secure volume specifiv access panel
Changed
replaced the Access tree with a new dynamic implementaion more siutable for the user case
the program tree now can display different column selections for each page
reworked nt to dos path resolution
improved maintenance menu
improved program item deletion
Fixed
improved driver loading added workarounf for outdated driver already being installed
fixed consistency issue in CTreeItemModel
fixed crash in CTraceModel
fixed issue when a service changes its BinaryPath
fixed issue not loading patterns for installed win32 programs
fixed performance issues with *.dat viewer
We are excited to announce the latest updates to Sandboxie Plus 1.15.3, these updates introduce impactful new features, significant improvements, and critical fixes to enhance user experience, customization, and security.
For enhanced security, this release includes a mechanism to restrict access to sandbox folders to the user who created them. Users can also choose to retain or modify Access Control Lists (ACLs) on sandboxed files, providing more flexibility in access management, though this may introduce compatibility issues in some cases. Importantly, this update addresses a security vulnerability documented under CVE-2024-49360.
This release also includes the introduction of a user proxy mechanism, enabling user-specific operations, along with support for the Encrypting File System (EFS). By adding the configuration EnableEFS=y to sandbox settings, users can now utilize EFS within the sandbox environment. The new OpenWPADEndpoint=y option allows access to system proxy configuration, expanding sandbox functionality. Additionally, trace logging filtering has been enhanced, and by enabling LogMessageEvents in global settings, all Sandboxie events can now be logged directly to the Windows Event Log for better tracking and analysis.
Technical improvements in this release include refinements to the startup processes for SandboxieCrypto, ensuring smoother operations. Applications launched via drag-and-drop now consistently use their parent folder as the working directory, improving user experience. Compatibility with Windows build 27749 has been validated to ensure a seamless experience for users. Additionally, crashes affecting Firefox Nightly have been resolved, ensuring better browser compatibility.
We thank our contributors and users for their invaluable feedback and support. Update now to take advantage of the latest features, enhancements, and security improvements in Sandboxie Plus.
Download: https://github.com/sandboxie-plus/Sandboxie/releases/tag/v1.15.3
Added
improved ini section editor, it now supports search Ctrl+F
added SBIE1321 to log all force process events, can be enabled with "NotifyForceProcessEnabled=y", Improves #4113
Changed
improved support notification
Fixed
fixed issues with SSL on ARM64 platform, breaking updater and cert retrieval
We are pleased to announce the release of version 1.15.2 / 5.70.2, introducing significant new features, improvements, and fixes to enhance your experience.
In this release, weâve added several new features to provide more control and customization options for users. You can now set specific MAC addresses and disk serial numbers for individual sandboxes, thanks to the contributions of Yeyixiao.
Users can now open a program in multiple sandboxes simultaneously, offering greater flexibility in managing applications. Additionally, a new âDescriptionâ field has been added to sandbox settings to help organize and document your configurations. For MSI installers, weâve introduced the default-enabled âNotifyMsiInstallerâ option to provide warnings (SBIE2194) when installers require exemptions.
Other notable additions include options to hide installed programs and the system tray icon, enhanced trace logging filtering, and the ability to monitor Sandboxie messages in the Windows Event Log. By enabling âLogMessageEventsâ in the global settings, all Sandboxie events can now be logged directly to the system event log for better tracking and analysis.
This version also addresses several critical issues. We resolved a problem with signing the .tmp file during installation or updates, fixed DLL unloading issues, and corrected file and folder access behavior in resource settings. Improvements have been made to eliminate deadlocks during file renaming and to fix errors when moving files or folders. Additionally, Firefox Nightly crashes caused by Sandboxie have been resolved, ensuring smoother browser compatibility.
Finally, this release includes compatibility validation with Windows build 27749. A minor change ensures that when applications are run via drag-and-drop, their parent folder is used as the working directory for better consistency.
We thank our contributors and users for their valuable feedback and ongoing support. Update now to enjoy the latest improvements and features in Sandboxie Plus!
Download: https://github.com/sandboxie-plus/Sandboxie/releases/tag/v1.15.2
Added
added "NetworkAdapterMAC=0,AA-BB-CC-DD-EE-FF" to set MAC address for each box (thanks Yeyixiao)
added "DiskSerialNumber=DeviceName,1234-ABCD" to set Disk Serial Number for indivdal box (thanks Yeyixiao)
added the ability to hide certificates in editbox in Global Setting (idea by Yeyixiao)
added Opening a program in several sandboxes at once #4231
added "Description" field inside the sandbox settings #4243
added "NotifyMsiInstaller=y" enabled by default to display message SBIE2194 when an MSI installer is run in a box without the recommended exemptions #4330
SBIE2194: MSI installer requires 'MsiInstallerExemptions=y' option to be set in the ini to be able to work correctly, however this option weakens the isolation.
added option to hide installed programs #4139
added Hide Tray Icon #4075
added improved trace logging filtering #4338
added EventLog monitoring for SbieMessages #4113
add 'LogMessageEvents=y' to the global settings to log all sbie events to the system event log
Fixed
fixed Sign the .tmp file that gets dropped when installing or updating Sandboxie Plus #2643Â #4343
fixed issue with DLL unloading
fixed Files Resource Access - Browse for Folder - allows access to excluded folders #4007
fixed "ForceDisableAdminOnly" is weird #4233
fixed deadlock on no op condition when renaming file or folder #4304
fixed Could not move file or folder #4329
"Run Sandboxed" from the quick-previewer should have only one option #4339
Sandboxie causing Firefox Nightly crashes #4183
Changed
validated compatibility with Windows build 27749 and updated DynData
when running via drag and drop now the apps parent folder is used as working dir #4073
The latest release of Major Privacy brings several substantial improvements to enhance user control and monitoring capabilities. Access logs are now saved to disk, offering long term, deeper insight into system operations. Additional features include auto-scrolling for trace logs, and filters within the program view, making it easier to manage and monitor activities effectively. The interface has been enhanced with new layout options and an improved, more intuitive behavior for navigating tree structures, including double-click expand/collapse functionality. Notably, a significant update to the Programs.dat format means older files wonât be compatible with this version. Alongside these new additions, several bug fixes address startup speed, driver compatibility with Windows 10, and minor cleanup issues, ensuring a smoother, faster experience. Major Privacy continues to build on its advanced privacy functions with a refined approach to access control, making it a powerful tool for users seeking robust protection of their personal data.
Download: https://github.com/xanasoft/MajorPrivacy/releases/tag/v0.96.1
Added
access log is now saved to disk
added option to trace registry accesses
added dat fiel viewer
added auto scroll to trace logs
added fitlers to program view
added new window layouts
Changed
improved tree behavioure (double click to expand/colapse all sub branches)
improved access tree behavioure a lot
improved traffic view
changed Programs.dat format
WARNING: the old file will be discarded and not impprted
Fixed
fixed minor issue in driver post op cleanup
fixed driver incompatybility with windows 10
fixed issues with slow startup causing error messages
There is a new build it fixes many issues, especially the memory usage.
Download: https://github.com/xanasoft/MajorPrivacy/releases/tag/v0.96.0
Changelog:
Added
added option to clean up all agent logs
addes view filters and toolbars to variouse lists
Changed
reworked volume rule handling, rules can now be stored in m p s y s file in the volume root itself
such rules can not be altered when the volume is not mounted adding protection against maliciouse modifications
reworked password handoff to imbox to make it more secure
improved mount error handling
improved GUI
improved access logging, allowed operations are now logged from the post op with status
this allows to ignore access atempts to non existing objects (see settings)
improved finder bar
when starting the agent now enums all loaded libraries
Fixed
fixed issues with volume unmounting
fixed issues with driver communication
fixed dnscache related memory leak
fixed a race condition in the process list
This build fixes a couple issues with 1.15.0 and updates compatibility to the latest windows insider build.
Download: https://github.com/sandboxie-plus/Sandboxie/releases/tag/v1.15.1
Fixed
fixed Sandboxie crypto fails to start in red boxes
fixed issue with breakout process when using explorer.exe
Changed
validated compatibility with Windows build 27729 and updated DynData
This build of Sandboxie Plus version 1.15.0 introduces several impactful enhancements, focusing on user-specific operations and security improvements. A notable addition is the new user proxy mechanism, which enables user-specific operations, as well as support for Encrypting File System (EFS) through the user proxy. By adding the configuration 'EnableEFS=y' to the sandbox, users can now leverage EFS within the sandbox environment. Furthermore, a breakout document feature has been implemented, allowing users to specify certain file paths and extensions that can escape the sandbox. However, users are warned to avoid paths terminated with wildcards as they may open up security vulnerabilities, enabling the execution of malicious scripts outside of the sandbox.
In terms of security, a new mechanism has been added to restrict access to box folders, allowing only the user who created the folder to access it by setting 'LockBoxToUser=y'. Additionally, users now have the option to retain the original Access Control Lists (ACLs) on sandboxed files or modify them, providing more flexibility in access management, this may introduce compatibility issues though. Another new feature is the 'OpenWPADEndpoint=y' option, which allows to open system proxy configuration access. On the technical side, improvements have been made to the startup processes for SandboxieCrypto and Sandboxed RPCSS, as well as refinements to the user interface controls.
These updates mark a significant step forward in both the security and functionality of Sandboxie Plus.
Download: https://github.com/sandboxie-plus/Sandboxie/releases/tag/v1.15.0
Added
added new user proxy mechanism to enable user specific operations
added Support for EFS using the user proxy #1980
to enable add 'EnableEFS=y' to the sandbox config
added break out document functionality #2741
use a syntax like this 'BreakoutDocument=C:path*.txt' to specify path and extension
Security Warning: do not use paths terminated with a wild card like 'BreakoutDocument=C:path*' as thay will allow for executeion ot maliciouse scripts outside teh sandbox!!!
added mechanism to set set box folder ACLs to allow only the creating user access 'LockBoxToUser=y'
added option to keep original ACLs on sandboxed files 'UseOriginalACLs=y'
added option 'OpenWPADEndpoint=y' #4292
Fixed
fixed ImDiskApp uninstall key is always written to the registry #4282
Changed
improved SandboxieCrypto startup
improved Sandboxed RPCSS startup
Set tab orders and buddies of UI controls #4300Â (thanks gexgd0419)
In the latest release, version 1.5.6, several key updates and changes were made to improve overall functionality and performance. One of the notable adjustments is that Task Explorer (TE) no longer lists mounted VHD/VHDX files as disks, focusing solely on real hardware. This change aims to streamline disk management and ensure the system resources are utilized more efficiently by disregarding virtual drives. Additionally, the PHlib library has been updated to version 3.1.24258, continuing the effort to maintain compatibility with the latest technology and ensuring smooth operation.
Important Note:
This build has a unsigned driver hence it is required to enable test signign mode to use it
Download:Â https://github.com/DavidXanatos/TaskExplorer/releases/tag/v1.5.6
In this release, we have introduced several new features and improvements that significantly enhance the user experience and provide greater flexibility in system operations. Most notably, users can now effortlessly obtain free 10-day evaluation certificates directly from the support settings page within the UI. These certificates are hardware-locked to the user's machine and allow for up to three requests per hardware ID, making it easier to test and evaluate the system with minimal setup.
Furthermore, new options have been added to increase privacy and security, such as the ability to modify the Windows Product ID in the registry to a random value and to return random values for disk serial numbers and network adapter MAC addresses when queried by applications. These features add an extra layer of obfuscation to protect against unwanted system identification.
Other enhancements include the ability to terminate all processes when Sandman exits, a new option for configuring DropConHostIntegrity directly from the UI, and an improved shared template feature in the New Box Wizard. The number of available shared templates has increased to 10, and the template names can now be easily updated by adjusting the corresponding settings.
In terms of fixes, we have addressed several key issues, including improving the "HideDiskSerialNumber" functionality to prevent application crashes, correcting the format of encrypted proxy passwords, and resolving an issue related to the "NtQueryDirectoryObject" function to avoid easy sandbox detection. These updates contribute to a more stable and secure environment for users.
Download: https://github.com/sandboxie-plus/Sandboxie/releases/tag/v1.14.7
Added
added "RandomRegUID"(bool) which could modify Windows Product Id in the registry to a rand value
added "HideDiskSerialNumber"(bool) return random value when applications tries to get disk serial number
added option to get free 10 days evaluation certificates from the support settings page.
The evaluation certificates are node lcoked to the HwID and for each HwID up to 3 certs can be requested.
added "TerminateWhenExit"(bool,in Sandboxie-Plus.ini) to terminate all processes when Sandman exits for #4171
added a question box to ask for Sandbox Import Location for #4169
added UI option to configure DropConHostIntegrity
added "HideNetworkAdapterMAC"(bool) return random value when applications tries to get network adapter mac address
added shared template selection to the Shared Template feature in the advanced options of the New Box Wizard #4199
The number of available shared templates has been increased to 10
To update the names displayed in the list, simply adjust the "Tmpl.Title" setting within each template
Fixed
This website is a work in progress it will present my Opensource tools that can be found on github:
Sandboxie Plus
Task Explorer
MajorPrivacy
DiskCryptor
You can support my work through donations, any help will be greatly appriciated.
Unlock with Patreon