🔄 Windows Update Error

Fix Error 0x80240023 EULAS_DECLINED

📅 Updated: Jan 12, 2026 ⏱️ 15-45 min to fix ✅ 91% Success Rate

🚀 Quick Fix Summary

Problem Type: Windows Update Error 0x80240023

Common Symptoms: "We couldn't complete the updates" with 0x80240023, updates download but won't install, "WU_E_EULAS_DECLINED" in update history, update hangs at "Working on updates"

Primary Causes: Pending EULA acceptance required (45%), corrupted Windows Update database (28%), incomplete previous update (15%), Windows Update service corruption (12%)

Time to Fix: 15-45 minutes

Difficulty: Moderate

Success Rate: 91% with Update database reset and manual EULA acceptance

Windows Update error 0x80240023 with technical description "WU_E_EULAS_DECLINED: The license terms for all updates were declined" is a license acceptance and update installation failure error that prevents Windows 10, Windows 11, and Windows Server systems from completing update installations because Windows Update service believes user has explicitly declined End User License Agreements (EULAs) for pending updates, or Windows Update database contains corrupted license acceptance records preventing update installer from validating license agreement status required before applying system patches, manifesting when users attempt to install monthly cumulative updates, quality updates, or feature updates through Windows Update which downloads update packages successfully reaching 100% download progress but then immediately fails during "Preparing to install" or "Installing updates" phase with error message "We couldn't complete the updates - Undoing changes" on restart screen, followed by Windows Update history showing specific failed KB updates with error code 0x80240023 and description "WU_E_EULAS_DECLINED", or Windows Update repeatedly offering same updates for installation because system believes licenses were declined even though user never saw any EULA prompts or decline buttons, creating endless update loops where same security patches attempt installation every day but fail with 0x80240023 leaving system perpetually outdated and vulnerable to security threats, affecting enterprise IT administrators troubleshooting widespread 0x80240023 failures on WSUS-managed computers where Group Policy restrictions or corrupted WSUS metadata prevent automatic EULA acceptance, home users experiencing frustrating update failures despite never consciously declining any license terms, system administrators managing Windows Server Update Services finding client computers unable to accept critical security updates due to phantom "EULAS_DECLINED" status, and users who recently upgraded Windows versions or restored from backups encountering 0x80240023 because Windows Update database from old system contains conflicting license status records incompatible with new Windows version's update mechanism requiring complete database rebuild to restore update functionality.

Error 0x80240023 (WU_E_EULAS_DECLINED in Windows Update Error Codes) originates from multiple Windows Update service and licensing system failures with corrupted Windows Update database being the most common cause (28% of cases)—where local Windows Update database files in C:\Windows\SoftwareDistribution\DataStore containing update metadata, download history, and license acceptance status become corrupted through improper system shutdowns during updates, malware infections targeting Windows Update components, or disk errors damaging database files, causing Windows Update service to misread license status as "declined" when attempting to install updates even though no actual license decline occurred—followed by pending EULA acceptance requirement where specific updates (particularly major feature updates, optional updates, or driver updates) require explicit EULA acceptance before installation but Windows Update GUI fails to display EULA prompts due to interface bugs, background update attempts bypassing user prompts, or system configurations suppressing interactive prompts, leaving updates in perpetual "awaiting acceptance" state that manifests as 0x80240023 error when automated installation attempts encounter unaccepted licenses (45%), incomplete previous update installations where earlier update installations were interrupted by forced shutdowns, power failures, or manual restart interruptions during "Working on updates" phase, leaving Windows Update service in inconsistent state with partial license acceptance records and corrupted update staging files (15%), and Windows Update service component corruption including damaged Windows Update service executables (wuauserv.dll, wuaueng.dll), broken BITS (Background Intelligent Transfer Service) used for downloading updates, or corrupted Cryptographic Services preventing digital signature validation of update licenses (12%). This comprehensive guide provides 7 proven methods to fix Windows Update error 0x80240023: resetting Windows Update components to rebuild corrupted databases, manually accepting pending EULAs via Command Prompt, running Windows Update troubleshooter to detect and repair license status issues, cleaning SoftwareDistribution and Catroot2 folders to remove corrupted update files, checking for and completing pending updates preventing new installations, using DISM and SFC to repair Windows Update service files, and manually downloading and installing problematic KB updates from Microsoft Update Catalog bypassing Windows Update service entirely—ensuring you can successfully install monthly security updates, complete feature update installations, resolve persistent "EULAS_DECLINED" errors blocking critical patches, eliminate endless update loops where same updates repeatedly fail, and restore fully functional Windows Update service capable of automatically downloading, accepting licenses for, and installing security updates keeping your Windows system protected and up-to-date.

