Path: csiph.com!eternal-september.org!feeder.eternal-september.org!reader02.eternal-september.org!.POSTED!not-for-mail
From: Rhino <no_offline_contact@example.com>
Newsgroups: comp.lang.java.programmer
Subject: Re: Seeking clarification on Java JDKs
Date: Mon, 1 Oct 2018 20:53:36 -0400
Organization: A noiseless patient Spider
Lines: 28
Message-ID: <poufif$u2k$1@dont-email.me>
References: <pnvl1k$opc$1@dont-email.me> <po008o$qbu$1@dont-email.me>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Injection-Date: Tue, 2 Oct 2018 00:53:35 -0000 (UTC)
Injection-Info: reader02.eternal-september.org; posting-host="79663d9f7662c75a0e25fb03fe2b419d"; logging-data="30804"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX1/j50uEj2FN3qIGbbpAl9kfKr4tIpIGcQ8="
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1
Cancel-Lock: sha1:tuUjHhCRwq5oX0zYrFevm9xWfnA=
In-Reply-To: <po008o$qbu$1@dont-email.me>
X-Antivirus-Status: Clean
Content-Language: en-US
X-Antivirus: Avast (VPS 181001-2, 2018-10-01), Outbound message
Xref: csiph.com comp.lang.java.programmer:38622

On 2018-09-20 7:28 AM, Eric Sosman wrote:
> On 9/20/2018 4:16 AM, Rhino wrote:
>> I've been away from Java for several years working on other things, 
>> including PHP and web development, and I'm just starting to learn 
>> Android development. I'm toying with writing an Android version of a 
>> game I originally wrote in Java for the desktop, which I haven't 
>> touched since 2012 (at which point I was probably running Java 6 on a 
>> Windows XP machine). In trying to get my game running again on Windows 
>> 10 and jdk 1.8.0_172, I'm encountering an error with respect to 
>> preferences; apparently, the root node key is missing in the Windows 
>> registry.
> 
>       Sounds familiar.  If it's the same problem I dimly recall from
> ages ago, try
> 
> https://stackoverflow.com/questions/4947555/where-are-the-java-preferences-stored-in-windows-7 
> 
> 
> ... which is a bit old, but so's the problem.
> 
A belated thanks for your very prompt reply! You got me going in the 
right direction, even if it did take a little longer to get back to the 
problem than I expected.

It turns out the issue had to do with Windows User Account Control.

-- 
Rhino