⚠️ 3 verified solutions available for Error 13930 — Last updated 2026-03-12
Error 13930 📋

Fix ERROR_IPSEC_DOSP_KEYMOD_NOT_ALLOWED — Windows Error Code 13930

Error 13930 (ERROR_IPSEC_DOSP_KEYMOD_NOT_ALLOWED) is a Windows Internet & WinHTTP error that occurs when ipsec dos protection received an ipsec negotiation packet for a keying module which is not allowed by policy.. This guide provides step-by-step solutions to resolve this issue.

🏷️ Code: 13930 📛 ERROR_IPSEC_DOSP_KEYMOD_NOT_ALLOWED 📅 Updated: 2026-03-12 ⏱️ 3 Solutions
⚡ Quick Fix

Take Ownership of the Resource: Open Command Prompt as Administrator

👇 See all 3 solutions below
🐞 Auto-Fix Script for Error 13930
⚠️ 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 13930? Common Causes Step-by-Step Solutions Prevention Tips Related Errors

💡 What is Error 13930?

Windows System Error Code 13930, known as ERROR_IPSEC_DOSP_KEYMOD_NOT_ALLOWED, is a Internet & WinHTTP error that occurs during WinHTTP, WinInet, and internet protocols. The error indicates that: IPsec DoS Protection received an IPsec negotiation packet for a keying module which is not allowed by policy. When this error is encountered, the Windows operating system was unable to complete the requested operation within the internet services subsystem. The error code 13930 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_IPSEC_DOSP_KEYMOD_NOT_ALLOWED 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 WinHTTP, WinInet, and internet protocols is essential for effective troubleshooting.

⚠️ Common Causes

  • Your user account lacks NTFS permissions on the target file or folder
  • User Account Control (UAC) is blocking the operation
  • The file is owned by SYSTEM or TrustedInstaller and requires ownership transfer
  • Group Policy or antivirus software is restricting access
📚 Comprehensive Guide

Troubleshooting COM and DCOM Architectural Failures (Event ID 10016)

A comprehensive guide on Component Object Model (COM), Distributed COM (DCOM), and how to safely interpret and resolve Event ID 10016 errors.

Read the full guide →

✅ Step-by-Step Solutions

1 Take Ownership of the Resource
  1. Open Command Prompt as Administrator
  2. Run: takeown /f "C:\path\to\file" /r /d y
  3. Then run: icacls "C:\path\to\file" /grant %username%:F /t
  4. Replace the path with the actual file or folder causing Error 13930 (ERROR_IPSEC_DOSP_KEYMOD_NOT_ALLOWED)
  5. Retry the operation that triggered Error 13930 (ERROR_IPSEC_DOSP_KEYMOD_NOT_ALLOWED)
Advertisement
[AdSense In-Article Ad Generator]
Show Advanced Solutions (2 more)
2 Disable UAC Temporarily for Testing
  1. Press Win+R, type msconfig, press Enter
  2. Go to Tools tab → find 'Change UAC Settings' → click Launch
  3. Move the slider down to 'Never Notify' (temporarily for diagnosis only)
  4. Restart your computer and test if Error 13930 (ERROR_IPSEC_DOSP_KEYMOD_NOT_ALLOWED) persists
  5. IMPORTANT: Re-enable UAC after testing for security
3 Check and Reset NTFS Permissions
  1. Right-click the affected file/folder → Properties → Security tab
  2. Click Advanced → Owner tab → Change owner to your account
  3. Check 'Replace all child object permissions'
  4. Click Apply, then re-grant Full Control to your user account

🎬 Video Tutorials

▶️ Watch Video Tutorials
How to fix Error 13930 (Ipsec Dosp Keymod Not Allowed)
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 "*13930*" -or $_.Message -like "*ERROR_IPSEC_DOSP_KEYMOD_NOT_ALLOWED*"} | Format-List

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

🛡️ Prevention Tips

  • Avoid modifying files in C:\Windows\System32 unless absolutely necessary
  • Use 'Run as Administrator' when performing system-level operations
  • Keep a backup admin account in case your primary account gets locked
Was this helpful?
Last updated: 2026-03-12
📖
Based on Official Microsoft Documentation
Solutions Tested on Windows 10 & 11
Error codes sourced from Microsoft Win32 SDK. Updated 2026-03-12.
🔧 Diagnose Your Error