Archive for October, 2009

Logitech iTouch Driver Update

October 15th, 2009 No comments

Logitech International is a well-known provider of computer peripherals as well as other digital devices based in Romanel-sur-Morges, Switzerland. The company creates and markets products like keyboards, mice, game controllers, microphones and webcams for computers. Logitech also develops home and computer speakers, headphones, wireless audio devices as well as audio devices for mobile phones and media players.

Aside from its headquarters in Switzerland, the company also has offices throughout Europe, as well as in Asia, Fremont,California and in other parts of America. Logitech’s marketing activities and sales are classified into four geographic regions: EMEA, Americas, China and Asia Pacific.

Among the popular products from Logitech are the iTouch keyboards. This keyboard series is brilliantly designed to enable the users to access the Internet, search, open e-mail and open applications with a single key press. The iTouch keyboards also feature one-touch multimedia control and a comfortable key design for an excellent typing touch. Some iTouch keyboard models come with built-in USB ports that let you connect additional devices to the keyboard as well as a unique cable management system keeps your workplace free of messy cables.

In order to enhance the performance of any Logitech iTouch keyboard, you can download its driver from this link. It is highly recommended you install the driver version 2.2.289 (October 15, 2009). This software is compatible with Windows 95, Windows 98, Windows 2000, Windows NT as well as Windows XP.

To protect your computer from incorrect installation, try to set a system restore point whenever you install a new driver update. This will prevent your computer from malfunctioning in case the wrong driver is installed. Problems usually occur when the hardware is too old or no longer supported.

Aside from updating your Logitech iTouch keyboard, remember to keep the other hardware on your computer working with the latest drivers.

Categories: Hardware, Input Devices Tags:

Problems with a specific USB device in Windows XP

October 12th, 2009 No comments

USB problems are usually an easy problem to solve. First, isolate the problem. Unplug all USB devices from the system, including USB hubs. Next, take a known good USB device and attach it to the system. If the known good device works, then you can be sure that there is nothing wrong with the port itself.

Now take the device that was malfunctioning and plug it directly into one of the computer’s USB ports while no other USB devices are connected to the system. If the device starts working, the problem most likely was that device was conflicting with another USB device. One way that USB devices can conflict with each other is if they share a common serial number. Each USB device in a system must have a unique serial number. Having two devices with a common serial number is very rare, but there are documented cases of it happening.

If the device now works and it isn’t sharing a serial number with another device, it was probably malfunctioning because of an overloaded USB hub or a conflicting device driver (Click here to run a scan for updated drivers). The only real way to sort out the problem is to use trial-and-error by plugging in various combinations of USB devices until you find the device or devices that the malfunctioning device is conflicting with. Once you track this down, you can usually solve the problem by moving the devices to different physical USB ports or by updating the drivers for both devices.

What if plugging in the malfunctioning device without any other USB devices being plugged in doesn’t cure the problem?

Try checking the computer’s Event Logs for clues to the malfunction. If the event log doesn’t give any clues, try plugging the malfunctioning device into another computer. If the device works on the other computer, then you can be sure that the device is good.

If the alternate computer is using an operating system other than Windows XP, the problem could be that the device or its driver isn’t Windows XP-compatible. Check to see if there are updates for your device for XP, if not, contact the device’s manufacturer to see if there are any known issues with using the device with Windows XP.

If the alternate computer is running Windows XP and the device is working, then I recommend checking out what version of the device driver is being used on each machine and using the one that works, even if it isn’t the most recent.

Code 31 Error in Device Manager

October 12th, 2009 No comments

This device is not working properly because Windows cannot load the drivers required for this device. (Code 31)

A Code 31 error can be related to any hardware device, but most Code 31 errors appear on optical drives like CD and DVD drives. A Code 31 error is caused by a number of reasons that stops Windows from loading the driver for a specific hardware device. (The exception is if you see the Code 31 error on the Microsoft ISATAP adapter in Windows Vista. Microsoft claims that there is not an issue here. Just ignore the error.)

Try these solutions to fix a Code 31 error:

  • Restart your computer (Sometimes this will solve the problem and you’re done.)
  • If you just installed a device or updated drivers, they might be the cause of the problem. Undo the change, or roll back the drivers. (You can also try to use the System Restore to undo Device Manager changes)
  • Try to update the device drivers, either automatically or by downloading them from the manufacturer’s website.
  • Make sure that your device is compatible with whatever version of Windows you are running. Any of Microsoft’s operating systems can experience a Code 31 Device Manager error.

