8 Replies Latest reply on Oct 2, 2014 1:22 PM by peetz

    Latest Windows patches break PowerCLI ImageBuilder ?!

    peetz Master
    User ModeratorsvExpert

      Hi all,

      since yesterday I'm seeing strange errors when using the ImageBuilder cmdlet Get-EsxImageProfile. It is simple to reproduce: Open a PowerCLI session and run the following commands


      Add-EsxSoftwareDepot https://hostupdate.vmware.com/software/VUM/PRODUCTION/main/vmw-depot-index.xml



      The Get-EsxImageProfile cmdlet will throw the following error:


      Get-EsxImageProfile : The parameter 'name' cannot be an empty string.

      Parameter name: name

      At line:1 char:1

      + Get-EsxImageProfile

      + ~~~~~~~~~~~~~~~~~~~

          + CategoryInfo          : NotSpecified: (:) [Get-EsxImageProfile], ArgumentException

          + FullyQualifiedErrorId : System.ArgumentException,VMware.ImageBuilder.Commands.GetProfiles


      However, -name is NOT a mandatory parameter. Strangely enough, after seeing this error subsequent Get-EsxImageProfile commands will throw even weirder errors ... It looks like the whole PowerCLI session is corrupted in a way.

      Weird is also that something like Get-EsxImageProfile "ESXi-5.5*" will work, but Get-EsxImageProfile "*" will throw the same error.


      These errors did not happen before yesterday, so what was changed? This is a Windows 8.1 x64 machine, and I installed the latest Microsoft patches that were published this week. Another user (who was trying to use my ESXi-Customizer-PS script) reported a similar error on a fully patched Windows 7 x64 machine. I'm not sure if that affects 32bit and other Windows versions as well, but it seems to happen independently from the PowerCLI version. I was trying with PowerCLI 5.5 R2 on top of PowerShell 4.0 first, then upgraded to the latest PowerCLI 5.8 R1, but this did not make the error going away. The other user was using PowerCLI 5.8 R1 on top of PowerShell 3.0.


      Can someone please confirm this behavior?

      How do you file a bug for PowerCLI to address that to the development team?