Skip to main content

Troubleshooting

Start with the exact error message, the selected drive, and the action you tried. Record the time so you can find the corresponding report or log entry.

Agent unavailable​

Symptom: no drive list, a service-unavailable message, or OODCMD exit code 3.

  1. Wait briefly for the agent connection after startup.
  2. Open Windows Services and check O&O Defrag Agent (OODefragAgent).
  3. If it is stopped, start it with appropriate administrator rights.
  4. If the interface or automatic-optimization page reports an outdated service, update or repair the product installation.
  5. Reopen the application and inspect the result.

If you selected Start hibernation mode in the tray menu, the agent was deliberately stopped. Choose Stop hibernation mode and check the service again.

Finish or deliberately stop maintenance before restarting a running service. If it will not start, collect the application and Windows service errors for support.

Drive missing or unavailable​

Check that Windows can access the volume and that it is connected, unlocked, and ready. Review Include removable drives and Include external drives in the relevant settings or job.

A network share is not a local volume. An offline job entry preserves configuration but cannot run while its drive is absent. Use Drive detection only to correct a type, not to recover a missing volume.

Start button or method unavailable​

Select a drive and check whether it is already running or queued. Analyze if the Advisor requests it. Review trial restrictions, SSD protection, and zone prerequisites.

If the Advisor says Nothing to do, inspect the explanation rather than repeatedly trying to force an action. In OODCMD, exit code 5 can indicate a busy drive or disabled zones.

Optimization is slow or waiting​

Large files, many files, low free space, complete methods, and competing drive activity can lengthen a run. Review Performance limits, job Activity Monitor guards, excluded processes, and power conditions.

Do not raise every limit blindly. Check whether the chosen goal is Stay responsive or whether a backup or other blocked process is still running.

Files remain fragmented​

Analyze again, then inspect the files. Possible causes include locks, exclusions, a large-file filter, insufficient working space, or the ROI policy.

Review the ROI factor and matching inclusion/exclusion rules. Use boot-time optimization for eligible locked files when justified. Repeated full-drive passes do not resolve every cause.

A job did not run​

Open Schedules and review:

  • Its saved schedule and selected weekdays.
  • At least one enabled drive method.
  • Drive availability and minimum fragmentation thresholds.
  • AC-power and wake conditions.
  • CPU, disk, and process guards.
  • End date, maximum runtime, and delayed-start settings.
  • Any pre-job command failure.

The job dialog's Next run field displays not scheduled without calculating the next execution time. Use the saved configuration, last-run data, and reports to determine whether the service executed the task.

No report appears​

Enable Create reports in global settings and inspect the job's own setting. Wait for the operation to finish and check the retention limit. A deleted or aged-out report cannot establish the latest result.

Windows RE preparation fails​

On Boot-Time Optimization, check both the Windows RE readiness result and the Fortress Mode version status. Use Set up if no environment is prepared, or Update if it was prepared for an older program version. Run and schedule controls require a ready environment for the current version and are unavailable in the trial. Setup or update alone does not schedule a run; choose a mode and then Restart and optimize now or At next system start.

If an automatic run returns to Windows without optimizing the intended drives, check their availability and the logs. The run also returns to Windows if no selected drive can be started or the agent connection is lost. See Fortress Mode.

Read the preparation error before restarting. Check recovery-environment availability and system-drive space. A failed recovery-image mount or commit can require Windows servicing investigation.

Enable logging and reproduce preparation. If the message points to DISM, collect %WINDIR%\Logs\DISM\dism.log as well as the Defrag log. If the installation directory cannot be found, repair or reinstall O&O Defrag.

Do not delete recovery partitions or change boot configuration as a generic fix. Contact support with the exact failure.

SSD TRIM cannot be changed​

An unknown state means Windows did not provide usable information. If Windows rejects a change, inspect administrator rights and storage support. Do not infer state from whether the Windows optimization schedule is enabled.

A tool will not open​

Check connectivity when a download is required, review the tool card's error, and use its offered installation or repair path. Downloads are suppressed in Windows RE. A signature error should be investigated rather than bypassed.

A hardware or file-system error appears​

Protect important data and investigate the drive before repeating heavy maintenance. Use Drive Health and the relevant check/repair tool. Defragmentation is not a hardware-repair operation.

If these steps do not resolve the problem, contact support with reports and logs.