Cannot update windows server 2019

Anonymous
2024-10-05T07:17:51+00:00

Hello, we are a small company with only one server and some clients, this server is dc, hyperv-host and file server. Now i cannot update the security updates, i run the microsoft defender business for server as antivirus and firewall:

2024-09 Cumulative Update for Windows Server 2019 (1809) for x64-based Systems (KB5043050) - Error 0x800f0988

I have tried everything i can find but i still get this error and i cannot seem to find more information in any logs.

i have tried disabling and changing name on the 2 folders as seen in some guides.

i have tried the dism commands and sfc scannow and they had a problem that the dism fixed so now i dont have any problems:
C:\Windows\system32>DISM /ONLINE /CLEANUP-IMAGE /SCANHEALTH

Deployment Image Servicing and Management tool

Version: 10.0.17763.3406

Image Version: 10.0.17763.4974

[==========================100.0%==========================] No component store corruption detected.

The operation completed successfully.

C:\Windows\system32>DISM /ONLINE /CLEANUP-IMAGE /CHECKHEALTH

Deployment Image Servicing and Management tool

Version: 10.0.17763.3406

Image Version: 10.0.17763.4974

No component store corruption detected.

The operation completed successfully.

i have also tried downloading the update and installing it manually where it just says error with no more information.

i also tried manually installing it from powershell directly and using wsus but still just says error.

i have tried a "clean boot" by disabling everything except windows components on startup but i get the same error.

i have also tried running the toubleshooter for update where it does not find any troubles

i need help, i cannot reinstall the entire server, that is just not an option since its a business critical server where everything is stored and the whole company works on that server (PDM system, Visma Economy systems, file server and more).

Windows for business | Windows Server | Devices and deployment | Install Windows updates, features, or roles

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

3 answers

Sort by: Most helpful
  1. Anonymous
    2024-10-07T07:13:20+00:00

    Hello  Rasmus Svets,

    Thank you for posting in Microsoft Community forum.

    Given the critical nature of your server and the persistent update issue, let's go through a few advanced steps to resolve the error 0x800f0988 on your Windows Server 2019 (1809).

    1. Reset Windows Update Components

    You may have already renamed the SoftwareDistribution and Catroot2 folders, but let's make sure to reset all Windows Update components completely.

    1. Open Command Prompt as Administrator.
    2. Stop the Windows Update services:
      
         net stop wuauserv 
      
         net stop cryptSvc 
      
         net stop bits 
      
         net stop msiserver 
      
      
    3. Rename the SoftwareDistribution and Catroot2 folders:
      
         ren C:\Windows\SoftwareDistribution SoftwareDistribution.old 
      
         ren C:\Windows\System32\catroot2 catroot2.old 
      
      
    4. Reset the Windows Update Components:
      
         exe /updatenow 
      
      
    5. Restart the services:
      
         net start wuauserv 
      
         net start cryptSvc 
      
         net start bits 
      
         net start msiserver 
      
      
    6. Try updating again.

    2. Clear BITS Queue

    If Background Intelligent Transfer Service (BITS) jobs are corrupted, they might cause update issues.

    1. Open Command Prompt as Administrator.
    2. Run the following commands:
      
         bitsadmin /reset /allusers 
      
      

    3. Check System Reserved Partition

    Sometimes, the System Reserved Partition is too small, preventing updates from applying.

    1. Open Disk Management (diskmgmt.msc).
    2. Check the System Reserved Partition size (should be around 500 MB).
    3. If it's less than 500 MB, you might need to extend it using third-party tools like GParted. However, this is a risky operation and should be done with backups in place.

    4. Manually Install Prerequisites

    Ensure all prerequisite updates are installed. Sometimes, specific updates are required before others can apply.

    1. Check for any prerequisite updates listed for KB5043050 and install them if necessary.

    5. Temporary Media Creation

    Another more advanced approach is to do an in-place upgrade repair install using an ISO.

    1. Download the Windows Server 2019 ISO file corresponding to your current version.
    2. Mount the ISO file.
    3. Run setup.exe from the mounted ISO.
    4. Choose to keep files and apps when prompted.

    This approach essentially re-installs the OS without losing your configurations or installed roles/features.

    Notes

    • Always ensure you have a complete backup of your server before making significant changes.
    • If downtime for manual update attempts is too risky, consider setting up a test environment that mirrors your production setup where you can safely perform these operations. 

    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. Anonymous
    2024-10-08T16:59:39+00:00
    1. did those with no difference.
    2. 0 out of 0 jobs cancelled
    3. KB5005112 listed is already installed
    4. I can only get hold of the evaluation iso and that does not work since its not the windows server 2019 standard edition, so i cannot make an "upgrade" repair and keep the files.
    0 comments No comments
  3. Anonymous
    2024-11-22T07:41:49+00:00

    The ISO of the evaluation version may be the cause of the problem, and it is recommended that you install the standard version to see if the problem can be fixed

    0 comments No comments