|
Thanks for the thread name change. But, it's not just a Windows 11 problem. I first noticed it on Windows 11 21H2, but the problem persisted across an update to Windows 11 *22H2*, a mostly clean (kept my data) re-install of Windows 11 22H2 and now, a full, clean install of Windows 10 22H2. So, the [Windows 11] tag isn't actually valid.
Sorry.
|