Skip to content

Konstantinos Tsoukalas

Konstantinos is the founder and administrator of Wintips.org. Since 1995 he works and provides IT support as a computer and network expert to individuals and large companies. He is specialized in solving problems related to Windows or other Microsoft products (Windows Server, Office, Microsoft 365, etc.).

7 Comments

  1. JDub
    April 15, 2021 @ 8:24 pm

    Thank you for this article!

    For anyone that runs across this article and cant get it working. Make sure you are using the RTM ISO.

    Reply

  2. George
    September 11, 2020 @ 11:46 pm

    Great!
    Finally I resolved the issue with enabling Defender!
    I also needed to install the correspond Servicing Stack Update for Windows Server 2016 for x64-based Systems first.
    And then the Windows Server 2016 for x64 cumulative update.
    Thank you so much!!!

    Reply

  3. mike
    May 23, 2020 @ 10:58 am

    thank for your tutorial
    To get the new MSU package working you have to first merge the latest build of "Servicing Stack Update"
    Or you will get a failure with Error: 0x800f0823
    https://www.catalog.update.microsoft.com/Search.aspx?q=KB4550994
    Now I have updated to windows10.0-kb4556813-x64

    Reply

  4. marc
    September 2, 2019 @ 9:27 pm

    C:\WINDOWS\system32>Dism /Online /Enable-Feature /FeatureName:Windows-Defender /all /source:WIM:C:\install.wim:1 /LimitAccess

    Deployment Image Servicing and Management tool
    Version: 10.0.14393.3085

    Image Version: 10.0.14393.3085

    Enabling feature(s)
    [==========================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 information 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

    Reply

    • lakonst
      September 3, 2019 @ 9:43 am

      Use the instructions at this method (NLITE) to extract the install.wim file and try the procedure again.

      Reply

      • BaBaVick
        July 23, 2023 @ 6:38 am

        After using NLITE to extract the install.wim file, do all the commands again, the same way? Or change all the references of .wim to .esd?

        Reply

        • lakonst
          July 24, 2023 @ 9:15 am

          If you have "install.esd", then yes you have to change the reference of "install.wim" to "install.esd"

          Reply

Leave a Reply

Your email address will not be published. Required fields are marked *