I think a policy only prevents "local" registry editing tools from running (and only default built-in tools) if you use a non Microsoft tool I think it will still run, or if you run it remotely as an Admin I think it will work.

Need to verify the ERROR CODES returned to determine what is really happening.