Device Manager Error Codes

October 9th, 2009 No comments

Device Manager error codes are codes, followed by error messages, that are reported in the Device Manager

Error codes in Device Manager are created when your PC is experiencing device driver issues, system resource conflicts, or other hardware problems.

Note: Device Manager error codes are completely different than system error codes even though some of the code numbers may be the same. If you see an error code outside of Device Manager, it’s not a Device Manager error code.

  • Device Manager Error Code 1

    This device is not configured correctly. (Code 1)

  • Device Manager Error Code 3 – Click here to Fix 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)

  • Device Manager Error Code 10

    This device cannot start. (Code 10)

  • Device Manager Error 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)

  • Device Manager Error Code 14

    This device cannot work properly until you restart your computer. (Code 14)

  • Device Manager Error Code 16

    Windows cannot identify all the resources this device uses. (Code 16)

  • Device Manager Error Code 18

    Reinstall the drivers for this device. (Code 18)

  • Device Manager Error Code 19

    Windows cannot start this hardware device because its configuration information (in the registry) is incomplete or damaged. To fix this problem you should uninstall and then reinstall the hardware device. (Code 19)

  • Device Manager Error Code 21

    Windows is removing this device. (Code 21)

  • Device Manager Error Code 22

    This device is disabled. (Code 22)

  • Device Manager Error Code 24

    This device is not present, is not working properly, or does not have all its drivers installed. (Code 24)

  • Device Manager Error Code 28

    The drivers for this device are not installed. (Code 28)

  • Device Manager Error Code 29

    This device is disabled because the firmware of the device did not give it the required resources. (Code 29)

  • Device Manager Error Code 31 – Click here to Fix Error Code 31

    This device is not working properly because Windows cannot load the drivers required for this device. (Code 31)

  • Device Manager Error Code 32

    A driver (service) for this device has been disabled. An alternate driver may be providing this functionality. (Code 32)

  • Device Manager Error Code 33

    Windows cannot determine which resources are required for this device. (Code 33)

  • Device Manager Error 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)

  • Device Manager Error 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)

  • Device Manager Error 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)

  • Device Manager Error Code 37

    Windows cannot initialize the device driver for this hardware. (Code 37)

  • Device Manager 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)

  • Device Manager Error Code 39

    Windows cannot load the device driver for this hardware. The driver may be corrupted or missing. (Code 39)

  • Device Manager Error Code 40

    Windows cannot access this hardware because its service key information in the registry is missing or recorded incorrectly. (Code 40)

  • Device Manager Error Code 41

    Windows successfully loaded the device driver for this hardware but cannot find the hardware device. (Code 41)

  • Device Manager Error Code 42

    Windows cannot load the device driver for this hardware because there is a duplicate device already running in the system. (Code 42)

  • Device Manager Error Code 43

    Windows has stopped this device because it has reported problems. (Code 43)

  • Device Manager Error Code 44

    An application or service has shut down this hardware device. (Code 44)

  • Device Manager Error Code 45

    Currently, this hardware device is not connected to the computer. (Code 45)

  • Device Manager Error Code 46

    Windows cannot gain access to this hardware device because the operating system is in the process of shutting down. (Code 46)

  • Device Manager Error 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. (Code 47)

  • Device Manager Error 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)

  • Device Manager Error Code 49

    Windows cannot start new hardware devices because the system hive is too large (exceeds the Registry Size Limit). (Code 49)

Error Code 3

October 9th, 2009 No comments

The Code 3 error is one of several Device Manager error codes. The Code 3 error will usually appear like:

The driver for this device might be corrupted, or your system may be running low on memory or other resources. (Code 3)

Important: Device Manager error codes are only seen in the Device Manager. If you see the Code 3 error somewhere else in Windows, it is most likely a system error.

What Causes the Code 3 Error?

