⚠️ 3 verified solutions available for Error 4424 — Last updated 2026-03-20
Error 4424 📋

Fix ERROR_SECUREBOOT_POLICY_NOT_SIGNED — Windows Error Code 4424

Error 4424 (ERROR_SECUREBOOT_POLICY_NOT_SIGNED) is a Windows DNS & WINS error that occurs when the secure boot policy is either not signed or is signed by a non-trusted signer.. This guide provides step-by-step solutions to resolve this issue.

🏷️ Code: 4424 📛 ERROR_SECUREBOOT_POLICY_NOT_SIGNED 📅 Updated: 2026-03-20 ⏱️ 3 Solutions
⚡ Quick Fix

Update Root Certificates: Open Command Prompt as Administrator

👇 See all 3 solutions below
🐞 Auto-Fix Script for Error 4424
⚠️ How to use: Open PowerShell as Administrator, paste the code above, and press Enter.
✓ Safe & Transparent ✓ No Downloads Required ✓ Review Before Running
📑 Table of Contents
What is Error 4424? Common Causes Step-by-Step Solutions Prevention Tips Related Errors

💡 What is Error 4424?

Windows System Error Code 4424, known as ERROR_SECUREBOOT_POLICY_NOT_SIGNED, is a DNS & WINS error that occurs during DNS resolution and WINS name resolution. The error indicates that: The Secure Boot policy is either not signed or is signed by a non-trusted signer. When this error is encountered, the Windows operating system was unable to complete the requested operation within the DNS/WINS services subsystem. The error code 4424 is returned by the GetLastError() function and provides developers with a specific identifier to diagnose the root cause of the failure. The symbolic name ERROR_SECUREBOOT_POLICY_NOT_SIGNED maps directly to this numeric code and is commonly referenced in Microsoft documentation, developer forums, and system logs. Understanding this error and its context within DNS resolution and WINS name resolution is essential for effective troubleshooting.

⚠️ Common Causes

  • System date/time is incorrect, causing certificate validation to fail
  • Root certification authorities are outdated or missing
  • TLS protocol mismatch between client and server
  • Antivirus or proxy is intercepting SSL traffic with an untrusted certificate
📚 Comprehensive Guide

Resolving Component Store (WinSxS) Bloat and Corruption

An encyclopedia on the Windows Component Store: safely reclaiming disk space, understanding hard links, and fixing deep WinSxS corruption.

Read the full guide →

✅ Step-by-Step Solutions

1 Update Root Certificates
  1. Open Command Prompt as Administrator
  2. Run: certutil -generateSSTFromWU roots.sst
  3. This downloads the latest root certificates from Microsoft
  4. Open certmgr.msc → Trusted Root Certification Authorities → import roots.sst
  5. Restart your browser and applications
Advertisement
[AdSense In-Article Ad Generator]
Show Advanced Solutions (2 more)
2 Fix System Date and Time
  1. Incorrect system time is the #1 cause of SSL/TLS errors
  2. Right-click the clock in the taskbar → Adjust date/time
  3. Enable 'Set time automatically' and 'Set time zone automatically'
  4. Click 'Sync now' under 'Synchronize your clock'
  5. If time is significantly off, manually set it first, then enable auto-sync
3 Clear SSL State and Cache
  1. Press Win+R, type inetcpl.cpl, press Enter
  2. Go to the Content tab → click 'Clear SSL State'
  3. Go to the Advanced tab → ensure TLS 1.2 and TLS 1.3 are checked
  4. Uncheck SSL 3.0 and TLS 1.0 (outdated and insecure)
  5. Click Apply → OK and restart your browser

🎬 Video Tutorials

▶️ Watch Video Tutorials
How to fix Error 4424 (Secureboot Policy Not Signed)
Open on YouTube →

💻 Diagnostic Command

Run this PowerShell command to find related events in your system log:

Get-EventLog -LogName System -Newest 20 | Where-Object {$_.Message -like "*4424*" -or $_.Message -like "*ERROR_SECUREBOOT_POLICY_NOT_SIGNED*"} | Format-List

💡 Open PowerShell as Administrator, paste the command above, and press Enter.

🛡️ Prevention Tips

  • Keep your system clock synchronized (Settings → Time & Language → Sync now)
  • Install Windows Updates regularly to keep root certificates current
  • Disable SSL inspection in antivirus software if it causes certificate errors
Was this helpful?
Last updated: 2026-03-20
📖
Based on Official Microsoft Documentation
Solutions Tested on Windows 10 & 11
Error codes sourced from Microsoft Win32 SDK. Updated 2026-03-20.
🔧 Diagnose Your Error