The application or file can not be opened using the built-in Administrator account: what should I do?

Quite often when installing Windows updates (especially especially for versions 8 and 10), users face an unpleasant problem - some standard or self-installed programs can not be opened using the built-in Administrator account. The system issues an appropriate notification. To correct such an error, depending on the situation, there are several methods.

The application can not be opened using the Administrator account: the causes of the error

Consider the problem, taking as the basis of Windows 10, because it often appears in this version of the system.

If the system reports that the program or some file can not be opened using the built-in Administrator account, the main reason is just that the tenth modification, like the two previous ones (7 and 8), is initially registered, but Hidden admin registration, which is inactive by default, but some programs (in particular, system utilities or applications from the standard system set) have to be launched on behalf of the Administrator.

In most cases, the issued notification refers to the viewing of photos by means of the system, the launch of the Edge browser, the calculator, etc. To solve the problem, you need to address specifically to the accounts and make some changes in their settings.

The program can not be opened using the built-in Administrator account (10th version of Windows): the simplest solution to the problem

The simplest solution to the problem, as evidenced by numerous expert feedback, is to change the level of control that is installed in the system by default.

To do this, enter the "Control Panel", which is prompted by the control command in the "Run" menu, and select a section of user accounts there. In it, select the hyperlink of the control and in the new window turn on UAC (put the slider on the second mark from the top or the highest one). After pressing the "OK" button the system is completely rebooted. Then the problem should disappear.

Additional Account Actions

Another solution to the problem that an application can not be opened using the built-in Administrator account can be the creation of a new "account" with the assignment of administrator rights (this is done from the same account management section).

Now let's look at the situation when the user is the only user on the computer and the second "account" he does not need, that is, he himself has the rights of the administrator. In this variant, a special terminal command launched on the command line (it is called via the "Run" console by entering the cmd combination) becomes the solution to the problem that has arisen. Here you need to register the net user Administrator / active: yes for the Russian-language versions of Windows (if the version is in English, you should use Administrator in the admin's name). Next, you need to exit the current "account" and enter under the activated administrator.

If, however, the user receives a system message again that an application can not be opened using the Administrator account, you can create a new login with administrator rights, log on to the system under it, run the command console with access at the admin level and use the previous command, But in the end, instead of yes, register no, which will deactivate the built-in "account" of the admin.

Conclusion

Here, in principle, a few typical situations and possible solutions to eliminate the problem. In the event that logon is not possible, you will have to start the troubleshooting process, and also reset the administrator password (disable password request when logging in).

In principle, if you understand, similar actions can be performed, say, in the group policy section or use some registry keys for this change in the corresponding editor. However, such methods for an unprepared user can be too complicated. That's why in this case they were not considered in principle, especially since a user in the same registry can accidentally change completely not what is needed, and then the system generally refuses to work. Moreover, in some cases, when an entry is made using local "accounting", access to the above means can be blocked by the administrator, and no matter how you try, you will not be able to enter the appropriate editors. You will need to contact the administrator for a password (in the simplest case) or require the installation of permissions and the right to change the system configuration.

So, the above methods are the simplest and require access to admin rights only when starting the command console, nothing more. And, as practice shows, such methods can be used by any user, regardless of the level of knowledge, training and qualification. As for the preference for applying some method, it is very difficult to advise something here. Everything depends on the situation. But in principle, you can work with activation and deactivation of the "account" admin, though, depending on what kind of registration is the entry made, and whether there are still registered users in the system. Well, then, as they say, the matter of technology.

But, to be objective, it is best to create a new registration and completely disable the built-in "account" of the admin. And easier, and more reliable. But each decides what kind of a tool to use in the end. All methods are good, but the drawback of the very first solution is that it can cause unforeseen failures in case of using an unlicensed copy of the system or OS that is loaded from unreliable sources and in which some important components may be missing.