It hasn't for me and my son now sees it on his Laptop (with a none preview release). We've sort of got used to it over the months.
I'm using 19h1_release 18356 and a reboot popped it up yet again. So no there has been no fix for this. You may just be lucky or happened to do something that unbeknown to use actually fixed it.