I’m having a Princess Leia moment over here, and I’m looking for an Obiwan Kenobi. No joy : the share misbehaves exactly the same. I also tried mounting the share from the command line using an elevated command prompt, hoping that it would convey my admin status to the connection. I also fear there may be unforeseeable consequences in doing so. However, I do not wish to go through my entire NAS share and change each executable file’s permission. It is possible to change the file permissions to allow execution. The proposed solution (adding an entry to the registry) has no effect. Which led me down an interesting rabbit hole, the bottom of which is this knowledge base article detailing what the screw-up is without calling it a screw-up : Of course, I have followed the advice of every flat-earther that ever flat-earthed and “done my own research”.
