Find property for Touch-/ Trackpad by RawInputDeviceInfo to distinguish independent of the model/ manufacturer in registry

Question

Find property for Touch-/ Trackpad by RawInputDeviceInfo to distinguish independent of the model/ manufacturer in registry

youki 1,021

Hello,
I want to recognize, if the input is coming from the touch-/ trackpad independent of the Laptop model/ manufacturer.
Is it possible?

I'm getting the devicename by RawInputDeviceInfo and i see that there is the possibility to compare it with the registry entries but i can't see any property that tells me that it's the trackpad.

Registry path:

Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\HID...

Regards

2 answers

Your answer

Answer 1

Strive Sun-MSFT 431

Hello, @youki

If you want to know whether the input comes from the touchpad, you can use GetCurrentInputMessageSource to retrieve the source of the input message.

The INPUT_MESSAGE_SOURCE structure that holds the device type and the ID of the input message source.

typedef enum tagINPUT_MESSAGE_DEVICE_TYPE {  
  IMDT_UNAVAILABLE,  
  IMDT_KEYBOARD,  
  IMDT_MOUSE,  
  IMDT_TOUCH,  
  IMDT_PEN,  
  IMDT_TOUCHPAD  
} INPUT_MESSAGE_DEVICE_TYPE;

Note: [Windows 8 desktop apps only

----------

Thank you!

If the answer is helpful, please click "Accept Answer" and upvote it.

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

youki 1,021 Reputation points

2021-11-13T18:59:29.497+00:00

Hi StriveSun (found my post by googling yesterday :) ),
unfortunately it's not working (it's always the mouse). I also tried GetPointerType (also always mouse) but maybe the following has to do with it?

If the touchpad is a precision touchpad, the input has had some filtering/transformations done on it at the kernel level, and (IIRC) the device handle is intentionally not passed

