Error code 4294967295

For all those that tried all solutions above and could not solve the issue. In my case it turned out that my WSL2 virtual disk was corrupted. Probably happened after executing wsl --shutdown.

After some investigation, I managed to fix it with these steps.

1. Install another Linux distro in WSL 2 mode

You must run some linux commands and since you can’t launch your current distro, you must install another one. In case you want to install the same version (for example, Ubuntu 20.04), check this: Manually download Windows Subsystem for Linux distro packages. For this example I used Ubuntu 20.04.

Remember to set that new distro to WSL 2 version. Also, remember to terminate completely your broken distro. Sometimes, even if it’s not running, the WSL process still retains the VHDX file open. I recommend to run wsl --shutdown to ensure all distros are closed before continuing.

2. Launch the new distro and install libguestfs_tools and a generic kernel.

Libguestfs is a set of tools that will allow you to mount and repair your corrupted WSL2 VHDX drive. Install it in ubuntu with this: sudo apt-get install libguestfs-tools linux-image-generic

3. Locate your corrupted WSL2 drive

Your WSL2 distro drive is usually located in the folder where your distro is installed. The file you want to find is named «ext4.vhdx». You will need to know its full path in a linux format. In my case I had my Ubuntu distro installed in a custom folder in the D: drive so my path was /mnt/d/wsl/ubuntu/ext4.vhdx.

Make a backup of your vhdx file in another folder, just in case.

4. Repair your VHDX drive

Once you know the path of your drive, run this command to list the filesystems in your VHDX file: sudo virt-list-filesystems /mnt/d/wsl/ubuntu/ext4.vhdx

It should give you the name for the mount, in my case it was /dev/sda.

Then you are ready to repair the drive. Run this command to start a new recovery linux VM where you’ll be able to repair your virtual drive: sudo virt-rescue -a /mnt/d/wsl/ubuntu/ext4.vhdx

Then in the new command prompt of that VM, run this command, using the name of the mount you found earlier: e2fsck -y /dev/sda

It should repair several things in your drive. Once it is done, run the command exit so it will sync all changes and exit the repair VM.

At this point, if all repairs went OK, your distro should be able to start again.

Are you frustrated with the error code 4294967295 displayed in Windows 11? It mainly occurs when the users are trying to start the Windows Subsystem for Linux. While installation of WSL is easy and hassle-free and can be done with a single command, problems can still arise, leading to the WSL process to exit or close. This post will talk about how you can fix the situation where the WSL process exited with code 4294967295 in Windows 11.

Why Does the WSL Process Exit with Code 4294967295 Occur?

Some users have reported the occurrence of the error code 4294967295 while trying to start Windows Subsystem for Linux. The message on the screen display states

A connection attempt failed because the connected party did not properly respond after a period of time, or an established connection failed because the connected host failed to respond.

Several users have reported that the error code appears when they browse the Linux distro with the Window File Explorer. Failure to access the distribution leads to this issue. It is largely a network problem, and can, fortunately, be resolved with multiple solutions.

There are several solutions you can apply to resolve the WSL error code 4294967295 on Windows 11/10:

1. Reset Winsock
2. Stop or Restart Hyper-V
3. Uninstall DNSCrypt
4. Disable/Enable WSL & Virtual Machine Platform

You will need to use an admin account to execute these suggestions.

1] Reset Winsock

Winsock is an excellent API that deals with the output and input requests related to internet applications in the system. Resetting Winsock has reportedly resolved the issue for many users. You can also try it out. These are the steps –

• Open Windows Search (Win + S)  and type WT
• Once Windows Terminal appears, Right-click on it and select Run as administrator from the drop-down menu.
• In the terminal,  type netsh winsock reset and hit Enter.
• Now, Restart the PC.

After that, you need to observe if the issue has been resolved or not.

2] Stop or Restart Hyper-V Service

Hyper-V is a hardware virtualization tool from Microsoft. It enables the users to create and successfully run a virtual machine. In order to run other OS on the Windows Subsystem for Linux natively, the presence of a Hyper-V is essential. However, to fix this issue, you can try restarting or stopping the Hyper-V.

To do so, follow the steps below:

• Open the Run prompt, type services, and press Shift + Enter to launch the Windows Services
• Locate HV Host Service
• Right-click on it and choose to restart  If it’s not running, start it.

3] Uninstall DNSCrypt

DNSCrypt is a software that authenticates and encrypts communications between the OpenDNS and the user. It prevents spying or obtaining data from one’s system without their knowledge. It boosts the security and privacy of the computer. However, in some cases, DNSCrypt can cause the error code 4294967295. In that case, you must uninstall DNSCrypt and see if the problem is resolved.

Follow the steps below that will help you to do so:

• Go to Windows Settings > Apps and locate DNSCrypt
• Click on the tree-dot menu next to DNSCrypt and select Uninstall from the drop-down. Follow the on-screen instructions.

Alternatively, you can use uninstaller.exe to remove the program. Follow the steps below:

