MajorPrivacy 0.101.0 introduces detailed usage graphs, smarter firewall rule handling, and support for key files and key slots, alongside substantial performance and stability improvements.
New usage graphs show CPU, GPU and NPU activity, disk I/O, and network traffic for selected programs. Live monitoring is complemented by historical statistics, retained for 30 days by default, making it easier to investigate resource usage over time. Network graphs distinguish internet from LAN traffic and show open connection counts, while interactive zooming and tooltips help identify the programs responsible for activity peaks. Statistics collection, retention, and saving to disk are configurable.
Firewall rule templates now support path patterns, reducing repeated prompts when applications move to new version-specific folders during updates. MajorPrivacy can suggest a pattern based on existing rules and offer to remember your decision as a template. Templates can also handle unauthorized rule changes, including moves between covered paths, while identical rules deleted and recreated by applications such as browsers can be approved automatically. Related changes are grouped into a single prompt, and answering one prompt clears other pending prompts covered by the same decision. A new tray indicator shows the current firewall mode.
An incremental data update mechanism and extensive improvements across the traffic, access, loaded modules, execution, and ingress views reduce unnecessary processing and improve responsiveness. Views preserve their expanded state when the program selection grows, and data files are now written more safely.
This release also fixes important monitoring and firewall issues, including traffic being attributed to the wrong program after process ID reuse, missing TCP transfer rates, duplicate traffic and access counts, and incorrect handling of rejected or recreated firewall rules. Driver fixes address a blue screen triggered by redirected file or named pipe opens and a possible null pointer dereference. Path pattern matching has also been corrected, including cases that could produce false matches or an out-of-bounds read.