locked
Cumulative updates failing on Windows Server 2016 Standard and Server 2012 R2 Standard RRS feed

  • Question

  • For months we have had two servers with the mentioned OS installations that fail when applying the Cumulative updates for that month.

    For one server the updates install in the OS but upon restarting the server an error occurs and all the changes are undone and all the updates are available again.

    For the other, the updates download but upon installing the progress bar gets to about 20% and then hangs for a long time, then fails with a generic "please try again later"

    Notes:

    Both servers have access to internet

    We have attempted to install updates from deployment software (GFI Languard) as well as while on the server remotely (RDP)

    We have attempted to rename/delete the SoftwareDistribution Folder and re-perform updates - same results.

    We have attempted to download the updates from the Microsoft Update Catalog and install them manually - same results.

    We have many other servers with these OS's that have had no issues with applying the cumulative updates.

    Would greatly appreciate any suggestions as we are out of ideas.

    Wednesday, October 31, 2018 4:20 PM

All replies

  • Hello,
     
    For the server which roll back after restarting, try use DISM to install it manually. Refer to following article.
     
    https://blogs.technet.microsoft.com/askcore/2011/02/15/how-to-use-dism-to-install-a-hotfix-from-within-windows/
     
    For the another server, what's the error code? Or you could upload the windowsupdate.log for further troubleshooting.
     
    There are other methods you could try to fix it.
     
    Fix windows update issues
    https://support.microsoft.com/en-sg/help/10164
    (Select Windows 10 for Server 2016 and Windows 8.1 for Server 2012 R2)
    (Make sure you have tried the troubleshooter tool and dism/sfc command)
     
    Hope my answer could help you.
     
    Best Regards,
    Ray
     

    Please remember to mark the replies as answers if they help.

    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Thursday, November 1, 2018 2:26 AM
  • Hello,
     
    I noticed that you have not updated the post for a while. Have your issue or question been resolved now? Or is there any update? Please feel free to feedback.
     
    Best Regards,
    Ray

    Please remember to mark the replies as answers if they help.

    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Friday, November 9, 2018 3:01 AM
  • I actually have a support ticket open with Microsoft Technical support at the moment. I'll update if they are able to resolve or if I need to come back for more suggestions.
    Friday, November 9, 2018 1:25 PM
  • I actually have a support ticket open with Microsoft Technical support at the moment. I'll update if they are able to resolve or if I need to come back for more suggestions.

    Do you already have any news on this case?

    We also have a Windows Server 2016 which is failing to install any Cumulative Update.

    The update installs, the server reboot, the percentage goes up to 99 percent and then it fails and undoes all the changes.

    Tuesday, January 8, 2019 2:00 PM
  • Hi Rene,

    you can find the error that caused the rollback of the updates in the c:\Windows\Logs\CBS\CBS.log file.

    Search for ", error" and should find the reason, post back if you have issues.

    Hope this helps,
    Andrei


    We could change the world, if God would give us the source code.

    Tuesday, January 8, 2019 4:55 PM
  • Hi Andrei

    Thank you for your hint. I indeed found some errors within the CBS logs.

    But unfortunately, it does not really help me sorting out the issue why it's reverting, or how to fix those error.


    2019-01-09 07:59:18, Error                 CSI    00000558@2019/1/9:06:59:18.115 (F) onecore\base\appmodel\inboxappinstallerai\appxreg.cpp(94): Error HRESULT_FROM_WIN32(1058) originated in function Windows::WCP::AppXRegistration::BasicInstaller::Install expression: RDSAppXOnlineNotifyPackageChanges(APPCHANGETYPE_INBOX)
    [gle=0x80004005]
    2019-01-09 07:59:18, Error      [0x018051] CSI    0000055a (F) Failed execution of queue item Installer: AppX Registration Installer ({f1aab1ba-6ee0-4d94-baeb-c9fd61f365cf}) with HRESULT HRESULT_FROM_WIN32(1058).  Failure will not be ignored: A rollback will be initiated after all the operations in the installer queue are completed; installer is reliable[gle=0x80004005]
    2019-01-09 07:59:18, Error                 CSI    0000056d@2019/1/9:06:59:18.364 (F) onecore\base\appmodel\inboxappinstallerai\appxreg.cpp(94): Error HRESULT_FROM_WIN32(1058) originated in function Windows::WCP::AppXRegistration::BasicInstaller::Install expression: RDSAppXOnlineNotifyPackageChanges(APPCHANGETYPE_INBOX)
    [gle=0x80004005]
    2019-01-09 07:59:18, Error      [0x018051] CSI    0000056e (F) Failed execution of queue item Installer: AppX Registration Installer ({f1aab1ba-6ee0-4d94-baeb-c9fd61f365cf}) with HRESULT HRESULT_FROM_WIN32(1058).  Failure will not be ignored: A rollback will be initiated after all the operations in the installer queue are completed; installer is reliable[gle=0x80004005]
    2019-01-09 07:59:25, Error                 CBS    Startup: Failed to process advanced operation queue, startupPhase: 0.  A rollback transaction will be created. [HRESULT = 0x800f0922 - CBS_E_INSTALLERS_FAILED]
    Wednesday, January 9, 2019 7:14 AM
  • Just figured out myself.

    The service "App readiness" was disable due to slow logon times on this server. After re-enabling the service, the cumulative update installed without any issues.

    Wednesday, January 9, 2019 7:46 AM
  • Depending on what we would have seen in the CBS.log file, we would know where to look next. For example the AppX Registration Installer is failing here, so we can look for more details under the following event logs:
    Microsoft-Windows-AppXDeploymentServer/Operational
    Microsoft-Windows-AppXDeployment/Operational

    The error code in our case also translates to:

    0x422 1058 ERROR_SERVICE_DISABLED The service cannot be started, either because it is disabled or because it has no enabled devices associated with it.

    Glad to hear that you solved it!

    Best regards,
    Andrei

    P.S.: Here is some more info about disabling services: https://docs.microsoft.com/en-us/windows-server/security/windows-services/security-guidelines-for-disabling-system-services-in-windows-server


    We could change the world, if God would give us the source code.

    Wednesday, January 9, 2019 5:02 PM
  • I have the same problem, but the App Readiness service isn't disabled.  Ready to call Microsoft just to get by, but hoping someone else has an idea.  I just tried the suggestion above to use dism to slip in the hotfix.  On reboot, it still reverted. 

    I've done everything else suggest, sfc/dism cleanup, reset the windows update folders/services.  I'm out of ideas.  Any help would be appreciated.

    Cbs.log info for failure:

    2019-01-18 11:43:33, Error                 CSI    000004fd@2019/1/18:17:43:33.474 (F) onecore\base\appmodel\inboxappinstallerai\appxreg.cpp(94): Error HRESULT_FROM_WIN32(ERROR_FILE_NOT_FOUND) originated in function Windows::WCP::AppXRegistration::BasicInstaller::Install expression: RDSAppXOnlineNotifyPackageChanges(APPCHANGETYPE_INBOX)
    [gle=0x80004005]
    2019-01-18 11:43:33, Info                  CBS    Added C:\Windows\Logs\CBS\CBS.log to WER report.
    2019-01-18 11:43:33, Info                  CBS    Added C:\Windows\Logs\CBS\CbsPersist_20190118174208.log to WER report.
    2019-01-18 11:43:33, Info                  CBS    Added C:\Windows\Logs\CBS\CbsPersist_20190118163926.log to WER report.
    2019-01-18 11:43:33, Info                  CBS    Added C:\Windows\Logs\CBS\CbsPersist_20190118155109.log to WER report.
    2019-01-18 11:43:33, Info                  CBS    Added C:\Windows\Logs\CBS\CbsPersist_20190117205043.log to WER report.
    2019-01-18 11:43:33, Info                  CBS    Added C:\Windows\Logs\CBS\CbsPersist_20190117193300.cab to WER report.
    2019-01-18 11:43:33, Info                  CBS    Could not get active session for current session file logging [HRESULT = 0x80004003 - E_POINTER]
    2019-01-18 11:43:33, Info                  CBS    Not able to add pending.xml.bad to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
    2019-01-18 11:43:33, Info                  CBS    Startup: Changing logon timeout to a static timeout: 10800000
    2019-01-18 11:43:34, Info                  CSI    000004fe Performing 1 operations as follows:
      (0)  LockComponentPath: flags: 0 comp: {l:16 b:c6636c5555afd401e8030000800ba40b} pathid: {l:16 b:c6636c5555afd401e9030000800ba40b} path: [l:115]'\SystemRoot\WinSxS\x86_microsoft.windows.s..ation.badcomponents_31bf3856ad364e35_10.0.14393.0_none_09e78f632173f4c5' pid: b80 starttime: 131923069289853253
    2019-01-18 11:43:34, Error      [0x018051] CSI    000004ff (F) Failed execution of queue item Installer: AppX Registration Installer ({f1aab1ba-6ee0-4d94-baeb-c9fd61f365cf}) with HRESULT HRESULT_FROM_WIN32(ERROR_FILE_NOT_FOUND).  Failure will be ignored: The failure was encountered during rollback; installer is reliable[gle=0x80004005]
    2019-01-18 11:43:34, Info                  CBS    Added C:\Windows\Logs\CBS\CBS.log to WER report.

    Friday, January 18, 2019 6:08 PM
  • Hi Mertz,

    Best way to determine why we get a file not found error is to run Procmon and take it from there.

    Best regards,
    Andrei


    We could change the world, if God would give us the source code.

    Sunday, January 27, 2019 8:08 PM
  •  This worked for me. Changed the App Readiness service to manual, started it and the updates installed. Worked on one problem 2016 server...now trying it on our 2nd problem server.
    Thursday, September 5, 2019 6:47 PM