PWAs fail to launch on my WoA (Arm64) environment

Question

For the past few months—coinciding roughly with an Edge Dev 153.0.4224.0 — PWAs have stopped launching on my Surface Pro 11th Gen (Arm64). When I click a PWA icon pinned to the taskbar, the progress cursor appears briefly, but nothing else happens. Clicking "Open" within the Edge Dev app management screen also yields no response.

The only exception is Figma: if I open it in browser mode and click a link within the application, it successfully launches in PWA mode.
PWAs appear to work without any issues in the retail version of Edge. I have already tried a repair installation of Edge Dev, but it did not resolve the problem.

I have submitted feedback directly through the Feedback Hub and built-in feedback feature in Edge Dev, but the issue remains unresolved after several months. Is this problem unique to my specific setup?

apsotech · Answer

Since PWAs work in the retail version of Edge but fail in Edge Dev, this points toward a possible issue with the Dev build or its PWA profile data rather than your Surface’s ARM64 hardware.

I’d try these steps:

Update Edge Dev to the latest available build and check whether the issue persists.
Test launching a PWA from edge://apps and compare it with the taskbar shortcut.
Create a fresh Edge Dev profile and install one PWA to see if the problem is profile-specific.
Check whether the installed PWA shortcuts still point to the correct Edge Dev executable.
If it still fails, capture the exact build number and submit a report through Feedback Hub, including the fact that Figma launches successfully through an in-app link.

Since you’ve already tried repairing Edge Dev, testing with a clean profile is a useful next step before reinstalling everything. For general technology tips and digital resources, you can also explore helpful online resources.

jamony · Answer

The useful comparison is that PWAs work in stable Edge on the same Surface, while both taskbar launch and the Dev app manager fail, and repairing Dev changed nothing. That narrows the investigation, but does not establish an Arm64-wide defect or a confirmed regression in the build you named. Update Edge Dev, record its full version and your Windows build, then create a separate Dev profile without importing extensions or settings. Install one affected PWA there and test it from that profile’s app manager. If it works, compare the original profile’s extensions and app installation; if it fails too, preserve that reproduction for Microsoft. Add both results and any relevant Application Error or crash details to your existing feedback. Use stable Edge’s working PWA installation meanwhile. Avoid deleting the original profile or app data before preserving anything important stored locally.

kaorunakajima · Answer

Thank you for your response.I have checked following items:&nbsp;A. I am using Edge Dev version 158.0.4344.0, which is likely the latest version. (Details regarding Windows, etc., will follow.)B. As previously mentioned, I have already tried a repair installation, but it made no difference.&nbsp;C. The issue does not occur on an x64 machine with a nearly identical configuration and profile.&nbsp;D. Launching PWAs via `edge://apps` does nothing; they fail to start. The same applies to attempts to launch them from the taskbar, Start menu, or desktop shortcuts.E. I created a new Edge Dev profile—with no extensions installed—and registered sites like microsoft.com and Google Calendar as PWAs; however, the issue persists, and the PWAs still fail to launch.F. I created a desktop shortcut via `edge://apps` and verified the target of the `.lnk` file.----Edge Dev (Main Profile):&nbsp;PWA fails to launch"C:\Program Files (x86)\Microsoft\Edge Dev\Application\msedge_proxy.exe" --profile-directory="Profile 1" --app-id=eocafagfdlbogdgjnjmoehjhjfnnpjln --app-url=https://www.microsoft.com/ja-jp --app-launch-source=4Edge Dev (Clean Profile): PWA fails to launch"C:\Program Files (x86)\Microsoft\Edge Dev\Application\msedge_proxy.exe" --profile-directory="Profile 13" --app-id=eocafagfdlbogdgjnjmoehjhjfnnpjln --app-url=https://www.microsoft.com/ja-jp --app-launch-source=4Edge Retail: PWA launches correctly"C:\Program Files (x86)\Microsoft\Edge\Application\msedge_proxy.exe" --profile-directory=Default --app-id=eocafagfdlbogdgjnjmoehjhjfnnpjln --app-url=https://www.microsoft.com/ja-jp --app-launch-source=4----G. In this state, simply changing the path from the Edge Dev directory to the Edge directory for `msedge_proxy.exe` allows the application to launch via the shortcut.H. The file "C:\Program Files (x86)\Microsoft\Edge Dev\Application\msedge_proxy.exe" does exist.I. While testing the above, I noticed that immediately after registering a site as a PWA in Edge Dev, the PWA window does not open. In the retail version of Edge, the PWA opens and displays a dialog (e.g., for pinning to the taskbar), whereas in Edge Dev, the PWA fails to open entirely.&nbsp;&nbsp;Taking all of this into account, it appears that the issue is not related to specific profiles or extensions, but rather to the behavior that occurs after `msedge_proxy.exe` is executed.I will submit this information to the Feedback Hub.&nbsp;Windows Version:Edition Windows 11 Enterprise Insider Preview Version 26H1&nbsp;Installed on 08/02/2026Evaluation expires: 11/01/2027 8:43OS build &lt;Will add more details later&gt;Serial number ----Experience Windows Feature Experience Pack 1000.26100.473.0Device:Device name pc-100021-2&nbsp;Processor Snapdragon(R) X 12-core X1E80100 @ 3.40 GHz (3.42 GHz)Installed RAM 16.0 GB (15.4 GB usable)Device ID ----Product ID ----System type 64-bit operating system, ARM-based processorPen and touch Pen and touch support with 10 touch points&nbsp;

kaorunakajima · Answer

28120.3302.&nbsp;

kaorunakajima · Answer

The above is my Windows 11 build information. I have added this as an update because, for some reason, my posts were being rejected when I tried to submit them to this forum.

Forum Discussion

PWAs fail to launch on my WoA (Arm64) environment

7 Replies