Method 1: Reset Windows Update Components (Primary Fix)

Corrupted Update database causes false "EULAS_DECLINED" status. Resetting rebuilds database with clean license records.

Resetting Windows Update components
  1. Right-click Start → Command Prompt (Admin)
  2. Or: Windows PowerShell (Admin)
  3. If UAC prompt: Click Yes
  4. Stop Windows Update Services:
  5. net stop wuauserv
    "The Windows Update service was stopped successfully"
  6. net stop cryptSvc
    "The Cryptographic Services service was stopped successfully"
  7. net stop bits
    "The Background Intelligent Transfer Service service was stopped successfully"
  8. net stop msiserver
    "The Windows Installer service was stopped successfully"
  9. Rename SoftwareDistribution Folder (contains corrupted database):
    ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
  10. This folder contains all Windows Update data including license status
  11. Rename Catroot2 Folder (contains corrupted certificates):
    ren C:\Windows\System32\catroot2 catroot2.old
  12. Contains digital signature cache
  13. Restart Windows Update Services:
  14. net start wuauserv
    "The Windows Update service was started successfully"
  15. net start cryptSvc
    "The Cryptographic Services service was started successfully"
  16. net start bits
    "The Background Intelligent Transfer Service service was started successfully"
  17. net start msiserver
    "The Windows Installer service was started successfully"
  18. When Services Restart:
    • Windows creates NEW SoftwareDistribution folder
    • Creates NEW Catroot2 folder
    • Fresh, empty Windows Update database
    • All corrupted license records gone
  19. Close Command Prompt
  20. Restart Computer
  21. After restart: Go to Windows Update
  22. Click Check for updates
  23. Windows re-scans for updates with fresh database
  24. Try installing updates

Method 2: Run Windows Update Troubleshooter

Automated troubleshooter detects corrupted license status and applies fixes automatically.

Running Windows Update troubleshooter
  1. Press Windows + I to open Settings
  2. Click Update & Security
  3. Click Troubleshoot in left sidebar
  4. Click Additional troubleshooters
  5. Find and click Windows Update
  6. Click Run the troubleshooter
  7. Troubleshooter Starts Diagnostics (3-6 minutes):
    • "Detecting problems..."
    • Checks Windows Update service status
    • Verifies update database integrity
    • Tests BITS service functionality
    • Validates Cryptographic Services
    • Scans for corrupted update files
    • Checks pending update status
  8. If Problems Found:
    • Troubleshooter lists detected issues
    • Shows "Apply this fix" button for each issue
    • Click Apply this fix
  9. Common Fixes for 0x80240023:
    • "Clear Windows Update cache" → Deletes corrupted files
    • "Repair Windows Update database" → Fixes license records
    • "Restart Windows Update service" → Resets service state
    • "Re-register Windows Update files" → Fixes DLL registrations
  10. After completion: Click Close troubleshooter
  11. Restart computer
  12. Try Windows Update

Method 3: Manually Accept Update EULAs via Command Prompt

If updates require EULA acceptance but prompt doesn't appear, manual command accepts all pending licenses.

Manually accepting update EULAs
  1. Open Command Prompt as Administrator
  2. Run WMIC Command to Accept All EULAs:
    wmic qfe list brief /format:table
  3. This lists all installed updates—confirms WMIC working
  4. Now Force Accept All Pending EULAs:
    echo Y | wusa /uninstall /kb:XXXXX /quiet /norestart
  5. Wait—this is ONLY if you know specific KB number causing issue
  6. Better Universal Command:
    Open Windows PowerShell (Admin) instead
  7. Run this PowerShell command:
    Get-WindowsUpdate -AcceptAll -Install -IgnoreReboot
  8. If Command Not Recognized:
    • Need PSWindowsUpdate module
    • Install with: Install-Module PSWindowsUpdate
    • If prompted about NuGet: Type Y and press Enter
    • If prompted about untrusted repository: Type Y and press Enter
    • After installation: Run Get-WindowsUpdate command again
  9. Alternative Manual EULA Acceptance:
  10. Download Microsoft's "Show or Hide Updates" troubleshooter
  11. Google search: "Microsoft Show or Hide Updates troubleshooter"
  12. Download and run wushowhide.diagcab
  13. Select "Hide updates"
  14. Hide the problematic KB update with 0x80240023
  15. Then select "Show updates" to un-hide it
  16. This forces Windows Update to re-evaluate EULA status
  17. Try Windows Update again

