cgoodman thank you for reporting the issue;
It happened after VS 2022 update, but it should be already fixed with the most recent update (17.5.2 I think).
This is sadly a Visual Studio feature, we don't interact with it.
Please let me know if the most recent update helped.