SESSION2_INITIALIZATION_FAILED Bug Check 0x6E [Solved]

Updating the drivers is the easiest fix

Windows 11 » Repair

Reading time icon 4 min. read

Calendar icon Published on

by Kazim Ali Alvi 

published on

Share this article

Readers help support Windows Report. We may get a commission if you buy through our links. Tooltip Icon

Read our disclosure page to find out how can you help Windows Report sustain the editorial team. Read more

fix SESSION2_INITIALIZATION_FAILED
A message from our partner

To fix various driver issues on your PC, you will need a dedicated tool to find the freshest and the original drivers. You can use PC HelpSoft Driver Updater to do it in 3 easy steps:

  • Download PC HelpSoft Driver Updater and install it on your PC
  • Start the scanning process to search for outdated or missing drivers that cause problems
  • Right-click on Update Now to allow the update process.
Download now PC HelpSoft has been downloaded by 0 readers this month

The SESSION2_INITIALIZATION_FAILED bug check, with a value of 0x0000006E, indicates that the Windows OS failed to load in the initialization stage. This usually happens due to corrupt system files, outdated, corrupt or buggy drivers, disk issues, problems with the RAM, and an improper Windows installation!

Before you start troubleshooting the Session2 Initialization Failed blue screen error, install pending Windows updates, disable startup apps, disconnect all non-critical peripherals, and fix overheating issues.

How can I fix the SESSION2_INITIALIZATION_FAILED BSOD error?

Note icon NOTE
If SESSION2_INITIALIZATION_FAILED keeps appearing at startup and you can’t access the PC, boot Windows into Safe Mode with Networking and then use the solutions listed below.

1. Repair the corrupt system files

  1. Press Windows + S to open Search, type Command Prompt in the text field, and click on Run as administrator.command prompt
  2. Click Yes in the UAC prompt.
  3. Paste the following three DISM commands individually and hit Enter after each: DISM /Online /Cleanup-Image /CheckHealth DISM /Online /Cleanup-Image /ScanHealth DISM /Online /Cleanup-Image /RestoreHealth
  4. Now, run this command for the SFC scan: sfc /scannowsfc scan to fix SESSION2_INITIALIZATION_FAILED
  5. Finally, reboot the PC and check for improvements.

In 3 out of 5 cases, the SESSION2_INITIALIZATION_FAILED blue screen error in Windows is caused by corrupt system files. To fix this, run the DISM (Deployment Image Servicing and Management) and SFC (System File Checker) scans, which will replace all corrupted system files with their cached copy stored on the PC!

2. Update all the drivers

  1. Press Windows + X to open the Power User menu, and select Device Manager.
  2. Expand the different entries here, individually right-click on the devices listed underneath, and select Update driver.update all drivers to fix SESSION2_INITIALIZATION_FAILED
  3. Choose Search automatically for drivers and wait for Windows to install the best locally available version. automatic driver search
  4. After updating all the drivers, restart the computer and check for improvements.

If, while updating the drivers, Windows can’t find the better version, go to the manufacturer’s website, check for the newest releases, and then manually install the latest driver.

To streamline the process, you can get a top-rated driver update software which will automatically fetch and install the latest driver version for all the devices.

3. Repair disk issues

  1. Press Windows + R to open Run, type cmd, and hit Ctrl + Shift + Enter.run as admin
  2. Click Yes in the UAC prompt.
  3. Paste the following command and hit Enter: chkdsk /r
  4. If asked to schedule the scan for the next restart, press Y, hit Enter, and then reboot the computer.chkdsk /r to fix SESSION2_INITIALIZATION_FAILED
  5. Wait for the Check Disk utility to detect and eliminate disk-related issues causing SESSION2_INITIALIZATION_FAILED.

4. Check for problems with the RAM

  1. Press Windows + S to open Search, type Windows Memory Diagnostic, and click on the relevant result.
  2. Click on Restart now and check for problems.memory test
  3. Let the utility run, and then check the Windows Memory Diagnostic logs for issues.

If the built-in utility doesn’t find any problems, you must run Memtest86+, an open-source RAM testing tool that runs a series of advanced scans on individual memory modules and detects even the smallest of the issues.

5. Reinstall Windows

When nothing else works, the last option is to reinstall Windows from scratch. In most of the SESSION2_INITIALIZATION_FAILED BSOD error cases, it was a software-based underlying cause, which should, in all likelihood, be fixed after a reinstall.

Creating a Windows 11 bootable USB drive

To reinstall Windows 11 > go to Microsoft’s official website > download the Media Creation Tool > plug in a pre-formatted USB drive > run the downloaded setup > follow the on-screen instructions to create a bootable Windows USB > change the boot order to the USB drive > install Windows.

If the SESSION2_INITIALIZATION_FAILED still keeps appearing, you can check the BSOD error logs, find what’s triggering the error, and take the necessary measures. Or you could always visit a local repair shop. They will also check the hardware for faults, another likely reason for the issue.

Before you leave, discover expert tips to make your Windows PC faster than ever and get unmatched performance!

For any queries or to share which fix worked for you, drop a comment below.

More about the topics: Blue Screen of Death, BSoD error codes, crash

Kazim Ali Alvi

Kazim Ali Alvi Shield

Windows Hardware Expert

Kazim has always been fond of technology, be it scrolling through the settings on his iPhone, Android device, or Windows PC. He's specialized in hardware devices, always ready to remove a screw or two to find out the real cause of a problem. Long-time Windows user, Kazim is ready to provide a solution for your every software & hardware error on Windows 11, Windows 10 and any previous iteration. He's also one of our experts in Networking & Security.

User forum

0 messages