I only wants to handle the "wipe with 2 fingers" function and the rawInput.Header.hDevice + rawInput.Header.dwType is always 0 (it's injected by the way). So it's not that bad (it tells me that it's the built in trackpad?!) or could it be an issue on other laptop's built in trackpad?

PS: If i have a monitor connected to my Thinkpad, rawinput doesn't respond to wiping on the laptop's display (set the same resolution like the monitor), that's weird. Anything else, for i.e. wiping with 1 finger is responding.

Regards
Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

Alx24 0

If, when a Mouse message arrives, the time in the MSG structure or GetTickCount() reveals that times, for example, WM_INPUT, are also recorded by the time in the MSG structure or GetTickCount() previously recorded by GetDoubleClickTime(), then we can safely assume that these are events from a real Mouse signaling the start of a new series of operations, and all variables should be reset to their original state for proper operation. Additionally, all laptops have a huge number of Touchpad features.

This way, you can separate the messages of the real Mouse from those generated by Windows when interacting with the Touchpad when everything is prepared by RegisterRawInputDevices() for Touchpad and the Input.inf file in the C:\Windows\INF directory contains the necessary constants and interesting information.

%HID_DEVICE_TOUCH_PAD% = HID_Raw_Inst,, hid_device_up:000d_u:0005

...


	UINT uiTouchpadRawInputTime = 0;
	// Main message loop:
	while (GetMessage(&msg, NULL, 0, 0)) 
	{
		if ( msg.message == WM_INPUT )
		{
			uiTouchpadRawInputTime = msg.time;
////////////////////////////////////////////////////////////////////////////////
			// Test
			char s[0x100];
			sprintf(s, "WM_INPUT: %1d", uiTouchpadRawInputTime);
			SetWindowText(msg.hwnd, s);
////////////////////////////////////////////////////////////////////////////////
		}
		if ( WM_MOUSEFIRST <= msg.message && msg.message <= WM_MOUSELAST || msg.message == WM_MOUSEHWHEEL )
		{
			if ( msg.time > uiTouchpadRawInputTime + GetDoubleClickTime() )
			{
				// normal mouse message processing
////////////////////////////////////////////////////////////////////////////////
				// Test
				if (msg.message != WM_MOUSEMOVE) // for fine picture only
				{
					RECT rc;
					GetClientRect(msg.hwnd, &rc);
					HDC hdc = GetDC(msg.hwnd);
					InvertRect(hdc, &rc);
					ReleaseDC(msg.hwnd, hdc);
				}
////////////////////////////////////////////////////////////////////////////////
			}
			else
				// windows generated mouse messages for Touchpad skipped here and by Windows
				continue;
		}
		// standard
		if (!TranslateAccelerator(msg.hwnd, hAccelTable, &msg)) 
		{
			TranslateMessage(&msg);
			DispatchMessage(&msg);
		}
	}

Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Alx24 0 Reputation points

2025-10-11T16:47:20.11+00:00

Code abowe works, the delay between last WM_INPUT for Touchpad tap and the Windows-generated WM_LBUTTONDOWN by GetTickCount() for these messages is 0-15ms.

If long-term processing of individual WM_INPUT messages is required in a specific program, this must be taken into account during the overall processing of messages. Once all the critical small processing is completed, you can use PostMessage(WM_COMMAND), unlike SendMessage(), to allow the operating system to perform all the necessary actions and then continue executing the long part of the message handler while processing this WM_COMMAND.

As usual in MS, processing of Mouse or Touchpad messages begins after the Mouse Button is released or WM_INPUT messages from the Touchpad cease to be received. However, instead of two options: Click or Press, there is only one Click. Formally, the button state can be evaluated using a timer started immediately upon pressing for the duration GetDoubleClickTime(), and after this time, the button state can be evaluated.

A unique feature of the user interface is that MSG.time or GetTickCount() (unsigned int) can be used to determine the message time. At the start of any action, the times of previous actions can be checked. If they are earlier, for example, GetDoubleClickTime(), all variables can be reset to their original state, and processing will resume as if nothing had happened before which is perfectly normal. Windows constantly scans the application message queue and optimizes it based on the relevance of the messages.

There is HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\PrecisionTouchPad\

It's worth noting that Apple uses the simultaneous pressing of the Mouse keys LB and RB, while Microsoft eliminates this in its Mouse keys via hardware and in WM_POINTER for Mouse keys via software. Technically, due to its extremely limited default functionality, it would be preferable to use the simultaneous pressing of LB and RB keys in the Touchpad.

It would be very nice if the input device was as comfortable to hold as a tennis racket and not with a constantly bent back hand.

Touchpads seem to be mostly i2C devices.

https://i2cdevices.org/

https://i2cdevices.org/devices
Alx24 0 Reputation points

2025-10-11T16:50:11.7066667+00:00

For Mouse Wheel at Raw Input

https://stackoverflow.com/questions/9245303/rawinput-how-to-get-mouse-wheel-data?rq=3

"RAWINPUT - How to get Mouse Wheel data"

https://free.blessedness.top/en-us/windows-hardware/design/component-guidelines/touchpad-mouse-collection

https://free.blessedness.top/en-us/windows-hardware/design/component-guidelines/touchpad-windows-precision-touchpad-collection

https://free.blessedness.top/en-us/windows-hardware/drivers/hid/hid-usages

Coordinates X,Y

#define HID_USAGE_GENERIC_X ((USAGE) 0x30)

#define HID_USAGE_GENERIC_Y ((USAGE) 0x31)

and

#define HID_USAGE_GENERIC_WHEEL ((USAGE) 0x38)

Mouse messages from Touchpad actions accompanying regular Mouse messages are designed to avoid writing code for Touchpad messages in most cases, and instead treat them as Mouse messages, since they share many similarities, including scrolling. With standard two-finger scaling with a Precision Touchpad, zooming by pressing the Ctrl key is artificially replicated via WM_KEYDOWN with VK_CONTROL, WM_MOUSEWHEEL, WM_MOUSEHWHEEL and WM_KEYUP. With standard two-finger scrolling with a Precision Touchpad, WM_VSCROLL and WM_HSCROLL messages are artificially generated.

Windows tries to keep user action processing simple and simple, and you can see that with two-finger Touchpad scrolling, WM_VSCROLL and WM_HSCROLL messages are generated in response to even the slightest finger movement without any parameters. Therefore, this processing is easy to implement independently in WM_INPUT.

Answer 2

youki 1,021

Since i want to track the wheel scrolling (also by RawInput), it doesn't make sense to search further because it's a lack of the api:

https://stackoverflow.com/questions/57552844/rawinputheader-hdevice-null-on-wm-input-for-laptop-trackpad

https://stackoverflow.com/questions/47005610/x-and-y-coordinate-from-precision-touchpad-with-raw-input

Any help is always appreciated.

Regards

MS Feedback Hub: https://insider.windows.com/en-us/feedbackhub/fb?contextid=386&feedbackid=91027b01-644f-4dc8-beb6-55551c16a8bd&form=1

Alx24 0 Reputation points

2025-10-12T05:09:21.3433333+00:00

The Precision Touchpad has five touch points, but we should always strive to simplify working with input devices, and these devices provide a good solution. For example, with Touch and Touchpad, you can continue moving the cursor with one finger and perform actions with another finger, as with the Windows Press and Tap gesture. By hovering the cursor on the Touchpad, you can perform over a dozen different operations if the subsequent tap occurs on different points of the Touchpad grid, as in the ASUS NumberPad. You can also click over a dozen points around the perimeter of the Touchpad, which is typically unused.

A single tap with one finger only has the options Tap, Press, and Press and Move (8 Directions). Double-tapping has four options: Double Tap (iPadOS simple scale, Apple Pencil), Tap + Press, Press + Tap, and Press + Press, of which only Double Tap and Tap + Press are useful. Triple-tapping has eight options: Tap + Tap + Tap (used in some cases, including Mouse), Tap + Tap + Press, Tap + Press + Tap, Tap + Press + Press, Preaa + Tap + Tap, Press + Tap + Press, Press + Press + Tap, Press + Press + Press, Press + Press + Press, of which only two are useful: Tap + Tap + Tap and Tap + Press. This is a fundamental limitation of the Touch Screen. Tap + Tap + Press can also be used as a simpler version of Tap + Tap + Tap.

Touchpad operations can be more varied using Ctrl and Shift, as is the case with the Mouse Wheel.

The number of single-finger operations is very limited, but with two fingers, there is a wide variety of simple, quick Tap and Press operations, depending on the distance between the fingers and their relative positions. After pressing with two fingers, you can also lift one of them to the right or left, and the same applies to a wide range of relative positions and distances between the fingers.

Formally, it seems possible to use RegisterRawInputDevices() for any window in an application, including Windows Controls, and use your own procedure to handle WM_INPUT, that is, user actions with this window.
Alx24 0 Reputation points

2025-10-13T04:27:55.76+00:00

Sample Touchpad

Registry for this Touchpad

VEN_06CB, DEV_0001

https://devicehunt.com/view/type/usb/vendor/06CB

"USB 06cb Synaptics, Inc. 0001 TouchPad"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\HID\06CB0001&Col02\5&14254c89&0&0001]

"Capabilities"=dword:000000e0

"Address"=dword:00000001

"ConfigFlags"=dword:00000000

"ContainerID"="{00000000-0000-0000-ffff-ffffffffffff}"

"HardwareID"=hex(7):48,00,49,00,44,00,5c,00,56,00,45,00,4e,00,5f,00,30,00,36,\

00,43,00,42,00,26,00,44,00,45,00,56,00,5f,00,30,00,30,00,30,00,31,00,26,00,\

43,00,6f,00,6c,00,30,00,32,00,00,00,48,00,49,00,44,00,5c,00,30,00,36,00,43,\

00,42,00,30,00,30,00,30,00,31,00,26,00,43,00,6f,00,6c,00,30,00,32,00,00,00,\

48,00,49,00,44,00,5c,00,2a,00,30,00,36,00,43,00,42,00,30,00,30,00,30,00,31,\

00,26,00,43,00,6f,00,6c,00,30,00,32,00,00,00,48,00,49,00,44,00,5c,00,56,00,\

49,00,44,00,5f,00,30,00,36,00,43,00,42,00,26,00,55,00,50,00,3a,00,30,00,30,\

00,30,00,44,00,5f,00,55,00,3a,00,30,00,30,00,30,00,35,00,00,00,48,00,49,00,\

44,00,5f,00,44,00,45,00,56,00,49,00,43,00,45,00,5f,00,55,00,50,00,3a,00,30,\

00,30,00,30,00,44,00,5f,00,55,00,3a,00,30,00,30,00,30,00,35,00,00,00,48,00,\

49,00,44,00,5f,00,44,00,45,00,56,00,49,00,43,00,45,00,00,00,00,00

"CompatibleIDs"=hex(7):00,00,00,00

"ClassGUID"="{745a17a0-74d3-11d0-b6fe-00a0c90f57da}"

"DeviceDesc"="@input.inf,%hid_device_touch_pad%;HID-compliant touch pad"

"Driver"="{745a17a0-74d3-11d0-b6fe-00a0c90f57da}\0010"

"Mfg"="@input.inf,%stdmfg%;(Standard system devices)"

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Class{745a17a0-74d3-11d0-b6fe-00a0c90f57da}\0010]

