Windows 10: How do I elevate all program to run as administrator without error?

In Windows 8.1 i can easily elevate all program to run as administrator via Local Policy.
in Windows 10. when i use that method most of metro apps even setting and control panel screw up because they using metro GUI instead windows GUI.

:)

 

Windows 10 issue "Subst" command doesn't work

So, you log in as the user "Administrator", correct?

You did not switch off UAC, correct?

If you answered both with "yes", the Administrator user does *not* run with administrative privileges. Only, if it needs administrative privileges it will prompt you for them and you click "yes". That's all.

You cannot "log in as an elevated user". You can elavate later for specific tasks if there is need. This is almost seamless.

If you login as a user *with* administrative privileges you do not have these privileges with normal actions! Because you don't need them! The system prompts you if you need them.

If you login as a user *without* administrative privileges the system prompts you if it needs administrative privileges. In this case you have a little more to do than say "yes". You have to click the administrative account that you want to use and enter
the password. You do not switch users! Only this task will be carried out with the privilege of that other user.

The normal way is to create a user account of your own, say "leonard". This user account gets created during installation and will have administrative privileges. There's no reason not to use it. In case you need admin privileges it will ask you.

If you do it that way then the Administrator account is locked and not usable. Only if you go to safe_mode (or there is no other user with admin privileges or you unlock it) you will have access to that Administrator account, which is not password-protected.
So, this Administrator account is mainly a safe-guard for you, in case, something's wrong with your normal account.

which I took to mean that if you run subst in the non-elevated command window, only users without
administrator privileges can see it.

This is correct, depending on the way you read it. It's not dependant on the basic user privileges, it's dependant on the privilege that the user has at that moment. A user with admin
privileges does normally *not* run elevated. Only if you do "run as administrator" you go to elevated state and only for that process/task, not for the "whole" logged-in user. So, if you are logged in as the Administrator user and run the subst command in
a normal command window then you have it in File Explorer and you should have it for most other operations. It won't be available for a process that runs elevated, e.g. installer for a program or in incompatible program that runs elevated all the time. For
this case you would have to run subst in an elevated command window additionally and you should be able to access that virtual drive no matter if that process is elevated or not. (There may be problems with the files created in elevated mode, once you run
a non-elevated process against it, depends on the permissions/integrity level set during creation.)

 

Windows 10 issue "Subst" command doesn't work

Yeah, I ran 7 & 8 on some of my machines. You wrote " "run with administrator" creates a drive that is accessible *only* with administrator privileges and if you do it without administrator
privileges it's only visible to your non-elevated user" which I took to mean that if you run subst in the non-elevated command window, only users without
administrator privileges can see it.

My understanding is that if you do not log in as an elevated user, you cannot do anything that requires administrator privileges. I should have said "log in as Administrator," not "run
as administrator.".

Perhaps I did misunderstand. What did you mean?