Import-Module PSCX error in pscx.wmi.psm1 - Get can not be found

Topics: Developer Forum, User Forum
Jun 1, 2012 at 10:51 AM

I just installed upgrade from V2 to V3. , and assuming that PSCX 2.0 should work on V3. 

Unzipped PSCX is in my <user home>/WindowsPowerShell/module location, and then

Import-Module PSCX. Ran into following errors.  

Any help much appreciated.

Property 'Get' cannot be found on this object. Make sure that it exists.At C:\Users\myname\Documents\WindowsPowerShell\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:\Users\myname\Documents\WindowsPowerShell\Modules\Pscx\Modules\Wmi\Pscx.Wmi.psm1' was not loaded because no valid module file was found in any module directory.At C:\Users\myname\Documents\WindowsPowerShell\Modules\Pscx\Pscx.psm1:197 char:4+             Import-Module $path -DisableNameChecking+             ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~    + CategoryInfo          : ResourceUnavailable: (C:\Users\myname\...i\Pscx.Wmi.psm1:String) [Import-Module], FileNotFoundException    + FullyQualifiedErrorId : Modules_ModuleNotFound,Microsoft.PowerShell.Commands.ImportModuleCommand

Jun 3, 2012 at 11:32 PM

2.0 doesn't work well with PowerShell v3.  There is a 2.1 beta on the PSCX site right now that works better but in a day or so we'll post a new version PSCX 3.0 that targets PowerShell V3 only.  Pscx3 should work in a side-by-side mode with Pscx 2.0 since both are module based.

Sep 10, 2012 at 9:58 AM
Edited Sep 10, 2012 at 11:15 AM

I've installed the PSCX 3.0 beta but I still get this error.


My bad, I thought I'd overwritten v2 but hadn't!