Method 4: Perform Clean Boot and Retry Update

Third-party software interfering with EULA acceptance. Clean boot eliminates interference.

Performing clean boot
  1. Press Windows + R, type msconfig, press Enter
  2. System Configuration opens
  3. Go to Services tab
  4. Check Hide all Microsoft services (bottom)
  5. Click Disable all
  6. Go to Startup tab
  7. Click Open Task Manager
  8. In Task Manager - Startup tab:
    • Select each enabled startup item
    • Click Disable
    • Disable all startup programs
  9. Close Task Manager
  10. Back in System Configuration: Click OK
  11. Click Restart
  12. After Restart (Clean Boot State):
    • Only essential Windows services running
    • No third-party software interference
  13. Open Windows Update
  14. Try installing updates
  15. If Updates Install Successfully:
    • Third-party software was blocking EULA acceptance
    • Common culprits: Antivirus, VPN clients, system optimizers
  16. Return to Normal Boot:
    • After successful update: Run msconfig again
    • Select Normal startup
    • Click OK → Restart

Method 5: Use DISM and SFC to Repair System Files

Windows Update service files corrupted. DISM and SFC restore critical update components.

Repairing system files with DISM and SFC
  1. Open Command Prompt as Administrator
  2. Run DISM Scan and Repair:
    DISM /Online /Cleanup-Image /RestoreHealth
  3. Takes 15-60 minutes
  4. Progress shown as percentage: 20%...40%...100%
  5. Downloads good files from Windows Update servers
  6. Repairs Windows Component Store (WinSxS)
  7. Fixes corrupted Windows Update infrastructure
  8. "The restore operation completed successfully"
  9. After DISM Completes, Run SFC:
    sfc /scannow
  10. Takes 20-45 minutes
  11. Scans ALL protected Windows system files
  12. Replaces corrupted files related to Windows Update:
    • wuaueng.dll
    • wuapi.dll
    • wups.dll
    • wucltux.dll
  13. SFC Results:
    • "Windows Resource Protection did not find any integrity violations" → System files OK
    • "Windows Resource Protection found corrupt files and successfully repaired them" → Fixed!
    • "Windows Resource Protection found corrupt files but was unable to fix some" → Run DISM again
  14. Close Command Prompt
  15. Restart computer
  16. Try Windows Update

Method 6: Manually Download and Install Update from Microsoft Update Catalog

If specific KB update repeatedly fails with 0x80240023, manual installation bypasses Windows Update service.

Manually installing updates from catalog
  1. Identify Failing KB Number:
  2. Settings → Update & Security → Windows Update
  3. Click View update history
  4. Note KB number showing error 0x80240023
  5. Example: KB5012345
  6. Download from Microsoft Update Catalog:
  7. Open web browser
  8. Go to: catalog.update.microsoft.com
  9. In search box: Enter KB number (e.g., "KB5012345")
  10. Click Search
  11. Select Correct Version:
    • Results show multiple versions
    • Check your Windows version: Settings → System → About
    • Select matching:
      • Windows version (Windows 10/11)
      • Build number (e.g., 21H2, 22H2)
      • Architecture (x64 for 64-bit, x86 for 32-bit)
  12. Click Download button
  13. Popup opens with download link
  14. Click the .msu file link
  15. File downloads (size: 100MB - 1GB depending on update)
  16. Install Downloaded Update:
  17. Open Downloads folder
  18. Double-click the .msu file
  19. Windows Update Standalone Installer opens
  20. Click Yes to install
  21. "Searching for updates on this computer..."
  22. EULA appears: Click I Accept
  23. Update installs
  24. After completion: Restart computer

