Power Automate for desktop - Build 2605

This article describes the new features, improvements and fixes to existing functionality that are included in this build.

Installer version 2.68.237.26118 - Microsoft Store version 11.2605.237.0 updates

New features

• The version comparison capability has now been introduced in the built-in version control of Power Automate for desktop, enabling users to compare two versions of a desktop flow side by side and see exactly what changed across subflows, actions, variables, UI elements, and images. A search function is available within the comparison view to quickly locate specific changes.

• The 'Run Power App' action has now been introduced in Power Automate for desktop, enabling users to create, open, and run a Power App that integrates directly with their desktop flow, unlocking important attended scenarios.

  This feature is currently available in preview.

• Support for co-presence has now been introduced in the flow designer of Power Automate for desktop, showing the avatars of other users who are currently working on the same flow and allowing teams to coordinate their work in real time.

• The ability to test individual subflows of a desktop flow has now been added to the Testing module via a new dedicated action, allowing users to run and validate a specific subflow in isolation without running the entire flow.

• The 'Filter list' action has now been introduced in the 'Variables' module, allowing users to filter list items based on configurable conditions.

Enhancements & Improvements

• Users can now modify existing desktop flows using natural language through Copilot. Describe the changes to apply, and the flow is updated accordingly.

  This capability is currently available in US environments, where describing a flow with Copilot is also enabled.

• Support for UIA3 Raw automation has now been introduced, expanding UI automation capabilities for applications that rely on the UIA3 Raw accessibility framework. The corresponding capturing mode for UI elements has been added to both the UI element picker and UI element inspector windows.

• A confirmation dialog has now been added to the ‘Restore’ option of version control, requiring explicit confirmation before a previous flow version is restored. This prevents accidental overwriting of the current version.

• A new DisableExamples registry setting is now available for administrators, enabling them to hide specific example categories or all examples in Power Automate for desktop. This provides a governance option for organizations where example flows are not governed by DLP policies.

• The file upload limit for OneDrive integration in desktop flows has now been increased from 4 MB to 250 MB.

Repaired functionality

The following list details issues in Power Automate for desktop that are now resolved:

• An issue where reverting the UIFlowService to its default service account using the Machine Runtime troubleshooting tool resulted in a StatusInvalidParameter error has now been resolved.

• An issue where a silent upgrade of Power Automate for desktop could encounter an unhandled COM exception during installer shutdown has now been resolved.

• An issue where Data Loss Prevention (DLP) policies failed to load intermittently in the flow designer due to a race condition has now been resolved.

• An issue where the input method editor (IME) candidate window appeared at the corner of the screen instead of near the cursor when typing in the variable picker search box has now been resolved.

• An issue where deleting a desktop flow that uses OneDrive storage could fail when the associated OneDrive resource was no longer present has now been resolved.

• An issue where saving a desktop flow could fail with a ‘Connection State is closed’ error has now been resolved.

• An issue where the flow checker stopped validating actions placed after a 'Run subflow' action in a subflow has now been resolved.

• An issue where saving a desktop flow that contained 500 or more associated binaries failed with a ‘too many operations’ error has now been resolved.

• An issue where the Testing module was not shown at the top of the actions list, when creating a new test flow with the preloaded designer instance option enabled, has now been resolved.

• An issue where test flows were not correctly identified and displayed as drafts in the Power Automate console has now been resolved.

• An issue where opening the desktop flow properties side panel showed a validation error for the Actions logs verbosity setting when the stored value was below the environment minimum has now been resolved. The verbosity setting is now automatically adjusted to the environment minimum when this condition occurs.

• An issue where the flow storage schema deprecation banner was displayed after switching to an environment that contains no V1 flows has now been resolved.

• An issue where the flow timeout property configured in the desktop flow details was not applied to cloud-initiated desktop flow runs has now been resolved.

• A more appropriate error message is now displayed when Dataverse permissions are missing during credential retrieval in desktop flows, providing clearer guidance on the required configuration.

• An issue where applying a filter to a data table using values that contain certain special characters caused a syntax error has now been resolved.

• An issue where the Java bridge was incorrectly attached during certain SAP automation sessions has now been resolved.

• An issue where the Windows credential picker was not displayed correctly during automated flow runs that require credential input has now been resolved.

• An issue where downloading a control repository whose content includes Japanese or other non-Latin characters resulted in corrupted file contents has now been resolved.

• An issue where certain navigation errors introduced in Microsoft Edge version 146 were incorrectly interpreted as IE Mode indicators, causing inconsistent behavior in browser automation actions, has now been resolved.

• An issue where a webhook action placed as the last step in a desktop flow could cause an error at the end of a cloud run due to a race condition, and an issue where the waiting state was not correctly preserved for webhook actions during cloud runs, have now been resolved.

• An issue where the Power Automate for desktop installer failed on machines where the Log On As Service right is restricted, because the crash monitor service was not granted the required permission during installation, has now been resolved.

• An accessibility issue in the applied filter count of the variables pane has now been resolved.

Return to the all version availability page.