So I found an article from Microsoft that says the issue was resolved on 12/10 on their end via patch KB5048667. However, I have this patch installed an still experiencing same issue. Can someone please confirm if it's fixed for them with this patch?...
