I was able to recreate the behavior on my end. It occurs when your OS is set to use Comma instead of Period for decimal separation (which I noticed in the OP screen shot). I've logged a bug to get this addressed. The workaround for now is to simply manually enter the correct values and either save as a new preset or, once you've created the file, use the "Recent" saved version for future new documents.