Also confirmed this is still an issue after this morning's updates (which included another .13 kernel for reference.).
Also confirmed this is still an issue after this morning's updates (which included another .13 kernel for reference.).