Patch Version 25.12.2 Released - Privilege Secure

[hano.grimm]

Want the full details? Click the link below!

Download Privilege Secure 25.12.2 here!

UI Refresh and Visual Improvements

Privilege Secure has been rebranded to align with the new Netwrix visual identity. The update delivers a cleaner, more modern interface with refreshed colors, typography, and iconography that match the broader Netwrix portfolio. This isn’t just a coat of paint - it creates a more consistent, recognizable experience across Netwrix products. Same capabilities, clearer branding, and a UI that’s fully aligned with the Netwrix platform.

Bug Fixes

The latest Hotfix, version 25.12.2 of Netwrix Privilege Secure, is now available, addressing the issue detailed below.

ID	Description
411913	Improved stability when calling built-in PowerShell scripts
412894	Resolved Active Login and Session Cancelled/Completed not appearing in SIEM events for certain activities
413510	Added stability to backend Quartz concurrency

Known Issues

ID	Description
410813	RDP sessions may have issues related to extending sessions, recording keystrokes, and viewing the mouse cursor when both the client and destination are a combination of Windows 11 and Windows Server 2025.
401699	NPS servers that don’t use a trusted certificate need to re-add ‘InsecureSkipVerify’ to Host Scan Service’s ‘appsettings.user.json’ after upgrading
410722	Error duplicate key value violates unique constraint “PK_host_user_group_join”

Need help with this update?

There are many different ways to get help with our products!

Situation	Action
If you feel the product is broken and not working as intended…	Contact Support
If you have a question you’d like to ask other experts…	Create a discussion in the community: Privilege Secure > Discussions & Questions
If you have a feature request…	Let our product team know directly: Privilege Secure > Ideas
If you have something cool to show…	Show everyone what you built: Privilege Secure > Show & Tell

What are your thoughts?

We are always happy to hear from our users on what you like, and what you hope to see in the future. Please, share your thoughts below!

[markd (Mark)]

We have a separate database (2 web servers and 1 (postgres) database) setup. Is there something in the release notes to indicate when the update would need to be applied to the database server as well?

[dpiazza (Dan Piazza)]

Hi Mark,

Our installer will automatically apply necessary database migrations and schema changes to the database that’s connected in NPS.DbCfg.exe, which can be found by default in: C:\Program Files\Stealthbits\PAM\DatabaseConfig\DatabaseConfigUI

[markd (Mark)]

OK - so only an update to the Postgres version (which would likely be called out as part of the update communication) would require an update directly on the database server?

[dpiazza (Dan Piazza)]

When we increment PostgreSQL’s versions it will be called out in the release notes. The installer will also alert you to that and walk you through the process. Nothing manual needs to be done outside of the installer.

[adam.sneed (Adam Lacroix Sneed)]

While not 0% risk, we do recommend applying hot fixes and security patches within Pgsl major version to your PostgreSQL server. Because no updates are without risk make sure you’ve backed up your database before hand. And we do NOT support major psql version upgrades outside of our installer…only minor version bumps (HF’s and patches) will be supported.