ALT+F4 Application Errors - Memory Leaks

crypticus

Well-Known Member
Happened after fresh install, I was at windowsupdate page, checked for updates it started to download some and then installed them, I went to kitchen to eat, so that page was open nearly 20 minutes on idle.. I came back screen was not locked, so I did alt+f4 to close that page , then i got this error.

1640375086054.png
I think others got the same error before. and i think i got this error when win11 first out too. used latest win11 and latest ntlite. so this bug was always here? edit: also here
 

Attachments

  • Windows 11.xml
    17 KB
Last edited:
nuhi, launcher ofc works fine. the problem happens when you alt+f4
edit: as you see in video this sould happen on anyone.



* yes, but launcher is enough to replicate issue, and to launch launcher, i put game in iso and only launch from there.
* on my end virtualbox works fine (i had same problem like you in the past, to solve it. you have to fresh install your main machine.) after that you wont get vbox errors and dont need to change any settings.
 
Last edited:
OK, I see the error on Alt+F4, man if I ever saw a weirder report :)
On it, thanks for your patience.
 
sorry it was my mistake, i know i don't always explain things clearly enough. i get a bit excited and write fast without re-reading....

btw garson had same error during installing firefox (without alt+f4). and i pin pointed it to the same component on his preset. maybe u can try that one too. it should happen in my preset too since it was the same component? idk.
 
I get systemsettings errors just by renaming something. Even if i rename to default the error stays.
A user at mdl gets an error running a debloat script. I think its a wider ms problem to be honest.
 
probably it can be triggered by many things then.... but still we found one triggered by component removal. microsoft can fix rest
 
sorry it was my mistake, i know i don't always explain things clearly enough. i get a bit excited and write fast without re-reading....

btw garson had same error during installing firefox (without alt+f4). and i pin pointed it to the same component on his preset. maybe u can try that one too. it should happen in my preset too since it was the same component? idk.
Nothing to be sorry about, the title of the topic states Alt+F4, it is me who is trying to save time.

So, here are my findings:
- Origin Online Launcher actually crashes on its own on Alt+F4, even on full intact Windows, if it gained connection to the server.
You can replicate it by not having internet, Alt+F4 will be silent even on removed error reporting component.
Once it connects, Alt+F4 is crashing it.
Someone could report that to them to fix, seems that they are not not gracefully exiting and closing the connection.

- That said, why then the error message after removing the Error Reporting pieces.
Because each time on that crash, Windows is submitting a report of a crash, and in this case if WerFault.exe is removed, it will produce that wonderfully undescriptive message, which silent app crash starts in the background.

You can also replicate that as well by simply removing/renaming c:\Windows\SysWow64\werfault.exe on full Windows.
Unfortunately going the opposite way from a removed component, it's not just that file that's enough to silence it.

In summary you can relax about the error, it's harmless as it's not causing the actual crash, just uncovers it.
But I will see about bypassing, or at least moving the needed binaries to the Error Reporting Service component, then keep only that for the usual silent crashing.
I do disable Error Reporting on removal, but seems like it's not working, or it's not fully applied for 32-bit, will double-check that as well.

As for Firefox, we'll go into more detail of it if it is not also silenced by this adjustment and keeping the Error Reporting Service in the future, I cannot find garson's preset to try and Firefox Offline setup worked.
 
To fix this, or should I say silence the app errors on OS-es having the Error Reporting removed, copy these from full OS image:
C:\Windows\SysWow64\werfault.exe
C:\Windows\System32\en-us\werfault.exe.mui
Note that first location is 32-bit, second one 64-bit, and replace en-us with your language, in this example
C:\Windows\System32\tr-tr\werfault.exe.mui
Of course for 64-bit apps, one would add C:\Windows\System32\werfault.exe to the mix.

Let me know how it goes, might even split this as a base component, so you can remove all else.
 
nuhi One of the latest vertsions of firefox has been buggy as hell and practically unusable. Dont bank on it being perfect.
 
- That said, why then the error message after removing the Error Reporting pieces.
Because each time on that crash, Windows is submitting a report of a crash, and in this case if WerFault.exe is removed, it will produce that wonderfully undescriptive message, which silent app crash starts in the background.

You can also replicate that as well by simply removing/renaming c:\Windows\SysWow64\werfault.exe on full Windows.
Unfortunately going the opposite way from a removed component, it's not just that file that's enough to silence it.

In summary you can relax about the error, it's harmless as it's not causing the actual crash, just uncovers it.
But I will see about bypassing, or at least moving the needed binaries to the Error Reporting Service component, then keep only that for the usual silent crashing.
I do disable Error Reporting on removal, but seems like it's not working, or it's not fully applied for 32-bit, will double-check that as well.

As for Firefox, we'll go into more detail of it if it is not also silenced by this adjustment and keeping the Error Reporting Service in the future, I cannot find garson's preset to try and Firefox Offline setup worked.
Hi nuhi

I think this is exactly what happened in my scenario with firefox installation. With error reporting present, I was getting error in Event Viewer->Windows Logs->Application, and that was caused by Windows Firewall component being removed (which is fine). And it was silent error, nothing was shown on the screen while firefox was being installed.
But if error reporting was removed, I was getting error popup saying Memory could not be read ... , and it was logged in Event Viewer, but in System section.

Here's my preset, it is in another topic.
I guess your findings will be same as mine.
 
Here is his preset nuhi from this topic:
edit1: it seems i was 3 mins late :)

edit2: yes u are probably right about this: Someone could report that to them to fix, seems that they are not not gracefully exiting and closing the connection. because even tho you cover that error by placing those files. still you will hear error sound coming from it when u make alt+f4 :) and yes placing them corrects the issue. i reported this problem to the owner of that game. thx

edit3: there is also same exe file in C:\Windows\System32 in original. but we don't need it right?

nuhi One of the latest vertsions of firefox has been buggy as hell and practically unusable. Dont bank on it being perfect.
yes its buggy on usage but, error is during installation
 

Attachments

  • Test Preset.xml
    26.5 KB
Last edited:
OK, thanks for the feedback.
Will add "Windows Error Reporting popup" compatibility option, enabled by default, which will protect the needed files for this popup to be silent as before removing the component.
Those that do not mind the errors can untick that.
 
Just reporting my findings :). I dont install, i just extract and run "portable". W7.
Is there any browser that's not buggy?:D
OK, thanks for the feedback.
Will add "Windows Error Reporting popup" compatibility option, enabled by default, which will protect the needed files for this popup to be silent as before removing the component.
Those that do not mind the errors can untick that.
Does this mean that you will still be able to remove Windows Error Reporting, but some files will be protected from deletion?
 
Is there any browser that's not buggy?:D
It was bad to the point it was unusable, had to go back to an older version. Thats why i mentioned it here, it was very bad.

Does this mean that you will still be able to remove Windows Error Reporting, but some files will be protected from deletion?
Prolly, like removing Internet Explorer but keeping a couple of files that are needed by Explorer.
 
yes yes probably only WerFault is needed.... i fixed it on my end by nuhis guide. its all ok now.
 
Refactored Windows Error Reporting component, released in build 8567, let me know if there are any remaining issues with the error popups if the newly split Error Reporting API component is kept.
 
Back
Top