Hewlett-Packard has done it again. Agrevate users with firmware updates (this seems to be the cause) that result in printer problems. Error 83C0000B is shown with a blue screen on the printer.
Like before, it appears that this is the result of a firmware update that includes dynamic security features. In the past, this has resulted in printers suddenly not working anymore if non-original ink or toner cartridges were used.
In the current case, it appears the error pertains to the OfficeJet 902x series printers. Resetting, disconnecting and reconnecting, unplugging, and plugging all seem to have no effect. As it would not be the case with a firmware issue.
Solving error 83C0000B
The only real solution would be an update from HP for the printer. That means you need to check the HP support website for a newer firmware version than the current version 002.2313A, dated May 16, 2023.
Visit the HP site for your printer model, for an OfficeJet Pro 9020 AiO for example. Then open the section with the firmware updates. Click Download to download the firmware installer file, and execute it after the download completes.
Note: You may need to change the OS selection to show the firmware option in the list.
The installer will show the HP Printer Update window where you need to select your printer and click the Update button.
Let’s hope HP releases an update soon! You are not alone with this problem.
In any case, make sure to contact HP support, as they might be able to offer a solution or replacement. Their generic instuctions for a full power down and reset do not seem to help. But specific instuctions for your model to do a SemiFull reset, as they call it, might be helpful.
Going back to a previous firmware version
In theory, downgrading the firmware would be a viable option as well to solve error 83C0000B. It was a solution in the past when HP first started using dynamic security to ensure people used original cartridges and toners from HP.
Using a USB stick, you can load older firmware (.ful2 extension) on the HP printer to install an older version. The process has a few challenges though. You need the exact match of firmware for your printer, and the steps need to be followed exactly to prevent problems during the downgrade process.
The Device Manager is a program to control all devices in a Windows system. It has been part of Microsoft Windows since Windows XP and is still present in Windows 11. Under normal circumstances, the Device Manager is not used, but if you have a problem with a device, the Device Manager can be used to solve it. The Device Manager error codes show the problems with hardware devices or drivers.
What are Device Manager Error Codes?
The error codes for devices in the Device Manager show the type of problem the device is experiencing. Although a lot of device issues are driver-related, devices can also show errors that are the result of hardware conflicts or resource problems. The error code shows the type of error, accompanied by an error message. If more details are available, the message can include an additional error message.
How Can I View a Device Error Code?
To view the error code for a device that has a problem, you can use the Device Manager program which is part of Windows. Here are the steps.
Open the Device Manager. Press the Windows + R keys simultaneously. In the Run dialog box, type “devmgmt.msc” and click Run or press Enter.
The Device Manager window will show. Locate the device with the error and right-click it. Tip: click the arrows to the left of the device category to show all devices in that category.
In the popup menu, select Properties.
Make sure the General tab is active (this should be the default).
You can see the device error code in the Device status section of the dialog box.
Tip: You can select and copy the text in the Device status section to use it for searching or communicating with support. Simply click and drag over the text with the mouse cursor and press Ctrl + C to copy it to the clipboard.
Close the device Properties dialog box when done. And then close the Device Manager window.
Note: In case you do not see the device in the tree list in the Device Manager, use the Show -> View hidden devices option to show all installed devices. After that, all devices that are not connected (or better: not seen as connected by Windows), will be included and shown in a lighter tone thant the other devices.
List of Device Manager Error Codes
To solve a problem with a device, you will need to know what the error code means. Below is a list of all possible error codes for Windows devices with their meaning and possible solutions.
Code 1 – This device is not configured correctly. (Code 1)
This is a driver-related problem. The steps in the how to fix section should help solve the code 1 error.
Code 3 – The driver for this device might be corrupted, or your system may be running low on memory or other resources. (Code 3)
This is either problem with limited available resources (memory) or a driver-related problem. The steps in the how to fix it section should help fix code 3 errors.
Code 9 – Windows cannot identify this hardware because it does not have a valid hardware identification number. For assistance, contact the hardware manufacturer. (Code 9)
If a device cannot be identified by the hardware ID, Windows cannot find a driver for it. As a result, the device cannot work. Either the hardware is faulty, or a firmware update is required.
Code 10 – This device cannot start. Try upgrading the device drivers for this device. (Code 10)
This is a driver-related problem. The steps in the how to fix section should help solve the code 10 error. If the fix does not work, the device might be defective.
Code 12– This device cannot find enough free resources that it can use. If you want to use this device, you will need to disable one of the other devices on this system. (Code 12)
This is a problem related to the resources assigned to a device. Conflicting or inadequate I/O addresses, interrupts, or memory space are common causes of code 12 errors. This error does not happen much on modern PCs but can be found with older Windows systems using older hardware.
Code 14 – This device cannot work properly until you restart your computer. To restart your computer now, click Restart Computer. (Code 14)
As the error indicates, restart your Windows PC to solve code 14 errors.
Code 16 – Windows cannot identify all the resources this device uses. To specify additional resources for this device, click the Resources tab and fill in the missing settings. Check your hardware documentation to find out what settings to use. (Code 16)
This error indicates that the device needs more configuration. In normal circumstances, devices are plug-and-play, and resources are assigned/allocated automatically. The Device Manager can be used to assign resources manually to the device. Again, this would only occur with older systems with older Windows versions.
Code 18 – Reinstall the drivers for this device. (Code 18)
This is a driver-related problem. The steps in the how to fix section should help solve the code 18 error.
Code 19 – Windows cannot start this hardware device because its configuration information (in the registry) is incomplete or damaged. (Code 19)
This is a driver-related problem. The device driver configuration information is not complete or has duplicate entries. Uninstalling the device and reinstalling the drivers should fix code 19 errors. If not, a system restore point can be used to restore a working configuration.
Code 21 – Windows is removing this device. (Code 21)
This error is a temporary one. Once the device is removed by Windows the error will automatically disappear. Rebooting the system will ensure the error clears as well.
Code 22 – This device is disabled. (Code 22)
Use the Device Manager to re-enable the device.
Code 24 – This device is not present, is not working properly, or does not have all its drivers installed. (Code 24)
This is a device or driver-related problem. If the device is not needed, remove the device. Otherwise, make sure you install the drivers to allow the device to properly function.
Code 28 – The drivers for this device are not installed. (Code 28)
This is a driver-related problem. The steps in the how to fix section should help solve the code 28 error.
Code 29 – This device is disabled because the firmware of the device did not give it the required resources. (Code 29)
Windows detects a device, but it does not respond as it should. It can be defective, but it could also simply be disabled in the BIOS of the motherboard (e.g. for audio, network, or video devices). Enable the device in the hardware configuration of the BIOS, and follow the steps in the how to fix section.
Code 31 – This device is not working properly because Windows cannot load the drivers required for this device. (Code 31)
This is a driver-related problem. An incorrect or outdated driver can cause this error. The steps in the how to fix section should help solve the code 31 error.
Code 32 – A driver (service) for this device has been disabled. An alternate driver may be providing this functionality. (Code 32)
This is a driver-related problem. Each driver is configured in the Windows Registry as a service (under the key: Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\). That service has a start type. If the start type is set to disabled, the code 32 error will show. Possible values are: Boot (0), System (1), Automatic (2), On demand (3), and Disabled (4).
The steps in the how to fix section will solve the code 32 error (use the device uninstall option).
Code 33 – Windows cannot determine which resources are required for this device. (Code 33)
This is a device configuration error, or the device is faulty. Communication with a device requires things like interrupts, I/O ports, direct memory access, and more. If these values cannot be identified for the device, it will not function and result in the code 33 error. Check the hardware and its configuration in the BIOS. Possibly reset the BIOS or update the firmware for the device and or motherboard.
Code 34 – Windows cannot determine the settings for this device. Consult the documentation that came with this device and use the Resource tab to set the configuration. (Code 34)
This error is similar to the code 16 error. Additional device configuration settings are required that need to be manually configured in the Resource tab for the device in the Device Manager.
Code 35 – Your computer’s system firmware does not include enough information to properly configure and use this device. To use this device, contact your computer manufacturer to obtain a firmware or BIOS update. (Code 35)
This is a hardware configuration problem. Try loading default BIOS settings, or upgrading the BIOS of the motherboard. Code 35 error is normally only found on older systems.
Code 36 – This device is requesting a PCI interrupt but is configured for an ISA interrupt (or vice versa). Please use the computer’s system setup program to reconfigure the interrupt for this device. (Code 36)
This error is a hardware misconfiguration error. Interrupt assignments can be checked and changed in the BIOS. If the settings cannot be changed, a BIOS upgrade may help solve the problem. Code 36 errors will typically only occur on older systems since modern motherboards do not have ISA slots anymore.
Code 37 – Windows cannot initialize the device driver for this hardware. (Code 37)
This is a driver-related problem. The steps in the how to fix section should help solve the code 37 error.
Code 38 – Windows cannot load the device driver for this hardware because a previous instance of the device driver is still in memory. (Code 38)
Reboot your system to solve the code 38 error. This will clear any previously running instances of the device driver.
Code 39 – Windows cannot load the device driver for this hardware. The driver may be corrupted or missing. (Code 39)
This is a driver-related problem. The steps in the how to fix section should help solve the code 39 error.
Code 40 – Windows cannot access this hardware because its service key information in the registry is missing or recorded incorrectly. (Code 40)
As has been mentioned in the code 32 error description, each device has a service associated which is configured in the Windows Registry. The code 40 error can be solved by reinstalling the driver. See the how to fix section.
Code 41 – Windows successfully loaded the device driver for this hardware but cannot find the hardware device. (Code 41)
If a driver is not automatically installed for a device, it needs to be manually installed. This can happen for non-plug-and-play devices. Once the driver is installed and no device is present, the code 41 error is the result. Make sure the device is connected and turned on (if applicable). Then reboot. If that does not work, reinstall the driver.
Code 42 – Windows cannot load the device driver for this hardware because there is a duplicate device already running in the system. (Code 42)
This is a driver-related problem. It can be a bus error or a duplicate device error. Both are normally resolved by restarting the computer. In some cases, an actual power down is required before restarting the computer.
Code 43 – Windows has stopped this device because it has reported problems. (Code 43)
In the case of USB devices, the status will often say “A request for the USB device descriptor failed.”.
First, try the steps in the how to fix section. If the error persists after those steps, it is most likely a hardware problem. Check the device manual or contact the hardware manufacturer.
Code 44 – An application or service has shut down this hardware device. (Code 44)
This is a temporary error status. Once the system is rebooted, the device should be working as before. If a reboot does not help, power down the PC before restarting. If the problem persists, you need to identify the service or application responsible for shutting down the device. The Windows Event Viewer can be helpful for this.
Code 45 – Currently, this hardware device is not connected to the computer. To fix this problem, reconnect this hardware device to the computer. (Code 45)
The error message indicates the problem, a device is installed but not present in the PC. Reconnect the device to solve the code 45 error. The error is normally associated with Bluetooth devices or USB devices, but the error can occur for all types of devices. For devices that cannot manually be connected to the system, follow the steps in the how to fix section.
Code 46 – Windows cannot gain access to this hardware device because the operating system is in the process of shutting down. The hardware device should work correctly next time you start your computer. (Code 46)
This error code is self-explanatory and would not be seen in normal Windows operating conditions.
Code 47 – Windows cannot use this hardware device because it has been prepared for safe removal, but it has not been removed from the computer. To fix this problem, unplug this device from your computer and then plug it in again. (Code 47)
This error code indicates that the device has been selected for Safe Removal. The Safe Removal action is used for USB storage devices like USB sticks and external hard drives. If access to the device is required, first try unplugging it and then plugging it back again. If that does not work, restart the PC.
Code 48 – The software for this device has been blocked from starting because it is known to have problems with Windows. Contact the hardware vendor for a new driver. (Code 48)
This is a driver-related problem. The driver software for the device is not compatible with the Windows version you are running. This can happen after a Windows upgrade, for example. Install an updated, compatible driver to solve the code 48 error. For older systems, make sure to check for architecture compatibility (32-bit / 64-bit). In some cases, older driver software can still be used when executed in compatibility mode.
Code 49 – Windows cannot start new hardware devices because the system hive is too large (exceeds the Registry Size Limit). (Code 49)
This error is a system error related to the Windows Registry. The system hive mentioned in the error message is a part of the registry that contains all critical information for Windows to function. If it becomes too large, the best way to address it is by removing any devices that are no longer used. This will free up the necessary space in the system hive to allow new hardware to be added.
Code 50 – Windows cannot apply all of the properties for this device. Device properties may include information that describes the device’s capabilities and settings (such as security settings for example). To fix this problem, you can try reinstalling this device. However, we recommend that you contact the hardware manufacturer for a new driver. (Code 50)
This is a driver-related problem. The steps in the how to fix section should help solve the code 50 error.
Code 51 – This device is currently waiting on another device or set of devices to start. (Code 51)
This is a rare error, and according to Microsoft, there is no solution to the problem. Try the steps in the how to fix section if you see this error. Microsoft recommends checking for other devices in the same device category for errors. If there are any, solve those first. Since it is a temporary problem, waiting it out can also automatically solve the problem.
Code 52 – Windows cannot verify the digital signature for the drivers required for this device. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source. (Code 52)
Device drivers run at a high privilege level in the Windows operating system. As such, they need to function reliably and need to be safe. For this reason, digital signatures are used to secure the device driver files. Without a digital signature, drivers cannot be installed in the latest Windows versions. Make sure you get a signed driver for your device to solve error code 52. If signed drivers are not available you can install unsigned drivers with additional steps.
Code 53 – This device has been reserved for use by the Windows kernel debugger for the duration of this boot session. (Code 53)
This error would not be visible in normal Windows operating modes. Developers may see the error if using kernel debugging. Disabling the debug mode will fix the code 53 error and let the device operate normally.
Code 54 – This device has failed and is undergoing a reset. (Code 54)
This error indicates that the device failed to respond correctly to an ACPI reset. Since the device is not functioning after that, a code 54 error is shown. To solve the problem, restart the PC. If that does not solve the issue, shut down the PC before restarting.
What Are Common Device Errors?
From all the listed device manager error codes, the most common ones are code 10, code 22, code 28, and code 39. You can follow the links to see specific steps that can be used to solve these errors. For all other errors, please follow the steps below to fix them. Some of the errors can happen for all types of devices, while other errors are more common with a specific device type.
How to Fix Device Errors?
To solve device-related problems several steps can be used. Even though the causes are different, the solution to many of these problems requires the same actions.
Reboot the system. This will ensure that no current state issues are causing the problem. Pending driver installs or uninstalls, pending reboot after update or software removal, and plugging and unplugging of devices, are all examples of situations that can require a restart to make sure the system is error-free.
Check for Windows Updates. Occasionally, pending updates can cause device errors. When a driver update is pending that addresses a problem for example. But even Microsoft generic system patches can address errors related to devices and drivers.
Run the Windows troubleshooter. This option is available for the latest Windows versions. Microsoft has included a troubleshooter function to solve common problems, including devices. The troubleshooter can reset a driver, restart a service, modify the registry, and others to try to solve the device problem.
Reinstall the driver for the device. As mentioned early on, a lot of device-related problems are caused by a device driver. Use the Device Manager to uninstall the device (and optionally the driver software). Then reboot or scan for hardware changes (using the Action menu) to reinstall the device with appropriate drivers. In the case of USB devices, uninstalling the parent device (USB Hub or USB Host Controller may be required as well).
Use a System Restore point to bring the Windows PC configuration back to a previous, working state. This solution can work for errors related to previously working configurations. Having the system restore option enabled is also a pre-condition.
For specific error codes, special steps may be required which will typically be indicated in the error message. E.g. if more memory is needed (code 3), if a reboot is required (code 14), or if a hardware device needs to be connected (code 45). Simply execute the indicated actions.
All hardware in a Windows PC is registered as a hardware device. Windows uses device drivers to communicate with these hardware devices. New drivers are added when new hardware is detected. New drivers can be installed automatically if device support is included with Windows. If not, drivers need to be installed manually. But what happens if you remove a hardware device or no longer use a device? Do you need to uninstall devices in Windows, or does that happen automatically?
For onboard hardware, like a CPU, bus controllers, and similar hardware, it is simple. The hardware is present in the system, so the device and driver need to be configured in Windows. But for external hardware (printers, scanners, mobile phones, and others) this is not straightforward. A lot of external devices are connected through USB, Bluetooth, or Wi-Fi. There is no automatic way to know if these devices are still being used.
Steps to uninstall devices in Windows
When a device is either present in a PC or connected to the PC, the device will show up in the Device Manager. To uninstall the device the Device Manager can be used. Right-clicking a device in the Device Manager will show a popup menu with the option to uninstall it. When selected, you can also confirm whether the driver software should be removed.
But what if the device is no longer present in the PC? Or the hardware is not connected and not available anymore? In that case, the device will not show up in the Windows Device Manager. But the device configuration and driver still exist on the system.
To remove a device from Windows when the hardware is no longer present, we first need to tell Windows to show these non-present devices in the Device Manager.
Note: These instructions apply to all Windows versions. Variations in the text on buttons, confirmations, and popup menus can be present.
Press the Windows + R keys to show the Run dialog.
Type cmd, click the Run button, or press Enter to open a Command Prompt window.
In the Command Prompt window, type set devmgr_show_nonpresent_devices=1 and press Enter. What this does is set an environment variable in Windows that is used by the Device Manager to show the non-present devices. Tip: Type set and press Enter to see all environment variables. This allows you to check that the value was set properly.
Close the Command Prompt window by typing exit and pressing Enter. Note: For Windows 7 and earlier, skip this step, as Windows clears the devmgr_show_nonpresent_devices flag automatically when the Command Prompt window is closed.
Next, open the Device Manager. Either use the Start menu or type devmgmt.msc in the Run box like in step 1.
In Device Manager, click the View menu and then click Show hidden devices.
You will now be able to see devices that are not connected to the computer.
Expand the category for the device to uninstall. Non-present devices will show with a grayed-out icon.
Right-click a non-present device.
In the popup menu, choose Uninstall device.
Confirm the removal of the device by clicking the Uninstall button in the Uninstall Device window.
Note: For some devices, the Uninstall Device confirmation window will also show a checkbox to delete the driver software for the device. Select that if the driver for the device is no longer needed.
The Device Manager window will refresh and the uninstalled device will no longer be shown.
Close the Device Manager window when done.
Why uninstall devices in Windows?
The need to uninstall a device in Windows is not common. In many cases, hardware devices are managed automatically, or only need to be dealt with one time during installation.
But there are two cases where uninstalling a device is required.
Reset the hardware device
If a device is showing an error or is not functioning properly, it can often be a problem with the device configuration or the driver software. Using the steps to uninstall a device in Windows, the device configuration is reset and the driver can also be reloaded (with the driver software uninstall option). Many device-related errors can be solved this way, so knowing how to uninstall a device in Windows can be very useful.
Solve error code 49
Error case 49 in the device manager means that Windows cannot start a new hardware device. This is a specific error that can occur when a new device is added and needs to be configured. All device configuration is stored in the Windows Registry. And since device information is critical for Windows to operate, the configuration details are stored in the System Hive. This is the core part of the Windows Registry that is kept in memory for quick access.
If the System Hive grows too large, it will exceed the size limit. That will then result in error code 49 if a device is attempted to be started. This error happens more on older Windows versions, simply because resource limits and size limits for the registry storage space could be a problem.
If a device shows a code 49 error, the solution is often to remove all non-present devices to free up space in the System Hive. If that does not solve the problem, try cleaning up the registry to free up more space.
Critical errors in Windows result in a blue screen showing the error details. The DRIVER PNP WATCHDOG error is one of these types of errors. Depending on the Windows version it will also show error code 0xc1900101. As the error message already indicates, the error is related to a driver and to something called PNP. PNP refers to plug-and-play and is basically a concept that allows devices in computers to be automatically detected and installed.
The error mostly occurs during a Windows installation or an upgrade. Since the error relates to a driver, which operates on a high-security level in Windows, the error results in the operating system being halted.
Causes for the Driver PNP Watchdog Error
Like any BSOD error on Windows, it is best to check the crash dump or minidump if available. The Microsoft WinDbg tool can be used to analyze a crash dump file. This process will help identify which driver caused the crash. That does not always mean the driver itself is causing the problem, but it helps pinpoint where to look for a solution.
The most common causes for this problem are disk or disk controller related. The inability to read or write data at some point can cause the blue screen error. Disk controllers, USB controllers, Raid controllers, and SATA controllers, all need the right driver to prevent problems. But even a faulty SSD can cause this type of error!
If your Windows device does not start at all, this will limit the troubleshooting options. The first thing to try is to start Windows in Safe Mode. If that succeeds, you can execute some, if not all, of the steps in the section Windows will still boot.
If Windows will not start at all, the only options are to use a bootable USB stick for your Windows version.
Make sure you can boot from the USB by configuring the BIOS options.
Plug the USB stick into a USB port and reboot the device.
When the screen shows Press any key to boot from USB, press a key.
When the Windows install screen comes up select the option Repair your computer in the bottom left. This will restart the device again and get you to Advanced Recovery.
Select the Advanced options to see more troubleshooting options.
Next, select Troubleshoot.
You can now try the Startup Repair option, use the Command Prompt for disk checking options, Uninstall Updates to revert to a previous configuration, change UEFI Firmware settings to configure the hardware of the device, or use System Restore if you have any previous restore point that can be used to restore the system.
Note: For Windows 10, the options are slightly different, but offer similar recovery and repair options.
If none of these steps work, try resetting the BIOS or UEFI to load the default options. The Advanced Configuration and Power Interface (ACPI) feature of the BIOS will allow devices to be configured automatically in most cases, which will ensure correct settings. Apart from that, try the diagnostic options in the BIOS/UEFI to test the hardware. If a problem is found at the hardware level, a component might need to be replaced. Setting a SATA controller to IDE has also helped some people solve this problem.
Although a bit more hands-on, check the cables in the system. A loose connector on any of the internal devices (not just storage related) can cause the error.
If the solutions so far don’t work, the only remaining option is to completely reinstall Windows from the bootable USB. I would recommend formatting (or initializing) the drive you will install Windows on. If there are any problems with the disk they can be detected during that process.
Windows will still boot
If you can still start Windows, there are more options to troubleshoot and fix the Driver PNP Watchdog error. Use the steps below to try and solve the error. The sequence is not critical, as any of these steps can provide the solution to the error depending on the actual cause of the problem.
Use the Disk Manager to make sure the disks in the system are properly detected and file formats are correct.
Disk Management can be started by right-clicking the Start menu button in Windows 11 and selecting Disk Management in the menu. It is also accessible in the Computer Management
If you are using an SSD, check your drive with a third-party tool. Most manufacturers provide software for this (e.g. Samsung Magician, SanDisk Dashboard, Intel – Solidigm Storage Tool). These tools can tell you if the SSD is functioning properly and if the drivers are working correctly.
Use the standard Windows command line tools to check the disk and check the system files. Run a command prompt with administrator-level privileges and then run these commands: CHKDSK /F /R SFC /SCANNOW The first command runs a disk check with options to fix errors on the disk and locate bad sectors. The second command scans for the integrity of the Windows system files and repairs any errors found as far as possible.
Note: If the drive is in use, you can opt to run the disk check at the next startup. This will happen when you run the chkdsk command on a system drive.
Use the Device Manager to check the device drivers. Open the Device Manager from the Start In the Device Manager window, right-click the devices and use the popup menu option Update driver to make sure the latest driver is installed for the device.
Start with the devices under the Storage controllers and Disk drives categories. If you were able to use the WinDbg tool to pinpoint the driver causing the crash, then focus on that device. It may also be possible that you need to do a driver rollback rather than an update. A newer version of the driver can just as easily cause the error as an older version.
Hopefully, the above tips will help you solve your Driver PNP Watchdog error and enable normal use of Windows. If you have any different experiences with this type of error, including alternate solutions, please do leave a comment.
For help finding any new, missing and updated drivers, we suggest using the DriverFinder software.
All Apple devices that can be connected to a PC using the USB port will use the Apple mobile device driver for Windows. To check which version of this driver is installed, use the following steps:
Make sure the iPad, iPhone or iPod is connected to the PC using a USB cable. (Otherwise it will not show up in the Device Manager, and you cannot check the version with these steps.)
Open the Windows Device Manager from the Control Panel, or type “devmgmt.msc” at the Start menu.
In the Device Manager, expand or open the Universal Serial Bus Controllers group.
Locate the Apple Mobile Device USB Driver, and right-click this device.
In the popup menu, select Properties.
Next select the Driver tab.
Check the Driver Date and Driver Version of the Apple USB driver to see if you have the latest version of the driver.
In case you do not see the Apple Mobile Device USB Driver under the Universal Serial Bus controllers category, it is possible that it is listed under the Universal Serial Bus devices categories.
The steps are the same, rick-click the Apple Mobile Device USB Composite Device, and in the popup menu select Properties and then select the Driver tab.
To update an Apple mobile device driver, you normally need to install the updated iTunes application. The iTunes software is quite large (install requires 400 MB of disk space), and you might not use it at all. So, if you download the stand alone Apple USB driver update using DriverFinder, you can simply update the driver without the need to download and install the complete iTunes software.
Once downloaded, simply run the AppleMobileDeviceSupport.msi (or AppleMobileDeviceSupport64.msi for 64-bit Windows versions) to install the new driver.
When you plug your iPod, iPhone or iPad, the new driver will automatically be used!