> ## Documentation Index
> Fetch the complete documentation index at: https://support.taltech.com/llms.txt
> Use this file to discover all available pages before exploring further.

# WinWedge stopped typing data into applications after a Windows 11 update

> If an older version of WinWedge receives device data but no longer types it into Excel or other applications on Windows 11, here is the cause and the fix.

Some older versions of WinWedge stop sending keystrokes into target applications after a Windows 11 update. WinWedge still receives the device data, but nothing appears in Excel or the other target application. This article shows how to confirm the cause and how to correct it.

## Confirm that WinWedge receives the data

First, make sure that the device data reaches WinWedge:

1. In WinWedge, go to **Port > Analyze**.
2. Send data from your device. Most devices send data when you press their PRINT button.
3. Look at the "Input" box.

If no data appears in the Input box, the problem is the connection, not the keystrokes. See [Device data is missing or unreadable](https://support.taltech.com/winwedge/device-data-is-missing-or-unreadable.md).

If data appears in the Input box but does not appear in your target application, continue below.

## Rule out the common causes

Make sure that the basic keystroke requirements are met:

1. Make sure that WinWedge is activated (**Activate > Test Mode** or **Activate > Normal Mode**).
2. Make sure that the cursor is in the target application, in the field where the data must go. In Keystrokes mode, WinWedge types into the window that has focus.
3. If data goes to the wrong program, see [Data is automatically entered into Notepad](https://support.taltech.com/winwedge/data-is-automatically-entered-into-notepad.md).

If the data still does not appear, and your PC updated to Windows 11, the version of WinWedge is the likely cause.

## Why this happens on Windows 11

Older versions of WinWedge use an earlier Windows method to send keystrokes. Windows 11 changed how it accepts these keystrokes. As a result, some older versions receive data correctly but cannot type it into other applications. The problem depends on the PC and the target application, so an older version can work on one Windows 11 PC and fail on another. See the [WinWedge Windows 11 compatibility guide](https://support.taltech.com/winwedge/winwedge-windows-11-compatibility-guide.md) for the full compatibility picture.

## The fix: upgrade to the latest version

The latest version of WinWedge sends keystrokes correctly on all versions of Windows, including Windows 11.

1. Download the [free trial of the latest version](https://www.taltech.com/support-resources/free-trial-downloads/) and install it on the Windows 11 PC.
2. Open your saved configuration file in the new version. Your settings carry over.
3. Activate WinWedge and make sure that the data appears in your target application.
4. If the trial resolves the problem, contact [sales@taltech.com](mailto:sales@taltech.com) to upgrade your license. Registered users get discounted upgrade pricing.

The trial is fully functional and stays active for 20 minutes at a time, which is enough to confirm the fix.

## Get help from an AI assistant

If you use an AI assistant (such as ChatGPT, Claude, or Copilot), you can copy this prompt to diagnose your exact situation:

Help me diagnose why WinWedge stopped typing data into my application.

First, read TALtech's article on this topic for full context: [https://support.taltech.com/winwedge/winwedge-stopped-sending-keystrokes-after-windows-11-update.md](https://support.taltech.com/winwedge/winwedge-stopped-sending-keystrokes-after-windows-11-update.md)

You are helping me troubleshoot WinWedge, a Windows program from TALtech that reads data from serial devices and types it into applications as keystrokes. My problem: data no longer appears in my target application. Ask me one question at a time to narrow the cause: whether data appears in WinWedge's Port > Analyze window when the device sends (if not, the problem is the serial connection, not keystrokes); whether WinWedge is activated in Test Mode or Normal Mode; whether the cursor was in the target field when data arrived (in Keystrokes mode, WinWedge types into the focused window); whether the PC recently updated to Windows 11; and which WinWedge version I run (Help > About). Known issue: some older WinWedge versions receive data but cannot send keystrokes on Windows 11. The fix is the latest version, and the free trial from taltech.com can confirm this before buying an upgrade. Walk me to the specific cause before recommending anything.

This article is from TALtech, makers of WinWedge and other Windows software
for collecting instrument data.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.