Config Admin can create illegal names on windows

The following names are not allowed to be used in a path on Windows:

CON, PRN, AUX, CLOCK$, NUL, COM1 ... COM9, LPT1 ... LPT9.

If the last part of the PID is one of these names then an exception results. I guess adding an extension (.cfg) to this file would prevent this clash. There might actually

java.io.IOException: Het systeem kan het opgegeven pad niet vinden
at java.io.WinNTFileSystem.createFileExclusively(Native Method)
at java.io.File.createNewFile(File.java:1006)
at java.io.File.createTempFile(File.java:1989)
at org.apache.felix.cm.file.FilePersistenceManager._store(FilePersistenceManager.java:621)
at org.apache.felix.cm.file.FilePersistenceManager.store(FilePersistenceManager.java:582)
at org.apache.felix.cm.impl.CachingPersistenceManagerProxy.store(CachingPersistenceManagerProxy.java:173)
at org.apache.felix.cm.impl.ConfigurationImpl.update(ConfigurationImpl.java:387)
at org.apache.felix.cm.impl.ConfigurationAdapter.update(ConfigurationAdapter.java:131)
at aQute.impl.configurer.Configurer.configure(Configurer.java:147)