This page is for when you started an analysis and it stopped because the analysis engine did not start. Look at the message on your screen, then try the steps below in order.
Try these first
- If the Upload screen says the analysis engine isn't ready yet, click Try again. While the app prepares the engine in advance, if the engine quits right away or cannot start at all, the app tries once more on its own and then shows this notice. If it stopped because it was taking too long, the app does not retry automatically.
- If you installed directly (.msi) recently, check When the first run is slow first. Right after installing, Windows security checks can affect how long the engine takes to get ready.
- Close Fabdose completely, open it again, and restart the analysis.
What to do for each message
Find the item below that is closest to the message on your screen. On the Upload screen, the notice shows an error code. The analysis-failed screen does not show an error code by itself; open Error details to see the error message. When you contact us, please include the error code from the Upload screen, or the message in Error details on the analysis-failed screen.
- Windows blocked the engine from starting: allow Fabdose in your security software, then try again. If it keeps happening, reinstall.
- The engine file can't be found, or the engine files have a problem: the analysis-failed screen shows a Check engine again button only in this case, so click it if you see it. If an engine problem notice appears at the top of the screen, click Recheck there. If the problem remains, click Repair automatically in the same notice, or reinstall.
- A security policy blocked the engine: your company or Windows security policy did not allow the engine to run. Ask your administrator to allow the Fabdose engine.
- Antivirus may have blocked the engine: restore the file from your antivirus quarantine list or add Fabdose as an exception, then try again.
- The analysis didn't finish in time: try again in a moment. Large or complex files can take longer.
- The engine stopped during the analysis: try again. If it keeps stopping on the same file, let us know.
- The engine couldn't start, with no other detail: restart Fabdose and try again. If it continues, tell us the error code from the Upload screen or the message in Error details.
The engine problem notice and automatic repair
When a problem with the engine files is confirmed, a notice appears at the top of the screen, and new analyses do not start in the meantime. If the notice says the engine files couldn't be verified, analysis is not paused, and you can recheck or close the notice for now and keep working.
If you installed directly (.msi), clicking Repair automatically makes the app download the installer and install again. If Windows asks for permission, click Yes. The app may restart when the installation finishes. Reinstall on the screen opens the download page on the official site.
If automatic repair can't finish, the screen shows the reason and what to do next. Reasons include low free disk space, an internet connection problem, another program using the files, or a restart being needed. After a failed repair you may have to wait before you can try again, and if it fails several times in a row, automatic repair pauses for a while. In that case, use Reinstall to download the installer from the official site and run it.
If it still doesn't work
Let us know through Contact. Including the following helps us check faster.
- The error code shown on the Upload screen (on the analysis-failed screen, the message inside Error details)
- Your Windows version
- How you installed (Store or .msi)
- What you already tried above
- The text you copied with Copy diagnostics in the engine problem notice