W
WongShiuCheongDavid
Guest
In the past, I have setup a GPO to configure the short date format (under Control panel -> Region -> Formats) to MM/dd/yyyy
It works for Windows 10 build 1603 up to build 1803.
Recently, I have some machines upgraded to build 1903, and found that the short date format was changed to M/d/yy instead during the machine startup. If I run "gpupdate /force" manually and I can successfully changed it back to MM/dd/yyyy.
However, after PC startup, after the group policy is applied by system automatically (as showed up in the event viewer), the short date format is reverted back to M/d/yy
Furthermore, I found that the registry key - sShortDate was mysteriously missing after the PC reboot (before PC reboot, it was still there). If this key is missing, then the default format of the short date will become M/D/yyyy (without the leading zero for day and month).
My existing workaround is to add the timeout command to sleep for 60 seconds at the end of the login script. After the timeout, then run "gpupdate force" to set the key value. But this is NOT a solution. It's just workaround. It is at risk if the user close the login script window before gpupdate is executed. we rely on the short date format in generating customer reports.
David Wong
More...