Precedence of local and user specific settings

It seems that when I apply both user specific and local specific settings, the user specific settings will take precedence. I'm not sure I like that but that obviously depends on other potential use cases ... my use case is this:

When I open a Hyper-V console from my machine to my machine, I get this error:

System.Management.ManagementException: User credentials cannot be used for local connections
at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode)
at System.Management.ManagementScope.InitializeGuts(Object o)
at System.Management.ManagementScope.Initialize()
at Devolutions.RemoteDesktopManager.Managers.ThreadManager.c348e783a1781e2653839d7d29c0ac214.c5270d6ea4265a9815d5d11ab0b681b22()
at Devolutions.RemoteDesktopManager.Managers.ThreadManager.cb336acd3438bdd362a289ff64cbf1ba3.c0d9783525d3185e81614d3643ffc1222(Object c0f3a9f21384dc89d2ff3a4ac11b9d047)

I tried to fix this by applying local specific credentials that are set to embedded <none>, effectively applying no credentials - and the error went away. However, when I apply user specific credentials at the same time (for when I'm working on another PC) they take precedence and the error reappears. So in my case, it would be nice if local specific settings were preferred.