New
#11
...in this case, only because earlier builds were not fully Win10-compatible.
FWIW:and I always make it a rule to reboot the machine after updating the database to recheck the version is just that plus the current letter (g) at time of typing so it should read 16.0.1.445 (g) when you click on tech support. I usually run the settings while the database is updating
According to the KL global website, the KL forum and my own system running KIS 2016 MR1 (16.0.1.445), the current patch build is (c), not (g).
Patch (g) is for KIS 2016 MR0 (16.0.0.614), which is NOT the latest release build and has some bugs (Win10 and other) that are fixed in MR1.
Cheers,
MM