I had the same error today:

Resolved by opening the command prompt with elevated permissions (run as Administrator) even though I'm already Enterprise Admin. Ran fine in admin mode

Maybe MS...