"Could not open/create prefs root node Software\JavaSoft\Prefs" - Windows 10 as regular user

[unsureifpublic@…]

What steps will reproduce the problem?

1. Downloaded josm-tested.jar within the past hour
2. Started normal command window, changed directory to folder with the jar
3. Invoked it with java -jar josm-tested.jar

What is the expected result?

Not to see error messages reported

What happens instead?

See error messages reported - see below

Please provide any additional information below. Attach a screenshot if possible.

Ran it on windows 10 machine (with java 8 u221 both x32 & x64)

Copy & paste of the error message:

2019-11-10 18:38:20.029 WARNING: Could not open/create prefs root node Software\JavaSoft\Prefs at root 0x80000002. Windows RegCreateKeyEx(...) returned error code 5.

URL:https://josm.openstreetmap.de/svn/trunk
Repository:UUID: 0c6e7542-c601-0410-84e7-c038aed88b3b
Last:Changed Date: 2019-11-01 23:59:01 +0100 (Fri, 01 Nov 2019)
Build-Date:2019-11-01 22:59:57
Revision:15492
Relative:URL: ^/trunk

Identification: JOSM/1.5 (15492 en) Windows 10 64-Bit
OS Build number: Windows 10 Home 1809 (17763)
Memory Usage: 302 MB / 2229 MB (168 MB allocated, but free)
Java version: 1.8.0_221-b11, Oracle Corporation, Java HotSpot(TM) 64-Bit Server VM
Screen: \Display0 1600x900, \Display1 1920x1080
Maximum Screen Size: 1920x1080

Last errors/warnings:
- W: No configuration settings found.  Using hardcoded default values for all pools.
- W: Region [TMS_BLOCK_v2] Resetting cache

[anonymous]

This error makes me wonder if the program is trying to write to HKEY_LOCAL_MACHINE, which is naturally going to fail when run as a regular (non-administrative) user?

[GerdP]

I didn't find any source in JOSM that would try to access this key. It looks like this is done by the JRE.

[Don-vip]

This is done by JOSM. See WinRegistry and PlatformHookWindows classes. I never tested with a regular user though.

[Don-vip]

Can't reproduce, even with a regular user. In fact it's ​javabug:8139507. It's caused by the Oracle Java installer and depends on what Java versions you installed, and in what order. Nothing we can do as the warning is logged by the Java runtime itself. Anyway the Oracle Java runtime has only one year more to live, next year we will ask everyone to switch to a free runtime (AdoptOpenJDK for example).