"DriverDesc"="HID-compliant touch pad"

"ProviderName"="Microsoft"

"DriverDateData"=hex:00,80,8c,a3,c5,94,c6,01

"DriverDate"="6-21-2006"

"DriverVersion"="10.0.15063.0"

"InfPath"="input.inf"

"InfSection"="HID_Raw_Inst.NT"

"MatchingDeviceId"="HID_DEVICE_UP:000D_U:0005"

Device Manager for this Touchpad

Details page

Path

HID\06CB0001&COL02\5&14254C89&0&0001

ID

HID\VEN_06CB&DEV_0001&Col02

HID\06CB0001&Col02

HID*06CB0001&Col02

HID\VID_06CB&UP:000D_U:0005

HID_DEVICE_UP:000D_U:0005

HID_DEVICE

HIDClass

There is "devcon" application from Microsoft Corp. with source code, SetupAPI, Config Manager (cfgmgr.h, cfgmgr32.h) https://devblogs.microsoft.com/scripting/use-hidden-wmi-classes-and-powershell-to-discover-hid-info/

Detailed text information about the manufacturer and model is usually contained in the device driver's Inf file, but devices such as the Touchpad use the standard Windows driver.
Alx24 0 Reputation points

2025-10-13T04:51:22.1566667+00:00

