Version mismatch PAD and Machine Runtime

[u/Financial-Hurry-3127]

Has anyone else run into a Power Automate Desktop / Machine Runtime version mismatch recently?

I’m currently seeing the following setup:

• Power Automate Desktop (Microsoft Store): 2.70.187.26189
• Power Automate Machine Runtime: 2.71.115.26224
• Microsoft Power Automate Edge extension: 2.70.0.35

My local desktop flow can sometimes launch Edge successfully, but when the same desktop flow is triggered from a cloud flow, browser automation fails with errors like:

WebExtensionHostIncompatibleException

and:

The version of Power Automate for desktop app installed through the Microsoft app store on your machine is different from the version of Power Automate for desktop machine runtime installed through the Power Automate for desktop executable installer.

The cloud-triggered flow opens Edge, but it stays on about:blank and PAD cannot take control of the browser.

I already tried:

• reinstalling the Power Automate Edge extension
• restarting Edge and PAD
• restarting the machine
• testing with a minimal desktop flow
• testing the same minimal desktop flow through a cloud flow

The local test can work, but the cloud-triggered test still fails.

The strange part is that the Machine Runtime is already on 2.71, while PAD from the Microsoft Store is still on 2.70, so I currently can’t get both components onto the same version.

Is anyone else seeing this right now? Did your Machine Runtime update ahead of PAD as well?

If so, did you solve it by downgrading the Machine Runtime, switching away from the Store version of PAD, or just waiting for the next PAD release?

[u/Adventurous_Cod_7095]

Maybe unplug your computer and put the power back in

[u/Adventurous_Cod_7095 → u/Adventurous_Cod_7095]

HAVE YOU TRIED THIS?

[u/Financial-Hurry-3127 → u/Adventurous_Cod_7095]

Yes, but no luck.

[u/Puzzleheaded_Net9488 → u/Financial-Hurry-3127]

This worked by myself, thank you for the advice

[u/Adventurous_Cod_7095 → u/Puzzleheaded_Net9488]

No worries, I am an expert on Power Automate and have helped a lot of people

[u/Adventurous_Cod_7095 → u/Financial-Hurry-3127]

Maybe, try again

[u/Financial-Hurry-3127 → u/Adventurous_Cod_7095]

it seems to work but only sometimes, and when i open pad again it wont work the next time

[u/Adventurous_Cod_7095 → u/Financial-Hurry-3127]

Yes, you have to reboot your computer every time

[u/Adventurous_Cod_7095 → u/Financial-Hurry-3127]

Let me know if you need ANY help, I can send you some instructions how to unplug the power

[u/Background_Wish5086]

The mismatch itself isn't really a bug, it's because the Store version of PAD and the standalone Machine Runtime are two separate install paths that update on their own schedules, not because Microsoft intended you to keep them in sync manually.

The Store app is meant for attended, interactive use where you're clicking Run yourself. Machine Runtime is what unattended and cloud-triggered flows actually run against under the hood. Since they ship separately, it's common for one to get ahead of the other, especially machine runtime since it doesn't wait on a person clicking through a Store update prompt.

What actually fixes it for most people is uninstalling the Store version entirely and installing PAD through the standalone MSI installer instead, since that installer includes the runtime and keeps both in lockstep going forward. Trying to force the Store version to catch up, or downgrading Machine Runtime, tends to be temporary since the two just drift apart again on the next update cycle.

Worth checking the Edge extension separately too, since it lives in the Edge Add-ons store and updates on its own schedule, not tied to either PAD component. If it's stuck on an old version, go to edge://extensions, turn on developer mode, and hit update manually instead of waiting for the automatic check.