• Find the DNSCrypt installation folder in C:Programs files or C:Program files(x86).
• Once you find it, scroll below and locate uninstaller.exe. Click on it and follow the steps after to uninstall DNSCrypt from the system.

4] Disable/Enable WSL & Virtual Machine Platform

Another excellent way to fix the error code 4294967295 is to disable and then re-enable WSL on the system. You don’t have to worry about thinking that the data from the computer will get erased. Take a look at the steps you need to follow –

• Type WT in the Windows search bar. Right-click on it and select Run as administrator.
• Once Windows Terminal is open, type the following command and execute it:

DISM /online /disable-feature /featurename:VirtualMachinePlatform /norestart

DISM /online /disable-feature /featurename:Microsoft-Windows-Subsystem-Linux /norestart

• Restart the computer.
• After the PC starts, you need to go to the Windows Terminal again and execute the following commands:

DISM /online /enable-feature /featurename:VirtualMachinePlatform /norestart

DISM /online /enable-feature /featurename:Microsoft-Windows-Subsystem-Linux /norestart

Restart the PC and see if the problem is resolved or not.

Error code 4294967295 appears when users attempt to use the Windows Subsystem for Linux. The network issue, though frustrating, can be resolved with multiple fixes. You can try any or all of the methods mentioned above to handle the problem. However, if the issue still remains, you must get in touch with a professional.

How do I know if WSL is installed?

While you can check in the features list, the easiest way to figure it out is to type WSL in the run prompt and press the Enter key. If there is no error, and you can see a terminal open up which looks like Linux, then you have WSL.

Is WSL enabled by default?

No. You can use the wsl --install command on any terminal available in Windows to install it. Once enabled, you can then install any of the Linux flavors from Microsoft Store.

I am trying to create my first react project and trying a tutorial. I am basing my webpack config off of that sample project, however when I run webpack, I get an error. Here is the npm-debug log:

