Fix it now
Both messages end with the same sentence in Microsoft’s published text: verify that you have sufficient privileges to stop, or to install, system services. Start there, because it is what the message actually says. Self-protection on a leftover security agent is the next most likely answer.
msiexec /i package.msi /l*v C:\temp\install.log
sc query <servicename>
sc qc <servicename>
sc queryex <servicename>
sc enumdepend <servicename>
- Confirm the installer is running elevated and the account is a local administrator.
net localgroup Administratorslists the members. - Get the service name from the verbose log rather than guessing – the message text carries it as [2] and [3], and deployment tools often strip it.
sc qcgives the binary path, which tells you which product actually owns the service.- If it belongs to a security product you are replacing, disable tamper or self-protection in that product’s own console first, then remove it with the vendor’s removal utility.
- Close Services and any Computer Management windows, then reboot. A service marked for deletion clears on restart and not before.
Install the new agent immediately after that reboot, before anything else has started. A half-removed agent that gets a chance to load its driver puts you back where you started.
If setup gets past the service stage, stop here. If not, the next section covers the four states the service control manager can be in and what each one needs.
Why it happens
To replace a service an installer has to stop the running instance, replace its binary, and register the new configuration. Each of those goes through the service control manager and each can be refused. Message 1921 is the stop being refused: “Service ‘[2]’ ([3]) could not be stopped. Verify that you have sufficient privileges to stop system services.” Message 1923 is the install being refused, with the same closing sentence about privileges.
That sentence is the first thing to test, and it is easy to skip because the security-agent story is more interesting. An installer launched without elevation, or launched by a deployment agent running as a context that is not a local administrator, produces both messages routinely and produces them on machines where nothing is protecting anything.
Security agents are the second story and a real one. Self-protection exists so malware cannot stop the scanner, and it does not distinguish between malware and an administrator running an installer. A half-removed or expired security product is a reliable source of 1921 for exactly that reason: the protection is still active even though the product no longer works properly, and the supported way past it is the vendor’s own removal tool rather than force.
The installer is not running with enough privilege
You have this one if 1921 or 1923 on a machine with no security product involved, or one where the install is being pushed by a management agent.
- Run the installer from an elevated session and confirm the account with
net localgroup Administrators. - For a pushed deployment, check what context the deployment agent runs as. A user-context deployment cannot install a system service.
- Read the log for what the installer attempted before the failure – it tells you whether the stop or the install was refused.
Self-protection on a security product is refusing the stop
You have this one if 1921 while deploying or replacing an endpoint agent, and the service will not stop from the Services console either.
- Disable tamper or self-protection in that product’s management console, not on the device, if it is still managed.
- Run the vendor’s own removal utility. That is the supported route and it handles the driver and the protected state together.
- Reboot, then install the replacement before anything else starts.
An expired licence does not switch self-protection off. An agent that has stopped updating still guards its own service, which is why expired products are such a common cause here.
Other services depend on the one being stopped
You have this one if 0x8007041B, ERROR_DEPENDENT_SERVICES_RUNNING: ‘a stop control has been sent to a service that other running services are dependent on.’
sc enumdepend <servicename>lists what depends on it, orGet-Service <name> -DependentServicesin PowerShell.- Stop the dependants first, in order, then the target service.
- If a dependant belongs to a different product, work out whether it should be running at all before stopping it.
The service is marked for deletion
You have this one if 0x80070430, ERROR_SERVICE_MARKED_FOR_DELETE: ‘the specified service has been marked for deletion.’
- Close every Services console, Computer Management window and Task Manager services tab. An open handle keeps the deletion pending.
- Reboot. The pending state clears on restart and there is no supported way to force it sooner.
- Install the new service after the reboot, before anything reopens a handle to the old name.
The new service installed but will not start
You have this one if 0x8007042C, ERROR_SERVICE_DEPENDENCY_FAIL: ‘the dependency service or group failed to start.’
sc qc <servicename>shows the declared dependencies. Check each one is present and startable.- Start the dependencies by hand in order and note which fails first – that is the real fault.
- A dependency removed by a cleanup script is a common cause, and it does not announce itself anywhere else.
Full reference
The four service messages, in Microsoft’s own words
| Message | Published text |
|---|---|
| 1920 | Service ‘[2]’ ([3]) failed to start. Verify that you have sufficient privileges to start system services |
| 1921 | Service ‘[2]’ ([3]) could not be stopped. Verify that you have sufficient privileges to stop system services |
| 1922 | Service ‘[2]’ ([3]) could not be deleted. Verify that you have sufficient privileges to remove system services |
| 1923 | Service ‘[2]’ ([3]) could not be installed. Verify that you have sufficient privileges to install system services |
All four carry the same privilege sentence, which is a strong hint about where Microsoft expects you to look first. The [2] and [3] placeholders are the service name and display name, and they are the reason a verbose log is worth capturing before you start theorising: without them you are guessing which service the installer was working on.
The companion HRESULTs
| Code | Win32 | Meaning |
|---|---|---|
0x8007042C |
1068 | ERROR_SERVICE_DEPENDENCY_FAIL – the dependency service or group failed to start |
0x8007041B |
1051 | ERROR_DEPENDENT_SERVICES_RUNNING – a stop control has been sent to a service that other running services are dependent on |
0x80070430 |
1072 | ERROR_SERVICE_MARKED_FOR_DELETE – the specified service has been marked for deletion |
Service control commands worth knowing
| Command | What it does |
|---|---|
sc query <name> |
Current state of the service |
sc queryex <name> |
Adds the process ID, which lets you find the running binary |
sc qc <name> |
Configuration: start type, binary path, declared dependencies |
sc enumdepend <name> |
What depends on this service – the list you need before stopping it |
sc stop <name> |
Sends the stop control |
Get-Service <name> -DependentServices |
The PowerShell equivalent of enumdepend |
net localgroup Administrators |
Who is actually a local administrator on this machine |
Replacing one security agent with another
- Plan the order before you touch anything. Removing the old product and installing the new one are two separate reboots’ worth of work, and the machine is unprotected in between.
- Disable tamper or self-protection at the management console while the old product is still managed. Once you have removed the console’s control you have lost the easy route.
- Uninstall through the vendor’s normal removal path first, and only reach for the dedicated removal utility if that fails.
- Reboot, and check no service from the old product survives –
sc query <name>on each one you know about. - Install the replacement immediately after that reboot.
- Confirm the new agent reports in to its own console before you consider the machine done.
Deleting a protected service’s registry key by hand to get past 1921 leaves the driver loaded and the machine in a state neither product understands. If the vendor publishes a removal tool, that is the supported route and it exists precisely because this cannot be done safely by hand.
When there is no security product involved
- Check the account and the elevation again. It is the first thing the message text points at and the easiest thing to assume you have already done.
- Look for a Group Policy restriction on service configuration. Managed estates sometimes lock service permissions and the failure looks identical.
- Check whether the service name already exists from a previous partial install, in which case 1923 is a name collision rather than a rights problem.
- Read the log for a 1920 as well. A service that installed and then failed to start is a different problem from one that could not be installed.
When a licence is the actual fix
The commercial question here is what happens on the day you replace the agent. Most of the pain in this article comes from a product that is expired, half-removed, or no longer talking to a console – self-protection still active, nobody able to turn it off centrally, and every machine needing a visit. A currently licensed, centrally managed endpoint tier such as Bitdefender GravityZone Business Security removes that specific failure mode: tamper protection is a policy setting you can change for a group from the console, and removal and re-deployment are pushed rather than performed at the desk. Two things to insist on when comparing options: that tamper protection can be turned off centrally for a scoped set of machines, and that the vendor publishes a removal utility for the state where the agent no longer checks in. Keeping a licence current is part of the fix, because an agent whose subscription has lapsed keeps protecting itself long after it stops protecting you.
Every code this article covers
| Code | What it points at | Source |
|---|---|---|
1921 |
Windows Installer message: “Service ‘[2]’ ([3]) could not be stopped. Verify that you have sufficient privileges to stop system services” | Microsoft Learn |
1923 |
Windows Installer message: “Service ‘[2]’ ([3]) could not be installed. Verify that you have sufficient privileges to install system services” | Microsoft Learn |
0x8007042C |
Win32 error 1068, ERROR_SERVICE_DEPENDENCY_FAIL: ‘the dependency service or group failed to start’ | Microsoft Learn |
0x8007041B |
Win32 error 1051, ERROR_DEPENDENT_SERVICES_RUNNING: ‘a stop control has been sent to a service that other running services are dependent on’ | Microsoft Learn |
0x80070430 |
Win32 error 1072, ERROR_SERVICE_MARKED_FOR_DELETE: ‘the specified service has been marked for deletion’ | Microsoft Learn |
Confirm the fix worked
sc query <servicename>shows the new service running with the expected start type.sc qc <servicename>shows the binary path belonging to the product you installed, not the one you removed.- No service from the previous product remains – check each name you know about.
- The new agent appears in its own management console after a reboot, not just immediately after install.
Questions people ask about this
The message mentions privileges but I am an administrator. Is that a red herring?
Not always. Check how the installer was launched rather than who you are – a deployment agent running in a user context, or an installer started without elevation from a shortcut, hits this on machines where the interactive account is an administrator.
Can I delete the stuck service registry key to get past 1921?
Do not. On a security product the driver stays loaded and the removal leaves a state neither the old nor the new product understands. Use the vendor’s removal utility, which exists for exactly this.
Why does 0x80070430 not clear until I reboot?
Because something still holds a handle to the service. An open Services console or Computer Management window is enough. Close them all, reboot, and the pending deletion completes – there is no supported way to force it sooner.
The new service installed but will not start.
That is 0x8007042C, a dependency failing to start. Read the declared dependencies with sc qc, start them by hand in order, and find which one fails first. A dependency removed by an earlier cleanup script is a common cause.
