How to fix Error 487 on Windows 11

by

Why This Error Happens

Error 487 (“Attempt to access invalid address”) occurs when a process tries to read or write to a region of memory it does not have permission to access, or that has already been freed. This is commonly triggered by corrupted application binaries, outdated or mismatched DLL files, incompatible drivers, or memory conflicts caused by faulty RAM modules. It frequently appears during software installation, Windows Updates, or when launching applications that rely on specific memory-mapped resources (like antivirus tools or virtualization software).

Step-by-Step Resolution Guide

  1. Run System File Checker (SFC) and DISM
    Open Command Prompt as Administrator and run:
   sfc /scannow

Followed by:

   DISM /Online /Cleanup-Image /RestoreHealth

This repairs corrupted system files that may be causing invalid memory pointers.

  1. Update or Reinstall the Affected Application
    Navigate to Settings > Apps > Installed Apps, locate the application throwing Error 487, and select Uninstall. Download the latest installer from the vendor’s official site and reinstall it cleanly, ensuring no leftover files remain in C:\Program Files\ or %AppData%.

  2. Check and Update Drivers
    Go to Device Manager, right-click on display, storage, and chipset drivers, and select Update Driver. Outdated drivers are a common cause of invalid memory address calls, especially after a Windows 11 feature update.

  3. Run Windows Memory Diagnostic Tool
    Press Win + R, type mdsched.exe, and press Enter. Choose Restart now and check for problems to scan for faulty RAM that could be causing memory access violations.

  4. Update Windows 11 Fully
    Go to Settings > Windows Update > Check for updates and install all pending updates, including optional driver updates, to ensure compatibility fixes for Error 487 are applied.

Alternative or Verification Steps

  • After applying fixes, reproduce the original action that triggered Error 487 (e.g., relaunch the app or repeat the installation) to confirm the error no longer appears in Event Viewer under Windows Logs > Application.
  • If the issue persists, boot into Safe Mode (Settings > Recovery > Advanced Startup) and attempt the same action — if the error doesn’t occur, a third-party background service or driver is likely the root cause.