0 info it worked if it ends with ok
1 verbose cli [ 'C:\Program Files\nodejs\node.exe',
1 verbose cli   'C:\Users\daford\AppData\Roaming\npm\node_modules\npm\bin\npm-cli.js',
1 verbose cli   'run',
1 verbose cli   'production' ]
2 info using npm@3.8.6
3 info using node@v5.10.0
4 verbose run-script [ 'preproduction', 'production', 'postproduction' ]
5 info lifecycle nestlepronourish@1.0.0~preproduction: nestlepronourish@1.0.0
6 silly lifecycle nestlepronourish@1.0.0~preproduction: no script for preproduction, continuing
7 info lifecycle nestlepronourish@1.0.0~production: nestlepronourish@1.0.0
8 verbose lifecycle nestlepronourish@1.0.0~production: unsafe-perm in lifecycle true
9 verbose lifecycle nestlepronourish@1.0.0~production: PATH: C:UsersdafordAppDataRoamingnpmnode_modulesnpmbinnode-gyp-bin;C:UsersdafordProjectsnestlepronourish.v2node_modules.bin;C:Program Filesnodejs;C:Ruby21-x64bin;C:cygwin64bin;C:ProgramDataOracleJavajavapath;C:Program Files (x86)PythonScripts;C:Program Files (x86)InteliCLS Client;C:Program FilesInteliCLS Client;C:Program Files (x86)AMD APPbinx86_64;C:Program Files (x86)AMD APPbinx86;C:Windowssystem32;C:Windows;C:WindowsSystem32Wbem;C:WindowsSystem32WindowsPowerShellv1.0;C:Program Files (x86)ATI TechnologiesATI.ACECore-Static;C:Program Files (x86)Microsoft SQL Server100ToolsBinn;C:Program FilesMicrosoft SQL Server100ToolsBinn;C:Program FilesMicrosoft SQL Server100DTSBinn;C:Program Files (x86)Microsoft SQL Server100ToolsBinnVSShellCommon7IDE;C:Program Files (x86)Microsoft Visual Studio 9.0Common7IDEPrivateAssemblies;C:Program Files (x86)Microsoft SQL Server100DTSBinn;C:Program Files (x86)Microsoft SQL Server90Toolsbinn;C:Program FilesIntelIntel(R) Management Engine ComponentsDAL;C:Program FilesIntelIntel(R) Management Engine ComponentsIPT;C:Program Files (x86)IntelIntel(R) Management Engine ComponentsDAL;C:Program Files (x86)IntelIntel(R) Management Engine ComponentsIPT;C:Program Files (x86)QuickTimeQTSystem;C:Program Files (x86)GitExtensions;C:Program Files (x86)Windows Kits8.1Windows Performance Toolkit;C:Program FilesMicrosoft SQL Server110ToolsBinn;C:Ruby21-x64bin;C:Ruby21-x64/lib/ruby/gems/2.1.0;C:HashiCorpVagrantbin;C:gitflow;C:Program Files (x86)MySQLMySQL Fabric 1.5 & MySQL Utilities 1.5;C:Program Files (x86)MySQLMySQL Fabric 1.5 & MySQL Utilities 1.5Doctrine extensions for PHP;C:Program Files (x86)Bitvise SSH Client;C:WindowsSystem32WindowsPowerShellv1.0;C:Program FilesTortoiseSVNbin;C:Program FilesJavajdk1.8.0_77bin;C:Program FilesJavaapache-maven-3.3.9bin;C:Program Filesnodejs;C:Program Files (x86)PythonScripts;C:Program Files (x86)Python;C:Program Files (x86)Microsoft VS Codebin;C:UsersdafordAppDataLocalProgramsPythonPython35-32;C:UsersdafordAppDataRoamingnpm
10 verbose lifecycle nestlepronourish@1.0.0~production: CWD: C:UsersdafordProjectsnestlepronourish.v2
11 silly lifecycle nestlepronourish@1.0.0~production: Args: [ '/d /s /c', 'webpack -p' ]
12 silly lifecycle nestlepronourish@1.0.0~production: Returned: code: 4294967295  signal: null
13 info lifecycle nestlepronourish@1.0.0~production: Failed to exec production script
14 verbose stack Error: nestlepronourish@1.0.0 production: `webpack -p`
14 verbose stack Exit status 4294967295
14 verbose stack     at EventEmitter.<anonymous> (C:UsersdafordAppDataRoamingnpmnode_modulesnpmlibutilslifecycle.js:239:16)
14 verbose stack     at emitTwo (events.js:100:13)
14 verbose stack     at EventEmitter.emit (events.js:185:7)
14 verbose stack     at ChildProcess.<anonymous> (C:UsersdafordAppDataRoamingnpmnode_modulesnpmlibutilsspawn.js:24:14)
14 verbose stack     at emitTwo (events.js:100:13)
14 verbose stack     at ChildProcess.emit (events.js:185:7)
14 verbose stack     at maybeClose (internal/child_process.js:850:16)
14 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:215:5)
15 verbose pkgid nestlepronourish@1.0.0
16 verbose cwd C:UsersdafordProjectsnestlepronourish.v2
17 error Windows_NT 6.1.7601
18 error argv "C:\Program Files\nodejs\node.exe" "C:\Users\daford\AppData\Roaming\npm\node_modules\npm\bin\npm-cli.js" "run" "production"
19 error node v5.10.0
20 error npm  v3.8.6
21 error code ELIFECYCLE
22 error nestlepronourish@1.0.0 production: `webpack -p`
22 error Exit status 4294967295
23 error Failed at the nestlepronourish@1.0.0 production script 'webpack -p'.
23 error Make sure you have the latest version of node.js and npm installed.
23 error If you do, this is most likely a problem with the nestlepronourish package,
23 error not with npm itself.
23 error Tell the author that this fails on your system:
23 error     webpack -p
23 error You can get information on how to open an issue for this project with:
23 error     npm bugs nestlepronourish
23 error Or if that isn't available, you can get their info via:
23 error     npm owner ls nestlepronourish
23 error There is likely additional logging output above.
24 verbose exit [ 1, true ]

I have tried searching but cannot figure out what the issue is. My npm version is 3.8.6 and my node version is 5.10.0

I am just starting so I only have a Hello World React compoment so far.

Thanks in advance.

I’m using WSL1 on Windows 11 Pro (Version 21H2 — Experience: Windows Feature Experience Pack 1000.22000.527.0). It’s been working fine for months, but then recently I have been unable to get it to start.

Normally I’ll start a terminal either in Windows or inside of VS Code, and essentially the same thing happens in either. After 1-4 mins of no prompt, I get an error:

Ubuntu-20.02 terminated with exit code 4294967295

Occasionally it simply says:

"Server execution failed"

Or

The I/O operation has been aborted because of either a thread exit or an application request.

[process exited with code 4294967295]

If I check Windows Powershell, it indicates that WSL has stopped:

PS C:Userscutups> wsl -l -v
  NAME            STATE           VERSION
* Ubuntu-20.04    Stopped         1

I did recently do some Windows updates, and it did seem to correlate with those.

Update for Microsoft Windows KB5010414
Update for Microsoft Windows KB5010474
Update for Microsoft Windows KB5009469
Security Update for Microsoft Windows KB5010386

However I rolled them back and the problem was not resolved. The only other change I made around the same time was uninstalling a MacAfee Antivirus trial that had expired.

Any tips?

Troubleshooting information & steps:

• Verified that I am not running through a proxy server or VPN
• Restarted the machine — no impact
• Ran netsh winsock reset as administrator from Powershell, then reboot. This worked on first attempt. After having to restart the machine for another reason, WSL would not start again. I tried the same method and it did not work. So unfortunately it hasn’t be a reproducible fix. After an additional restart, I was able to restart WSL, but it immediately output An error occurred mounting one of your file systems. Please run 'dmesg' for more details.