Trojan:Win32/Cerdigent.A!dha was the label Microsoft Defender used in a confirmed May 2026 false positive affecting certain DigiCert root certificates. If your affected item is a certificate or rootcert: record, start by updating Defender and checking its action status. If it is a downloaded program, script, archive, or other file, keep it quarantined: the certificate incident does not establish that your file is safe.
For an unknown file or fresh detections after cleanup, use Gridinsoft Anti-Malware to check beyond the item Defender caught. A related payload, bundled app, or startup component may remain after one file is isolated. Download from the official source, update the database, run a Full Scan, review and remove detected threats, then restart when requested. An old history entry alone is not a reason to treat the PC as newly infected.
Check the affected item, time, and action
Open Windows Security → Virus & threat protection → Protection history and expand the Cerdigent event. Record three things before changing anything:
- Affected item: a certificate/rootcert record, an ordinary file path, or a container such as an archive or browser cache.
- Time: the original event date, or a new detection after an update, reboot, download, or application launch.
- Action: quarantined, removed/blocked, action needed, or remediation incomplete. Expand an incomplete-remediation card for its remaining recommended action. [4]
The same detection name can appear in different situations. A certificate record deserves a trust-store check; an unknown executable deserves file containment and a malware scan. A folder such as Temp or AppData is a clue to investigate, not a verdict by itself.

What happened in the DigiCert false-positive incident?
On May 4, 2026, DigiCert confirmed that a Microsoft security-intelligence update had incorrectly flagged certain DigiCert root certificates as Trojan:Win32/Cerdigent.A!dha. DigiCert attributed this to a detection-logic error and said Microsoft had released a corrected signature. Its guidance was to keep Defender fully updated; incorrectly removed certificates were expected to be restored automatically after updating. [2]
That statement concerns a specific certificate incident. It does not mean every later Cerdigent alert, every certificate, or every file signed by DigiCert is harmless. It also should not be confused with the separate April 2026 code-signing-certificate misissuance event discussed in the same notice.
Microsoft’s public entry lists this exact detection but provides no detailed technical behavior. The name alone therefore does not identify a particular stealer, backdoor, or persistence method on your PC. Use the event details to choose the next step. [1]
If Defender flagged a DigiCert/rootcert item
A root certificate belongs to the certificate trust store rather than being a program to launch. When the record fits the reported DigiCert case, use the update-and-recheck route:
- Install current security intelligence. In Windows Security, open Virus & threat protection → Protection updates → Check for updates. Let the update complete before scanning again. Microsoft’s current instructions use this route; an old minimum version from the May incident is not today’s update target. [3]
- Recheck the event. Compare its timestamp and action result with the saved record. A completed old event remaining in the list does not by itself show that the current certificate is still being detected.
- Run an updated scan. Check whether it produces a fresh detection, and whether that item is still the same certificate or is now an ordinary file. Follow any remaining action shown in Windows Security.
- Check any trust problem separately. If applications or sites started reporting certificate errors after the quarantine, confirm whether the affected trust issue is resolved after updating. On a work device, give IT the certificate record, event time, and update result.
DigiCert’s restoration guidance is a reason to update and verify the result, not to import a certificate from a forum or restore every quarantined object. Do not delete root certificates indiscriminately, create broad exclusions, or bypass browser certificate warnings to make an application work. If trust errors continue, use your administrator or official support channel.
If Cerdigent points to a file, use the cleanup route
An alert on an installer, crack, game mod, script, mail attachment, or executable needs its own assessment. The certificate false positive does not explain an unrelated download. Keep that item isolated while you establish its source.

- Stop reopening the source. Do not extract the same archive, run the installer, or restore the DLL to see whether the alert returns. Remove an unwanted source package through normal cleanup when appropriate.
- Run Gridinsoft Anti-Malware’s Full Scan. Install it from the download above, update its database, scan the PC, review the findings and affected paths, and apply the appropriate removal actions.
- Restart and compare fresh findings. If another file is detected, record its path and source rather than assuming every alert belongs to the same infection.
- Investigate persistence only when the evidence calls for it. If genuinely new files or unwanted behavior return, review the related recently installed app, startup entry, scheduled task, service, browser extension, or exclusion. Do not remove everything in a directory or change entries you cannot identify.
If security tools cannot run, use an offline recovery route or specialist help, then return to a full scan once access is restored. If an untrusted program executed and accounts may have been exposed, change important passwords and revoke unfamiliar sessions from a clean device. Cleanup does not recover information already disclosed, and the Cerdigent name alone does not prove account theft.
Why Cerdigent.A!dha may keep coming back
Use the pattern of new events to decide what to investigate. Clearing Protection history is not a cleanup method.
- Same old timestamp, action complete: you may be rereading the original event. Look for a new scan result before escalating recovery.
- New alert after reopening one archive or installer: that source can recreate the detected file. Keep it closed and remove the unwanted source; do not repeatedly restore it.
- New certificate detection after an update: record the certificate details and security-intelligence version and ask IT or official support to review the current event. Do not assume an old incident explains every new certificate alert.
- New file after reboot without reopening the source: run the cleanup scan and correlate the file’s return with the app or startup activity that creates it. This is different from an unchanged quarantined event.
Microsoft documents Protection history as a record of Defender actions, including quarantine and incomplete remediation. Read the action and time together; a threat name displayed in that history is not a live process monitor. [4]
How to review a possible false positive on a legitimate app
For a file from a known developer, preserve its exact release, download source, full affected path, detection date, and any hash already recorded by your security tool. A valid signature is useful context, but neither a familiar publisher nor an unsigned build decides the case by itself.
Ask the developer or IT team to review that exact artifact. If quarantine prevents access, use the event metadata and let the developer examine its own release. Do not restore a blocked file just to hash, inspect, or submit it. For a concrete example of package and DLL identity checks, see the Posilod alert reported in an agent-browser browser package.
For another detection label, use the Microsoft Defender detection reference. Related guides cover Vigorf.A and driver-related alerts and Kepavll!rfn file verification and cleanup. Their names are not interchangeable with Cerdigent.
FAQ
Do I need to reinstall Windows because of a rootcert alert?
A single event matching the confirmed certificate false-positive case does not justify that step. Start with current Defender updates, the action result, and a fresh scan. Escalate based on unresolved trust problems or evidence of an additional infection.
Can a malware scan repair certificate trust automatically?
A malware scan checks for detectable threats. The documented DigiCert fix involved Defender updates and restoration of incorrectly removed certificates. Verify trust recovery separately; do not treat a clean scan as proof that the certificate store is correct.
Is the name Cerdigent or Certigent?
The Microsoft detection is Trojan:Win32/Cerdigent.A!dha. “Certigent” is a spelling seen in discussions, not the exact label to use when recording or reporting this event.
References
- Microsoft. “Trojan:Win32/Cerdigent.A!dha.” Microsoft Security Intelligence; accessed November 4, 2026. Detection entry.
- Lakshmi Hanspal. “Microsoft and code-signing certificates: What to know.” DigiCert, May 4, 2026; accessed November 4, 2026. Certificate false-positive notice.
- Microsoft. “Virus and Threat Protection in the Windows Security App.” Microsoft Support; accessed November 4, 2026. Current protection-update workflow.
- Microsoft. “Protection History in the Windows Security App.” Microsoft Support; accessed November 4, 2026. Quarantine and action states.

