# Virtual Controller Startup Issue - non-admin account

**URL:** <https://tech-community.robotics.abb.com/t/virtual-controller-startup-issue-non-admin-account/10695>\
**Category:** RobotStudio\
**Created:** [April 18, 2022, 11:25pm UTC](https://tech-community.robotics.abb.com/t/virtual-controller-startup-issue-non-admin-account/10695 "2022-04-18T23:25:17Z")\
**Posts on this page:** 5\
**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:** [April 18, 2022, 11:25pm UTC](https://tech-community.robotics.abb.com/t/virtual-controller-startup-issue-non-admin-account/10695/1 "2022-04-18T23:25:17Z")

</div>

I’m having trouble getting RobotStudio to run virtual controllers for non-admin accounts. Has anyone else encountered this issue? Running as an admin seems to correct but isn’t a solution for users with non-admin accounts.

Starting a virtual controller will yield the following popups:

“RobVC::Launch: vcrunLoadSystem failed to load dll, e.g. unresolved symbols.”

and

This popup duplicated in the output pane:

4/18/2022 4:10:58 PM

There was a problem when starting the virtual controller

The release directory

C:\Users[username]\AppData\Local\ABB\RobotWare\RobotWare\_6.05.2005

is missing or corrupt, and cannot be used when launching a VC.

Update 2/2/23-solution below

---

<div class="post-metadata">

**Author:** ![RsRc](https://avatars.discourse-cdn.com/v4/letter/r/3da27b/32.png) [@RsRc](https://tech-community.robotics.abb.com/u/RsRc)\
**Post date:** [February 2, 2023, 3:09pm UTC](https://tech-community.robotics.abb.com/t/virtual-controller-startup-issue-non-admin-account/10695/2 "2023-02-02T15:09:30Z")

</div>

Hello.

It seems that i have same problem.

Does anybody know how to solve these problems?

---

<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:** [February 2, 2023, 4:54pm UTC](https://tech-community.robotics.abb.com/t/virtual-controller-startup-issue-non-admin-account/10695/3 "2023-02-02T16:54:53Z")

</div>

Update - we finally got a solution working with our ABB support and our IT security team. Our security software was preventing the virtual controllers .dll from running. IT was able to watch a log of what was blocked when we tried starting a VC. You can also reference the .dlls being launched from the log RobotStudio can generate (File\>Help\>Support Tool\>Fault Log Files Tab). NOTE - our system had to have a whitelist rule with a wildcard as each version of robotware is running from a different pathname.

Good luck

---

<div class="post-metadata">

**Author:** ![RsRc](https://avatars.discourse-cdn.com/v4/letter/r/3da27b/32.png) [@RsRc](https://tech-community.robotics.abb.com/u/RsRc)\
**Post date:** [February 9, 2023, 2:37pm UTC](https://tech-community.robotics.abb.com/t/virtual-controller-startup-issue-non-admin-account/10695/4 "2023-02-09T14:37:36Z")

</div>

I have been in touch with my local ABB, and have sended XNOR´s solution to them to solve if we have same issue going on.

Hopefully we have same issue with security softaware 🤞

---

<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:** [February 20, 2023, 7:36pm UTC](https://tech-community.robotics.abb.com/t/virtual-controller-startup-issue-non-admin-account/10695/5 "2023-02-20T19:36:01Z")

</div>

ABB can’t do anything about your security software – You’ve got to get your IT team to create the exception.