Runtime Error 216: what it means and how to fix it

Error 216 — typically “Runtime error 216 at” plus a memory address — is one of the oldest Windows error numbers still in circulation. It comes from software built with old Pascal/Delphi-era tools: the program touched memory it didn't own (an access violation) and the runtime shut it down. On a modern PC it almost always involves an old program — or, rarely, something pretending to be one.

What it means

Old runtimes numbered their failures, and 216 was “access violation”: the program read or wrote memory outside its own space. Modern Windows enforces memory boundaries strictly, so habits that slipped by on Windows 95/XP — stray pointers, use-after-close bugs in old code — now end the program immediately. The address after “at” is where it happened, useful to the program's maker, not needed for the fix.

The fix, in order

  1. Identify the program. Note what was starting, running, or closing when it appeared. If the message appears at login with no program obvious, check Task Manager's Startup tab for legacy items.
  2. Update or reinstall that program. Even old software often has a final version that's far better behaved on modern Windows — get it from the maker, not an archive of random downloads.
  3. Use compatibility settings: right-click the shortcut → Properties → Compatibility → run in compatibility mode for Windows 7 or XP, and “Run as administrator” if the program keeps its data in its own folder. Apply and test.
  4. Repair the Visual C++ Redistributables if the program is C++-based (Settings → Apps → each redistributable → Modify → Repair) — cheap to do, occasionally the whole answer.
  5. Run a full Microsoft Defender scan — specifically if error 216 appears and no old program explains it. Decades ago, malware was written with the same old tools and produced this exact error; an unexplained 216 earns a scan.
  6. Check Event Viewer (Windows Logs → Application) for the faulting program and module at the error's time — it names names when the dialog doesn't.
Do not download a “runtime error 216 removal tool.” That exact phrasing is a scareware staple. The real fixes are compatibility settings, a clean copy of the actual program, and Windows' built-in Defender scan — all free.

If it still happens

If one beloved old program simply cannot run on current Windows even with compatibility settings, the remaining honest options are the maker's modern replacement, or running the old program inside a virtual machine with an older Windows (VirtualBox plus a licensed old Windows image). If 216s appear across many programs with random addresses, suspect hardware instead — run Windows Memory Diagnostic; failing RAM produces exactly that scatter pattern.

Common questions

Is runtime error 216 a virus? Usually not — it's an old program crashing. But it earned a scan if nothing old is installed, because ancient malware built with the same tools threw the same error.

Why does it appear at shutdown? A legacy program or service is closing badly — unloading in the wrong order. Identify it via Event Viewer; updating it or disabling its startup entry ends the message.

Related errors

Runtime Error 217 · Runtime Error 339 · Runtime Error 6025