none
Windows server 2016 can't install Windows Update RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    Windows server 2016 cannot install the KB5025228,  I checked the CBS log file, found below log for reference. 

    2023-04-28 16:05:57, Info                  CBS    Appl: detect Parent, Package: Package_127_for_KB5023788~31bf3856ad364e35~amd64~~14393.5771.1.0, Parent: Microsoft-Windows-WinPE-Package~31bf3856ad364e35~amd64~~10.0.14393.0, Disposition = Detect, VersionComp: EQ, BuildComp: EQ, RevisionComp: EQ, Exist: present
    2023-04-28 16:05:57, Info                  CBS    Appl: detectParent (exact match): Parent: Microsoft-Windows-WinPE-Package~31bf3856ad364e35~amd64~~10.0.14393.0, parent state: Absent
    2023-04-28 16:05:57, Info                  CBS    Appl: Evaluating package applicability for package Package_127_for_KB5023788~31bf3856ad364e35~amd64~~14393.5771.1.0, applicable state: Absent
    2023-04-28 16:05:57, Info                  CBS    Appl: detect Parent, Package: Package_128_for_KB5023788~31bf3856ad364e35~amd64~~14393.5771.1.0, Parent: Microsoft-Windows-ServicingStack-OneCore-CrossArch-Package~31bf3856ad364e35~amd64~~10.0.14393.0, Disposition = Detect, VersionComp: EQ, BuildComp: EQ, RevisionComp: EQ, Exist: present
    2023-04-28 16:05:57, Info                  CBS    Appl: detectParent (exact match): Parent: Microsoft-Windows-ServicingStack-OneCore-CrossArch-Package~31bf3856ad364e35~amd64~~10.0.14393.0, parent state: Installed
    2023-04-28 16:05:57, Info                  CBS    Appl: detect Parent, Package: Package_128_for_KB5023788~31bf3856ad364e35~amd64~~14393.5771.1.0, Parent: Microsoft-Windows-WinPE-Package~31bf3856ad364e35~amd64~~10.0.14393.0, Disposition = Detect, VersionComp: EQ, BuildComp: EQ, RevisionComp: EQ, Exist: present
    2023-04-28 16:05:57, Info                  CBS    Appl: detectParent (exact match): Parent: Microsoft-Windows-WinPE-Package~31bf3856ad364e35~amd64~~10.0.14393.0, parent state: Absent
    2023-04-28 16:05:57, Info                  CBS    Appl: Evaluating package applicability for package Package_128_for_KB5023788~31bf3856ad364e35~amd64~~14393.5771.1.0, applicable state: Absent
    2023-04-28 16:05:57, Info                  CBS    Appl: detect Parent, Package: Package_129_for_KB5023788~31bf3856ad364e35~amd64~~14393.5771.1.0, Parent: Microsoft-Windows-ServicingStack-Base-Package~31bf3856ad364e35~amd64~zh-CN~10.0.14393.0, Disposition = Detect, VersionComp: EQ, BuildComp: EQ, RevisionComp: EQ, Exist: present
    2023-04-28 16:05:57, Info                  CBS    Appl: detectParent (exact match): Parent: Microsoft-Windows-ServicingStack-Base-Package~31bf3856ad364e35~amd64~zh-CN~10.0.14393.0, parent state: Absent
    2023-04-28 16:05:57, Info                  CBS    Appl: Evaluating package applicability for package Package_129_for_KB5023788~31bf3856ad364e35~amd64~~14393.5771.1.0, applicable state: Absent
    2023-04-28 16:05:57, Info                  CBS    Appl: detect Parent, Package: Package_130_for_KB5023788~31bf3856ad364e35~amd64~~14393.5771.1.0, Parent: Microsoft-Windows-ServicingStack-Shell-Package~31bf3856ad364e35~amd64~~10.0.14393.0, Disposition = Detect, VersionComp: EQ, BuildComp: EQ, RevisionComp: EQ, Exist: present
    2023-04-28 16:05:57, Info                  CBS    Appl: detectParent (exact match): Parent: Microsoft-Windows-ServicingStack-Shell-Package~31bf3856ad364e35~amd64~~10.0.14393.0, parent state: Installed
    2023-04-28 16:05:57, Info                  CBS    Appl: detect Parent, Package: Package_130_for_KB5023788~31bf3856ad364e35~amd64~~14393.5771.1.0, Parent: Microsoft-Windows-WinPE-Package~31bf3856ad364e35~amd64~~10.0.14393.0, Disposition = Detect, VersionComp: EQ, BuildComp: EQ, RevisionComp: EQ, Exist: present
    2023-04-28 16:05:57, Info                  CBS    Appl: detectParent (exact match): Parent: Microsoft-Windows-WinPE-Package~31bf3856ad364e35~amd64~~10.0.14393.0, parent state: Absent
    2023-04-28 16:05:57, Info                  CBS    Appl: Evaluating package applicability for package Package_130_for_KB5023788~31bf3856ad364e35~amd64~~14393.5771.1.0, applicable state: Absent
    2023-04-28 16:05:57, Info                  CBS    Appl: detect Parent, Package: Package_131_for_KB5023788~31bf3856ad364e35~amd64~~14393.5771.1.0, Parent: Microsoft-Windows-ServicingStack-OneCore-Extra-CrossArch-Package~31bf3856ad364e35~amd64~~10.0.14393.0, Disposition = Detect, VersionComp: EQ, BuildComp: EQ, RevisionComp: EQ, Exist: present
    2023-04-28 16:05:57, Info                  CBS    Appl: detectParent (exact match): Parent: Microsoft-Windows-ServicingStack-OneCore-Extra-CrossArch-Package~31bf3856ad364e35~amd64~~10.0.14393.0, parent state: Installed
    2023-04-28 16:05:57, Info                  CBS    Appl: detect Parent, Package: Package_131_for_KB5023788~31bf3856ad364e35~amd64~~14393.5771.1.0, Parent: Microsoft-Windows-WinPE-Package~31bf3856ad364e35~amd64~~10.0.14393.0, Disposition = Detect, VersionComp: EQ, BuildComp: EQ, RevisionComp: EQ, Exist: present
    2023-04-28 16:05:57, Info                  CBS    Appl: detectParent (exact match): Parent: Microsoft-Windows-WinPE-Package~31bf3856ad364e35~amd64~~10.0.14393.0, parent state: Absent
    2023-04-28 16:05:57, Info                  CBS    Appl: Evaluating package applicability for package Package_131_for_KB5023788~31bf3856ad364e35~amd64~~14393.5771.1.0, applicable state: Absent
    2023-04-28 16:05:57, Info                  CBS    Appl: detect Parent, Package: Package_132_for_KB5023788~31bf3856ad364e35~amd64~~14393.5771.1.0, Parent: Microsoft-Windows-ServicingStack-Base-Package~31bf3856ad364e35~amd64~pt-BR~10.0.14393.0, Disposition = Detect, VersionComp: EQ, BuildComp: EQ, RevisionComp: EQ, Exist: present
    2023-04-28 16:05:57, Info                  CBS    Appl: detectParent (exact match): Parent: Microsoft-Windows-ServicingStack-Base-Package~31bf3856ad364e35~amd64~pt-BR~10.0.14393.0, parent state: Absent
    2023-04-28 16:05:57, Info                  CBS    Appl: Evaluating package applicability for package Package_132_for_KB5023788~31bf3856ad364e35~amd64~~14393.5771.1.0, applicable state: Absent

    Who can help me some tips about this situation？ Thank you in advance. 

    Kenneth 

    Friday, May 5, 2023 9:14 AM
    |

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    If you're having trouble installing Windows updates on Windows Server 2016, here are a few steps you can try to resolve the issue:

    Check for internet connectivity: Ensure that your server has an active internet connection and that it can access the Windows Update server. If the server cannot connect to the Windows Update server, you may need to check your firewall settings or network configurations.

    Restart the Windows Update service: Restarting the Windows Update service can sometimes help resolve update installation issues. To do this, open the Services Manager, locate the Windows Update service, and restart it.

    Run the Windows Update troubleshooter: Windows Server 2016 comes with a built-in troubleshooter for Windows Update. Run the troubleshooter by going to Settings > Update & Security > Troubleshoot > Windows Update.

    Manually download and install the updates: If the automatic update installation process is not working, you can try manually downloading the updates from the Microsoft Update Catalog and installing them on the server.

    Check for disk space: Ensure that you have enough disk space on your server's system drive to install updates. Windows Server 2016 requires a minimum of 32 GB of free disk space to install updates.

    Check for pending updates: Sometimes, updates may fail to install due to a pending update that is waiting to be installed. Check for any pending updates by going to Settings > Update & Security > Windows Update > Check for Updates.

    If none of the above steps work, you may need to check the Windows Update logs for any error messages that could be causing the installation issues. Additionally, if the server is part of a domain, you may need to check group policy settings that could be preventing updates from installing.
    Sunday, May 7, 2023 8:05 AM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote
    Restart the Windows Update service: Restarting the Windows Update service can sometimes help resolve update installation issues. To do this, open the Services Manager, locate the Windows Update service, and restart it.

    Run the Windows Update troubleshooter: Windows Server 2016 comes with a built-in troubleshooter for Windows Update. Run the troubleshooter by going to Settings > Update & Security > Troubleshoot > Windows Update.
    Tuesday, May 9, 2023 8:51 AM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote

    There could be several reasons why a Windows Server 2016 machine may not be able to install Windows Updates. Here are some possible solutions to try:

    Check the Windows Update settings: Make sure the Windows Update settings are configured correctly. Go to Settings > Update & Security > Windows Update and ensure that the machine is set to receive updates automatically.

    Check disk space: If there isn't enough disk space on the machine, Windows Updates may fail to install. Check the available disk space and free up space if necessary.

    Restart the Windows Update service: Sometimes the Windows Update service may get stuck or become unresponsive. Try restarting the service by opening an elevated command prompt and running the following commands:

    net stop wuauserv
    net start wuauserv

    Check for malware: Malware or viruses on the machine may interfere with the Windows Update process. Run a full system scan with an antivirus software to ensure that the machine is free of malware.

    Manually install updates: If all else fails, try manually downloading and installing the updates from the Microsoft Update Catalog. You can search for the specific update you need, download it, and then install it manually on the machine.

    Regards,

    Richard

    Friday, May 12, 2023 5:34 AM
    |