[SOLVED] Error 0x80244019 in Windows 10 while running check for updates

AjeetYadav

Member
Joined
Aug 7, 2021
Posts
7
While running check for updates in one Windows 10 PC I am getting error "0x80244019- There was a problem downloading some updates, but we will try again later"

I am trying to install August Windows Updates from my WSUS server.
 
Last edited:
Hello.

If you are still getting this error, try these two methods for a start:

Method 1:

Run the Windows Update Troubleshooter and check if it resolves the issue.

  1. Press Windows + X keys on the keyboard and select Control Panel
  2. Type Troubleshooting in the search bar on the Control Panel.
  3. Click on System and security under Troubleshoot computer problems.
  4. Click on Windows Update under Windows.
  5. Click on Advanced on the Windows update dialog box and click on Run as administrator (Enter the credentials if required).
  6. Click on Next and follow onscreen instruction complete the Windows Update troubleshooter.
If the issue still persist, follow the below method.


Method 2:


I would suggest you to manually reset the Windows Updates Components, restart the computer and check if that helps.

a) Press Windows Key + X on the keyboard and then select “Command Prompt (Admin)” from the menu.

b) Stop the BITS, Cryptographic, MSI Installer and the Windows Update Services. To do this, type the following commands at a command prompt. Press the “ENTER” key after you type each command.

net stop wuauserv

net stop cryptSvc

net stop bits

net stop msiserver


c) Now rename the SoftwareDistribution and Catroot2 folder. You can do this by typing the following commands in the Command Prompt. Press the “ENTER” key after you type each command.

ren C:\Windows\SoftwareDistribution SoftwareDistribution.old

ren C:\Windows\System32\catroot2 Catroot2.old


d) Now, let’s restart the BITS, Cryptographic, MSI Installer and the Windows Update Services. Type the following commands in the Command Prompt for this. Press the ENTER key after you type each command.

net start wuauserv

net start cryptSvc

net start bits

net start msiserver


e) Type Exit in the Command Prompt to close it.


Now you may try running the Windows Updates and check if the above steps resolve the issue.
 
Hello.

If you are still getting this error, try these two methods for a start:

Method 1:

Run the Windows Update Troubleshooter and check if it resolves the issue.

  1. Press Windows + X keys on the keyboard and select Control Panel
  2. Type Troubleshooting in the search bar on the Control Panel.
  3. Click on System and security under Troubleshoot computer problems.
  4. Click on Windows Update under Windows.
  5. Click on Advanced on the Windows update dialog box and click on Run as administrator (Enter the credentials if required).
  6. Click on Next and follow onscreen instruction complete the Windows Update troubleshooter.
If the issue still persist, follow the below method.


Method 2:


I would suggest you to manually reset the Windows Updates Components, restart the computer and check if that helps.

a) Press Windows Key + X on the keyboard and then select “Command Prompt (Admin)” from the menu.

b) Stop the BITS, Cryptographic, MSI Installer and the Windows Update Services. To do this, type the following commands at a command prompt. Press the “ENTER” key after you type each command.

net stop wuauserv

net stop cryptSvc

net stop bits

net stop msiserver


c) Now rename the SoftwareDistribution and Catroot2 folder. You can do this by typing the following commands in the Command Prompt. Press the “ENTER” key after you type each command.

ren C:\Windows\SoftwareDistribution SoftwareDistribution.old

ren C:\Windows\System32\catroot2 Catroot2.old


d) Now, let’s restart the BITS, Cryptographic, MSI Installer and the Windows Update Services. Type the following commands in the Command Prompt for this. Press the ENTER key after you type each command.

net start wuauserv

net start cryptSvc

net start bits

net start msiserver


e) Type Exit in the Command Prompt to close it.


Now you may try running the Windows Updates and check if the above steps resolve the issue.
Thanks, I tried this prior to your response and it helped but the actual problem was related to WSUS registry setting manged by my organizations AD server. User was trying to change the WSUS server path in PCs registry settings manually and each time AD policy was updated the server was pusing the values of the old server. This was causing the issue.
I got the settings in AD policy changed from AD server end and the issue got resolved.
 
hi,,

anyone have the any solution for this that we are user WSUS Win16 server for windows 10 clients for MS patching & update for all win 10 ver as 1507,1611,1703,1709,1803,1809,1903,1909,2004,20H2 & 21h1. but now after UPGRADE THE CLIENT SYSTEMS older OS built Ver to 20H2 & 21H1. its built version showing same as previous OS built in WSUS Console. as discussed with MS social tech team, according to them in WSUS console it showing the windows update client ver. not OS built ver. but now we have problem that we have more than 3000+ systems in our domain. ground team is upgrading Old outdate OS ver to new 20H2 & 21h1 OS Ver. now it difficult to us determine the actual OS version on Client system to Move the systems in OS built group in WSUS server. have you any resolution please.
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top