Troubleshooting Hard-to-Find Windows Subsystem for Linux (WSL) Crash Due to Issues with NTVDMx64

Minh Danh Nguyen (ToughDev)

Rate me:

5.00/5 (4 votes)

18 Jan 2024CPOL5 min read

3.9K

This article describes how to use WinDbg to identify issues that may prevent Windows Subsystem for Linux (WSL) from starting.

Recently I faced startup issues with my WSL instance despite ensuring hardware virtualization availability and uninstalling VMware. After attaching WinDbg to wslinstaller.exe, I managed to identify incompatibilities between WSL and NTVDMx64, a third-party utility for running 16-bit DOS applications on 64-bit Windows. Both tools modify Windows DLL files, leading to conflicts and preventing WSL from initializing correctly.

Views

Daily Counts

License

This article, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Written By

Minh Danh Nguyen (ToughDev)

Technical Writer

Singapore

Since 2008, ToughDev has been publishing technical sharing articles on a wide range of topics from software development to electronics design. Our interests include, but are not limited to, Android/iOS programming, VoIP products, embedded design using Arduino/PIC microcontrollers, reverse-engineering, retro-computing, and many others. We also perform product reviews, both on new and vintage products, and share our findings with the community. In addition, our team also develops customized software/hardware solutions highly adapted to suit your needs. Contact us for more information.

Troubleshooting Hard-to-Find Windows Subsystem for Linux (WSL) Crash Due to Issues with NTVDMx64

Views

License

Comments and Discussions