This has always been one of the most frustrating bugs in Windows 10 1903, but it looks like Microsoft has finally deployed this fix.
According to tests and reports, the bug has been fixed in Windows 10 kb4524570 (updated on Tuesday). This fix is also obviously available for windows 10 November 2019 update.