After installation operating system windows 10 you may encounter some problems and most likely you will encounter the fact that you will not be able to open some of the embedded applications.
This may be the Microsoft Edge browser, the built-in photo gallery, windows store, calculator and a number of other applications. When you start any of them, you will receive the same message - you cannot open the application.
The application cannot be opened using the built-in administrator account.
Log in with another account and try again.
In some cases, you may receive an error in which it will be said that the activation of this application on behalf of the built-in administrator account is not possible.
How to be? What to do in this situation and how to fix this problem?
Open applications in the "Top Ten"
In fact, in most cases, to solve the problem is very simple.1. Go to the control panel. This can be done by right-clicking on the “Start” button and selecting the appropriate line - the control panel.
2. In the control panel, click on the link "User Accounts".
3. In this window, once again select "".
4. On this page you can make changes to your account and now we need to select the item "".
5. Finally, in this window, you need to change the settings for the notification of changes in computer settings. There is a special regulator - a kind of scale. And there is a regulator that needs to be raised to the very top, so that later on you will have the opportunity to open applications in windows 10.
Pull the slider to the top and press the "OK" button.
6. Restart the computer.
Everything, as you can see is nothing complicated. However, if you have any questions, I recommend to watch a special video on this topic.
Video: what to do if you can not open the application in windows 10?
The new version of the operating system is not only new features, but also new problems. Unfortunately, this is the case; modern programs are quite complex and it is almost impossible to avoid mistakes in them. But even more often, ignoring new mechanisms and opportunities leads to problems, along with the use of old approaches to solving some problems. Our case today is one of those.
This story happened completely by accident. Being on my own business in one of the office centers, I decided to go to drink coffee with my good friends, who here had an office of a small family business. In the process of drinking coffee, they asked me to look at new computerwho began to behave somehow inadequately.
The main complaint was that the photos and scans stopped opening, but as soon as it turned out, all Modern Apps stopped running. Outwardly, this was manifested by such a simple message:
First of all, the mention of the built-in administrator account was alarming; however, the user logged into the system under his usual account. But why does the system think that we are trying to start the application on behalf of the local admin? Already at this moment, the first suspicions began to creep in ...
But let us make a small digression and think about what the system gave us. Some may habitually begin to resent, somehow, why I can not run something on behalf of the administrator, what kind of administrator is this ?! Yes, windows administrator - this is far from root in Linux, which can kill everything, even with a flick of the wrist, but the Linux security concept does not involve running applications as root and even openly condemns this practice.
AT Windows user Traditionally, he worked on behalf of a local administrator, which eventually became a fairly serious security problem. To remedy this situation, Microsoft has introduced a technology such as UAC into the new OS line that largely follows the concept of security in Linux. All programs are launched in the context of the user, and if elevation is required, then it is explicitly requested in such a way that the application has no opportunity to programmatically click the "Yes" button.
And what will happen if we disable UAC? Applications will start with full rights ...
I think many have already guessed. Well, let's check. That's right, the UAC slider is in the lowest position.
As the small “investigation” showed, the problems started after this computer The electronic reporting system was installed by the operator’s employee.
In general, it remains a mystery to us why in 2016 we need to completely disable UAC. During the ten years of existence of this technology, which Windows vista It was quite annoying, not customizable and incompatible with many software, it was polished to an ideal state, and third-party developers brought their programs to a compatible state.
The reason why MS forbids launching modern applications with administrator rights is also understandable, especially since these applications will be installed by the widest masses from the store. Here you can refer to the example of Android, where despite all the efforts, frankly malicious or spyware leaks from time to time to the store. And about the fact that "Flashlight" access to contacts, calls and SMS, most users somehow do not think.
In general, the problem is understandable, as are the ways to solve it. Raise the UAC slider up and restart the computer.
As expected, after the inclusion of UAC, all modern applications began to work again.
And I once again thought about the question of what makes people consciously refuse new technologies and lower the security and stability of the system?
For 13 days, two fighters kept the all-round defense in a tank sunken in a swamp tank! On a cold day on December 17, 1943, fierce fighting was going on for the village of Demeshkovo near the town of Nevel of the Pskov Region. The 328th Tank Battalion, which was part of the 118th Separate Tank Brigade, tried to repel it from the Nazis. The Germans knocked out six of our tanks. And the seventh, in the heat of the offensive, landed in a snow-covered marsh a hundred meters from the village. Trying to seize the T-34, the Nazis launched several attacks that day. The crew and infantrymen who remained near the tank bravely fought off the enemy, but the forces were unequal. Under the cover of night, the machine gunners retreated, taking with them a seriously wounded lieutenant Tkachenko. The driver of the Bezukladnikov died. In the tank remained one 18-year-old Komsomol member Viktor Chernyshenko. Senior sergeant Alexey Sokolov volunteered to help him - a native of the village of Petrovka, Lekarevsky village council of Asekeevsky district. He was an experienced fighter - he fought with the White Finns on the Karelian Isthmus in 1939 - 1940, fought at Stalingrad, twice burned in a tank and was considered the best driver-mechanic of the unit. "Thirty-four" firmly stuck in the quagmire - it was not possible to free it. And the small garrison staunchly repelled the furious fascist attacks. Having let them in at close range, two tankers smashed the enemy with machine-gun fire, the benefit of which was a lot of ammunition. The Germans made several attacks in the afternoon, tried to seize the steel fortress under the cover of night. But Chernyshenko and Sokolov did not give up. Having lost hope of taking the Soviet tank along with the crew, the Nazis began to fire at it directly from the guns. One of the shells pierced the armor and wounded the guys. But they continued to repel the attacks of the Germans. On the twelfth day the shells and ammunition ended. Bleeding, frostbitten, hungry tankers kept their last effort. Victor threw three grenades at the fascists who picked up close to the tank. The surviving Germans fled. The tankers postponed the last grenade as a last resort ... On the thirteenth day, December 30, our troops broke the enemy defenses with a powerful blow and captured the village of Demeshkovo. Approaching the hollow where our T-34 was stuck, the fighters discovered a lot of Nazi corpses. Carefully removed from the tank two completely exhausted, frostbitten tank crews. One of them was unconscious, the other muttered something, but also fell into unconsciousness. Chernyshenko underwent several operations. In the hospital, he, who was still in bandages, was attached to his tunic the Order of Lenin and the "Golden Star" of the Hero. Rescue senior sergeant Sokolov failed. He died on December 31, never regaining consciousness. The title of Hero of the Soviet Union was awarded to him posthumously. He was buried in the same place where he fought bravely. In the same place, local residents erected a monument reminiscent of the heroism of tankers. But Lovetsky secondary school, located seven kilometers from Demeshkov, began to bear the name of the Hero of the Soviet Union, Aleksey Sokolov. The guy from the Orenburg heartland forever enlisted in the regiment, in which he served. On the eve of Victory Day, on May 6, in Asekeevsky district, in the courtyard of Lekarevskaya secondary school, which officially was named after Alexey Sokolov since February 2009, a rally was held to mark the opening of a memorial plaque in memory of the countryman-hero. On May morning, doctors and schoolchildren gathered here, who are now rightfully referred to as "falconates", as well as local residents, including those who survived the war. School director Vasily Lebedev opened the celebration. Hero's nephew Sergey Sokolov and World War II participant Gennady Glazunov, who once collected the material about our heroic fellow countryman for a documentary story, scattered the white canvas from the marble board installed at the entrance to the school.
Often enough when installing windows updates (this is especially true for versions 8 and 10) users are faced with an unpleasant problem - some standard or independently installed programs it is impossible to open using the built-in account Administrator. The system issues a notification. To correct this error, depending on the situation, there are several methods.
The application can not be opened using the Administrator account: the cause of the error
Consider the problem, based on Windows 10, since it most often appears in this version of the system.
If the system reports that a program or some file cannot be opened using the built-in Administrator account, the main reason is that the tenth modification, like the two previous ones (7 and 8), is initially registered, but hidden registration admin, which by default is inactive, but the launch of some programs (in particular, system utilities or applications from the standard set of systems) have to be produced on behalf of the Administrator.
In most cases, the notification is related to viewing photos using the system, launching the Edge browser, calculator, etc. To solve the problem, you need to turn to the accounts and make some changes in their settings.
The program cannot be opened using the built-in Administrator account (Windows 10th version): the simplest solution to the problem
The simplest solution to the problem, as evidenced by numerous expert reviews, is to change the level of control that is installed in the system by default.
To do this, enter the “Control Panel”, which is quickly called by the control command in the “Run” menu, and select the section In it, select the control hyperlink and in the new window enable UAC (put the slider on the second mark above or at the highest). After pressing the “OK” button, the system is completely overloaded. Then the problem should disappear.
Additional account activity
Another solution to the problem that an application cannot be opened using the built-in Administrator account can be the creation of a new “account” with assignment of administrator rights (this is done from the same section of account management).
Now let's look at the situation when the user is the only user on the computer and does not need the second “account”, that is, he himself has the rights of an administrator. In this variant, a special terminal command launched in command line (it is called via the Run console by entering the cmd combination). Here you need to register the net user Administrator / active: yes for Russian speakers windows versions (if the version is in English, use the Administrator in the admin name). Next, you need to exit the current "account" and enter under the activated administrator.
If the user again receives a message from the system that some application cannot be opened using the Administrator account, you can create new registration with admin rights, log in to the system under it, run the command console with access at the admin level and use the previous command, but at the end, instead of yes, write no, which will allow deactivating the built-in administrator account.
Conclusion
Here, in principle, a few typical situations and possible solutions to eliminate the problem. In the event that login is impossible, you will have to start the troubleshooting process and also reset admin password (disable password requesting upon login).
In principle, if you look at it, you can perform similar actions, say, in the group policies section, or use some registry keys in the corresponding editor for this change. However, such methods for an unprepared user can be too complicated. That is why in this case they were not considered fundamentally, especially since the user in the same registry can accidentally change absolutely not what is needed, and then the system will refuse to work at all. Moreover, in some cases, when the entrance is carried out using a local account, access to the above means may be blocked by the administrator, and, no matter how you try, enter the appropriate editors will not work. You will have to contact the administrator for a password (in the simplest case) or require the installation of permissions and rights to change the system configuration.
So, the methods described above are the most simple, and access to admin rights is required only when starting the command console, nothing more. And, as practice shows, any user will be able to apply such methods, regardless of the level of knowledge, training and qualifications. As for the preferences in the application of some method, here it is very difficult to advise something. It all depends on the situation. But in principle, it is possible to work with the activation and deactivation of the administrator account, however, depending on what registration you enter, 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 administrator account. And easier, and more reliable. But each decides for himself which of the above means to use in the end. All methods are good, but the disadvantage of the very first solution is that it can cause unforeseen failures in the case of using an unlicensed copy of a system or OS that is loaded from unreliable sources and which may lack some important components.
