Operate in Server Core Test fails - "DismGetFeatureInfo failed with error code: -2146498548" RRS feed

  • Question

  • I am trying to certify a device on Server 2016 Core (standard) and "Operate in Server Core Test" always fails with the message  "DismGetFeatureInfo failed with error code: -2146498548".

    That error code in hex is 0x800f080c which is what "dism /online /Get-FeatureInfo ..." returns for an unknown feature.  I looked at the binary for servercorecheck.dll (the binary for OiSCT) and it looks like it is trying to run DismGetFeatureInfo for three different GUI features - "ServerCore-FullServer", "Server-Gui-Shell", and "Server-Gui-Mgmt" to make sure that they are in the state of "Disabled with payload removed" but those features are not even present in a Server 2016 Core installation.  So it must be assuming that they were possibly removed from a GUI installation in order to run OiSCT Which is what I had to do for Server 2012-R2 to pass that test.   But look what the documentation for "Operate in Server Core Test" for S2016 says:

    If you installed the "Full Server" or "Server with a GUI" during Setup, you should reinstall Windows and select the "Server Core Installation" option in Setup to ensure that no traces of Server with a GUI remain on the server running certification. All installation and configuration tests for your driver must be done from within Server Core

    Previously there was a Filter 5856 to get around the problem of not being able to switch from GUI to Core but it expired in November of 2016.  And apparently the expectation was to run all driver verification test under Server Core.  I don't know how work around this.  I applied the latest filter and that did not help.

    Hope someone can help with this. 


    Saturday, March 25, 2017 12:41 AM

All replies

  • Windows Server 2016 can no longer be changed from GUI to Core. . .

    Therefore, it seems that there is no choice but to do HLK test with ServerCore.

    There are many people who face the same problem, so some threads are already up. . .

    By using the sconfig command, diskpart command, devcon command etc., it will be possible to manage the environment somehow.

    It is hard to memorize, but let's do our best.

    By setting the remote management, you can operate it to some extent with the GUI.
    1.2 Manage with Server Manager

    Monday, March 27, 2017 4:59 AM
  • Thanks for the response, hirosea.  I think you might have misunderstood my issue.  I do not need the Server GUI support.  I am able to setup my target machine completely with Server Core.  My problem is that it does not pass "Operate in Server Core Test" and I infer from the error message that the test expects a feature which is missing.  In particular I believe there are three such features it tests for (as I mentioned in my original post).  I'm sorry if I am missing something.  I looked at your links and they did not help for this problem.


    Monday, March 27, 2017 4:02 PM
  • I 'm Sorry.

    By the way, are there versions of HLK and OS versions?

    For the product version of Windows Server 2016, you should only be able to use the version 1607 HLK.


    I think Filter 5856 is about the time of Windows Server 2016 TP 5 + HLK Version 1511.

    Tuesday, March 28, 2017 3:56 AM
  • Hello,

    What build of the kit/OS you are using?

    10586 is version 1511, and WS2016 did not ship until 14393. 

     The OS and the HLK builds must match

    We allowed early submissions of WS2016 during preview/beta period (with the mentioned errata), but it had a cut-off of RTM plus 90 days, which has long passed …

    Per Windows Hardware Compatibility Policy, all partners must transition to HLK version 1607 and use the HLK version 1607 Compatibility playlist no later than October 31, 2016. After this date, logs from HLK version 1511 and corresponding playlist will no longer be accepted for Compatibility submissions.

    I would recommend updating your controller to HLK 14393 and test against matching OS 14393 (1607)


    Thursday, March 30, 2017 5:15 PM