locked
Windows Update KB3213986 keeps failing to install RRS feed

  • Question

  • I updated about 20 Windows Server 2016 Datacenter servers when the January Windows Updates were released last week with no issues except for one server where I get the following error:

    Cumulative Update for Windows Server 2016 for x64-based Systems (KB3213986) - Error 0x800f0900

    I've tried rebooting the server and installing the update again but every time I retry the reinstall it fails. I tried the Windows Update troubleshooting tool but this didn't help. I also tried deleting the contents on the SofitwareDistribution folder but this also didn't help. I even manually downloaded the update from the Windows Catalog but it still wouldn't install. I'm not running any 3rd party Anti-Virus except for the builtin Windows Defender.

    Currently I have 14393.577 installed on the server I am trying to install KB3213986 (14393.693) on.

    What else can I try to successfully install this update?

    Thanks!


    • Edited by SW97C Tuesday, January 17, 2017 10:11 PM
    Tuesday, January 17, 2017 10:10 PM

Answers

  • When I restored the VM it was done on a date BEFORE the server had downloaded the Jnauary Windows Updates.
    • Marked as answer by SW97C Thursday, January 19, 2017 8:32 PM
    Thursday, January 19, 2017 8:13 AM

All replies

  • You might try;

    dism /online /cleanup-image /restorehealth

    Also try some of the individual listed here to further trouble shoot.

    https://support.microsoft.com/en-us/help/4009938/january-10-2017-kb3213986-os-build-14393-693

     

     

     



    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows Server] Datacenter Management

    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees, and confers no rights.

    Tuesday, January 17, 2017 10:37 PM
  • I can tell you this update KB3213986 has installed 4 times since 1/11/17 and twice today 1/17/17! Running OS build 14393.693. Incredibly I uninstall it and it just reinstall on reboot. SFC was fine, tried Windows Update repair tool. Will see if that fixes it. It found a registry error it says it fixed. Fingers crossed. X
    Wednesday, January 18, 2017 1:51 AM
  • So I ran dism /online /cleanup-image /restorehealth and get the following:

    Deployment Image Servicing and Management tool
    Version: 10.0.14393.0

    Image Version: 10.0.14393.0

    [==========================100.0%==========================]
    Error: 0x800f081f

    The source files could not be found.
    Use the "Source" option to specify the location of the files that are required to restore the feature. For more informat
    ion on specifying a source location, see http://go.microsoft.com/fwlink/?LinkId=243077.

    The DISM log file can be found at C:\Windows\Logs\DISM\dism.log

    In the dism.log the following warnings/errors appeared:

    2017-01-18 07:12:47, Warning               DISM   DISM OS Provider: PID=4488 TID=4348 Unable to set the DLL search path to the servicing stack folder. C:\Windows may not point to a valid Windows folder. - CDISMOSServiceManager::Final_OnConnect
    2017-01-18 07:12:47, Warning               DISM   DISM Provider Store: PID=4488 TID=4348 Failed to Load the provider: C:\Users\CARETA~1\AppData\Local\Temp\A7CBD260-59B4-4DBF-B85F-72A264134C24\PEProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
    CDISMProviderStore::Internal_GetProvider

    2017-01-18 07:12:49, Warning               DISM   DISM Provider Store: PID=4488 TID=4276 Failed to Load the provider: C:\Users\CARETA~1\AppData\Local\Temp\A7CBD260-59B4-4DBF-B85F-72A264134C24\EmbeddedProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)


    2017-01-18 07:18:27, Error                 DISM   DISM Package Manager: PID=4488 TID=2444 Failed finalizing changes. - CDISMPackageManager::Internal_Finalize(hr:0x800f081f)
    2017-01-18 07:18:27, Error                 DISM   DISM Package Manager: PID=4488 TID=2444 The source files could not be found; their location must be specified using the /source option to restore the feature. - GetCbsErrorMsg
    2017-01-18 07:18:27, Error                 DISM   DISM Package Manager: PID=4488 TID=2444 Failed processing package changes with session option CbsSessionOptionRepairStoreCorruption - CDISMPackageManager::RestoreHealth(hr:0x800f081f)
    2017-01-18 07:18:27, Error                 DISM   DISM Package Manager: PID=4488 TID=2444 The source files could not be found; their location must be specified using the /source option to restore the feature. - GetCbsErrorMsg
    2017-01-18 07:18:27, Error                 DISM   DISM Package Manager: PID=4488 TID=2444 Failed to restore the image health. - CPackageManagerCLIHandler::ProcessCmdLine_CleanupImage(hr:0x800f081f)
    2017-01-18 07:18:27, Error                 DISM   DISM Package Manager: PID=4488 TID=2444 Failed while processing command cleanup-image. - CPackageManagerCLIHandler::ExecuteCmdLine(hr:0x800f081f)
    CDISMProviderStore::Internal_DisconnectProvider

    What else can I try?

    Wednesday, January 18, 2017 7:35 AM
  • Looks like DISM needs a repair source.

    https://technet.microsoft.com/en-us/library/hh825020.aspx?f=255&MSPPError=-2147217396

    or you can also try a repair install.

    https://support.microsoft.com/en-us/kb/2255099

    but I suppose if it were me I'd rebuild that one.

     

     

     



    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows Server] Datacenter Management

    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees, and confers no rights.

    Wednesday, January 18, 2017 2:27 PM
  • I'd like to avoid a rebuild if possible so is there anything else I can try?

    I don't seem to be having any luck with using DISM with a repair source.

    Wednesday, January 18, 2017 10:03 PM
  • Then I'd try the repair install.

     

     



    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows Server] Datacenter Management

    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees, and confers no rights.

    Wednesday, January 18, 2017 10:08 PM
  • Ok that didn't help. I ended up having to restore the VM from before I downloaded the Windows Updates and this allowed me to successfully download and install the January Windows Updates. Makes no sense to me...
    Wednesday, January 18, 2017 11:04 PM
  •  from before I downloaded the Windows Updates and this allowed me to successfully download and install the January Windows Updates.

    Glad to hear it's sorted but I don't understand what this even means.... before you downloaded what updates?

     

     



    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows Server] Datacenter Management

    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees, and confers no rights.

    Wednesday, January 18, 2017 11:26 PM
  • When I restored the VM it was done on a date BEFORE the server had downloaded the Jnauary Windows Updates.
    • Marked as answer by SW97C Thursday, January 19, 2017 8:32 PM
    Thursday, January 19, 2017 8:13 AM
  • Hi SW97C,

    Thanks for your feedback. Then, you may mark your resolution as answer so that the reply can be highlighted.

    Best Regards,

    Anne


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.



    Thursday, January 19, 2017 9:51 AM