A Code 3 error is generated when the Device Manager can’t start the device due to  outdated or corrupted drivers or poor system resources.


  1. Restart your computer. There is always the chance that the error Code 3 you’re seeing on a device was caused by some temporary memory problem or an issue in the Device Manager or with the hardware. Sometimes rebooting your machine might fix the Code 3 error.
  2. Undo Recent Changes. If you recently installed a device or made a change in the Device Manager just before the Code 3 error appeared, then undo whatever change you made to see if the error is still there. Depending on the changes you made, you might try to:
    • Remove or reconfigure the newly installed device.
    • Roll back the driver to a previous version.
    • Use System Restore to go back to a date prior to your Code 3 error.
  3. Reinstall the drivers for the device. Uninstalling and then reinstalling the drivers for the device is a likely solution to a Code 3 error. (If a USB device is generating the Code 3 error, uninstall every device under the Universal Serial Bus controllers hardware category in the Device Manager as part of the driver reinstall.) It is important to note that a full driver reinstall involves completely removing the currently installed driver and then letting Windows install it over again from scratch.
  4. Update the drivers for the device. It’s also very possible that installing the latest drivers for the device could correct the Code 3 error. If it does, it means that the stored Windows drivers you reinstalled in Step 3 were were probably damaged.
  5. Install the latest Windows service pack Microsoft often releases service packs and other patches for Windows, one of which might contain a fix for the Code 3 error.
  6. Replace the hardware. A problem with the hardware device might be causing the Code 3 error, in which case replacing the hardware is your next logical step. Another possibility, is that the device is not compatible with your version of Windows. You can check the Windows HCL to be sure. If you’re positive that a hardware problem isn’t causing the Code 3 error, you could try to repair your Windows instillation. If that doesn’t work, as a last resort, you may need to contact a local repair shop or try a clean install of Windows.

Device Class GUIDs for Popular Types of Hardware

October 1st, 2009 No comments

Other than programming for a device driver, the Globally Unique Identifier (GUID) for a device class is useful when tracking down driver information in the Windows Registry.

For example, the solution to several Device Manager errors include removing specific registry entries after a device’s GUID.

Note: This is not a complete list of device class GUIDs. Devices can generate unique classes based on various variables making it virtually impossible to list them all.

Device Class Class GUID Notes
Battery Devices Battery {72631e54-78a4-11d0-bcf7-00aa00b7b32a} This class includes battery devices and UPS devices.
Biometric Device Biometric {53D29EF7-377C-4D14-864B-EB3A85769359} Starting with Windows Server 2003, this class includes all biometric-based personal identification devices.
Bluetooth Devices Bluetooth {e0cbf06c-cd8b-4647-bb8a-263b43f0f974} Starting with Windows XP SP1, this class includes all Bluetooth devices.
CD-ROM Drives CDROM {4d36e965-e325-11ce-bfc1-08002be10318} This class includes CD-ROM drives, including SCSI CD-ROM drives. By default, the system’s CD-ROM class installer also installs a system-supplied CD audio driver and CD-ROM changer driver as Plug and Play filters.
Disk Drives DiskDrive {4d36e967-e325-11ce-bfc1-08002be10318} This class includes hard disk drives. See also the HDC and SCSIAdapter classes.
Display Adapters Display {4d36e968-e325-11ce-bfc1-08002be10318} This class includes video adapters. Drivers for this class include display drivers and video miniport drivers.
Floppy Disk Controllers FDC {4d36e969-e325-11ce-bfc1-08002be10318} This class includes floppy disk drive controllers.
Floppy Disk Drives FloppyDisk {4d36e980-e325-11ce-bfc1-08002be10318} This class includes floppy disk drives.
Hard Disk Controllers HDC {4d36e96a-e325-11ce-bfc1-08002be10318} This class includes hard disk controllers, including ATA/ATAPI controllers but not SCSI and RAID disk controllers.
Human Interface Devices (HID) HIDClass {745a17a0-74d3-11d0-b6fe-00a0c90f57da} This class includes interactive input devices that are operated by the system-supplied HID class driver. This includes USB devices that comply with the USB HID Standard and non-USB devices that use a HID minidriver. For more information, see HIDClass Device Setup Class.. (See also the Keyboard or Mouse classes later in this list.)
IEEE 1284.4 Devices Dot4 {48721b56-6795-11d2-b1a8-0080c72e74a2} This class includes devices that control the operation of multifunction IEEE 1284.4 peripheral devices.
IEEE 1284.4 Print Functions Dot4Print {49ce6ac8-6f86-11d2-b1e5-0080c72e74a2} This class includes Dot4 print functions. A Dot4 print function is a function on a Dot4 device and has a single child device, which is a member of the Printer device setup class.
IEEE 1394 Devices That Support the 61883 Protocol 61883 {7ebefbc0-3200-11d2-b4c2-00a0C9697d07} This class includes IEEE 1394 devices that support the IEC-61883 protocol device class.

