Share via

I2C HID Device error in Asus Zenbook and Touch Pad is not Working

Anonymous
2025-04-02T21:46:44+00:00

Hello There!

I have facing I2C HID Device error and touchpad is not working but my external mouse is working. I have tried installing asus driver, did uninstalling and disabling, tried bios reset too but none has worked. Later contacted microsoft support chat and they suggested to re install windows 11 and i set up again but still same error showing.

Is there any permanent solution for this?

Windows for home | Windows 11 | Devices and drivers

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

4 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2025-07-01T17:54:01+00:00

    I had the same issue. Touchpad not working ASUS Zenbook laptop Q409 Series. I2C not working. Started about a month ago. Was not showing touchpad on ANY settings in Windows 11 or MyASUS.

    Looked up every possible "solution" online today 7/1/2025....could not find any thing that worked.

    After much fooling around myself....THIS METHOD WORKED FOR ME.....

    I first deleted/removed I2C device in device manager. It had a yellow caution icon on it.

    Then removed MyASUS App.

    Next, went to ASUS support website. Drivers and Bios & Firmware. Enter your model # and expand all. I went through and manually downloaded the latest versions of all except for Display, Wi-Fi, Bluetooth and Intel related downloads ( Intel Driver and Support Assistant should have updated these ).

    You will have to restart your PC numerous times !! I didn't use the auto-update link ( near top of page in blue print because I didn't want it to download things I didn't need. So, I don't know if that method will work.

    Last, I re-installed MyASUS app. Make sure you have your password handy.

    My specs....

    Edition Windows 11 Home
    Version 24H2
    Installed on ‎10/‎3/‎2024
    OS build 26100.4484
    Experience Windows Feature Experience Pack 1000.26100.128.0

    1 person found this answer helpful.
    0 comments
  2. Emmanuel Santana 38,845 Reputation points Independent Advisor
    2025-04-04T11:56:22+00:00

    Thanks for the info.

    If you boot into UEFI/BIOS, not Windows, does the touchpad respond there (e.g., move the pointer, register in diagnostics if available)?

    When you run pnputil /enum-devices /connected in Command Prompt (as admin), does it list any active device tied to the I2C bus related to HID or touch input?

    0 comments
  3. Anonymous
    2025-04-03T14:40:38+00:00

    This device cannot start. (Code 10)

    A request for the HID descriptor failed.

    Firmware is responding and updated to latest version. Tried by reseting bios too.

    0 comments
  4. Emmanuel Santana 38,845 Reputation points Independent Advisor
    2025-04-03T00:24:15+00:00

    Hello, thank you for reaching out to the Microsoft Community. I'm here to help with your questions or issues.

    After boot, does Device Manager show the I2C HID device under "Human Interface Devices" with a code 10, code 43, or is it missing entirely?

    Please do the following:

    1. Press Windows + X on your keyboard.
    2. Click Device Manager from the list.
    3. In Device Manager, expand Human Interface Devices.
    4. Look for I2C HID Device (might also be listed as “HID-compliant touch pad” or similar).
    5. If it’s there:
      • Right-click it and choose Properties.
      • In the new window, go to the General tab.
      • Look for the Device status box and read the error code. It will say something like “This device cannot start. (Code 10)” or “Code 43”.

    Copy exactly what it says and send that back.

    1. If it’s not listed at all, go back to Device Manager, click View at the top, then click Show hidden devices.
      • Check again under Human Interface Devices and also under Other devices.
      • If it appears grayed out or under a different name (like Unknown device), click it and read the error code from Properties again.

    That code tells us if the firmware is responding or if Windows is getting a hardware fault.

    0 comments