Windows BSOD Error 0x0000006D — SESSION1_INITIALIZATION_FAILED Fix

What Does This Error Mean?

Error 0x0000006D means Windows failed to start Session 1 — the first user session that Windows creates during startup. Without Session 1, no user can log in, so Windows crashes immediately. This is typically caused by corrupted Windows session manager files, a bad driver, or damaged system components after a failed update.

Affected Models

Windows 10
Windows 11
Windows 8.1
Windows 7
Windows Server

Common Causes

The Windows Session Manager (smss.exe) file is corrupted or missing
A critical system DLL required by the session manager is damaged or deleted
A bad driver is preventing the session initialization process from completing
A failed Windows update left the session manager components in a broken state
Malware deleted or replaced the smss.exe process to disable system monitoring

How to Fix It

Boot into the Windows Recovery Environment. Force it to appear by turning your PC off three times while Windows is starting. Choose Troubleshoot > Advanced options > Startup Repair.

Startup Repair can often detect and fix missing or corrupted session manager files automatically.
Restore smss.exe from the recovery Command Prompt. Open Command Prompt in the recovery environment and type: sfc /scannow /offbootdir=C:\ /offwindir=C:\Windows — let it complete and restart.

SFC can restore the smss.exe and related files from the Windows component store if they are intact.
Check for malware using an offline scanner. Download Kaspersky Rescue Disk or Windows Defender Offline Scan from another PC, boot from it, and run a full scan before Windows loads.

Malware that replaces smss.exe will not be detected by scanners that run inside the infected Windows installation.
Run DISM to repair the Windows component store. In recovery Command Prompt: DISM /Image:C:\Windows /Cleanup-Image /RestoreHealth — restart after completion.

If the component store itself is damaged, sfc cannot restore files from it. DISM repairs the store first.
Perform a Windows repair install as a last resort. Download the Windows Media Creation Tool, create a bootable USB, and choose to upgrade/repair the existing installation. This keeps your personal files.

A repair install replaces all Windows system files including smss.exe and its dependencies.

When to Call a Professional

If system repair tools cannot restore the session manager, a technician can perform a repair install of Windows. If smss.exe was replaced by malware, professional malware removal before reinstalling is strongly recommended to avoid reinfection.

Frequently Asked Questions

What is smss.exe and why is it important?

smss.exe stands for Session Manager Subsystem. It is one of the first processes Windows starts after the kernel loads. Its job is to set up the Windows environment — creating sessions, starting essential subsystems like the Windows subsystem, and launching the login process (winlogon.exe). Without smss.exe running correctly, no user can ever reach the Windows login screen.

How do I know if malware replaced my smss.exe?

The real smss.exe lives in C:\Windows\System32 and is a very small file (usually under 100 KB). If you see smss.exe in any other folder, or if the file is unusually large, it is likely malware. Never trust any smss.exe located outside of System32.

Does this error mean I have to reinstall Windows?

Not always. In many cases, the Startup Repair tool or the SFC command can restore the damaged files without a full reinstall. A repair install is only needed if those tools cannot fix the problem. Even a full reinstall does not have to mean losing your files — a repair install keeps them.