Sample Touch Screen

VEN_04F3, DEV_224A

https://devicehunt.com/view/type/usb/vendor/04F3

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\HID\04F3224A&Col01]

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\HID\04F3224A&Col01\5&3034472b&0&0000]

"Capabilities"=dword:000000e0

"ConfigFlags"=dword:00000000

"ContainerID"="{00000000-0000-0000-ffff-ffffffffffff}"

"HardwareID"=hex(7):48,00,49,00,44,00,5c,00,56,00,45,00,4e,00,5f,00,30,00,34,\

00,46,00,33,00,26,00,44,00,45,00,56,00,5f,00,32,00,32,00,34,00,41,00,26,00,\

43,00,6f,00,6c,00,30,00,31,00,00,00,48,00,49,00,44,00,5c,00,30,00,34,00,46,\

00,33,00,32,00,32,00,34,00,41,00,26,00,43,00,6f,00,6c,00,30,00,31,00,00,00,\

48,00,49,00,44,00,5c,00,2a,00,30,00,34,00,46,00,33,00,32,00,32,00,34,00,41,\

00,26,00,43,00,6f,00,6c,00,30,00,31,00,00,00,48,00,49,00,44,00,5c,00,56,00,\

49,00,44,00,5f,00,30,00,34,00,46,00,33,00,26,00,55,00,50,00,3a,00,30,00,30,\

00,30,00,44,00,5f,00,55,00,3a,00,30,00,30,00,30,00,34,00,00,00,48,00,49,00,\

44,00,5f,00,44,00,45,00,56,00,49,00,43,00,45,00,5f,00,55,00,50,00,3a,00,30,\

00,30,00,30,00,44,00,5f,00,55,00,3a,00,30,00,30,00,30,00,34,00,00,00,48,00,\

49,00,44,00,5f,00,44,00,45,00,56,00,49,00,43,00,45,00,00,00,00,00

"CompatibleIDs"=hex(7):00,00,00,00

"ClassGUID"="{745a17a0-74d3-11d0-b6fe-00a0c90f57da}"

"DeviceDesc"="@input.inf,%hid_device_touch_screen%;HID-compliant touch screen"

"Driver"="{745a17a0-74d3-11d0-b6fe-00a0c90f57da}\0003"

"Mfg"="@input.inf,%stdmfg%;(Standard system devices)"

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Class{745a17a0-74d3-11d0-b6fe-00a0c90f57da}\0003]

"DriverDesc"="HID-compliant touch screen"

"ProviderName"="Microsoft"

"DriverDateData"=hex:00,80,8c,a3,c5,94,c6,01

"DriverDate"="6-21-2006"

"DriverVersion"="10.0.15063.0"

"InfPath"="input.inf"

"InfSection"="HID_Raw_Inst.NT"

"MatchingDeviceId"="HID_DEVICE_UP:000D_U:0004"

Device Manager for this Touch screen

Details page

Path

HID\04F3224A&COL01\5&3034472B&0&0000

ID

HID\VEN_04F3&DEV_224A&Col01

HID\04F3224A&Col01

HID*04F3224A&Col01

HID\VID_04F3&UP:000D_U:0004

HID_DEVICE_UP:000D_U:0004

HID_DEVICE

HIDClass
Alx24 0 Reputation points

2025-10-13T04:54:07.7433333+00:00

Pen

VEN_04F3, DEV_224A

https://devicehunt.com/view/type/usb/vendor/04F3

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\HID\04F3224A&Col06]

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\HID\04F3224A&Col06\5&3034472b&0&0005]

"Capabilities"=dword:000000e0

