I had the same issue. Turns out having an ampersand ("&") in the batch file name caused this issue for me. Simply removing it allows the script run successfully as administrator.

I would suggest removing any symbols and go from there.