The 61883 component includes the 61883.sys protocol driver that transmits various audio and video data streams over the 1394 bus. These currently include standard/high/low quality DV, MPEG2, DSS, and Audio. These data streams are defined by the IEC-61883 specifications.

IEEE 1394 Devices That Support the AVC Protocol AVC {c06ff265-ae09-48f0-812c-16753d7cba83} This class includes IEEE 1394 devices that support the AVC protocol device class.
IEEE 1394 Devices That Support the SBP2 Protocol SBP2 {d48179be-ec20-11d1-b6b8-00c04fa372a7} This class includes IEEE 1394 devices that support the SBP2 protocol device class.
IEEE 1394 Host Bus Controller 1394 {6bdd1fc1-810f-11d0-bec7-08002be2092f} This class includes 1394 host controllers connected on a PCI bus, but not 1394 peripherals. Drivers for this class are system-supplied.
Imaging Device Image {6bdd1fc6-810f-11d0-bec7-08002be2092f} This class includes still-image capture devices, digital cameras, and scanners.
IrDA Devices Infrared {6bdd1fc5-810f-11d0-bec7-08002be2092f} This class includes infrared devices. Drivers for this class include Serial-IR and Fast-IR NDIS miniports, but see also the Network Adapter class for other NDIS network adapter miniports.
Keyboard Keyboard {4d36e96b-e325-11ce-bfc1-08002be10318} This class includes all keyboards. That is, it must also be specified in the (secondary) INF for an enumerated child HID keyboard device.
Media Changers MediumChanger {ce5939ae-ebde-11d0-b181-0000f8753ec4} This class includes SCSI media changer devices.
Memory Technology Driver MTD {4d36e970-e325-11ce-bfc1-08002be10318} This class includes memory devices, such as flash memory cards.
Modem Modem {4d36e96d-e325-11ce-bfc1-08002be10318} This class includes modem devices. An INF file for a device of this class specifies the features and configuration of the device and stores this information in the registry. An INF file for a device of this class can also be used to install device drivers for a controllerless modem or a software modem. These devices split the functionality between the modem device and the device driver. For more information about modem INF files and Microsoft Windows Driver Model (WDM) modem devices, see Overview of Modem INF Files and Adding WDM Modem Support.
Monitor Monitor {4d36e96e-e325-11ce-bfc1-08002be10318} This class includes display monitors. An INF for a device of this class installs no device driver(s), but instead specifies the features of a particular monitor to be stored in the registry for use by drivers of video adapters. (Monitors are enumerated as the child devices of display adapters.)
Mouse Mouse {4d36e96f-e325-11ce-bfc1-08002be10318} This class includes all mouse devices and other kinds of pointing devices, such as trackballs. That is, this class must also be specified in the (secondary) INF for an enumerated child HID mouse device.
Multifunction Devices Multifunction {4d36e971-e325-11ce-bfc1-08002be10318} This class includes combo cards, such as a PCMCIA modem and netcard adapter. The driver for such a Plug and Play multifunction device is installed under this class and enumerates the modem and netcard separately as its child devices.
Multimedia Media {4d36e96c-e325-11ce-bfc1-08002be10318} This class includes Audio and DVD multimedia devices, joystick ports, and full-motion video capture devices.
Multiport Serial Adapters MultiportSerial {50906cb8-ba12-11d1-bf5d-0000f805f530} This class includes intelligent multiport serial cards, but not peripheral devices that connect to its ports. It does not include unintelligent (16550-type) multiport serial controllers or single-port serial controllers (see the Ports class).
Network Adapter Net {4d36e972-e325-11ce-bfc1-08002be10318} This class includes NDIS miniport drivers excluding Fast-IR miniport drivers, NDIS intermediate drivers (of virtual adapters), and CoNDIS MCM miniport drivers.
Network Client NetClient {4d36e973-e325-11ce-bfc1-08002be10318} This class includes network and/or print providers.
Network Service NetService {4d36e974-e325-11ce-bfc1-08002be10318} This class includes network services, such as redirectors and servers.
Network Transport NetTrans {4d36e975-e325-11ce-bfc1-08002be10318} This class includes NDIS protocols, CoNDIS stand-alone call managers, and CoNDIS clients, in addition to higher level drivers in transport stacks.
PCI SSL Accelerator Security Accelerator {268c95a1-edfe-11d3-95c3-0010dc4050a5} This class includes devices that accelerate secure socket layer (SSL) cryptographic processing.
PCMCIA Adapters PCMCIA {4d36e977-e325-11ce-bfc1-08002be10318} This class includes PCMCIA and CardBus host controllers, but not PCMCIA or CardBus peripherals. Drivers for this class are system-supplied.
Ports (COM & LPT ports) Ports {4d36e978-e325-11ce-bfc1-08002be10318} This class includes serial and parallel port devices. See also the MultiportSerial class.
Printers Printer {4d36e979-e325-11ce-bfc1-08002be10318} This class includes printers.
Printers, Bus-specific class drivers PNPPrinters {4658ee7e-f050-11d1-b6bd-00c04fa372a7} This class includes SCSI/1394-enumerated printers. Drivers for this class provide printer communication for a specific bus.
Processors Processor {50127dc3-0f36-415e-a6cc-4cb3be910b65} This class includes processor types.
SCSI and RAID Controllers SCSIAdapter {4d36e97b-e325-11ce-bfc1-08002be10318} This class includes SCSI HBAs (Host Bus Adapters) and disk-array controllers.
Smart Card Readers SmartCardReader {50dd5230-ba8a-11d1-bf5d-0000f805f530} This class includes smart card readers.
Storage Volumes Volume {71a27cdd-812a-11d0-bec7-08002be2092f} This class includes storage volumes as defined by the system-supplied logical volume manager and class drivers that create device objects to represent storage volumes, such as the system disk class driver.
System Devices System {4d36e97d-e325-11ce-bfc1-08002be10318} This class includes HALs, system buses, system bridges, the system ACPI driver, and the system volume manager driver.
Tape Drives TapeDrive {6d807884-7d21-11cf-801c-08002be10318} This class includes tape drives, including all tape miniclass drivers.
USB USB {36fc9e60-c465-11cf-8056-444553540000} This class includes USB host controllers and USB hubs, but not USB peripherals. Drivers for this class are system-supplied.
Windows CE USB ActiveSync Devices WCEUSBS {25dbce51-6c8f-4a72-8a6d-b54c2b4fc835} This class includes Windows CE ActiveSync devices.