"ConfigFlags"=dword:00000000

"ContainerID"="{00000000-0000-0000-ffff-ffffffffffff}"

"HardwareID"=hex(7):48,00,49,00,44,00,5c,00,56,00,45,00,4e,00,5f,00,30,00,34,\

00,46,00,33,00,26,00,44,00,45,00,56,00,5f,00,32,00,32,00,34,00,41,00,26,00,\

43,00,6f,00,6c,00,30,00,36,00,00,00,48,00,49,00,44,00,5c,00,30,00,34,00,46,\

00,33,00,32,00,32,00,34,00,41,00,26,00,43,00,6f,00,6c,00,30,00,36,00,00,00,\

48,00,49,00,44,00,5c,00,2a,00,30,00,34,00,46,00,33,00,32,00,32,00,34,00,41,\

00,26,00,43,00,6f,00,6c,00,30,00,36,00,00,00,48,00,49,00,44,00,5c,00,56,00,\

49,00,44,00,5f,00,30,00,34,00,46,00,33,00,26,00,55,00,50,00,3a,00,30,00,30,\

00,30,00,44,00,5f,00,55,00,3a,00,30,00,30,00,30,00,32,00,00,00,48,00,49,00,\

44,00,5f,00,44,00,45,00,56,00,49,00,43,00,45,00,5f,00,55,00,50,00,3a,00,30,\

00,30,00,30,00,44,00,5f,00,55,00,3a,00,30,00,30,00,30,00,32,00,00,00,48,00,\

49,00,44,00,5f,00,44,00,45,00,56,00,49,00,43,00,45,00,00,00,00,00

"CompatibleIDs"=hex(7):00,00,00,00

"ClassGUID"="{745a17a0-74d3-11d0-b6fe-00a0c90f57da}"

"DeviceDesc"="@input.inf,%hid_device_pen%;HID-compliant pen"

"Driver"="{745a17a0-74d3-11d0-b6fe-00a0c90f57da}\0008"

"Mfg"="@input.inf,%stdmfg%;(Standard system devices)"

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Class{745a17a0-74d3-11d0-b6fe-00a0c90f57da}\0008]

"DriverDesc"="HID-compliant pen"

"ProviderName"="Microsoft"

"DriverDateData"=hex:00,80,8c,a3,c5,94,c6,01

"DriverDate"="6-21-2006"

"DriverVersion"="10.0.15063.0"

"InfPath"="input.inf"

"InfSection"="HID_Raw_Inst.NT"

"MatchingDeviceId"="HID_DEVICE_UP:000D_U:0002"

Device Manager for this Pen

Details page

Path

HID\04F3224A&COL06\5&3034472B&0&0005

ID

HID\VEN_04F3&DEV_224A&Col06

HID\04F3224A&Col06

HID*04F3224A&Col06

HID\VID_04F3&UP:000D_U:0002

HID_DEVICE_UP:000D_U:0002

HID_DEVICE

HIDClass
Alx24 0 Reputation points

2025-10-13T23:58:56.0066667+00:00

It is worth noting that Microsoft Devices, like everyone else, have a standard description in Device Manager.

"Sculpt Mobile Mouse"

Human Interface Device

USB Input Device

USB\VID_045E&PID_07B2&MI_00\6&28FE2443&2&0000

Mice and other pointing devices

HID-compliant mouse

mouclass.sys

mouhid.sys

HID\VID_045E&PID_07B2&MI_01&COL01\7&978DD85&0&0000

Very nice information

https://devicehunt.com/view/type/usb/vendor/045E

USB 045e Microsoft Corp. 07b2 2.4GHz Transceiver v8.0 used by mouse Wireless Desktop 900

"Arc Touch Mouse"

HID\VID_045E&PID_07B1&MI_01&COL01\7&1BF3CD21&0&0000

However, if you install Microsoft's Mouse & Keyboard software, probably more information

appears.

File Input.inf

; INPUT.INF -- This file contains descriptions of USB HID devices

...

; Mice

;

[MSMice.NTamd64]

%USB\VID_045E&PID_0009.DeviceDesc%=HID_Inst,, USB\VID_045E&PID_0009

%USB\VID_045E&PID_001E.DeviceDesc%=HID_Inst,, USB\VID_045E&PID_001E

%USB\VID_045E&PID_0023.DeviceDesc%=HID_Inst,, USB\VID_045E&PID_0023

%USB\VID_045E&PID_0024.DeviceDesc%=HID_Inst,, USB\VID_045E&PID_0024

%USB\VID_045E&PID_0025.DeviceDesc%=HID_Inst,, USB\VID_045E&PID_0025

