I have the same problem:
When running directly on the machine hosting Workstation I did not have this problem.
When connected to the same machine via remote desktop, starting up Workstation, and then running a virtual machine the error showed up.
The workaround, as suggested before, was to run Workstation as administrator.
Any chance this could be fixed so we don't have to use this workaround?