none
Install-ContainerImage NanoServer / WindowsServerCore on Windows 10 14332.1001 gives Certificate error RRS feed

  • Question

  • I'm running latest Windows 10 (1511 OS Build 14332.1001) with Hyper-V and Containers enabled, are TP5 containers supposed to work with this release?

    > Find-ContainerImage gives

    Name                           Version          Source           Summary
    ----                           -------          ------           -------
    NanoServer                     10.0.14300.1010  ContainerImag... Container OS Image of Windows Server 2016 Technical Preview 5 : Nano Server Installation
    WindowsServerCore              10.0.14300.1000  ContainerImag... Container OS Image of Windows Server 2016 Technical Preview 5 : Windows Server Core Installation

    Running Install-ContainerImage then gives the error:

    Failed to process file in optimization with error: A certificate was explicitly revoked by its issuer. (Exception from HRESULT: 0x800B010C)
    At C:\windows\system32\windowspowershell\v1.0\Modules\Containers\1.0.0.0\Containers.psm1:376 char:9

    Installing WindowsServerCore gives the same error.

    Install-ContainerOSImage -WimPath F:\NanoServer\NanoServer.wim from the latest TP5 iso also gives the same error.

    Thursday, April 28, 2016 8:19 AM

Answers

  • Hi folks, we are tracking a two bugs on Windows 10 Insider builds...

    The first (which is not the bug) effects both 14328 and 14332 - it results in the container host bluescreening when running a container.

    The second bug (this issue) effects 14332 and is due to how we preform code integrity validation on the container image.  It's doesn't effect all systems but on systems it effects we are not aware of any workaround.

    We are actively working on fixes for both of these issues and once they are validated in the insider branch I'll let you know what build number they are fixed in - we're hoping to get them in for the next flight but quality fixes trump fast fixes :).

    Thanks and sorry that your container testing is stalled a bit - you can try TP5 and we even have a script to automate setting up a Tp5 Vm for you (https://msdn.microsoft.com/virtualization/windowscontainers/quick_start/container_setup).


    -Taylor

    Thursday, April 28, 2016 8:26 PM

All replies

  • I think the issue is in the Install-containerimage that check if version of OS is 14300 while yours is 14332. 

    from the Install-containerhost.ps1

    Test-ContainerImageProvider

                    $hostBuildInfo = (gp "HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion").BuildLabEx.Split(".")
                    $version = $hostBuildInfo[0]

                    $InstallParams = @{
                        ErrorAction = "Stop"
                        Name = $imageName
                    }

                    if ($version -eq "14300")
                    {
                        $InstallParams.Add("MinimumVersion", "10.0.14300.1000")
                        $InstallParams.Add("MaximumVersion", "10.0.14300.1010")
                        $versionString = "-MinimumVersion 10.0.14300.1000 -MaximumVersion 10.0.14300.1010"
                    }

    So I suspect that when you run the Install-containerimage will apply the same logi findinf that the two versions (14332.1001 and 14300.1000/1010) are different.

    Thursday, April 28, 2016 9:40 AM
  • Well everything installs fine. It's the Install-ContainerImage / Install-ContainerOsImage part the fail when calling into vmcompute.dll likely the ContainerCiCacheContinue method.
    Thursday, April 28, 2016 11:48 AM
  • Hi folks, we are tracking a two bugs on Windows 10 Insider builds...

    The first (which is not the bug) effects both 14328 and 14332 - it results in the container host bluescreening when running a container.

    The second bug (this issue) effects 14332 and is due to how we preform code integrity validation on the container image.  It's doesn't effect all systems but on systems it effects we are not aware of any workaround.

    We are actively working on fixes for both of these issues and once they are validated in the insider branch I'll let you know what build number they are fixed in - we're hoping to get them in for the next flight but quality fixes trump fast fixes :).

    Thanks and sorry that your container testing is stalled a bit - you can try TP5 and we even have a script to automate setting up a Tp5 Vm for you (https://msdn.microsoft.com/virtualization/windowscontainers/quick_start/container_setup).


    -Taylor

    Thursday, April 28, 2016 8:26 PM
  • Thanks Taylor for the explanation and for getting back to me.

    Thursday, April 28, 2016 8:41 PM
  • Windows Insiders Build 14342 still has this issue unfortunately :(
    Wednesday, May 11, 2016 6:48 PM
  • I also get this error 

    Failed to process file in optimization with error: A certificate was explicitly revoked by its issuer. (Exception from HRESULT: 0x800B010C) At C:\windows\system32\windowspowershell\v1.0\Modules\Containers\1.0.0.0\Containers.psm1:376 char:9

    any news on that?

    Wednesday, June 1, 2016 5:40 PM
  • This is fixed in latest insider build (Windows 10 Build 14352.1002).
    Wednesday, June 1, 2016 5:46 PM
  • ist this error really built in the builds of pre 14352 or is there a workaround?

    14342 is last build from slow ring, not everyone can forward to the next fast ring build.

    (sorry for the big font in the last Post, it was not intended)
    • Edited by rs38 Thursday, June 2, 2016 6:42 AM
    Thursday, June 2, 2016 6:41 AM
  • The issue was first resolved in newer builds, unfortunately no known workarounds.
    Thursday, June 2, 2016 8:20 AM