Possible Regression After PAD and Windows Update – Hyphen Character Removed During Web Input

林志忠 20 Reputation points
2026-11-18T06:12:29.2266667+00:00

Environment

Operating System:

Windows 11 Enterprise 25H2

Power Automate Desktop:

(please fill in current PAD version)

Issue Summary

A previously stable PAD flow began experiencing a significant increase in failures immediately after system updates.

The issue appeared after both:

  1. Power Automate Desktop update
  2. Windows 11 Enterprise 25H2 update

Since both updates occurred around the same time, it is currently unclear which component introduced the issue.

Expected Behavior

Document numbers should be entered exactly as stored in the source data.

Example:

A30-Q00164

Observed Behavior

During web form input, the hyphen character ("-") is occasionally removed.

Expected:

A30-Q00164

Actual:

A30Q00164

As a result, the target system cannot locate the corresponding document and returns a document-not-found result.

Business Impact

Before the updates:

309 records processed

2 failures

After the updates:

309 records processed

Approximately 78 failures

The issue causes roughly 25% of records to fail.

Additional Observations

The automation process itself has not been modified.

The source data remains unchanged.

Manual entry of the same document number works correctly.

The problem was first observed immediately after both the PAD update and Windows 11 25H2 update.

Request

Please help determine whether this behavior is related to:

  • Power Automate Desktop update
  • Windows 11 25H2 update
  • Browser automation compatibility changes

Any known issues, workaround recommendations, or hotfix plans would be greatly appreciated.

Windows Version:

25H2

Browser: 

Microsoft Edge 157.0.4341.60

PAD Version: 2.74.191.26302

Input Action Used: Get subtext

Populate text field on web page

(or Send Keys / Set Text)

The document number is extracted and processed using PAD text actions (including "Get subtext") before being entered into a web page.

After recent PAD and Windows updates, some document numbers lose the hyphen ("-") during execution.

I have not yet been able to determine whether the issue occurs during text processing or during web input.

Original value from Excel:

A30-Q00164

Value after Get subtext:

A30-Q00164

Value entered into webpage:

A30Q00164

Windows for business | Windows Client for IT Pros | Performance | Application technologies and compatibility

Answer accepted by question author
Chen Tran 13,630 Reputation points Independent Advisor
2026-11-18T07:22:24.54+00:00

Hello,

Thank you for posting question on Microsoft Windows Forum!

Based on the issue description as well as the provided logs, the problem probably occurs during the web input step, not during text processing. Your observation that Get subtext produces A30-Q00164 with the hyphen intact might be a clue. The hyphen is being lost when Power Automate Desktop (PAD) hands the string over to the browser. The combination of PAD build 2611 (2.74.191.26302, released November 10, 2026) and the updated Edge/Windows 25H2 stack might introduce a compatibility regression in how PAD simulates input for the “Populate text field on web page” action.

The “Populate text field on web page” action has two modes, configured under Advanced options. For JavaScript injection (default) of which PAD sets the field’s value directly via script. This is fast but can be silently altered by the page’s own JavaScript validation or event handlers, especially after a browser engine update. On the other hand, for “Populate text using physical keystrokes” of which PAD emulates actual keyboard events character by character. This is more faithful to real user input but is sensitive to timing, focus, and keyboard layout changes.

The recommended workaround to test a small batch of records after each change is to toggle the “Physical Keystrokes” option by going to your “Populate text field on web page” action → Advanced → and uncheck “Populate text using physical keystrokes”. Then run a test batch. If the hyphen is still lost, re-enable it and test again. Some environments require the opposite toggle state after an update.

If the web action remains unreliable, you can try to bypass it by using “Populate text field in window” instead. This action sends genuine hardware-level keystrokes to the control and is less dependent on the browser’s JavaScript layer. Using the UI element picker to target the same field, but select the window-based action. Ensure the field is focused first (via a “Click” action) before populating.

In order to rule out any subtle data-type or encoding issue, I suggest to temporarily replace the variable in the populate action with a hard-coded string like TEST-HYPHEN-123. If the hyphen survives, the problem is variable-related (like a hidden character). If it still disappears, the action/browser combination is definitely at fault.

Please be aware: Your build is the current worldwide release. It is suggested to monitor PAD release notes and check the official “Released versions for Power Automate for desktop” page periodically for a 2612 or 2611-update build that may include a fix for input simulation regressions.

For further reference:

Hope this might help. If it is. Please free feel to accept the answer.

Was this answer helpful?

1 person found this answer helpful.

0 additional answers

Sort by: Most helpful

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.