We just received an update from engineering that after a series of validations, the issue that you are experiencing is an expected behavior based on the way Windows handles localization. For more information, please check the link.
We just received an update from engineering that after a series of validations, the issue that you are experiencing is an expected behavior based on the way Windows handles localization. For more information, please check the link.