2024-08 Cumulative Update for Windows Server 2019 (1809) for x64-based Systems (KB5041578) - Error 0x80070002

Anonymous
2024-08-15T17:32:01+00:00

Hi,

I'm supporting a friend remotely who has a dell server running Windows Server 2019 (remote desktop access).

Since I installed it in 2021, I never been able to install cumulative updates, always errors.

I already renamed catroot2 and swdistrib directory, ran troubleshooter, and tried several things I have seen in this community without any success.

If somebody is available to help me, I would appreciate.

Thanks in advance.

Best.

Windows for business | Windows Server | Devices and deployment | Set up upgrades and drivers

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question. To protect privacy, user profiles for migrated questions are anonymized.

0 comments No comments
{count} votes

5 answers

Sort by: Most helpful
  1. Anonymous
    2024-08-19T03:10:24+00:00

    Hello  Stephane Blazy,

    Thank you for posting in Microsoft Community forum.

    The 0x80070002 error usually indicates that some files are missing or the update process is having trouble accessing certain files. Here are some additional steps you can try:

    1. Check Date and Time Settings:
      • Ensure the date and time settings on the server are correct. Incorrect settings can sometimes block updates.
    2. Run Windows Update Troubleshooter:
      • Although you mentioned you tried the troubleshooter, ensure you ran it as an administrator for it to have proper privileges to fix issues.
    3. Restart Windows Update Services:
      • Open Command Prompt as an administrator and run the following commands one by one:
        
             net stop wuauserv 
        
             net stop cryptSvc 
        
             net stop bits 
        
             net stop msiserver 
        
        
      • Then, rename the SoftwareDistribution and Catroot2 folders:
        
             ren C:\Windows\SoftwareDistribution SoftwareDistribution.old 
        
             ren C:\Windows\System32\catroot2 Catroot2.old 
        
        
      • Restart the services:
        
             net start wuauserv 
        
             net start cryptSvc 
        
             net start bits 
        
             net start msiserver 
        
        
    4. SFC and DISM Scans:
      • Run the System File Checker and DISM tools to repair Windows system files:
        
             sfc /scannow 
        
        
      • After that, run the following DISM command:
        
             DISM /Online /Cleanup-Image /RestoreHealth 
        
        
    5. Check Disk Space:*
      • Ensure that there's enough disk space on the server to download and install updates. 
    6. Manually Download and Install the Update:
    7. Check Windows Update Log:
      • View detailed logs for Windows Update errors. Open Event Viewer, go to Windows Logs > Application and Windows Logs > System, and look for any errors related to Windows Update.
      • Additionally, you can check the Windows Update log:
        
             Get-WindowsUpdateLog 
        
        
      • This will create a WindowsUpdate.log file on the desktop which you can review for more detailed error information.
    8. Clean Boot:
      • Perform a clean boot to see if a startup item or service is causing the issue:
        • Open msconfig, go to the Services tab, check "Hide all Microsoft services", and then click "Disable all".
        • Go to the Startup tab and click "Open Task Manager".
        • Disable all startup items.
        • Restart the server and try updating again.

    By following these steps, you should be able to identify and resolve the issue preventing Windows Server 2019 from installing cumulative updates. Some of the methods provided above may have already been tried, and you can ignore them or try again.

    I hope the information above is helpful.

    If you have any question or concern, please feel free to let us know.

    Best Regards,

    Haijian Shan

    0 comments No comments
  2. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.


    Comments have been turned off. Learn more

  3. Anonymous
    2024-08-19T07:45:39+00:00

    Hi Haijian,

    Thank you very much for the details provided.

    I need to organise the clean boot on site, and will happen most probably next week.

    Remotely, SFC reports several errors, and the CBS.log file contains several message such as: HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND

    and DSIM reports error 2 as well.

    Any idea to fix this please ?

    Best regards,

    Stephane.

    0 comments No comments
  4. Anonymous
    2024-08-26T02:53:26+00:00

    Hello  Stephane Blazy,

    Thank you for your reply.

    Given that SFC and DISM are reporting errors and you've received the ERROR_FILE_NOT_FOUND messages, it indicates that there might be critical system files missing or corrupted. Here are some additional steps and suggestions to help resolve these errors before proceeding to a clean boot:

    1. Check Windows Update Component Store:* The component store might be corrupted and preventing updates from installing.
      • Clear the component store:* Open Command Prompt as an administrator and run:
        
             DISM /Online /Cleanup-Image /StartComponentCleanup 
        
        
    2. Use the Microsoft Update Catalog:

    Manual installation of updates can sometimes succeed where automatic updates fail.

    • Search for KB5041578 in the Microsoft Update Catalog.
    • Download the appropriate update package for your system.
    • Manually install it by running the downloaded .msu file.
    1. Check the CBS.log for Specific Errors:
      • The CBS.log file may contain clues about which specific files are missing or corrupted.
      • Open the CBS.log file located at C:\Windows\Logs\CBS\CBS.log and look for detailed error messages around "HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND".
    2. Check Registry Settings:
    • Incorrect settings in the registry can cause update issues. Carefully check the following registry keys:
      • HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Version
      • HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update

    By following these steps, you should be able to identify and fix the issues preventing your server from updating. If the CBS.log and DISM logs provide specific missing files, you might need to replace those manually from another identical system or from installation media.

    Best Regards,

    Haijian Shan

    0 comments No comments
  5. Anonymous
    2024-08-28T14:23:40+00:00

    Hi Haijian Shan,

    Once again, thank you very much for the detailed and support provided.

    I have progressed in one direction by running the manual installation with success for the first time (tried several times before).

    Unfortunately, after the reboot, Windows update is reporting the same error and I have now other issues such as printer svc not working anymore (not even able to add printer - neither with IP @ or with HP software), and as well Server Console not showing roles & functionalities anymore.

    Therefore, I believe the best option at this stage is to run a new installation from scratch which is planned next Monday September the 2nd.

    In case you see any alternative at this stage, feel free to answer this post.

    Thank you.

    Best regards,

    Stephane.

    0 comments No comments