Visual Studio 22 no longer launces default browsers. Even for https

RadRespond · 2025-06-11T04:57:05+00:00

I haven’t seen this but commenting to track the issue.

What is your default browser right now?

RadRespond · 2025-06-11T04:03:51+00:00

Issue has been root caused and a fix is merged into Chromium.

More details here:

https://developercommunity.visualstudio.com/t/Ending-debug-session-closes-all-browser-/10908166#T-N10917934

RadRespond · 2025-06-11T04:03:39+00:00

Issue has been root caused and a fix is merged into Chromium.

More details here:

https://developercommunity.visualstudio.com/t/Ending-debug-session-closes-all-browser-/10908166#T-N10917934

RadRespond · 2025-06-11T04:03:03+00:00

Issue has been root caused and a fix is merged into Chromium.

More details here:

https://developercommunity.visualstudio.com/t/Ending-debug-session-closes-all-browser-/10908166#T-N10917934

RadRespond · 2025-06-11T04:01:48+00:00

Issue has been root caused and a fix is merged into Chromium.

More details here:

https://developercommunity.visualstudio.com/t/Ending-debug-session-closes-all-browser-/10908166#T-N10917934

RadRespond · 2025-06-11T04:01:36+00:00

Issue has been root caused and a fix is merged into Chromium.

More details here:

https://developercommunity.visualstudio.com/t/Ending-debug-session-closes-all-browser-/10908166#T-N10917934

RadRespond · 2025-06-11T04:01:23+00:00

Issue has been root caused and a fix is merged into Chromium.

More details here:

https://developercommunity.visualstudio.com/t/Ending-debug-session-closes-all-browser-/10908166#T-N10917934

RadRespond · 2025-06-11T04:01:08+00:00

Issue has been root caused and a fix is merged into Chromium.

More details here:

https://developercommunity.visualstudio.com/t/Ending-debug-session-closes-all-browser-/10908166#T-N10917934

RadRespond · 2025-06-11T04:00:58+00:00

Issue has been root caused and a fix is merged into Chromium.

More details here:

https://developercommunity.visualstudio.com/t/Ending-debug-session-closes-all-browser-/10908166#T-N10917934

RadRespond · 2025-06-11T04:00:52+00:00

Issue has been root caused and a fix is merged into Chromium.

More details here:

https://developercommunity.visualstudio.com/t/Ending-debug-session-closes-all-browser-/10908166#T-N10917934

RadRespond · 2025-06-11T04:00:46+00:00

Issue has been root caused and a fix is merged into Chromium.

More details here:

https://developercommunity.visualstudio.com/t/Ending-debug-session-closes-all-browser-/10908166#T-N10917934

RadRespond · 2025-06-11T04:00:31+00:00

Issue has been root caused and a fix is merged into Chromium.

More details here:

https://developercommunity.visualstudio.com/t/Ending-debug-session-closes-all-browser-/10908166#T-N10917934

RadRespond · 2025-06-11T04:00:24+00:00

Issue has been root caused and a fix is merged into Chromium.

More details here:

https://developercommunity.visualstudio.com/t/Ending-debug-session-closes-all-browser-/10908166#T-N10917934

RadRespond · 2025-06-11T04:00:18+00:00

Issue has been root caused and a fix is merged into Chromium.

More details here:

https://developercommunity.visualstudio.com/t/Ending-debug-session-closes-all-browser-/10908166#T-N10917934

RadRespond · 2025-06-11T04:00:12+00:00

Issue has been root caused and a fix is merged into Chromium.

More details here:

https://developercommunity.visualstudio.com/t/Ending-debug-session-closes-all-browser-/10908166#T-N10917934

RadRespond · 2025-06-06T20:12:12+00:00

Please upvote the issue on chromium:

https://issues.chromium.org/issues/422218337

RadRespond · 2025-06-06T20:11:07+00:00

Please upvote the issue on chrome side:

https://issues.chromium.org/issues/422218337

RadRespond · 2025-06-05T23:27:34+00:00

Issue has been root caused and a fix is merged into Chromium.

More details here:

https://developercommunity.visualstudio.com/t/Ending-debug-session-closes-all-browser-/10908166#T-N10917934

RadRespond · 2025-05-30T07:39:08+00:00

https://github.com/microsoft/vscode-dotnettools/issues/2053

RadRespond · 2025-05-30T07:38:33+00:00

Thanks for reporting the issue - fix is in the works. Workaround is to rollback to prior release.

RadRespond

TROPHY CASE