Select the product you need help with
- Internet Explorer
- Windows Phone
- More products
You hear a beep sound when you change the selection in a classic style ListView when the "Select" option for the system sound is set to "None" in Windows Vista
Article ID: 944150 - View products that this article applies to.
Important This article contains information about how to modify the registry. Make sure that you back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/322756/ )How to back up and restore the registry in Windows
When you change the selection in a classic-style ListView, you may hear a beep sound even when the Select option for the system sound is set to None.
This problem does not occur in applications that have been updated to use the themed ListView in Windows XP or in Windows Vista.
This problem occurs if the Select option for the system sound is changed in the Sound Control Panel item, and then the system sound is changed back to None. This problem occurs if the system sound is changed directly or as part of a sound scheme. When the system sound is changed in this manner, an empty sound key is stored in the registry. However, in this case, no sound key should be stored in the registry. The classic ListView plays a default beep sound when an empty sound key is stored in the registry.
To resolve this problem, use one of the following methods.
Method 1: Change the system sound to a silent .wav file
Method 2: Delete the .Current registry subkeyWarning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall the operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Article ID: 944150 - Last Review: November 6, 2007 - Revision: 1.1