Hexnode Agent service missing from services.msc causing sync failure on Windows 11Solved

Hello,

Thanks for reaching out to Hexnode Connect.

It sounds like the background service registration for the Hexnode Agent has become corrupted or was unexpectedly removed—perhaps by an overzealous antivirus or system cleanup tool—even though the application executable is still present in Task Manager.

Normally, for Windows sync issues, we recommend the following checks:

1. Press Win + R and type services.msc.
2. Locate the Hexnode Agent service.
3. If it is stopped, manually restart it and ensure the startup type is set to Automatic.

Since the service is completely missing from your list, a normal system reboot will not recreate it because the underlying Windows registry keys for that service are gone.

Fortunately, you do not need to perform a full device re-enrollment. You can simply reinstall the Hexnode Agent. Running the installer will act as an in-place repair, restoring the missing Windows service and allowing the device to resume syncing.

I hope this helps. If you find any more issues or need further assistance feel free to reach out.

Best regards,
George,
Hexnode UEM

Thanks George. That makes sense regarding the registry keys. Just to confirm before I push this fix to my field tech: if I run the Hexnode Agent installer again over the existing setup, it won’t create a duplicate device entry in the portal or mess up the policies currently assigned to the machine, right?

Hello,

That is correct. Running the Hexnode Agent installer over the existing setup will not create a duplicate device record in your Hexnode portal, nor will it disrupt any of the policies or configurations currently assigned to the machine.

To proceed, simply download the Hexnode Agent installer directly from your portal’s enrollment URL on the affected device and run it. The installer will recognize the existing enrollment identifiers, patch the missing application files, and properly re-register the Hexnode Agent service with the Windows OS.

Once the installation completes, open services.msc again to confirm that the Hexnode Agent service is now present and running. The device should then automatically check in with the server and process any pending sync actions normally.

I hope this helps. If you find any more issues or need further assistance feel free to reach out.

Best regards,
George,
Hexnode UEM