Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

5
  • Downside: You yourself cannot modify these files any more.
    – harrymc
    Commented Apr 5, 2016 at 9:19
  • Not sure what you mean, harrymc. Can you please be more specific? Are you speaking of problems accessing the permissions? As an administrator you are still master over every file on your computer, though Microsoft throws monkey wrenches in the way sometimes. But if you understand how permissions works you can do anything you want. The files are on YOUR computer after all. If you mean that you've removed your own permissions, I worded it badly. I meant that I REMOVED permissions, not added a Deny setting. I should have used the word "Disallow".
    – NoelC
    Commented Apr 6, 2016 at 20:41
  • Once deny is set, to re-access the permissions one has to first set himself as owner of the files.
    – harrymc
    Commented Apr 7, 2016 at 5:15
  • Right. DO NOT check a box in the "Deny" column. Rather, UNCHECK "Read & execute" under the Allow column.
    – NoelC
    Commented Jun 4, 2016 at 16:18
  • 2
    Based on my post-Update 3 experience, just changing the permissions on vshub.exe to remove execute access appears to be enough.
    – NoelC
    Commented Jul 14, 2016 at 16:39