Property 'Get' cannot be found on this object. Make sure that it exists.


Property 'Get' cannot be found on this object. Make sure that it exists.
At C:\Windows\system32\WindowsPowerShell\v1.0\Modules\Pscx\Modules\Wmi\Pscx.Wmi.psm1:8 char:6
  • if (!$acceleratorsType::Get.ContainsKey($name))
  • ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    • CategoryInfo : NotSpecified: (:) [], ParentContainsErrorRecordException
    • FullyQualifiedErrorId : PropertyNotFoundStrict
      Import-Module : The specified module 'C:\Windows\system32\WindowsPowerShell\v1.0\Modules\Pscx\Modules\Wmi\Pscx.Wmi.psm1
      ' was not loaded because no valid module file was found in any module directory.
      At C:\Windows\system32\WindowsPowerShell\v1.0\Modules\Pscx\Pscx.psm1:197 char:4
  • Import-Module $path -DisableNameChecking
  • ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    • CategoryInfo : ResourceUnavailable: (C:\Windows\syst...i\Pscx.Wmi.psm1:String) [Import-Module], FileNot
    • FullyQualifiedErrorId : Modules_ModuleNotFound,Microsoft.PowerShell.Commands.ImportModuleCommand
Closed Oct 17, 2013 at 2:25 PM by r_keith_hill


r_keith_hill wrote Sep 7, 2012 at 1:46 PM

This has already been fixed in trunk (3.0) and the 2.1 branch. We will be releasing release candidates shortly with the fix.

jmanning wrote Sep 24, 2012 at 2:42 PM

Keith - is there a patch/diff we can apply to 2.0 installs in the meantime?


r_keith_hill wrote Sep 24, 2012 at 4:55 PM

If you can't move to the 2.1 RC (now posted) then your best bet is to grab the 2.1 ZIP file and extract just the Pscx\Modules\Wmi.Pscx.Wmi.ps1 file OR you could grab the contents of that file via the source tab and use that to overwrite your 2.0 version.