The IntelliMouse Optical Wheel Mouse Scroll Wheel Does Not Work As Expected (327808)



The information in this article applies to:

  • Microsoft Windows XP Home Edition
  • Microsoft Windows XP Professional
  • Microsoft Intellimouse Optical Wheel Mouse

This article was previously published under Q327808
IMPORTANT: This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:

256986 Description of the Microsoft Windows Registry

SYMPTOMS

When you try to use your Microsoft IntelliMouse Optical Wheel Mouse, the scroll wheel does not work as expected.

CAUSE

This behavior may occur if both of the following conditions are true:
  • You connected your mouse to your computer through the PS/2 port.

    -and-
  • You installed Windows by using Remote Installation Services (RIS) and an image that was created by using the Riprep tool.

RESOLUTION

To work around this issue, use one of the following methods.

Method 1: Set the Wheel Detection Option

  1. Click Start, and then click Run.
  2. In the Open box, type main.cpl, and then click OK.
  3. Click the Hardware tab, click Microsoft IntelliMouse Optical Wheel Mouse, and then click Properties.
  4. Click the Advanced Settings tab, and then click Assume wheel is present in the Wheel Detection list.
  5. Click OK, and then click OK.

Method 2: Delete the EnableWheelDetection DWord Value

If 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\EnableWheelDetection

You can use the following script to delete this key from Setupreg.hiv:
reg.exe LOAD HKLM\t Path_to_setupreg.hiv_in_the_flat_image
reg.exe DELETE HKLM\t\ControlSet001\Services\i8042prt\Parameters /v EnableWheelDetection /f
reg.exe UNLOAD HKLM\t
				

Method 3: Set the EnableWheelDetection DWord Value in the Registry

For multiple computers, you can set the Wheel Detection option to Assume wheel is present by modifying the registry.

WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.

Follow these steps, and then quit Registry Editor:
  1. Click Start, click Run, type regedit, and then click OK.
  2. Locate and then click the following value in the registry:

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\ACPI\PNP0F13\DEVICE GUID\Device Parameters\EnableWheelDetection

  3. On the Edit menu, click Modify.
  4. Type 2, and then press ENTER.
(In step 2, DEVICE GUID is the globally unique identifier [GUID] for your mouse.)

If a PNP0F06 key exists under the ACPI key, set EnableWheelDetection to 2 for this key. Follow these steps, and then quit Registry Editor:
  1. Click Start, click Run, type regedit, and then click OK.
  2. Locate and then click the following value in the registry:

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\ACPI\PNP0F06\DEVICE GUID\Device Parameters\EnableWheelDetection

  3. On the Edit menu, click Modify.
  4. Type 2, and then press ENTER.
(In step 2, DEVICE GUID is the GUID for your mouse.)

NOTE: You must restart Windows for these changes to take effect.

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

Modification Type:MinorLast Reviewed:12/31/2002
Keywords:kbbug KB327808