This article was previously published under Q273033
This article has been archived. It is offered "as is" and will no longer be updated.
When you are using function keys or special volume control keys on your keyboard to change the volume settings, these volume control settings may not persist after you restart your computer.
In addition, if the Volume Control tool is open, you may see the Volume Control slider change according to your settings, and then when you close the Volume Control tool, and restart your computer, the slider is reset to its original position.
This problem can occur if the following conditions exist:
You are using a Windows Driver Model (WDM) audio driver.
You have adjusted the volume settings by pressing the appropriate volume, or mute key on your computer keyboard, or by using one of the following key combinations:
FN+PAGE UP (increase volume)
FN+PAGE DOWN (decrease volume)
The volume control settings are in the registry. When you are using the function keys, and special keys to change the volume settings, these changes are not saved to the registry. Thus, when the computer starts, the original settings are reloaded from the registry, and are applied by the audio driver as current settings.
Another reason for this behavior is that when you open the Volume Control tool, it always reads the volume control settings from the registry, and displays the controls accordingly. When you quit, and then restart Volume Control, the slider is reset to the original position.
To resolve this problem, obtain the latest service pack for Windows 2000. For additional information, click the following article number to view the article in theMicrosoft Knowledge Base:
260910 How to Obtain the Latest Windows 2000 Service Pack
To work around this problem, double-click the Volume icon, which is located on the taskbar, adjust the appropriate volume settings, and then quit the Volume Control tool.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Windows 2000 Service Pack 2.
The fix for this issue will be included in a later Service Pack.