Could not connect to Debug Target (Could not find any debuggable target)

Describe the bug
Receive an error when trying to launch chrome from visual studio with an Angular application. We have 2/3 developers experiencing the error, and I have my personal and work computers both having the same error. The chrome browser starts immediately after starting the debug but stays on the 'about:blank' page. Usually after starting the debug session, VS code connects to the chrome debug session and redirects to the localhost/port of the application specified in the launch.json.

Error: Unable to launch browser: "Could not connect to debug target at http://localhost:9222: Could not find any debuggable target"

To Reproduce
Steps to reproduce the behavior:

1. Start angular/.net application with "Debug Chrome" launch config or "Debug Both" launch config (launch config attached below).

Log File: vscode-debugadapter-62f25232.json

Launch File: launch.json

VS Code Version: 1.102.0

Additional context
This configuration has been working for 4+ years, have started getting this error in the last week. I usually run the project using "Debug Both". I have checked if 9222 port is being used, it is not. Seems like the debugger is trying to attach before chrome is ready. I created an attach to chrome launch configuration temporarily until this has been fixed.

Ports
Angular: 4200
.NET: 44356
Chrome debug: 9222