Key file generates to wrong location

[msing]

I installed UVNC on a machine, then I used that machine to install UVNC viewer on my flash drive. I'm assuming the second install overwrote a bunch of registry values.

The problem is when I gen a new AES key no key was written to the original installation directory.

Anyway I went through the registry and changed all the values that included "u:\programs\ultravnc\" (the flash drive installation) to "d:\programs\ultravnc" (the original installation).

However that didn't solve the problem. I did a search for new_aesv2.key and found it inside "c:\windows\system32".

Any idea why it's placing the key there, or what registry value (if any) can change that? Or do you think I should just reinstall UVNC on the machine again to overwrite everything with correct data?

[bevtech]

if a key is currently in use and you generate a new one it will place it in the system32 or at least on mine it will windows xp pro mine does the exact same thing. Might be a minor bug but as far as I know you and I are the only ones

[msing]

Yeah but I don't think I had ever generated a key before. The plugin config did not recognize one (and defaulted to using the password), and there wasn't already a key in the UltraVNC directory. Yet it still placed it in system32.

Whereas on my flash drive, I generated a key while the drive was plugged into another PC and it placed it inside the right directory on the drive.

Oh well not that big of a problem I guess after retrieving the key and placing it correctly. Just a pain if I want to change the key occasionally.

[redge]

you had generate the key from the server as service with service helper
so, is default location for any file of service mode is:
%systemroot%\system32
or
%windir%\system32


otherwise as application mode
the key is placed on default location of the application creator lunched.

for solve the issue, generate the key from the vncviewer instead of winvnc.

[bevtech]

yep that is how I am running it.

[msing]

I C.