How to use the command 'Enable-PnpDevice' (with examples)

The Enable-PnpDevice cmdlet in PowerShell is a powerful tool that is used to enable Plug and Play (PnP) devices in a Windows environment. This command allows administrators to re-enable hardware devices that have been previously disabled. The functionality is exclusively available through PowerShell, and administrative privileges are required to execute the command. The cmdlet can be extraordinarily useful in scenarios where certain hardware devices need to be enabled after being unintentionally or temporarily disabled, thereby restoring their functionality without requiring a full system restart or manual intervention through the Device Manager.

Use case 1: Enable a device

Code:

Enable-PnpDevice -InstanceId 'RETRIEVED USING Get-PnpDevice COMMAND'

Motivation for using this example:

This use case is particularly relevant when a specific device is disabled, perhaps due to a manual action or a system issue, and needs to be re-enabled to resume its intended functionality. For instance, a network adapter might be disabled accidentally, rendering the system unable to connect to the internet. By using this command, an administrator can quickly re-enable the adapter without delving into the graphical Device Manager interface, thus saving time and reducing the potential for errors.

Explanation of arguments:

• -InstanceId: This parameter specifies the unique instance ID of the PnP device that needs to be enabled. The instance ID can be retrieved using the Get-PnpDevice cmdlet. The ID uniquely identifies each device on the system and ensures that the correct device is targeted for re-enabling.

Example output:

Upon executing the command, you may not receive an explicit success message if the operation completes without issue. Instead, if you run Get-PnpDevice again, the device should now appear as enabled in the output, verifying that the operation was successful and the device is operational.

Use case 2: Enable all disabled PnP devices

Code:

Get-PnpDevice | Where-Object {$_.Problem -eq 22} | Enable-PnpDevice

Motivation for using this example:

This scenario is useful in environments where multiple devices are disabled, perhaps due to a system policy or a misconfiguration. By enabling all devices that are disabled with a specific problem code, administrators can efficiently address widespread device issues across a system. This is especially beneficial in scenarios where manually enabling numerous devices via the GUI would be cumbersome and time-consuming.

Explanation of arguments:

• Get-PnpDevice: Retrieves all PnP devices within the system.
• Where-Object {$_.Problem -eq 22}: Filters the list to include only those devices with a problem code of 22, which indicates that the device is disabled.
• Enable-PnpDevice: Once filtered, this cmdlet enables those devices, restoring their operational status.

Example output:

Similar to the previous point, upon success, no specific confirmation message is shown. However, if you re-run Get-PnpDevice, devices previously listed with a problem code of 22 will now appear as enabled, confirming the cmdlet’s successful execution.

Use case 3: Enable a device without confirmation

Code:

Enable-PnpDevice -InstanceId 'RETRIEVED USING Get-PnpDevice COMMAND' -Confirm:$False

Motivation for using this example:

In environments where scripting and automation are key, it is often beneficial to bypass manual confirmation prompts. This can streamline automated processes, eliminating the need for human intervention and allowing for unattended execution. This particular use case is ideal for scripts designed to run autonomously or during off-peak hours without waiting for user input.

Explanation of arguments:

• -InstanceId: Identifies the specific device to be enabled.
• -Confirm:$False: Suppresses the prompt for confirmation, allowing the command to proceed without user input or further confirmation requests.

Example output:

No new output will be received, but like the prior examples, confirming the device’s enabled state via Get-PnpDevice indicates success.

Use case 4: Dry run of what would happen if the cmdlet runs

Code:

Enable-PnpDevice -InstanceId 'USB\VID_5986&;PID_0266&;MI_00\7&;1E5D3568&;0&;0000' -WhatIf:$True

Motivation for using this example:

Before executing potentially disruptive commands on a production system, it’s wise to perform a test run or “dry run” to understand the command’s impact. The -WhatIf parameter allows administrators to simulate the command’s effect, providing a description of actions the cmdlet would perform without making any actual changes or enabling devices.

Explanation of arguments:

• -InstanceId: Specifies the precise device intended for enabling.
• -WhatIf:$True: This parameter tells PowerShell to simulate the command’s actions rather than executing them. It acts as a precautionary check to confirm that the correct command syntax and parameters are chosen without making changes to system configurations.

Example output:

The output will show a descriptive message indicating what would happen if the cmdlet runs. For example: “What if: Performing the operation…”

Conclusion:

The Enable-PnpDevice cmdlet is an effective method for managing the status of PnP devices using PowerShell. Whether enabling a single device, multiple devices, bypassing confirmations, or simulating the command’s impact, these examples demonstrate the versatility and efficiency of PowerShell in system administration. Each use case provides unique advantages in maintaining system hardware functionality while optimizing administrative processes.