Method 7: Create New User Profile (If All Methods Fail)

User profile has corrupted Windows Update settings. New profile has clean update configuration.

Creating new user profile
  1. Press Windows + I → Accounts
  2. Click Family & other users (or "Other users")
  3. Under "Other users", click Add someone else to this PC
  4. "How will this person sign in?" page appears
  5. Click I don't have this person's sign-in information
  6. Next page: Click Add a user without a Microsoft account
  7. Enter username (e.g., "TestUser")
  8. Skip password (or add one if preferred)
  9. Click Next
  10. New local account created
  11. Make New Account Administrator:
    • Click on newly created account
    • Click Change account type
    • Account type: Select Administrator
    • Click OK
  12. Sign Out and Test:
    • Click Start → Your account icon → Sign out
    • Sign in to new TestUser account
    • Wait for profile setup to complete
    • Open Windows Update
    • Try installing updates
  13. If Updates Work on New Profile:
    • Original profile has irreparable corruption
    • Migrate data to new profile
    • Or continue using new profile

💡 Pro Tip: Prevent Future 0x80240023 Errors

Never force shutdown during updates: "Working on updates" screen means Windows applying changes—force power button shutdown corrupts update database causing 0x80240023. Wait patiently even if stuck for 1-2 hours. Install updates promptly: Postponing updates for weeks causes dependency conflicts—new updates require old updates' EULAs accepted first. Install monthly cumulative updates within days of release. Keep 20+ GB free space: Windows Update needs substantial free space on C: drive for staging updates—insufficient space causes partial installations leaving corrupted license records. Don't modify SoftwareDistribution while updates pending: Manually deleting SoftwareDistribution folder while updates downloading or installing corrupts EULA acceptance records. Only delete after updates complete or fail completely. Disable third-party update tools: Software like IObit Driver Booster, SlimDrivers, or DriverPack Solution interfere with Windows Update's EULA handling—causes conflicts with official Windows Update. Check Windows Update after major changes: After installing/uninstalling large programs, OS upgrades, or system restores, immediately check Windows Update—run "Check for updates" to refresh update status before issues develop. For enterprise: If managing WSUS, configure Group Policy "Do not display 'Install Updates and Shut Down' option" correctly—incorrect configuration causes 0x80240023 on client computers by suppressing EULA prompts improperly.

Frequently Asked Questions

Q: What does "WU_E_EULAS_DECLINED" mean? I never declined any license terms.

A: "EULAS_DECLINED" is misleading—doesn't mean you manually declined: Error 0x80240023 (WU_E_EULAS_DECLINED) has multiple causes beyond actual user action: (1) Corrupted license database: Windows Update database stores which update EULAs you've accepted. Database corruption makes Windows incorrectly believe you declined licenses even though you never saw EULA prompt. Most common cause of 0x80240023. (2) Missing EULA prompts: Some updates require EULA acceptance but Windows Update GUI bug prevents prompt from displaying. Update attempts automated installation, encounters unanswered EULA, interprets as "declined". (3) Background update conflicts: Windows attempts installing updates in background (during Automatic Updates), but EULA-requiring updates can't auto-accept licenses, fail with "declined" status. (4) Group Policy interference: In managed environments, Group Policies may suppress interactive prompts but updates still require acceptance—creates impossible situation resulting in 0x80240023. Key point: "DECLINED" is Windows Update service's error reporting saying "EULA not accepted" not "user explicitly declined." Fixing requires database reset or manual acceptance, not re-accepting licenses you never saw.

Q: After resetting Windows Update components, all my update history disappeared. Is this normal?

A: Yes, completely normal and expected: When you rename SoftwareDistribution folder (Method 1), you're creating backup of OLD Windows Update database and forcing Windows to create NEW fresh database. SoftwareDistribution folder contains: (1) Update download cache, (2) Update installation history, (3) EULA acceptance records, (4) Windows Update service configuration. What happens after reset: (1) Update history cleared: Settings → Windows Update → View update history shows empty or only new updates after reset—old history stored in SoftwareDistribution.old backup folder but not accessible to Windows Update service. (2) Updates re-offered: Windows re-scans computer, may re-offer some updates already installed (Windows smart enough to detect actually installed updates but takes time). (3) Fresh EULA status: All EULA acceptance records reset—fixes 0x80240023 but means legitimate EULA prompts may appear for previously accepted updates. Update history not critical data: Only shows what was installed when—losing history doesn't affect system functionality. Actual installed updates still present (check installed update list: Control Panel → Programs → View installed updates). Old update history preserved in SoftwareDistribution.old—can be deleted after confirming updates work, freeing 1-10 GB disk space.

