Windows 11 Error 340: “The Supplied Kernel Information Version Is Invalid”
Why This Error Happens
Error 340 typically occurs when there is a mismatch between the Windows kernel version and the drivers or system files attempting to interface with it, often following an incomplete Windows Update or a botched driver installation. This can also result from corrupted system files in the WinSxS store or a kernel-mode driver that was compiled against a different Windows build than the one currently installed. In some cases, third-party virtualization or security software (like antivirus kernel hooks) fails to recognize the updated kernel version signature after a feature update.
Step-by-Step Resolution Guide
- Run the System File Checker (SFC) and DISM tools
Open Command Prompt as Administrator and run:
sfc /scannow
Followed by:
DISM /Online /Cleanup-Image /RestoreHealth
This repairs corrupted system files and restores the WinSxS component store, which often resolves kernel version mismatches.
-
Update or Roll Back Recent Drivers
Go to Settings > Windows Update > Advanced options > Optional updates > Driver updates. If the error started after a driver update, open Device Manager, locate the recently updated driver (commonly display, storage, or virtualization drivers), right-click it, select Properties > Driver tab > Roll Back Driver. -
Check for Pending Windows Updates
Navigate to Settings > Windows Update and ensure your system is fully patched. Partial updates can leave kernel files out of sync with associated drivers. Install any pending Cumulative or Feature Updates and restart. -
Uninstall Recently Added Virtualization or Security Software
If you use Hyper-V, WSL2, VMware, or third-party antivirus with kernel-level hooks, temporarily disable or uninstall these via Control Panel > Programs > Turn Windows features on or off (for Hyper-V/WSL) or the vendor’s uninstaller. Restart and check if Error 340 persists. -
Perform an In-Place Upgrade Repair
If the error remains, download the Windows 11 Installation Assistant from Microsoft’s official site and choose the “Keep personal files and apps” option. This refreshes all kernel-related system files without wiping your data.
Alternative or Verification Steps
- Verify the fix: Open Event Viewer (
eventvwr.msc), navigate to Windows Logs > System, and confirm Error 340 no longer appears after a fresh restart and triggering the action that previously caused it. - Alternative: If the error persists only within a specific application (e.g., a VM tool), check that application’s changelog for a kernel-compatible update, as it may need patching to support the current Windows 11 build version (run
winverto confirm your build number).