Dates not showing in COBOL executed entry screen since latest Windows Update installed overnight.  Date showing is blank.   Anyone else having this issue today.

The user is using WIndows 10 Pro

---

Dates not showing in COBOL executed entry screen since latest Windows Update installed overnight.  Date showing is blank.   Anyone else having this issue today.

We have a similar issue when using the calendar control, using Win 10 Pro with the 1703 (Creator) update, with 9.1.1 runtime.  The dates in the calendar control display are not blank, but they do not display correctly.  The control itself still works (we can pop the calendar and select a date), and the date selected is correctly interpreted by the program - it is only the display that is broken.

---

Dates not showing in COBOL executed entry screen since latest Windows Update installed overnight.  Date showing is blank.   Anyone else having this issue today.

This is a known issue with Microsoft's "Creator's Update" for Windows 10.
developercommunity.visualstudio.com/.../datetimepicker-control-broken-after-upgrade-to-win.html

"A fix for this issue is scheduled to be included in the June cumulative update for Windows 10." (from social.msdn.microsoft.com/.../date-time-picker-garbled-after-windows-10-creators-update

---

Dates not showing in COBOL executed entry screen since latest Windows Update installed overnight.  Date showing is blank.   Anyone else having this issue today.

Below is a few grabs of info from Windows reporting of the issue.
Date Time Picker garbled after Windows 10 Creators Update


More info, appears the Windows Update is #1703.

This is a bug in the Date Time Picker control implemented in COMCTL32.DLL version 5. There should be a fix for this issue in the near future.
The Date Time Picker control implemented in COMCTL32.DLL version 6 does not appear to be affected by this issue.

Another user complained and said give us the version 6 then, and then Microsoft, said there is other issues with version 6 that we cannot give it to you due to the other issues.
So the best recommend is:
to inform my customers to use group policies to stop all Windows updates until this is fixed.

Thanks for everyone's replies

---