It's bad practice. If you can fix the issue by only changing credentials on a folder, that should be the solution you go for. Giving system wide privileges to the process instead is not an acceptable work around, rather a way to verify this is a permission issue.
That is correct. I just thought there was a particular reason for "running as admin" not to be recommended in what concerns handling private keys (hence why I said I have no keys online on Armory). Although Armory binaries and bitcoind are safe it's a good pratice not to do such a thing Thank you for all the answers, Armory now seems to be working.