The WCEUSBS setup class supports communication between a personal computer and a device that is compatible with the Windows CE ActiveSync driver (generally, PocketPC devices) over USB.

Windows SideShow SideShow {997b5d8d-c442-4f2e-baf3-9c8e671e9e21} This class includes all devices that are compatible with Windows SideShow. This class is supported in Windows Vista and later versions of Windows.

System-Defined Device Setup Classes Reserved for System Use

Device Class Class GUID Notes
Adapter Adapter {4d36e964-e325-11ce-bfc1-08002be10318} This class is obsolete.
APM APMSupport {d45b1c18-c8fa-11d1-9f77-0000f805f530} This class is reserved for system use.
Computer Computer {4d36e966-e325-11ce-bfc1-08002be10318} This class is reserved for system use.
Decoders Decoder {6bdd1fc2-810f-11d0-bec7-08002be2092f} This class is reserved for future use.
Global Positioning System GPS {6bdd1fc3-810f-11d0-bec7-08002be2092f} This class is reserved for future use.
Host-side IEEE 1394 Kernel Debugger Support 1394Debug {66f250d6-7801-4a64-b139-eea80a450b24} This class is reserved for system use.
IEEE 1394 IP Network Enumerator Enum1394 {c459df55-db08-11d1-b009-00a0c9081ff6} This class is reserved for system use.
No driver NoDriver {4d36e976-e325-11ce-bfc1-08002be10318} This class is obsolete.
Non-Plug and Play Drivers LegacyDriver {8ecc055d-047f-11d1-a537-0000f8753ed1} This class is reserved for system use.
Other Devices Unknown {4d36e97e-e325-11ce-bfc1-08002be10318} This class is reserved for system use. Enumerated devices for which the system cannot determine the type are installed under this class. Do not use this class if you are unsure in which class your device belongs. Either determine the correct device setup class or create a new class.
Printer Upgrade Printer Upgrade {4d36e97a-e325-11ce-bfc1-08002be10318} This class is reserved for system use.
Sound Sound {4d36e97c-e325-11ce-bfc1-08002be10318} This class is obsolete.
Storage Volume Snapshots VolumeSnapshot {533c5b84-ec70-11d2-9505-00c04F79deaf} This class is reserved for system use.
Categories: Troubleshooting Tags: , ,