cygrunsrv CWE-428
Corinna Vinschen
corinna-cygwin@cygwin.com
Fri Apr 24 11:56:03 GMT 2026
Hi James,
On Apr 23 10:04, James Warnock via Cygwin wrote:
> On 4/22/26 02:29, Corinna Vinschen via Cygwin wrote:
>
> > Most of the time it's just a permission issue. You have to have
> > (domain) admin perms on the remote machine and you have to run in an
> > elevated shell.
>
> I didn't have a domain set up so I had to do that. Once I got it all
> up and running, The remote service install progressed further but
> failed to open the key. When I checked what key it was opening it was:
>
> "SOFTWARE\\Cygnus Solutions\\Cygwin\\mounts v2\\/"
>
> After some research, it appears that might be an old key. I changed it
> to:
>
> "SOFTWARE\\Cygwin\\setup"
>
> And changed the value name from "native" to "rootdir". With those
> changes, the remote install worked. I don't know if I did something
> wrong and that necessitated those extra changes, but I think my test
> still counts.
>
> My changes are based on master with the commit hash
> bfc6c36a052914cd4aa93d883e73a2964969e4e5. Maybe I'm on the wrong
> repository or commit and that is why I am seeing the old key.
> Hopefully I'm not working from the wrong place and just wasting your
> time.
Wow, that's weird. No, you're not on the wrong branch or something.
Given how long we don't use these reg keys anymore, you can see how many
people are actually utilizing remote access :}
> Anyway, the new version of the patch is attached (hopefully correctly).
Thanks, I pushed your patch.
Would you mind terribly, to send a patch for the above problem as well,
basically just changing the registry path?
Thanks,
Corinna
More information about the Cygwin
mailing list