# Manual Scan Timed Out

Last Updated On: 23 Oct 2026

5 minutes read

## Problem

A manually initiated patch scan displays the error **Scanning Timed Out**.

## Cause

- The server firewall blocks data.
- Computers in remote offices are switched off or the agent service is not running.
- Multiple IP addresses are enabled on the server computer.
- UAC and Remote UAC are enabled on Windows computers in a workgroup.

## Resolution

The timeout means that the server has not recorded completion within the scan timeout period. The message alone does not identify the cause.

If the agent and Central Server run on the same computer, first confirm whether the failed operation is a patch scan or an inventory scan. Record the scan start time and the server update or restart time. For a patch scan, check the agent records for the scan start, scan completion and result upload.

If no scan process is visible, the scan might have started and then exited. Check the recorded error before you select a repair procedure. If another scan is running, avoid starting repeated scans.

If the scan completed but result upload failed, investigate the recorded transfer or server-response error. If the agent reports successful upload but the console status does not change, provide the matching agent and Central Server records to Support. For a persistent patch scan timeout, follow the [persistent scan-failure log-collection procedure](https://www.manageengine.com/kb/patch-management/patch-scan-failed.html#persistent-scan-failure). Include both agent and Central Server logs for the same attempt.

1. **Check firewall ports:** Add ports 8383 and 8027 to the server firewall exception list. Port 8383 is used for agent-server communication and console access. Port 8027 is used for on-demand tasks, including patch scanning.
2. **Check remote-office computers:** Ensure that the computers are switched on during the scan and that the Patch Manager Plus agent service is running.
3. **Check server IP addresses:** If the server computer has multiple IP addresses from virtual adapters or multiple network adapters, disable the unused virtual adapters.

**Important**

The following UAC and Remote UAC changes apply only to computers in a workgroup. Setting UAC to Never Notify or changing `LocalAccountTokenFilterPolicy` reduces Windows security protections. Try the firewall, reachability, service, and multiple-IP checks first, and obtain security or change approval before applying these settings.

### Disable UAC on workgroup computers

1. Open **Start → Settings → Control Panel → User Accounts**.
2. Open **User Account Control Settings**, move the slider to **Never Notify**, and click **OK**.

### Disable Remote UAC on workgroup computers

1. Open **Start → Run**, enter `regedit`, and click **OK**.
2. Navigate to `HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System`.
3. Create or modify the DWORD value `LocalAccountTokenFilterPolicy`, set its value data to `1`, and click **OK**.

## Related

- [Patch scan](https://www.manageengine.com/vulnerability-management/help/patch-management/patch-scan.html)