When I open the HOG 3 on my "limited" account, an error pops up. When I run the HOG 3 on an "administrator" account it procedes to the show selection. How do I make the HOG 3 work on my limited account so i don't have to change my account to admin mode?
the "Unknown exception" that occurs immediately after launching launcher is caused by a couple of things, but i'm going to call out specifically a misconfiguration in the 3PC installer, introduced between builds 2071 and 2417.
the issue is permissions on registry keys; the 3PC installer goes out of its way to remove a standard user's permission to read keys in the registry, via the LockPermissions table (or, rather, a WiX , if i presume correctly)
when permission to read/traverse these keys is not explicitly removed, UAC registry virtualization facilities are able to kick in and the dhcp and tftp subkeys and their values can be created and modified by any standard user, without launcher throwing on RegCreateKey.
but this thread asks about XP, which doesn't benefit from UAC.
so, i'm not sure why, instead of relaxing permissions on the FPS keys so that standard users can write to them, they've been tightened so that standard users cannot even read them...
of course, i'm also not sure why i hadn't noticed sooner...
the "Unknown exception" that occurs immediately after launching launcher is caused by a couple of things, but i'm going to call out specifically a misconfiguration in the 3PC installer, introduced between builds 2071 and 2417.
the issue is permissions on registry keys; the 3PC installer goes out of its way to remove a standard user's permission to read keys in the registry, via the LockPermissions table (or, rather, a WiX , if i presume correctly)
when permission to read/traverse these keys is not explicitly removed, UAC registry virtualization facilities are able to kick in and the dhcp and tftp subkeys and their values can be created and modified by any standard user, without launcher throwing on RegCreateKey.
but this thread asks about XP, which doesn't benefit from UAC.
so, i'm not sure why, instead of relaxing permissions on the FPS keys so that standard users can write to them, they've been tightened so that standard users cannot even read them...
of course, i'm also not sure why i hadn't noticed sooner...
