Table of contents
TOC
Collapse the table of content
Expand the table of content

Known Issues in WMF 5.1

Krishna|Last Updated: 1/9/2017
|
8 Contributors

Note: This information is subject to change.

Starting PowerShell shortcut as Administrator

Upon installing WMF, if you try to start PowerShell as administrator from the shortcut, you may get an "Unspecified error" message. Reopen the shortcut as non-administrator and the shortcut now works even as administrator.

Pester

In this release, there are two issues you should be aware of when using Pester on Nano Server:

  • Running tests against Pester itself can result in some failures because of differences between FULL CLR and CORE CLR. In particular, the Validate method is not available on the XmlDocument type. Six tests which attempt to validate the schema of the NUnit output logs are known to fail.
  • One Code Coverage test fails currently because the WindowsFeature DSC Resource does not exist in Nano Server. However, these failures are generally benign and can safely be ignored.

Operation Validation

  • Update-Help fails for Microsoft.PowerShell.Operation.Validation module due to non-working help URI

DSC after uninstall WMF

  • Uninstalling WMF does not delete DSC MOF documents from the configuration folder. DSC won't work properly if the MOF documents contain newer properties which are not available on the older systems. In this case, run the following script from elevated PowerShell console to to clean up the DSC states.

      $PreviousDSCStates = @("$env:windir\system32\configuration\*.mof",
              "$env:windir\system32\configuration\*.mof.checksum",
              "$env:windir\system32\configuration\PartialConfiguration\*.mof",
              "$env:windir\system32\configuration\PartialConfiguration\*.mof.checksum"
             )
    
      $PreviousDSCStates | Remove-Item -ErrorAction SilentlyContinue -Verbose
    
© 2017 Microsoft