No, this has not been solved. Today is the middle of March of 2022 and I am on a brand new Surface Studio Laptop, up to date as of today, and the issue is still bugging the hell out of me. What are the clowns at MS doing?
That's because like everyone else commenting here you need to wait for the next update which should hopefully address this issue. I say 'should' because I've yet to see any official announcements confirming the fix but I do know that the Microsoft Insider Channel has now reported this issue as having been fixed. You do understand what the Insider Channel is don't you? Microsoft Insiders test things before they go to public release. Therefore if they're now reporting a fix has resolved this issue then a public release will follow.