On-Prem WSUS with Azure issues

BatchPatch Forums Home Forums BatchPatch Support Forum On-Prem WSUS with Azure issues

Viewing 1 post (of 1 total)
  • Author
    Posts
  • #13237
    doug
    Moderator

    106G means that the target computer was able to communicate with the WSUS, but the search was not able to complete properly. In the past we have only ever seen

    HRESULT -2145124338 => 0x8024000E WU_E_XML_INVALID Windows Update Agent found invalid information in the update's XML data

    However, in your case you’re seeing

    HRESULT -2145116137 => 0x80242017 WU_E_UH_NEW_SERVICING_STACK_REQUIRED The OS servicing stack must be updated before this update is downloaded or installed

    More info at the following link, but I think your easiest option is probably to run Windows Update one time with the server selection in BP set to ‘Windows Update’ or ‘Microsoft Update’. After installing updates that way and rebooting, your check for updates against the managed WSUS should work. If for some reason that doesn’t work then you’ll likely need to locate the standalone servicing stack update that your machines need in the Microsoft Update Catalog directly. Then install it manually or with the Deployment feature in BP.

    More here:
    https://techcommunity.microsoft.com/t5/windows-server-for-it-pro/error-0x80242017-when-installing-kb5004945-from-wsus-but-not/m-p/2524094

Viewing 1 post (of 1 total)
  • You must be logged in to reply to this topic.