# Workaround for admin rights to start virtual controller?

**URL:** <https://tech-community.robotics.abb.com/t/workaround-for-admin-rights-to-start-virtual-controller/10908>\
**Category:** RobotStudio\
**Tags:** startup-issue, error, virtual-controller\
**Created:** [October 14, 2022, 8:07pm UTC](https://tech-community.robotics.abb.com/t/workaround-for-admin-rights-to-start-virtual-controller/10908 "2022-10-14T20:07:33Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![XNOR](https://avatars.discourse-cdn.com/v4/letter/x/f0a364/32.png) [@XNOR](https://tech-community.robotics.abb.com/u/XNOR)\
**Post date:** [October 14, 2022, 8:07pm UTC](https://tech-community.robotics.abb.com/t/workaround-for-admin-rights-to-start-virtual-controller/10908/1 "2022-10-14T20:07:33Z")

</div>

Anyone know a workaround for starting a virtual controller when RobotStudio isn’t started with admin rights?

---

<div class="post-metadata">

**Author:** ![EricH](https://avatars.discourse-cdn.com/v4/letter/e/ea5d25/32.png) [@EricH](https://tech-community.robotics.abb.com/u/EricH)\
**Post date:** [October 18, 2022, 7:56am UTC](https://tech-community.robotics.abb.com/t/workaround-for-admin-rights-to-start-virtual-controller/10908/2 "2022-10-18T07:56:46Z")

</div>

Try changing the location.