Skip to main content

Troubleshooting

Each section names a symptom, its usual cause and the steps that resolve it. For the meaning of the fields of a finding, see Results and the performance index.

Update results are missing or unavailable​

Cause: Update queries run on demand, not during every refresh. They need network access and a working update source; application updates are queried through winget.

Solution:

  1. Start the update query from the finding.
  2. Check the network connection and wait for the query to finish; it can take longer than local measurements.
  3. If winget is unavailable or the query fails, the finding shows an unavailable check. Install updates with Windows Update or the update function of the application concerned, then select Refresh. See Update checks and reports.

The score changes between runs​

Cause: Memory, CPU and process findings reflect the current activity. A running game, backup or update, as well as changed settings or disk space, change the result.

Solution:

  1. Close unrelated workloads.
  2. Select Refresh and compare only sessions under similar conditions.
  3. Compare reports by application version and date of the check.

A change has no effect on the findings​

Cause: The findings are a snapshot. Some changes, such as a pending restart, only take effect after Windows restarts; refreshing SpeedCheck does not replace a restart.

Solution:

  1. Restart Windows if a restart is pending.
  2. Select Refresh to see the new findings. See Actions and Windows settings.

Exporting the findings fails​

Cause: The selected folder is not writable, or there is not enough free disk space.

Solution:

  1. Choose Export findings... again and select a writable folder.
  2. Check the available disk space.
  3. Use Copy findings as an alternative to obtain a text report.

No boot time is shown​

Cause: Boot measurements come from the Diagnostics-Performance event log of Windows. If it contains no suitable events, no boot time can be derived.

Solution: This is not an error of SpeedCheck. The finding remains without a value until Windows records suitable boot events.

The application does not start​

Cause: The application needs administrator rights and all files of the package supplied by O&O.

Solution:

  1. Approve the Windows administrator prompt with an administrator account.
  2. Use the complete package supplied by O&O; a copy of the executable alone can lack required runtime components. See System requirements.

The application update cannot be applied​

Cause: The package cannot replace itself, or the application runs in a Windows recovery environment, where update checks are suppressed.

Solution:

  1. Finish active work and start the update again from the Updates page.
  2. If the update action opens the download page instead, download the current package there and replace the application manually. See Settings and updates.