DisplayCAL Profile Loader: Keep Calibration Applied
You calibrated your display, the report looks great — and then you reboot, and everything looks wrong again. (Haven’t run a calibration yet? Start with the quickstart guide, then come back here.) The fix is the DisplayCAL Profile Loader: a small background tool that keeps your calibration actually applied.
The DisplayCAL Profile Loader (DisplayCAL-apply-profiles) is a startup utility that loads your display calibration into the graphics card’s lookup tables (the “vcgt” tag) every time you sign in, so the calibration you measured stays active across reboots instead of silently dropping back to the uncalibrated state.
Why you need it
A display profile has two parts: the calibration (corrections loaded into the GPU so the display behaves linearly) and the characterization (the ICC profile color-managed apps use to interpret colors). The ICC profile file sits on disk either way — but the calibration curves must be actively loaded into the graphics card on every boot. Without the loader, Windows starts with uncalibrated video LUTs, and your carefully measured calibration is simply not in effect until something loads it.
Setting up the Profile Loader on Windows
- Install DisplayCAL from the download page (3.9.19 with ArgyllCMS 3.5.0 as of 2026). The Profile Loader is included.
- Enable it to run at startup. The loader is designed to start automatically with Windows. After installation, check that DisplayCAL-apply-profiles is registered to run at sign-in (Task Manager → Startup apps, or the Startup folder, depending on your setup).
- Associate each display with its profile. In DisplayCAL’s profile association settings, bind each monitor to the profile you created for it. This matters most with multiple monitors — see our multi-monitor matching guide.
- Keep the loader running. It typically lives as a small tray/system process. If you kill it or block it from starting, calibration curves are not loaded and your display runs uncalibrated — silently.
- Reboot and check. After a restart, your display should look the way it did right after calibration. If grays look off or colors look “default” again, the loader did not run — work through the troubleshooting list below.
Multi-display notes
- Each display needs its own profile — never copy one monitor’s profile to another, even for identical models. Panels vary.
- The loader applies the correct profile per display based on the association you set. If two monitors look swapped after boot, the associations are crossed — reassign them.
- On laptops with external monitors, the internal and external panels almost always need different profiles (different panels, different backlights).
How to confirm the loader is actually working
The loader is quiet by design, so “is it running?” deserves an explicit check after setup:
- Look for the loader process after signing in. DisplayCAL-apply-profiles should appear among your startup/background processes. If it is absent, it is not registered to start — re-enable it.
- Do a before/after visual test. Temporarily disable the loader’s startup entry, reboot, and open a neutral gray test image; then re-enable it, reboot, and compare. If you cannot see any difference, either your panel’s uncalibrated state is already close to the calibrated one (possible on well-behaved displays) or the loader was not loading anything — verify the profile association in that case.
- Check per-display association. With two or more monitors, open DisplayCAL’s display/profile association view and confirm each monitor name maps to the profile you built for it. A single crossed association makes one display look right and the other look wrong, which is easy to misread as a bad calibration.
Calibration vs. profile: the 30-second recap
People conflate these constantly, so here is the distinction the loader exists for:
| Term | What it is | Where it lives |
|---|---|---|
| Calibration | Corrections that linearize the display (grayscale tracking, tone response) | Loaded into the GPU’s lookup tables at every sign-in — this is the loader’s job |
| Profile (characterization) | Measured description of what the calibrated display can do (gamut, tone curve) | An ICC file on disk, used by color-managed applications |
A color-managed app like Photoshop reads the profile to convert colors correctly — but if the calibration was never loaded into the GPU, the display is not in the state the profile describes, and the conversions are wrong. The loader closes that gap, silently, on every boot.
Troubleshooting
| Symptom | Likely cause | Fix |
|---|---|---|
| Calibration lost after reboot | Loader not starting with Windows | Re-enable DisplayCAL-apply-profiles in Startup apps; check antivirus did not quarantine it |
| Wrong profile on a monitor | Profile association crossed | Reassign each display to its own profile in DisplayCAL |
| Loader reports “Errors in…” on startup | False-positive bug in older versions | Fixed in 3.9.19. Update DisplayCAL — the new version corrected these spurious error reports |
| Colors change when a game launches | Fullscreen apps resetting the GPU LUTs | Exit and let the loader re-apply; some games reset LUTs by design |
A note on the 3.9.19 fix. If the Profile Loader used to greet you with “Errors in…” messages at startup even though everything seemed fine, you were hitting a known false-positive — 3.9.19 corrected it. Update before chasing the error further.
The loader only keeps a good calibration alive — it cannot fix a bad one. If the underlying profile is wrong, re-calibrate first (see the verification guide to check), then make sure the loader is keeping the right profile applied.
Frequently asked questions
What is DisplayCAL-apply-profiles?
It is the DisplayCAL Profile Loader: a small utility that runs at Windows startup and loads your display calibration curves (the vcgt data) into the graphics card. Without it, the calibration part of your profile is not active after a reboot, even though the ICC file still exists on disk.
Do I need the Profile Loader if I only have one monitor?
Yes. The loader’s job — loading calibration curves into the GPU at every sign-in — applies whether you have one display or three. A single-monitor setup without the loader loses its calibration on every reboot just the same.
The loader shows ‘Errors in…’ at startup. Is my calibration broken?
Probably not. Older DisplayCAL versions reported these errors spuriously — a false positive that was fixed in 3.9.19. Update DisplayCAL first; if the message persists after updating, then investigate the actual profile association.
Why do my colors change when I launch a fullscreen game?
Many fullscreen games reset the GPU’s lookup tables when they take over the display, which unloads your calibration until the loader re-applies it. This is normal behavior for those applications, not a DisplayCAL bug.