Problems seen with the Monosign AD Password Filter (v2026.11 and later), how to find their cause and how to fix them. Installation and settings: Active Directory Password Filter.
The filter never blocks a password because of a Monosign-side problem: whatever goes wrong below, users can still change their passwords. Only Block weak passwords with a password that breaks the policy refuses a password.
First steps
Open the source's Password Filter tab in Management. The card at the top names the one thing to do now, and each domain controller row shows its status and, under it, the reason of a problem.
On the domain controller, run Check health from Commands for a domain controller (or
monosign-adpf.exe statusinC:\Program Files\Monofor\Monosign AD Password Filter). It prints Healthy, or Unhealthy with the reasons.Look at Activity with Problems only on, or search the user's name.
Logs
File | Content |
|---|---|
| Service log, one file per day, kept 14 days (500 MB at most). Never contains a password. |
| The last health the service computed (what Check health prints). |
Windows Application event log, source | Start, stop and problems of the DLL and the service. |
| Records waiting to reach Monosign (a sync that could not be delivered, a skipped check). They never contain a password. At most 100,000 are kept; above that the oldest are deleted. |
| Records that will not be sent: Monosign refused them, or they cannot be read. They are kept for review and never contain a password. |
Collect for support
Send the output of Check health, the logs folder of the last days, health.json and, when it has files, the outbox\bad folder. Never send secret.bin: it holds the domain controller's connection key.
Read the audit log
Audit | Meaning |
|---|---|
| Monosign recorded the new password. |
| Active Directory accepted a password that never reached Monosign; the detail says why. |
| Active Directory accepted a password without the policy check; the detail says why (for example a timeout). |
| The password failed the policy check (blocked in Enforce, listed as Would reject in Monitor). |
Useful log lines
Line | Meaning |
|---|---|
| Blocked: the user had to choose another password. |
| Monitor: accepted, listed in Activity. |
| A process other than Windows' own lsass tried to use the service; it was refused. |
| The domain controller cannot report to Monosign: check the key (run the install command again) or the Servers page. |
| Monosign refused this synced password and it will not be sent again; the user's audit has the reason. |
| Monosign does not accept the domain controller's key. Nothing is lost yet: the waiting passwords are kept for up to 24 hours and sent once the key works. See Needs attention below. |
| Monosign refused an audit record; it was moved to |
| The domain controller could not reach Monosign for a long time and the oldest waiting audit records were deleted. |
Problems
The Password Filter tab is missing
The source is not on the Active Directory / LDAP User Provider. The filter works with Active Directory sources only.
The tab says the application is missing
The AD Password Filter application is missing. Run the seed (upgrade) first. The v2026.11 database upgrade has not run. Run it, then reload the tab.
The installer stops
Message | Fix |
|---|---|
| The download was changed on the way (often a proxy). Run the command again; if it repeats, use the offline install with |
| A file of the package does not carry Monofor's signature: the download was changed or is incomplete. Download the script and the package again from the Password Filter tab. If it repeats, send the message to support; do not install the files. |
| Seen with Install on every domain controller: the script changed while it was copied to that domain controller. Run the command again; if it repeats, install on that domain controller directly. |
| The Monosign API URL in the command does not start with |
| Nothing was changed on the domain controller (an upgrade restored the previous version). Send the logs to support. |
| Wait for the other run to finish. |
| Close the Services console (and any tool showing services) and run the command again. |
The setup key is refused | The install command is older than 24 hours or was replaced. Press New command under More options and copy it again. |
The domain controller stays at "Reboot"
Windows loads password filters only at startup. Restart the domain controller once; the tab updates by itself. If it still says the DLL is not loaded after the restart, see the next entry.
The filter is not loaded after the restart (LSA protection)
LSA protection (RunAsPPL) is not supported yet. On a domain controller where it is turned on, Windows does not load the filter DLL, and restarting again does not help. Password changes work as usual there, but they are neither checked nor synced.
How to recognise it:
The installer printed
Note: LSA protection (RunAsPPL) is on.Check health says
DLL not loaded, and LSA protection (RunAsPPL) is on: …(older builds say onlyDLL not loaded yet: reboot this domain controller).Event Viewer > Applications and Services Logs > Microsoft > Windows > CodeIntegrity > Operational has event 3033 (or 3063) naming
MonosignADPF.dll: "did not meet the Microsoft signing level requirements".
To check whether LSA protection is on (1 or 2 means on):
(Get-ItemProperty HKLM:\SYSTEM\CurrentControlSet\Control\Lsa -Name RunAsPPL -ErrorAction SilentlyContinue).RunAsPPL
What to do: the filter cannot run on that domain controller for now. Either leave it installed (it does nothing and harms nothing) or run Remove. Do not turn LSA protection off only for the filter without your security team: with Secure Boot the setting is also stored in the firmware and is not undone by changing the registry. Tell support that you need the filter with LSA protection.
The domain controller shows "Not reporting"
No report for 2 minutes: the service is stopped, the domain controller is down, or it cannot reach Monosign over HTTPS. Run Check health on it and check Services for Monosign AD Password Filter. Password changes there are not affected.
The domain controller shows "Needs attention"
The reason is shown under the status. The common ones:
Reason | Fix |
|---|---|
| Run the install command again on that domain controller (no restart needed). |
| In Monosign, check that the AD Password Filter application is enabled and that its permissions were not changed. Then run the install command again on that domain controller (no restart needed). Waiting passwords are kept for up to 24 hours and sent once the key works. |
| The domain controller cannot reach Monosign. Check HTTPS from the domain controller to the Monosign API URL; the records are sent once it can. |
| These audit records will not be sent. Send the |
| The domain controller could not reach Monosign for a long time and more than 100,000 audit records were waiting. Restore the connection to Monosign. The deleted records cannot be recovered; the passwords themselves were accepted by Active Directory as usual. |
| LSA protection is not supported yet; see the entry above. |
| Monosign answered too slowly or not at all. Check Monosign's health, or raise Answer wait under Advanced. |
| The data folder's permissions were changed. Run the install command again. |
"Not installed" rows on the tab
A writable domain controller of the domain has no filter (often a newly added one). A password changed there is neither checked nor synced. Run the install command on it.
A weak password was accepted
Block weak passwords is off (Monitor): Activity shows Would reject (Monitor).
The check was skipped: Activity shows Check skipped (Monosign did not answer within the answer wait).
Many passwords were changed at the same moment (a bulk reset, for example): a domain controller checks up to 64 changes at once, and the extra ones show as Check skipped. Spread bulk resets over time or over several domain controllers.
The user is not in Monosign (Not a Monosign user) or is in Exclusions.
The password was changed on a domain controller without the filter (Not installed), or on one where the filter is not loaded because of LSA protection.
A domain controller overrides the tab in its
config.json(its row says set on this DC).
A password changed in Active Directory is not in Monosign
Check Activity for the user: Not a Monosign user (not synced to Monosign), Several users (more than one Monosign user matches), Sync missed (the detail says why). With Sync passwords to Monosign off, nothing is sent. A stored copy also needs Password Management = By Provider and Keep Password Changes on the source.
The domain controller's row says "Differs from the tab"
The domain controller has not picked up a change saved in the last minute, its config.json sets the value (the row says set on this DC; run monosign-adpf.exe mode default, sync default or timeout default to hand it back), or its version is older than the setting (run Upgrade).
The filter must stop now
Run Pause now on the domain controller: no restart, and it works even when the service cannot start. Resume turns it back on. To take the DLL out of Windows: Remove, restart, Check removal. If the domain controller cannot start normally, remove MonosignADPF from HKLM\SYSTEM\CurrentControlSet\Control\Lsa\Notification Packages and restart, or delete C:\Windows\System32\MonosignADPF.dll in Directory Services Restore Mode.
Useful checks
& "$env:ProgramFiles\Monofor\Monosign AD Password Filter\monosign-adpf.exe" status Get-Service MonosignADPF (Get-ItemProperty HKLM:\SYSTEM\CurrentControlSet\Control\Lsa).'Notification Packages' Test-NetConnection <Monosign API host> -Port 443