Device Management PowerShell Cmdlets

This module exposes cmdlets that calls into SetupAPI functions and provides device enumeration and management functions.

 
 
 
 
 
4.6 Star
(24)
39,759 times
Add to favorites
Hardware
9/24/2012
E-mail Twitter del.icio.us Digg Facebook
Sign in to ask a question


  • Windows 7 compatibility. Error with Disable-Device
    4 Posts | Last post August 12, 2014
    • Hi, and thank you for this module.
      
      I'm trying to use it in Windows 7 (32bit), and get the following error, when running the command below:
      
          Get-Device | Where-Object -Property Name -eq 'Intel(R) 82566DM-2 Gigabit Network Connection' | Disable-Device
      
          Disable-Device : Error calling SetupDiCallClassInstaller()
          At line:1 char:99
          + ... Connection?" | Disable-Device
          +                    ~~~~~~~~~~~~~~
              + CategoryInfo          : NotSpecified: (:) [Disable-Device], Win32Exception
              + FullyQualifiedErrorId : System.ComponentModel.Win32Exception,DeviceManager.Commands.DisableDeviceCommand
      
      Also i've noticed that using the like operator like this doesn't return anything:
          Get-Device | Where-Object -Property Name -Like 'Intel(R) 82566DM-2 Gigabit Network Connection'
      
      But when a questionmark is added at the end, it does:
          Get-Device | Where-Object -Property Name -Like 'Intel(R) 82566DM-2 Gigabit Network Connection?'
      
      When looking at the value of the Name property, a space seems to be appended at the back, but when adding it to the -like compare, it still doesn't return anything. (so replace the questionmark with a space. This is surprising, since when using -eq, it -doesn't- work when you add the space, but only works when you -don't- add it. This is also the case for some of the other properties, and feels like a bug.
    • I did NOT YOUR QUESTION
    • Hi! I have a same problem on Windows 8 x64
      
      Get-Device | Where-Object -Property Name -eq "Realtek High Definition Audio" | Disable-Device
      
      Disable-Device : Error calling SetupDiCallClassInstaller()
      строка:1 знак:80
      + Get-Device | Where-Object -Property Name -eq "Realtek High Definition Audio" | D ...
      +                                                                                ~
          + CategoryInfo          : NotSpecified: (:) [Disable-Device], Win32Exception
          + FullyQualifiedErrorId : System.ComponentModel.Win32Exception,DeviceManager.Commands.DisableDeviceCommand
    • I'm having exactly the same problem on Windows 8 x64. Is this component being supported?
  • Import-Module fails with HRESULT: 0x80131515
    5 Posts | Last post May 29, 2014
    • The downloaded files may be blocked by Windows due to being downloaded from the Internet. For each of the extracted files, right-click, select "Properties" and then "Unblock".
    • Unblocking the archive itself instead of every single file in it sounds like a better idea to me. This module is meant to be used on Windows 8 and Server 2012 and they come with PowerShell 3.0 and a new cmdlet - Unblock-File.
    • Great feedback Aleksandar! Thanks. :)
    • I also had to add a .NET 4.5 Windows Feature
      
      "Add-WindowsFeature NET-Framework-45-ASPNET"
    • Any other thoughts on why I might be getting this. I've tryed unblocking them I've tryed add-windowsefauter net-framework-45.aspnet.   I'm running Server 2012.  
  • Remove cmdlet
    1 Posts | Last post May 11, 2014
    • Any chance of adding a remove-device
      
      I don't think  saw this question.
      
      Also is this the latest version of this Module, I see '9/24/2012'
      
      I really want to clean up ghosted NICS etc.
      
      Right now I do this manually via: set devmgr_show_nonpresent_devices=1
      
      Then manually delete them.
      
      So I guess support for hidden devices would be cool, not sure if I missed this feature?
  • Windows 8.1 compatibility
    3 Posts | Last post March 27, 2014
    • jrv
      GEt_Driver works  - Get-Device throw exception 
      
      Windows 8.1 / PowerShell V4 (WMF 4.0)
      PS C:\scripts> get-device
      get-device : Error calling SetupDiGetDeviceProperty()
      At line:1 char:1
      + get-device
      + ~~~~~~~~~~
          + CategoryInfo          : NotSpecified: (:) [Get-Device], Win32Exception
          + FullyQualifiedErrorId : System.ComponentModel.Win32Exception,DeviceManager.Commands.GetDeviceCommand
    • Hi jrv,
      are you running this on a "elevated" PowerShell session?
      Thanks,
      Ricardo
    • I am having the same error message as jrv. And yes I'm in an elevated session
  • win7 compatibility
    1 Posts | Last post November 20, 2012
    • When is the win7 compatible version coming out?
      
      
  • A proper name
    2 Posts | Last post September 07, 2012
    • The module has a generic name - PSCmdlet. A proper name should be something like DeviceManagement. If the name is PSCmdlet how can user know what to expect from it when he lists all the available modules on a system?
      
      Also, the cmdlets are missing help. They need at least a synopsis, description, and examples. 
    • Aleksandar,
      The help implementation is on the way, I plan to refresh the bits soon.
      Regards,
      Ricardo
      
  • Windows 7 compatibility and overall usage
    1 Posts | Last post August 25, 2012
    • Thanks for providing this module Ricardo.
      
      For anyone interested, the only commands that work on Windows 7 are the *-Device cmdlets.  This is still useful for documenting devices on your machine and what version drivers they have.  
      
      Especially useful for companies that need to know what devices are in their environment and which drivers they are using and/or need.  Devices sometimes show up as 'Unknown Device' in device manager and the easiest way to determine which driver you need is to search for the InstanceID and this module allows you to gather that for all devices easily.
11 - 17 of 17 Items