question

djlaserman avatar image
0 Votes"
djlaserman asked ZiemowitLaski-7262 commented

The debugger's worker process (msvsmon.exe) unexpectedly exited | VS 19, VS 22 in Win 11

After a fresh install of VS 19 and or VS 22, upon creating a WPF project and not doing anything else on it, trying to launch it with debugging churns out "The debugger's worker process (msvsmon.exe) unexpectedly exited..." in Windows 11. So basically no Visual Studio works in Windows 11. I've tried to add the entire folders of VS installations, individual files as well including the msvsmon.exe to antivirus and antimalware exclusions, checked if 127.0.0.1 was still my localhost address, ran sfc /scannow, ran chkdsk and the host of DISM commands to check health and restore health, restarted the PC, shut it down and brought it on again, but seems like the only development software that still works from Microsoft is VS Code. This is so disappointing noting that this error has been around since 2015 versions of VS and is still there in the very latest VS 2022! Same with Windows itself, the famous volume icon disappearing is still a thing in Windows 11, after having reported this a million times since Windows 7 as a Windows Insider, I got tired of sending reports. Now I just ignore the blank volume screen and quietly use EarTrumpet. But must I also abandon Visual Studio and rework my projects in Delphi because that always works and has never churned out dumb errors like this. A debugger that doesn't work in an IDE?! really. Microsoft is really going down the tubes. The Windows 11 start menu is also another eyesore and can't be organized, resized or grouped and looks like last minute noodles... OMG. Even the Tags in this very form don't work... not surprising

vs-generalvs-debugging
· 2
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Hello @djlaserman , welcome to Microsoft Q&A forum. I notice that there were several reported issues which are similar or the same to the error that you mentioned above, on our Developer Community. Could you share me the detailed version number of VS 2019(and VS 2022) and the detailed version of Windows 11 that you are using?

0 Votes 0 ·

I'm seeing the same behavior with Windows 10 Pro 21H2 (19044.1645, Experience Pack 120.2212.4170.0) and Visual Studio 2022 Community Version 17.2.1.
.

0 Votes 0 ·

0 Answers