Forum Discussion
Random PWA Identity Proxy Host background crashes
Windows Reliability monitor is showing a lot of random PWA Identity Proxy Host MoAppHangs which seem to be related to Edge Chromium. They seem to randomly occur after closing Edge Chromium. Using version 95.0.1020.53 (Official build)
Does anyone else see these instances in the Reliability Monitor?
22 Replies
Good morning
, I'm still having this issue on my W10 PC (21H2, version 10.0.19044). Do you have any suggestions to solve this issue? Many thanksBe quite random but still present in the latest Edge !
Pirmil Thanks for the heads up.
Alexandra-R Could you please check this issue again? Many still have this silent crash with the latest Edge version, even after the assumed fix.
Just found this thread tonight - same crash occurring here on Win 11 as of earlier this afternoon. Fully updated, actually did a Reset of Windows a couple days ago too.
I've had this the last 2 days where I close Edge after a day of it being on. I wouldn't know there was a problem unless I had way back (unrelated and gone but kept looking as a habit). I hope this gets resolved. It appears to be a behind the scenes, minor problem but nonetheless it's going to bug me.
- Sorry if this is a older thread but I wanted to chime in with my Windows 11 clean install experience and Edge v98, I just had my first PWA crash. Not sure why this is happening but I wanted to provide anything I can to help resolve.
Source
PWA Identity Proxy Host
Summary
Stopped responding and was closed
Date
2/11/2022 7:20 PM
Status
Report sent
Description
A problem caused this program to stop interacting with Windows.
Faulting Application Path: C:\Program Files (x86)\Microsoft\Edge\Application\98.0.1108.50\identity_helper.exe
Problem signature
Problem Event Name: MoAppHang
Package Full Name: Microsoft.MicrosoftEdge.Stable_98.0.1108.43_neutral__8wekyb3d8bbwe
Application Name: praid:App
Application Version: 98.0.1108.50
Application Timestamp: 6203c260
Hang Signature: 0000
Hang Type: 2097152
OS Version: 10.0.22000.2.0.0.256.48
Locale ID: 1033
Additional Hang Signature 1: 00000000000000000000000000000000
Additional Hang Signature 2: 0000
Additional Hang Signature 3: 00000000000000000000000000000000
Additional Hang Signature 4: 0000
Additional Hang Signature 5: 00000000000000000000000000000000
Additional Hang Signature 6: 0000
Additional Hang Signature 7: 00000000000000000000000000000000
Extra information about the problem
Bucket ID: 7ee0ba8423fcb64863536d4f7a66c893 (1392576897911015571) - Alexandra-R
Microsoft
Hey there OP! Feel free to respond on your other thread, but pasting this here in case anyone not caught in that one finds this and is seeing these crashes.
What version of Windows are you on, and are you interacting with Edge before you see these errors or are they somewhat 'random'? Have you installed any apps from the Microsoft Store, or have you installed any websites as PWAs prior to seeing this?
Alex Rowell (she/her)
Community Manager - Microsoft Edge
Discuss Stable features and issues on the answers.microsoft.com forums, join us on Twitter, or join the communities over on Reddit in r/MicrosoftEdge or r/edge- Im not geting this error anymore in version 97.0.1072.55,windows fuly updated.
I found your reply in the Reddit thread, will post my answer here as well:
1. I'm on Windows 10 21H1 (19043.1348), another user here is having the same issue. There are also ppl on Windows 11 having the same issue shown here . He had to disable Web Apps to solve this (I don't have this option to disable at all in the Edge "flags" link)
2. I think this seem to happen randomly when closing Edge but I'm not sure. Mind you it's very random and doesn't always occur.
3. As for the Store apps, I have the standard Microsoft Store apps along with nVidia Control Panel, Realtek Audio and Piano10 app.
4. I have not installed any PWA's.
johnjansenThanks for reporting this, JohnnyGui. I think this is a crash we are familiar with and believe we have fixed in the version 96 which should be available very soon.
If these continue after updating to 96, please let me know. Due to the somewhat random behavior, we cannot be 100% sure we fixed it completely.
-John Jansen
Engineering Manager, Edge
