Thanks @Dan. I see it now. For the future, it can be replicated by US users (and other cultures that use a period for the decimal point) by the following. Alternately, you can set up a new user account with the needed language settings).
- Go to Settings
- Go to time and language
- Select Administrative language settings
- click Formats tab
- click Additional Settings
- Change “decimal symbol” to comma (pick from drop-down, don’t enter it)
- Click OK and back out of everything.
Going to Status/Version
then results in nothing. Internally, an exception was being thrown as a hardcoded version string (“1.193”) was converted to a double. This caused an exception. The solution was to convert with CultureInfo.InvariantCulture
This will be fixed in 1.194. Hopefully out next week.