%USB\VID_045E&PID_0029.DeviceDesc%=HID_Inst,, USB\VID_045E&PID_0029

%USB\VID_045E&PID_0039.DeviceDesc%=HID_Inst,, USB\VID_045E&PID_0039

%USB\VID_045E&PID_0040.DeviceDesc%=HID_Inst,, USB\VID_045E&PID_0040

%USB\VID_045E&PID_0047.DeviceDesc%=HID_Inst,, USB\VID_045E&PID_0047

%USB\VID_045E&PID_0059.DeviceDesc%=HID_Inst,, USB\VID_045E&PID_0059

...

USB\VID_045E&PID_0009.DeviceDesc="Microsoft USB IntelliMouse"

USB\VID_045E&PID_001E.DeviceDesc="Microsoft USB IntelliMouse Explorer"

USB\VID_045E&PID_0023.DeviceDesc="Microsoft USB Trackball Optical"

USB\VID_045E&PID_0024.DeviceDesc="Microsoft USB Trackball Explorer"

USB\VID_045E&PID_0025.DeviceDesc="Microsoft USB IntelliMouse with IntelliEye"

USB\VID_045E&PID_0029.DeviceDesc="Microsoft USB IntelliMouse Web"

USB\VID_045E&PID_0039.DeviceDesc="Microsoft USB IntelliMouse Optical"

USB\VID_045E&PID_0040.DeviceDesc="Microsoft USB Wheel Mouse Optical"

USB\VID_045E&PID_0047.DeviceDesc="Microsoft USB IntelliMouse Explorer 3.0"

USB\VID_045E&PID_0059.DeviceDesc="Microsoft USB Wireless IntelliMouse Explorer"

File msmouse.inf

; MSMOUSE.INF -- This file contains descriptions of Mouse class devices

...

%HID\VID_045E&PID_0009.DeviceDesc%=HID_Mouse_Inst,, HID\VID_045E&PID_0009

%HID\VID_045E&PID_001E.DeviceDesc%=HID_Mouse_Inst,, HID\VID_045E&PID_001E

%HID\VID_045E&PID_0023.DeviceDesc%=HID_Mouse_Inst,, HID\VID_045E&PID_0023

%HID\VID_045E&PID_0024.DeviceDesc%=HID_Mouse_Inst,, HID\VID_045E&PID_0024

%HID\VID_045E&PID_0025.DeviceDesc%=HID_Mouse_Inst,, HID\VID_045E&PID_0025

%HID\VID_045E&PID_0029.DeviceDesc%=HID_Mouse_Inst,, HID\VID_045E&PID_0029

%HID\VID_045E&PID_0039.DeviceDesc%=HID_Mouse_Inst,, HID\VID_045E&PID_0039

%HID\VID_045E&PID_0040.DeviceDesc%=HID_Mouse_Inst,, HID\VID_045E&PID_0040

%HID\VID_045E&PID_0047.DeviceDesc%=HID_Mouse_Inst,, HID\VID_045E&PID_0047

%HID\VID_045E&PID_0059.DeviceDesc%=HID_Mouse_Inst,, HID\VID_045E&PID_0059&Col01

...

HID\VID_045E&PID_0009.DeviceDesc="Microsoft USB IntelliMouse"

HID\VID_045E&PID_001E.DeviceDesc="Microsoft USB IntelliMouse Explorer"

HID\VID_045E&PID_0023.DeviceDesc="Microsoft USB Trackball Optical"

HID\VID_045E&PID_0024.DeviceDesc="Microsoft USB Trackball Explorer"

HID\VID_045E&PID_0025.DeviceDesc="Microsoft USB IntelliMouse with IntelliEye"

HID\VID_045E&PID_0029.DeviceDesc="Microsoft USB IntelliMouse Web"

HID\VID_045E&PID_0039.DeviceDesc="Microsoft USB IntelliMouse Optical"

HID\VID_045E&PID_0040.DeviceDesc="Microsoft USB Wheel Mouse Optical"

HID\VID_045E&PID_0047.DeviceDesc="Microsoft USB IntelliMouse Explorer 3.0"

HID\VID_045E&PID_0059.DeviceDesc="Microsoft USB Wireless IntelliMouse Explorer"

There is hidi2c.inf

Microsoft Arc Mouse ( Surface Arc Mouse ) Bluetooth
Alx24 0 Reputation points

2025-10-14T12:32:08.9933333+00:00

