Skip to main content

Fixed | WSUS 2016 | Error Code 0x8024401c | Windows 10 | Windows Server 2016

Scenario :

Server : Windows WSUS Server 2016
Client : Windows 10, Windows Server 2016

Error Code :  0x8024401c on Windows 10 or Windows Server 2016

Solution :
1) Go to IIS Manager on WSUS Server

2) Goto Advance Settings of  WsusPool.

3) Make sure following settings are present/configured on the Pool, if not change it to below:
Queue Length: 25000
Limit Interval (minutes): 15
"Service Unavailable" Response: TcpLevel
Private Memory Limit (KB): 0

4) Make sure, the WSUS Entry in the Registry is having fully qualified domain name of WSUS Server.


5) Stop the IIS

6) Edit the web.config located at following location on WSUS Server :
C:\Program Files\Update Services\WebServices\ClientWebService\web.config

<httpRuntime maxRequestLength="4096" />
<httpRuntime maxRequestLength="204800" executionTimeout="7200"/>

7) Start the IIS

8) Retry updating clients.


Let me know if it has helped to you.

Source :


  1. Still have the same issue. Problem I see is any new 2016 server gets this error so I think it is related to the client version on the server vs WSUS

  2. Ok I feel bad now as just found the fix (used this back in XP) for all those with similar issues (2016 WSUS server, new clients throwing error: 0x8024401c) try this simple fix:
    Open an elevated CMD Prompt, Type "Netsh" and hit enter, Type "winhttp import proxy source=ie" and hit enter. You should problem is fixed. I used to use this to solve WSUS problems with proxy settings in XP but despite having no proxy on my network this seems to have cured all, hope it helps someone else.

    1. All my Windows 10 1607 and Server 2016 1607 had error 0x8024401c.
      Some IIS Application Pool tuning tips didn't help.
      Adamj's Clean-WSUS PowerShell 3 script running on WSUS Srv solved the problem:

  3. 0x80240fff error windows 10 - The 0x80240fff error windows 10 error is very frustrating. The error prevents you from searching for available updates and prevents you from downloading the latest updates. There are many reasons for the 0x80240fff error possible reasons include firewall errors, connectivity issues, a corrupted file system, window 10 updater has an error, or your system is outdated. There are several ways you can correct the error. You can use the windows updater troubleshooter. You can also try to restart the BITS (Background Intelligent Transfer Service) or try updates after disabling your windows firewalls, or check if the computer system files are corrupt. For more visit:


Post a Comment

Popular posts from this blog

How to backup / Restore Brocade FC Switch Config

Hi All,

Backup of everything is MUST in admins life.

This document will help you to backup or Restore the Brocade Fibre Switch Configuration.

1) Login to switch using Utility like Putty / Kitty.
2) Download Portable FTP Server Utility :
3) Start it and add one user. Give LRW Permissions. (e.g. Shown below)

Create Temp Folder in C:\ and point it

Windows Server 2008 R2 always boots in recovery mode

If you are facing below Issues :
- You faced the Windows Server 2008 R2 Clean boot issue
- Windows Server 2008 R2 starts in recovery mode
- After installing windows updates on Windows server 2008 R2 system goes in recovery mode after reboot
- Safe mode also doesn't work in above case and get stuck at classpnp.sys

Then this is the solution for all above:

1. Boot into Windows Recovery Mode
2. Open Command Prompt
3. Type:


4. Goto following location :

Check out for pending.xml file.
If it is present, then DELETE it.

5. Reboot the system.

6. Select normal boot mode. 

You have done it!