Windows 10: Bug: Currency decimal digits showing incorrect value on build 1909

Hi All,


We are using below code to get decimal digits supported by currency.

NumberFormatInfo.CurrencyDecimalDigits VS 2017


For windows build prior to 1909, it was showing decimal digits as 0 which was correct for Colombian peso es-CO,COP

In 1909 it's showing as 2.


Does anyone know workaround for this?

:)

 

Win32PrioritySeparation with a value of decimal 26

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\PriorityControl]
"Win32PrioritySeparation"

Does the value of decimal 26 for Win32PrioritySeparation have a different effect on separation the hexdecimal 26?

if it does what would the effects be?

 

AMD Overdrive Updated to 2.1.5

AMD OverDrive™ Utility 2.1.5 (2008-11-7) Update list:

1. Fixed bug that BIOS version info is mistake.
2. Fixed bug that GPU memory size info for RV770 is wrong.
3. Fixed bug of CPU Fan speed reading: the value is incorrect on some boards.
4. Fixed bug that CPU temperature reads zero for some old K8 CPUs.
5. Improve AutoClock process to reset the system automatically if it hangs.
6. Fix bug CPU multiplier shows only one digit if there are two decimal digits in AutoClock page.
7. Fix bug GPU engine shows zero for RV770 graphic cards in GPU Status page.

 

Windows Calculator decimal separator is always comma

Hi,



To change the decimal symbol back to a period, follow these steps:

• In Control Panel, click Region. Click on Advance settings.
• Click the Number tab.
• Change the Decimal Symbol setting to a period (.).
• Click OK.

Please let us know if the issue still persists.