It's worth keeping in mind that even if a mouse isn't connected to the laptop, but there is a touchpad, Device Manager's "Devices by type" section under "Mice and other pointing devices" shows "HID-compliant mouse," which has Touchpad data in the registry, as shown above:

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\HID\06CB0001&Col02\5&14254c89&0&0001]

"Capabilities"=dword:000000e0

"Address"=dword:00000001

"ConfigFlags"=dword:00000000

"ContainerID"="{00000000-0000-0000-ffff-ffffffffffff}"

"HardwareID"=hex(7):48,00,49,00,44,00,5c,00,56,00,45,00,4e,00,5f,00,30,00,36,\

00,43,00,42,00,26,00,44,00,45,00,56,00,5f,00,30,00,30,00,30,00,31,00,26,00,\

43,00,6f,00,6c,00,30,00,32,00,00,00,48,00,49,00,44,00,5c,00,30,00,36,00,43,\

00,42,00,30,00,30,00,30,00,31,00,26,00,43,00,6f,00,6c,00,30,00,32,00,00,00,\

48,00,49,00,44,00,5c,00,2a,00,30,00,36,00,43,00,42,00,30,00,30,00,30,00,31,\

00,26,00,43,00,6f,00,6c,00,30,00,32,00,00,00,48,00,49,00,44,00,5c,00,56,00,\

49,00,44,00,5f,00,30,00,36,00,43,00,42,00,26,00,55,00,50,00,3a,00,30,00,30,\

00,30,00,44,00,5f,00,55,00,3a,00,30,00,30,00,30,00,35,00,00,00,48,00,49,00,\

44,00,5f,00,44,00,45,00,56,00,49,00,43,00,45,00,5f,00,55,00,50,00,3a,00,30,\

00,30,00,30,00,44,00,5f,00,55,00,3a,00,30,00,30,00,30,00,35,00,00,00,48,00,\

49,00,44,00,5f,00,44,00,45,00,56,00,49,00,43,00,45,00,00,00,00,00

"CompatibleIDs"=hex(7):00,00,00,00

"ClassGUID"="{745a17a0-74d3-11d0-b6fe-00a0c90f57da}"

"DeviceDesc"="@input.inf,%hid_device_touch_pad%;HID-compliant touch pad"

"Driver"="{745a17a0-74d3-11d0-b6fe-00a0c90f57da}\0010"

"Mfg"="@input.inf,%stdmfg%;(Standard system devices)"

[HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Class{745a17a0-74d3-11d0-b6fe-00a0c90f57da}\0010]

"DriverDesc"="HID-compliant touch pad"

"ProviderName"="Microsoft"

"DriverDateData"=hex:00,80,8c,a3,c5,94,c6,01

"DriverDate"="6-21-2006"

"DriverVersion"="10.0.15063.0"

"InfPath"="input.inf"

"InfSection"="HID_Raw_Inst.NT"

"MatchingDeviceId"="HID_DEVICE_UP:000D_U:0005"

If Raw Input is used, then there are both WM_INPUT messages from the Touchpad and Mouse messages generated by Windows under appropriate conditions, and they can be separated as described above.

If we use the VBS code below to obtain the properties of the Win32_PointingDevice WMI class, the Touchpad is represented as a pure Mouse.

Availability

Caption HID-compatible mouse

ConfigManagerErrorCode 0

ConfigManagerUserConfig False

CreationClassName Win32_PointingDevice

Description HID-compatible mouse

DeviceID HID\06CB0001&COL01\5&14254C89&0&0000

DeviceInterface 162

DoubleSpeedThreshold

ErrorCleared

ErrorDescription

Handedness

HardwareType HID-compatible mouse

InfFileName msmouse.inf

InfSection HID_Mouse_Inst.NT

InstallDate

IsLocked

LastErrorCode

Manufacturer Microsoft

Name HID-compatible mouse

NumberOfButtons 0

PNPDeviceID HID\06CB0001&COL01\5&14254C89&0&0000

PointingType 2

PowerManagementCapabilities

PowerManagementSupported False

QuadSpeedThreshold

Resolution

SampleRate

Status OK

StatusInfo

Synch

SystemCreationClassName Win32_ComputerSystem

SystemName DESKTOP-AQ9A0EE

The Touchpad and Mouse have buttons. Mouse Wheel functions are implemented on the Precision Touchpad via Scroll and Scale Gestures. The MS Surface Arc Mouse and Microsoft Arc Mouse use Touch, Touch + Move (V, H) instead of buttons and wheel. At one time, in the field of mini-computers, they tried to represent any device as a file, but Microsoft Corp. went the way of different classes of devices, but the Mouse and Touchpad are also close in software and can generate identical messages and are classified as "Mice and other pointing devices."

