Uninstalled PostgreSQL 16 but Services Still Showing

PostgreSQL services often remain registered in the Windows Service Control Manager after a standard uninstall because the removal process deletes application files but does not always deregister the underlying service entries. To resolve this, you must manually delete the leftover service keys using the Command Prompt with administrative privileges or by editing the Windows Registry directly. This ensures that the "Services" snap-in no longer displays ghosted PostgreSQL instances, allowing for a clean reinstall if necessary.

Why Services Persist After Uninstall

When you uninstall PostgreSQL 16 via the Windows Installer or the control panel, the executable binaries and data directories are removed from your disk. However, the Windows operating system maintains a separate database of registered services in the registry. The uninstaller script may fail to execute the final cleanup step that calls DeleteService on these entries. Consequently, the Service Control Manager still holds references to services like postgresql-16 or postgresql, even though the actual program files are gone. Attempting to start these services will result in an error stating that the service cannot be found, as the binary path it points to no longer exists. This is a common issue on Windows systems where manual cleanup is required to fully remove software components that interact deeply with the OS kernel. Ignoring these entries can cause confusion when managing other services or when attempting to reinstall PostgreSQL, as the port might already be bound or the service name conflicts with new installations.

Method 1: Removing Services via Command Prompt

The most straightforward way to remove these orphaned services is using the built-in sc (Service Control) utility in the Windows Command Prompt. This method is preferred over manual registry editing because it handles the necessary permissions and updates the service database correctly. First, open the Start menu, type cmd, right-click on Command Prompt, and select "Run as administrator". Administrative rights are mandatory because modifying the service configuration affects the entire system. Once the elevated command window is open, you need to identify the exact name of the lingering service. You can list all services by running:

sc query type= service state= all | findstr /i postgres

This command filters the output for any service containing the word "postgres". Look for lines indicating the service name, which typically looks like postgresql-16. If multiple entries appear, note each one. To delete a specific service, use the following syntax, replacing SERVICE_NAME with the exact name found in the previous step:

sc delete SERVICE_NAME

For example, if the service is named postgresql-16, you would run:

sc delete postgresql-16

If the deletion is successful, the command prompt will return [SC] DeleteService SUCCESS. If you receive an error such as "Access Denied," verify that you are indeed running the Command Prompt as an administrator. Repeat this process for every PostgreSQL-related service listed. After deleting all relevant services, restart your computer or refresh the Services management console (services.msc) to see the changes take effect.

Method 2: Manual Registry Cleanup

In cases where the sc command fails or returns errors due to corrupted service entries, manual removal via the Windows Registry Editor is the next step. This approach requires caution, as incorrect modifications to the registry can destabilize the system. Always back up the registry before proceeding. Press Win + R, type regedit, and press Enter to launch the Registry Editor. Navigate to the following path:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services

Expand the Services folder and look for subkeys named after the PostgreSQL services (e.g., postgresql-16). These keys contain the configuration data for the service, including the binary path and startup type. Right-click on the key corresponding to the uninstalled version and select "Delete". Confirm the action when prompted. Be careful not to delete other unrelated services. If you are unsure about a specific key, search online for its purpose or check the "ImagePath" value within the key to see if it points to a PostgreSQL directory. Once you have deleted all relevant PostgreSQL service keys, close the Registry Editor. The services should now disappear from the Services list. For a comprehensive guide on handling stubborn programs that resist normal removal, you may wish to review our article on How to Uninstall a Program that Cannot be Uninstalled Normally.

Verifying the Removal

After performing either of the methods above, it is crucial to verify that the services have been completely removed. Open the Services management console by pressing Win + R, typing services.msc, and hitting Enter. Scroll through the list and look for any remaining PostgreSQL entries. If the list is clear, you have successfully cleaned up the system. You can now proceed to reinstall PostgreSQL 16 if needed. During the reinstallation, ensure that you choose a different service name or port if you intend to run multiple versions simultaneously, although this is generally not recommended for production environments. Additionally, check the Event Viewer under Windows Logs > Application for any residual errors related to missing PostgreSQL services, which can help confirm that the system has stopped trying to load them. If you encounter issues with other Windows services or system components during this process, refer to resources on Why is there no clipboard user service on Windows 11? for context on how Windows manages user-specific versus system-wide services.

Frequently Asked Questions

What happens if I don't remove the old services?

The services will remain in the list but will fail to start because their executable paths are missing. This clutter makes it difficult to manage your system and can confuse troubleshooting efforts if you suspect a service issue later.

Can I rename the service instead of deleting it?

Yes, you can modify the service name in the registry or using the sc config command, but renaming does not solve the problem of the broken binary reference. Deleting is the cleaner solution to free up resources and avoid conflicts.

Will deleting the service delete my data?

No, deleting the service entry only removes the registration from the Windows Service Control Manager. Your actual database files, which are stored in the data directory (usually under Program Files\PostgreSQL\16\data), remain untouched unless you manually delete those folders.

How do I know if the sc delete command worked?

A successful execution returns the message "[SC] DeleteService SUCCESS". If you see an error code, check your administrative privileges or try the registry method. You can also run sc query postgresql-16 again; if it says "the specified service does not exist as an installed service," the deletion was successful.

Is it safe to edit the registry for this task?

It is generally safe if you navigate precisely to the CurrentControlSet\Services key and delete only the known PostgreSQL entries. However, always export the specific key as a backup before deleting it, so you can restore it if you accidentally remove something critical.