Completely agree.
They know the issue happened as soon as a Cumulative patch and code was sent to machines to enable "Tabbed Explorer Browsing" (back in November/December time last year). As the default first Windows 11 22H2 image (from September/October) that released did not have tabbed explorer browsing and did not have this issue we are all experiencing.
I think they worked out early on that any future Cumulative patch would not resolve this issue with out removing Tabbed Explorer Browsing. They wont remove tabbed explorer browsing due to it being a unique selling point. They sold this feature to companies saying "its a good time to switch to Windows 11 now from 10 to gain access to this long requested feature".
The reason MS worked out from early on of this exact issue, is of people like my self (IT Admins) and many others whom reported the issue to MS directly via our companies premium support package plus community members (i.e. this original post too!)
The only way they was able to fix this issue currently is to release a whole new OS (23H2), which we have tested and the last two preview builds they have released does have this fix in place.
What's shocking and sad to see, is moderators must see the amount of people posting here, and it shouldn't be left to the community to predict how MS work and predict when they will release a fix.
My prediction will be this will be only fixed when they officially release 23H2 in the Autumn/Fall period of this year. But again, its sad we have to do this type of prediction.
As a side note, I have prevented my company of 20,000 computers from migrating to Windows 11 because of this bug. I would imagine many more companies have done the same. Or they have spotted this issue too late and rolling back to issuing Windows 10 again.
Its a serious bug.