Problems with .NET Framework and Certificate of Authorization

Hi, First, treat the two problems as likely related by an automated repair or third‑party process reverting Windows Features and removing the certificate; check Task Scheduler, startup scripts, and any management agent or update tool that could toggle the .NET Framework feature or remove certificates. On the .NET side, verify Windows Features shows .NET Framework 4.8.1 enabled, then run an offline repair sequence: use DISM to restore component store health and sfc to repair system files, then confirm Windows Update history for any package that may be rolling back the component.

Inspect the event logs (Application and System) for sources like MsiInstaller, TrustedInstaller, or UpdateAgent that coincide with the time .NET reverts, and temporarily disable any third‑party installers or maintenance utilities during your test.

If a vendor installer for CCURE or a companion product is downgrading .NET, capture its installer logs and coordinate with the vendor to obtain a compatible build. For the Certificate of Authorization issue, audit the local and machine certificate stores for recent deletions and enable object access auditing on the Certificates registry keys to capture the deleting process in the Security event log.

Check IIS and the Victor web service application pool identity, confirm the certificate’s private key permissions grant read access to the service account, and export the certificate with private key to a secure backup so you can quickly re-import if it disappears. Review CCURE and Victor logs for any automation that reconfigures SSL bindings or reinstalls connectors; ensure no startup script or deployment package resets bindings at service start.

As an immediate mitigation, place a read‑only ACL on the certificate private key for the SYSTEM account only after confirming the service account still has access, and maintain a scheduled script that checks and rebinds the certificate automatically if missing.

Finally, run a controlled pilot: enable verbose logging, reproduce the issue, capture timestamps, and escalate to vendor support for CCURE/Victor with the collected logs if the root cause appears inside their components.

If this helps, please hit “accept answer”

Best regards, VP

Hi Benjamin Smith,

Have you tackled the problem yet? If you have, please accept the answer so that others can benefit too. If not, please let me know if I can assist further :)

Vivian