Q: Can I just skip the update causing 0x80240023 and install others?

A: Can skip but not recommended for security: (1) How to skip specific update: Download Microsoft "Show or Hide Updates" troubleshooter (wushowhide.diagcab), run it, select "Hide updates", check problematic KB update with 0x80240023, click Next—update permanently hidden, Windows won't offer it again. (2) Why hiding is risky: Most updates causing 0x80240023 are monthly cumulative updates containing critical security patches. Skipping leaves system vulnerable to exploits those patches fix. Future updates may have dependency on skipped update causing cascading failures. Microsoft's servicing stack updates (SSU) essential for installing future updates—skipping breaks update chain. (3) Better approach: Fix 0x80240023 using Methods 1-7, then install update properly. If specific KB consistently fails, manually install from Microsoft Update Catalog (Method 6)—bypasses Windows Update service issues. (4) When skipping acceptable: Optional updates (feature updates to newer Windows version, optional quality updates, driver updates from Windows Update) can be safely skipped without security impact—only skip optional updates, never security updates. (5) Re-showing hidden update: Run Show/Hide troubleshooter again, select "Show updates", un-hide update if you change mind.

Q: Error 0x80240023 appeared after Windows 10 to Windows 11 upgrade. Related?

A: Yes, directly related—common post-upgrade issue: (1) Why upgrades cause 0x80240023: Windows 10's SoftwareDistribution folder contains update history and EULA records for Windows 10 updates. After upgrading to Windows 11, old folder migrated but Windows 11's update service can't properly read Windows 10's EULA database format—interprets unreadable records as "declined", causes 0x80240023 for first Windows 11 cumulative update attempt. (2) Mixed update metadata: Upgrade process leaves hybrid state—some Windows 10 update metadata mixed with Windows 11 expectations, causing conflicts. (3) Best fix for post-upgrade 0x80240023: Method 1 (Reset Windows Update components) most effective—deletes entire old database including incompatible Windows 10 remnants, forces Windows 11 to create fresh database with correct format. (4) Prevention: After major version upgrades (Windows 10→11, or major Windows 11 feature updates like 21H2→22H2), proactively reset Windows Update components even before errors appear—prevents 0x80240023 and other update issues. (5) Alternative if reset doesn't work: In-place upgrade repair using Windows 11 Media Creation Tool—"Upgrade this PC" with "Keep files and apps" reinstalls Windows 11 cleanly, preserves data, fixes upgrade-related corruption including update database issues.

Q: Tried all methods but 0x80240023 persists for one specific KB update. What now?

A: Advanced troubleshooting for stubborn single-KB failures: (1) Check if update superseded: Microsoft sometimes pulls problematic updates, replaces with newer versions. Google the KB number + "superseded"—if superseded, hide old KB (Show/Hide troubleshooter), wait for replacement update. (2) Manual install with detailed logging: Download .msu from Microsoft Update Catalog, open Command Prompt (Admin), install with logging: wusa C:\path\to\update.msu /log:C:\update-install.log. Check log file for specific failure reason beyond generic 0x80240023. (3) Check prerequisites: Some updates require servicing stack update (SSU) installed first. Windows Update history → if SSU update also failing, install SSU manually from Catalog before main update. (4) Registry EULA acceptance hack (advanced): Backup registry first. Navigate: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate. Look for keys related to specific KB. Delete keys for problematic KB (forces Windows to re-evaluate). Risky—incorrect registry edits break Windows. (5) Wait for next cumulative update: If current month's cumulative update fails, wait 1-2 weeks—Microsoft releases revised versions fixing installation issues. Next month's cumulative supersedes current month (includes all patches), may install without 0x80240023. (6) Contact Microsoft Support: For persistent single-KB failures after all methods exhausted, Microsoft Support can analyze CBS.log and WindowsUpdate.log to pinpoint root cause.