Bluetooth devices and Common POS peripherals fail to connect on Windows Embedded for Point of Service systems
Raksts
This article helps you resolve the problem where the Human Interface Device Access Service, or HID Input Service fails to start on Windows Embedded for Point of Service.
Original product version: Human Interface Device Access Service, HID Input Service Original KB number: 2009753
Symptoms
The Human Interface Device Access Service, or HID Input Service fails to start on Windows Embedded for Point of Service, the SCM ID 7023 error is seen in the Event Log.
This missing service can be the root cause of a Windows Embedded for Point of Service failure to enumerate Bluetooth devices. It can also result in the failure of common POS HID devices such as Scanners, Magnetic Strip Readers, and other peripherals that rely on the HID Input Service to connect to a Windows Embedded for Point of Service system.
Cause
If there is no HID device attached during the Windows Embedded for Point of Service installation, the HIDSERV.DLL file may not install to the system, preventing the HID Service from starting. If HID devices are later added to the Windows Embedded for Point of Service system, or other functionality dependent on the HID Service is required, the failure of the HID Service prevents them from working.
Resolution
If the HID Input Service or the underlying Bluetooth dependencies are not requirements for the Windows Embedded for Point of Service system, the Service can be disabled to clear up the error reporting in the Event Log.
If the HID Input Service is required, install the missing file following the steps below to start the service.
Browse to the %systemroot%\i386 folder.
Double-click the sp2.cab file, the compressed files in the .cab file will be listed.
Copy the hidserv.dll file to the %systemroot%\system32 folder.
Restart the HID Input Service, or reboot the computer.
This module discusses the role of operating system services and how to troubleshoot issues that restrict functionality. This module also discusses resolving issues with signing in to Windows.
This article provides resolutions for the problem that allows driver packages that contain hardware IDs that are not owned by the publisher to be downloaded and installed from Windows Update.
This article provides workarounds for the problem where a significant increase in Processor utilization (Interrupt & DPC time) while streaming Isochronous data to or from an IEEE 1394 device with Windows 7 IEEE 1394 bus driver, as compared with previous versions of the Windows IEEE 1394 bus driver.
This article provides a resolution for the problem where the hot-pluggable PCI Express or ExpressCard device may still appear in Device Manager after you remove the device.
This article provides a workaround for the issue that occurs when you configure the Wi-Fi connection settings in the Network Connections item in Control Panel on a Windows Embedded Compact 7 device.
This article provides resolutions for the problem when a User connects to a remote computer with RDP and attempts to load a graphics mirror driver on a remote system, the mirror driver may fail to install or start.
This article provides resolutions for the problem in which the actual I/O timeout is 10 times shorter than the specified value in User-Mode Driver Framework 2.0.