Almost every modern ECU checks its own memory with checksums. Change a single map value and the stored checksum no longer matches, so a file that is flashed without correction may be rejected or leave the car unable to start. This guide shows how checksum correction works in WinOLS with checksum plugins: the F2 dialog, finding the right module, what happens automatically, and what to check before you export. It is based only on EVC’s public WinOLS 5.94 manual and EVC’s own product pages.
Facts checked on 30 October 2026 in the WinOLS 5.94 manual (English PDF) and the WinOLS software and plugin pages on evc.de, linked in the sources at the end. Shortcuts and dialogs can change between WinOLS versions. For the theory behind checksums, see our ECU checksum explainer.
source). EVC’s plugin page lists the available checksum modules with the ECU families each one supports (source); check that page for your ECU instead of relying on third-party lists. Each module recognises automatically whether it can handle the file in the current project (source, source).The manual describes a checksum as an area that is checked, an address where the checksum is stored and the parameters that define the calculation. A project can contain any number of checksums (source).
Before you start: the Original must be the real stock read
This is the most common reason checksum correction fails. EVC states that some checksum modules require an unmodified original version: the data read from the car must be loaded as the project’s Original, otherwise the checksum may not be recognised or not calculated correctly. The same warning appears for automatic checksums in the checksum dialog chapter (source). If you have not set up the project yet, follow our guide to importing an original read into WinOLS first, and make your changes in a version.
Step by step: correcting checksums with F2
- Open the checksum dialog. Menu Edit > Checksum, hotkey F2 (or C) (source). The simple view shows the current checksum status; the extended view lists every block found.
- Click Search. All installed checksum plugins check whether they can handle the current file. If you own the right module, it is applied automatically and the checksum is calculated and, if you choose, always corrected (source).
- No module? Search online. Click Search checksum online. The project is compressed and uploaded to the EVC server (internet needed) and a few seconds later you get an answer telling you which checksum module works for your data. EVC describes this check as free and without any commitment (source). If you need a proxy, it is set at Miscellaneous > Configuration > Miscellaneous > Internet (source).
- Check that the module is registered. ? > Info about plug-ins (or the Installed Plugins button in the dialog) lists what is installed. EVC notes that if a plug-in is installed but not registered, its search works but the checksum is not calculated (source).
- Work on your version. With automatic correction active, changes inside a checksum area are corrected as you edit. The status bar shows the state of the checksum modules while you work (source).

Before you export: apply and verify
- Apply all checksums and patches: Ctrl+Alt+F2 (source).
- Apply one block: Edit > Apply checksum (Alt+F2) recalculates the block at the cursor. It is only available with the cursor inside a checksum block and the plugin installed and registered; with automatic correction enabled you normally do not need it (source).
- Look at the dialog once more. In the extended view, Description shows a block’s parameters and Apply applies the selected checksum immediately (source).
- Then export the version in the format your flash tool expects.
Manual checksums, sync blocks and patches (for experienced users)
- Manual checksums. In the extended view, Add and Edit create or change checksums by hand (source). The manual default is an additive checksum: the sum of all values in an address range is kept constant. The range must contain all your changes and be smaller than the manufacturer’s checksum range (smaller is better), and EVC suggests using the next address after the range as the correct-to address. The target must not be inside the checked range but must be inside the range the ECU’s software uses (source).
- Fullbyte checksums. A variant where the register is wider than the data, so the full difference has to be compensated; you enter a target range instead of a single address (source).
- Sync blocks. The small triangle next to Add creates a sync block, which keeps two identical memory ranges identical when one of them changes (source).
- Patches. Some automatic checksums insert patches to correct the ECU; without an automatic checksum you can manually add a patch tag block in an empty area (source).
- Addresses. Addresses in the checksum dialog refer to the <All elements> view, not the current element (source).
A wrong manual checksum is worse than none. If you are not sure, use a module or let a file service handle it.
Automatic checksum search on import
In Miscellaneous > Configuration > Automatically > Import, the Search checksums option makes WinOLS search for checksums after every import; if checksums were already found in the project, they are recalculated (source). The warnings settings also let you stop the request dialogs that appear when checksums are found (source). When you compare or import changes between files, note that changes to checksums and patch blocks are not carried over (see our WinOLS compare and import changes guide), so run F2 again on the new version.
Common problems
- Search finds nothing. Check the Original is the true stock read, then use Search checksum online to see which module fits (source).
- Module found but nothing is corrected. Check Info about plug-ins: installed but not registered means search only (source).
- Checksum OK in WinOLS, but the ECU still complains. Some ECUs also need tool-side or patch handling; check with your flash tool’s maker and do not keep re-flashing.
Need the file done for you?
If you do not have the module for your ECU, upload your original read to ECU File Market with the vehicle, ECU hardware and software numbers and the tool you used. Credit prices are on our pricing page; checksum correction is a paid extra, and most files are returned in under one hour during support hours.
Good practice: only work on vehicles you own or are authorised to work on, keep the original file for the life of the car, and keep all emission control systems fitted and working. This guide does not cover removing or disabling DPF, EGR, SCR/AdBlue or any other emission equipment.
Sources (checked 30 October 2026)
- EVC WinOLS 5.94 manual (English PDF), chapters 1.4 Checksums, 1.7.5 The original, 2.11 Correcting checksums, 5.21 to 5.23 checksum dialogs, 10.3.5.1 Configuration / Automatically / Import, 12.6 Info about plug-ins: evc.de/ftp/winols/WinOLS HelpEn.pdf
- EVC, WinOLS software page: evc.de/en/product/ols/software/
- EVC, WinOLS plugins and checksum modules: evc.de/en/product/ols/plugins.asp
WinOLS is a registered trademark of EVC electronic GmbH. ECU File Market is an independent tuning file service and is not affiliated with, endorsed by or sponsored by EVC. The name is used only to describe compatibility and workflow. Use only genuine, licensed software and checksum modules.