Press the Windows key on the keyboard to go to the Windows 8 Start screen. Windows 8 – fix “System error 5 has occurred” Notice that the title of this window is ‘ Administrator: Command Prompt’ which shows that it is running with elevated system privileges – just opening cmd on its own (without a right click) displays only the basic title of ‘Command Prompt’ so you can easily tell which is which. Now try running the same command again – as shown below, you can see that in my example the command is now successful: Type cmd into the ‘Type here to search’ search box.Īt the top of the search results, right click on the ‘Command Prompt’ Desktop app result and select ‘Run as administrator’.Ī User Account Control box may now appear – if it does, click the ‘Yes’ button to allow the app to make changes to this computer.Ī black Command Prompt window opens with the word ‘Administrator’ at the beginning of the title bar.
Windows 10 – fix “System error 5 has occurred”Ĭlick on the Windows ‘Start’ button in the bottom left of the screen.
This should provide sufficient administrator privileges to run the command successfully.įollow the 2 steps below for Windows 10, Windows 8, Windows 7 or Vista. To fix a ‘System Error 5 Has Occurred’ message, you need to open an elevated Command Prompt window and then run the command again. net start and net stop) or that manage file sharing (e.g. High elevated privileges are required to run many other unrestricted or system-wide commands in a Command Prompt window – especially commands that manage Windows services (e.g. So if you try to run that command without these privileges, you will get the System error 5 message. So, for security reasons, stopping that service requires elevated system privileges – it is not enough to just be logged in as an Administrator. However, you have to fix the incorrect security only one time after the upgrade.In this example, the print spooler is a core Windows service that should normally run all the time. We don't recommend this workaround because the permissions are reapplied during Group Policy updates.
Select OK to apply the Group Policy changes.Īpply the GPO to the affected computers by waiting for Group Policy to update or by starting the update manually.
Query Template, Query Status, Enumerate Dependents, Start, Pause, and continue, Interrogate, Stop Query Template, Query Status, Enumerate Dependents, Pause, and continue, Interrogate, User-Defined Control Query Template, Query Status, Enumerate Dependents, Start, Pause, and continue, Interrogate, Read Permissions, User-Defined Control Select the Define this policy setting check box, and then select Enabled.Įxpand the Security node to make sure that the following properties and objects are set to Allow. Locate the policy: Computer Configuration\Policies\Windows Settings\Security Settings\System Services. And it should be linked so that the new GPO is applied to only the affected computers.Įdit Group Policy in the Group Policy Management Console. A new Group Policy object (GPO) should be created for this workaround.
You can use the Group Policy Management Console to configure a domain-based policy that sets security to the default configuration after you upgrade the server. Try to use one of the following features:Īlso, make sure that you can switch users and that the Secondary Logon service starts correctly. Sc sdset seclogon D:(A CCLCSWRPWPDTLOCRRC SY)(A CCDCLCSWRPWPDTLOCRSDRCWDWO BA)(A CCLCSWRPDTLOCRRC IU)(A CCLCSWDTLOCRRC SU)(A CCLCSWRPDTLOCRRC AU)S:(AU FA CCDCLCSWRPWPDTLOCRSDRCWDWO WD) You should log on as an administrator before you run these commands.Īt the command prompt, type the following command, and then press ENTER: You can use the Sc.exe command prompt utility to set the security to the default configuration after you upgrade the server. Workaround 1: Use the Sc.exe command prompt utility This problem prevents a standard user from starting this service and from running an application as a different user. The discretionary access control list (DACL) for the Secondary Logon service isn't set correctly when you upgrade Windows Server. In this scenario, you receive the following error message: