TL;DR: A bug in Windows 11 23H2, following the KB5046633 update ... this is merely a visual bug, meaning the problem itself ...