The difference between modern Windows Touchpads and Mouses is the 3-Finger System Gestures. And it's no time to rejoice that the application receives all the Raw Input information, because System Gestures are still functional. The lack of an alternative to the Touchpad on most laptops can be somewhat depressing, but Surface devices have a Touch Screen and Touch Pen, and Windows supports simple operations, while more complex ones can be handled both as Raw Input and as Pointer messages (WM_POINTER...), WM_TOUCH, WM_GRSTURE, WM_TABLET_FLICK.

Alx24 0

If you place this code in a VBS file and double-click it, an HTML file will be generated containing the names (Name = Property.Name) and parameter values (s = objInstance.properties_(Name)) of the WMI classes from "root\cimv2." You can substitute any valid class name from the cimwin32.mof file in the C:\Windows\System32\wbem directory for "WIN32_PointingDevice." This file has kernel-level access.

Dim objService
set wmiLocator = CreateObject ("WbemScripting.SWbemLocator")   
set ObjService = wmiLocator.ConnectServer (".", "root\cimv2")
ObjService.Security_.ImpersonationLevel = 3
Dim objClass
Set objClass = objService.Get ("WIN32_PointingDevice")
Set objEnumerator = objService.ExecQuery("Select * from WIN32_PointingDevice")
Dim fso, tf
Set fso = CreateObject("Scripting.FileSystemObject")
Set tf = fso.CreateTextFile("PointingDevice.Htm", True)
tf.WriteLine("<html>") 
tf.WriteLine("<head>") 
tf.WriteLine("<meta http-equiv=Content-Type content=""text/html; charset=windows-1251"">") 
tf.WriteLine("</head>") 
tf.WriteLine("<body>") 
tf.WriteLine("<TABLE>") 
For Each objInstance in objEnumerator
    If Err.Number Then
        Err.Clear
    Else
        If objInstance is nothing Then
            Break
        Else
            ON ERROR RESUME Next
            For each Property in objClass.Properties_
                If Err.Number Then
                    Err.Clear
                Else
                   tf.WriteLine("<TR VALIGN=""top"">") 
                Name = Property.Name
                tf.Write("<TD width=50%>") 
                tf.Write(Name) 
                tf.WriteLine("</TD>") 
                s = objInstance.properties_(Name)
                strMessage = Space(6) & s
                tf.Write("<TD width=50%>") 
                tf.Write(strMessage) 
                tf.WriteLine("</TD>") 
                tf.WriteLine("</TR>") 
                End If
            Next
        End If
    End If
    tf.WriteLine("<TR VALIGN=""top"">") 
    tf.Write("<TD width=50%>-</TD>")
    tf.Write("<TD width=50%>-</TD>")
    tf.WriteLine("</TR>") 
    tf.WriteLine("<TR></TR>") 
Next
tf.WriteLine("</TABLE><BR>") 
tf.WriteLine("</body>") 
tf.WriteLine("</html>") 
tf.Close

Alx24 0 Reputation points

2025-10-14T13:27:17.2133333+00:00

Finally, it is very convenient to use a simple capacitive stylus with the Touchpad, which easily provides the necessary density of touch on its own for a long time.
Alxndr 21 Reputation points

2025-10-24T10:22:46.5733333+00:00

Unlike the Mouse, the Precision Touchpad has full support for Scroll V, Scroll H, and Scale. On a Mouse with Scroll H, Scale can be accessed by pressing the Mouse Right Button and rotating the Wheel, without affecting Mouse Right Button Click. It's worth noting that on modern large monitor screens, the Menu, Toolbar, and Scrollbars are located very far from the center of the screen and the user's actions location, and moving the cursor to and from them takes a very long time. For example, by pressing the Mouse Right Button and making a small movement in several directions, you can perform several operations as provided for the Pen.

https://free.blessedness.top/en-us/previous-versions/windows/desktop/ms703447(v=vs.85)

https://free.blessedness.top/en-us/windows/win32/tablet/flicks-gestures

And in this case FLICK_DATA structure (tabflicks.h) contains:

BOOL fControlModifier: 1;

BOOL fMenuModifier: 1;

BOOL fAltGRModifier: 1;

BOOL fWinModifier: 1;

BOOL fShiftModifier : 1;

which would significantly expand the Surface Pen's capabilities by adding a keyboard. This is also used for Mouse.

Share via

Find property for Touch-/ Trackpad by RawInputDeviceInfo to distinguish independent of the model/ manufacturer in registry

2 answers

Your answer