BUG: Visual Basic SendKeys causes incorrect keyboard status or freezes keyboard

This article was previously published under Q297108
This article has been archived. It is offered "as is" and will no longer be updated.
SYMPTOMS
You have a Microsoft Visual Basic program that uses the SendKeys function. The program works fine on Windows 95, Windows 98, or Windows NT-based computers. However, when you run the application on Windows 2000, either from the Desktop or through Terminal Services, the keyboard may freeze or go into an incorrect status.
CAUSE
On Windows NT and Windows 2000, the Visual Basic SendKeys function toggles NUM LOCK, CAPS LOCK, and SCROLL LOCK when they are on. The Windows 2000 keyboard driver may not handle this behavior correctly, which causes the keyboard status to be incorrect or the keyboard to freeze.
RESOLUTION

Service pack information

To resolve this problem, obtain the latest service pack for Visual Basic 6.0. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
834001 List of bugs that are fixed in Visual Studio 6.0 Service Pack 6

Hotfix information

A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that this article describes. Apply it only to systems that are experiencing this specific problem.

Note You must have a Visual Studio license agreement to obtain this hotfix.

To resolve this problem, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.
   Date              Version      Size      File name        -----------------------------------------------------   04/23/2001        6.0.91.15    1.33 MB   MSVBVM60.dll     04/23/2001        6.0.0.8965   1.62 MB   VBA6.dll				

STATUS
Microsoft has confirmed that this is a bug in the Microsoft products that are listed in the "Applies to" section.This bug was corrected in Visual Basic 6.0 Service Pack 6.
REFERENCES
For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
834001 List of bugs that are fixed in Visual Studio 6.0 Service Pack 6
Properties

Article ID: 297108 - Last Review: 02/27/2014 21:08:20 - Revision: 6.2

Microsoft Visual Basic 6.0 Learning Edition, Microsoft Visual Basic 6.0 Professional Edition, Microsoft Visual Basic 6.0 Enterprise Edition

  • kbnosurvey kbarchive kbbug kbfix kbqfe kbpending KB297108
Feedback