SCCM 2007 Error code 0x8024000B

Error Code
Error message when you try to install updates from the Windows Update or Microsoft Update Web site: "0x8024000B"


Cause


When you try to install updates by using the Windows Update or Microsoft Update Web site, you may receive the following error message:
0x8024000B


This problem may occur if Windows Update or Microsoft Update cannot read the update manifest.


Soluion


To resolve this problem, rename the Spupdsvc.exe file, and then try to install the updates again. To do this, follow these steps:
Click Start, and then click Run.
Copy the following text, paste it into the Run box, and then click OK or press ENTER:
Cmd /c ren %WinDir%\System32\Spupdsvc.exe Spupdsvc.old
Try to install the updates again. If you still cannot install the updates, see the "References" section for information about how to contact Windows Update support or Microsoft Update support.

Comments

  1. AnonymousJanuary 29, 2014 at 8:44 AM

    There is no Spupdsvc file in that location

    ReplyDelete
  2. akhilapriya404October 11, 2018 at 5:20 AM

    The information which you have provided is very good. It is very useful who is looking for MSBI online training Hyderabad

    ReplyDelete
  3. akhilapriya404October 11, 2018 at 5:20 AM

    The information which you have provided is very good. It is very useful who is looking for MSBI online training Hyderabad

    ReplyDelete
  4. EmilySeptember 25, 2023 at 5:49 AM

    SCCM 2007 error code 0x8024000b can be perplexing, but this guide offers practical steps to address it. PVP Game Modes Understanding and troubleshooting such issues is crucial for effective system management by following instructions.

    ReplyDelete

Post a Comment

Popular posts from this blog

SCCM Software updates error WUAHandler.log errors

If you find errors in the WUAHandler.log as below "OnSearchComplete - Failed to end Search job. Error = 0x80072efd Scan failed with error = 0x80072efd" Error 0x80072efd means: 'The attempt to connect to the server failed. Can you check the following logs for more information "%Windir%\WindowsUpdate.log and ScanAgent.log Server not being able to talk to the WSUS server because port 8530 might be blocked lack of  communication  between the client and the SCCM sup if you are working with custom WSUS ports. Do not forget to open the used ports in the Windows Firewall Create a rule for inbound TCP (WSUS ports). In my case it was for 8530 and 8531. 
Read more

ConfigMgr 2012+ Version Numbers

Release Version Build Baseline D/L Link Our Guides SCCM 2012 RTM 5.00.7711.0000 7711 N/A N/A N/A SCCM 2012 RTM - CU1 5.00.7711.0200 7711 N/A KB2717295 N/A SCCM 2012 RTM - CU2 5.00.7711.0301 7711 N/A KB2780664 N/A SCCM 2012 SP1 5.00.7804.1000 7804 N/A N/A N/A SCCM 2012 SP1 - CU1 5.00.7804.1202 7804 N/A KB2817245 N/A SCCM 2012 SP1 - CU2 5.00.7804.1300 7804 N/A KB2854009 N/A SCCM 2012 SP1 - CU3 5.00.7804.1400 7804 N/A KB2882125 N/A SCCM 2012 SP1 - CU4 5.00.7804.1500 7804 N/A KB2922875 N/A SCCM 2012 SP1 - CU5 5.00.7804.1600 7804 N/A KB2978017 N/A SCCM 2012 R2 5.00.7958.1000 7958 N/A N/A Installation guide SCCM 2012 R2 - CU1 5.00.7958.1203 7958 N/A KB2938441 N/A SCCM 2012 R2 - CU2 5.00.7958.1303 7958 N/A KB2970177 Upgrade guide SCCM 2012 R2 - CU3 5.00.7958.1401 7958 N/A KB2994331 Upgrade guide SCCM 2012 R2 - CU4 5.00.7958.1501 7958 N/A KB3026739 Upgrade guide SCCM 2012 R2 - CU5 5.00.7958.1604 7958 N/A KB3054451 Upgrade guide SCCM 2012 R2 SP1 5.00.8239.1000 8239 N/A N/A Up...
Read more