#Cant run as administrator update
My understanding is that Win 7 has only the System Update Readiness Tool for repairing.Īnd if you scroll down in that article to the end, you’ll see some info about manual repairs that might be relevant.Īlso suggest running sfc /scannow again (from your cmd-as-admin window), followed by System Update Readiness Tool, and then followed by sfc /scannow.Īnd don’t forget my earlier alternate suggestion, “Go to Installed Updates and UNinstall the most recent updates. (In Win 10, this would be Dism /Online /Cleanup-Image /RestoreHealth.) Hope this helps … what a sneaky backdoor into administrative command prompt ?Ĭybertooth – per my understanding, the DISM I recommended,ĭoesn’t repair Win 7 does not have the repair option the way Win 10 does. If “consent.exe” is either missing from the Windows System32 folder or it’s corrupted, as indicated above, “SFC /scannow” should resolve this issue.
Other 3rd party Anti-Virus products/updates (Symantec Endpoint Protection was one) may also have injected their DLL(s) into consent.exe which may have corrupted it. If so, it may have been moved to the Anti-Virus’s protected quarantine for possible future restoration and may still be there. It’s been known in the past that Avast & AVG (maybe others?) mistakenly flagged the “consent.exe” file in the Windows System32 folder a virus and deleted it from the System32 folder. It sounds like the “consent.exe” file in Windows System32 may be missing or corrupt.
#Cant run as administrator password
When a user tries to execute an elevated command/script/program (child process) from the console (a parent process without admin privileges) regardless of whether or not the user is an administrator & dependent upon the system’s User Account Control (UAC) settings, UAC calls “consent.exe” (Consent User Interface for Administrative Applications) to ask for permission and/or administrator’s password to execute the command/script/program under elevated administrative privileges. When “cmd.exe” (the child process) is executed by the “elevated administrator task manager” (the parent process), cmd.exe (child) acquires its elevated administrator’s privileges from the elevated administrative task manager (parent) and runs as “admin” as expected.