Windows 10 Taskbar bug presented in 1709, worst on 1803 upgrade

Just another quick update...there was an RS5 build 17744.100.1 that was released a couple of days ago, and I haven't seen the jumplist font scaling issue with that, and the notification overflow icons are still good (I haven't seen padding / missing problems either).

Jason also called me today, to convey that the Windows Defender and other Microsoft teams have engaged on their blurry icon problems. In all likelihood that issue will be resolved for MS applications when RS5 (version 1809) is released.

I appreciate you sharing added information on this concern Jim Harle (O365). I guarantee that I'll keep monitoring and also will be updating everyone on this thread for and progress on this issue. I'll have this added on the report, as it also may help our developers. Thank you for your assistance.

If you have additional questions, please let me know by replying to this thread. This way, I'll get notified and respond back to you as soon as I can.

Best regards,

17738.1000 continues to be a good thing for the notification icons on my main PC. The only "real" issue I'm seeing, is that the font on jump lists is not always scaled properly:

Normal:

Wrong scaling:

I'd MUCH rather live with this, vs. the notification icon problem.

Thank you for sharing this your inputs on this issue. I'll be adding this on the report for the investigation.

I encourage everyone to please not hesitate to share your inputs on this thread. This is so I'd be able to have this added on the report I have submitted. 

Best regards,

I decided to "take one for the team" by installing the RS5 build 17738.1000 on my main PC. I've been running it for several days, and definitely see improvements, for both the missing icons and cutoff issues. It appears they have implemented what BryanLesher first suggested, in that the size of the overflow notification box is now (or mostly) correct.

There are still some weird padding issues (extra space) at times, as well as the blurry icon problem, but I'd say the current behavior is close to version 1709. Hopefully what I'm seeing proves true for others, and when the final 1809 version is released.

As a side note, I also tried putting the Enterprise edition of 17738.1000 on a couple of VMs (I like the "dark mode" that's been added, though it's not really complete yet). Both of those needed to be rolled back, as 17738.1000 broke the Edge browser, in that it wasn't able to create "content processes" making it completely useless. I also tried new user profiles and repairing Edge, neither of which fixed that. The Edge problem isn't happening on my main PC (running the Pro edition). It's not that I like Edge (I don't), but it is useful for a selection of work web sites that I use regularly, and not have to be consuming Firefox nor Chrome tabs. I guess that's a long way of saying, beware of installing the prerelease build on Enterprise edition.

Edit/Update: The Edge problem was rooted to the CrowdStrike Falcon agent being installed...it's not currently compatible with RS5 builds. Also, IPv6 is required to be turned on for Edge to function (it won't work if IPv6 is disabled on all adapters).