weeemrcb wrote:
Resolved the issue.... The long term solution.... fixed it for me.
This is not a resolution, solution or fix, but a
workaround. You still have the problem, you are just hiding it. Knowing that it works when running as administrator is a good step in troubleshooting, but it is not the end of troubleshooting (where everything works as expected - and running as administrator is not expected) and should not really be considered and certainly not recommended as a solution, because it isn't one.
weeemrcb wrote:I think Microsoft hardened the security in Win 10 v1909 and this was accidentally caught up in the OS lockdown.
Using 1909 here, shortcut keys for macros working just fine without admin rights.
I guess something else changed during your rebuild, that broke this (and cantabile, and who knows what else)
![Sad :(](./images/smilies/icon_e_sad.gif)
What you have done has avoided a symptom of some other problem, but the problem still exists, so it might be worth your time to figure out what else changed, in case that problem comes back to be annoying to you in the future.
Since the issues you are seeing seem to be related exclusively to VM, perhaps there was something wrong during the installation, so I'd try reinstalling it first. There are instructions over here:
viewtopic.php?f=6&t=442
It is possible, that your application is taking exclusive access to the keyboard (as you are aware, you were in the thread where this was discussed:
viewtopic.php?f=6&t=863&p=2805&hilit=ad ... 02c0#p2803) but that would not explain crackling audio, and it is unlikely that all of your games suddenly changed to have this same behaviour, at the same moment that you rebuilt your PC.
Anyway, in that case, the true "resolution"/"fix"/"solution" is not to run VM as administrator, but for the developer of the application to fix the application so that the system works as expected.
Since you've had other unusual problems with VM (
viewtopic.php?f=6&t=826&p=2656&sid=c214 ... 02c0#p2656) and now that's gone and there is a whole new one, perhaps there is something wrong with the build process of your PC. Perhaps you install some software or do some kind of "tweak" which is messing with VM somehow?
As Vincent mentioned in that thread, your first step is to describe a method for others to reproduce the problem. In this thread, your method to reproduce the problem, was to start VM as normal and play games, and since that doesn't reproduce the problem for others, it means there's something missing from that method. Before you can fix a problem, you need to know what you are trying to fix
![Smile :)](./images/smilies/icon_e_smile.gif)