🚀 go-pugleaf

 What I'm trying to do is reading the registry of a remote machine using 
different user credentials. For that I'm using the Win API functions: 
LogonUser and ImpersonateLoggedOnUser (for user impersonation) than 
RegConnectRegistry. If I supply a wrong user name/password, meaning the user 
name/password being valid but the user does not have enough rights to access 
the remote registry, I'll get ACCESS DENIED. Then all subsequent attempts to 
access the remote registry will fail with ACCESS DENIED even if I supply the 
right user/pass combination. This persists until the app is restarted and 
the right user/pass are provided in the first place.
 In conclusion:
  1. LogonUser & ImpersonateLoggedOnUser both succeed (valid user/pass)
  2. RegConnectRegistry fails with ACCESS DENIED (user does not have enough 
rights)
  3. This will still happend even if I supply the user/pass of a user with 
enough rights.
 Questions:
  1. Why is this happening?
  2. How can it be avoided?