Article ID: 327808 - View products that this article applies to.
This article was previously published under Q327808
When you try to use your Microsoft IntelliMouse Optical Wheel Mouse, the scroll wheel does not work as expected.
This behavior may occur if both of the following conditions are true:
To work around this issue, use one of the following methods.
Method 1: Set the Wheel Detection Option
Method 2: Delete the EnableWheelDetection DWord ValueIf you are maintaining the RIS image, work around this problem for all Riprep images that are deployed from the server. To do this, delete the EnableWheelDetection DWord value in the Setupreg.hiv file in the installation image on the RIS server.
NOTE: This change is to the flat image hive (.hiv) file and not the hive file in the RIPREP image.
To do this, delete the following registry value from the Setupreg.hiv file:
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Services\I8042PRT\Parameters\EnableWheelDetectionYou can use the following script to delete this key from Setupreg.hiv:
Method 3: Set the EnableWheelDetection DWord Value in the RegistryFor multiple computers, you can set the Wheel Detection option to Assume wheel is present by modifying the registry.
Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
(https://support.microsoft.com/kb/322756/ )How to back up and restore the registry in Windows
Follow these steps, and then quit Registry Editor:
If a PNP0F06 key exists under the ACPI key, set EnableWheelDetection to 2 for this key. Follow these steps, and then quit Registry Editor:
NOTE: You must restart Windows for these changes to take effect.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.
Article ID: 327808 - Last Review: December 31, 2002 - Revision: 1.3