0

I am seeing a situation where a PowerShell script can't write to the Software key of the Local Machine hive, but the user can manually do it in Regedit. Is there a Group Policy that would limit programatic access but not manual access?

Gordon
  • 175
  • 6
  • 1
    Are you running as administrator? – xR34P3Rx Sep 23 '17 at 14:52
  • At this point we have tried running as a regular user, as a local administrator, and as an administrator with elevated privileges. All fail. We did get one run, on a freshly built VM, where an early write to registry worked, and a later one didn't, which sounds to me like Group Policy getting applied in the background as the script is running. The script is installing Autodesk software, which can take literally hours, so plenty of time for GP to be applied while the script is running. – Gordon Sep 23 '17 at 15:16
  • 2
    Please [edit] your question and add a [Minimal, Complete, and Verifiable example](http://stackoverflow.com/help/mcve), i.e. provide basic part of Powershell code as well as full error message. – JosefZ Sep 23 '17 at 15:40
  • There isn't an example, that's the problem. The code I am using WORKS, on 99% of machines in the office. But a few have something going on with GPO that blocks writing to the registry. I was hoping someone recognizes a policy that would create this behavior. Looks like we'll have to do it the hard way. – Gordon Sep 24 '17 at 20:33

0 Answers0