> And I stumbled on an bug doing this. Oddly, reading the registry only works if the program is running on the local hard drive. If it is on a network share (\\share\name or a mapped drive), the exception handling I have in it spits back with this exception basically complaining about registry permission issues.

I don't think that is a bug, it is by design. I admit my knowledge of .Net security is rather lacking (so much to learn, the .Net framework is enormous) but I do know that security really cramps your style when running things over the network.

Have you actually succeded in writing to the registry from a program running over the network? My understanding is that RegistryPermission won't do squat by itself, and the local machine still has to have its security setting set up to allow it.