Share via

Terminal exiting with code 4294967295 every time

Anonymous
2022-06-03T21:47:32+00:00

I have been struggling with this problem very recently. The terminal will give me the regular prompt, at which point I can quickly type something in and maybe get it to run, but then in about 5 seconds I get the "[process exited with code 4294967295 (0xffffffff)]" message.

When and Where

This problem occurs in any terminal I open, be it Command Prompt, the Terminal app, or Visual Studio Code.

What I've Tried

I have tried disabling and shutting down WSL2 because that was recommended, but it changed nothing. I have no clue how to fix it, and since I haven't found anything else online that seems to address this problem I don't want to try to do something funny in Safe Mode, so I haven't done that. I have tried removing my Linux profile from the Terminal app, but it changed nothing.

If anyone can give me some help, that would be great. Obviously, I can't do anything that requires the terminal (besides maybe a quickly executing one-liner), except in the terminal I can bring up using the advanced startup menu (Shift + Restart)

Windows for home | Windows 11 | Performance and system failures

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

4 answers

Sort by: Most helpful
  1. Anonymous
    2022-06-04T02:59:14+00:00

    Hi EBFoster,

    Welcome to post in Microsoft Community. I'm Mosken, let me help you figure it out.

    According to your description, I knew that you are always getting error 4294967295 when using Windows terminal, even if you try to disable/enable WSL2 and reset Linux configuration. If my understanding is wrong, please correct me in the reply.

    First of all, according to the error code you provided, it is generally because your current host and your Linux subsystem connection timed out and did not respond. You can try to fix it with the following solutions.

    1. Reset network related settings, restart related services

    You can try the following commands to try to fix it. Please run Command Prompt as an administrator ("Win" logo key + "Q", enter "cmd", select "Run as administrator"), and enter the following commands one by one.

    netsh winsock reset
    
    net start HvHost & net stop HvHost & net start HvHost
    

    2. Set the Hypervisor to start automatically

    The Windows Hypervisor Platform is used to manage software related to virtual machines so that WSL can install other operating systems. Please run Command Prompt as an administrator ("Win" logo key + "Q", enter "cmd", select "Run as administrator"), and enter the following command.

    bcdedit /set hypervisorlaunchtype auto
    

    After doing the above, restart your computer and see if it works.

    The above steps are provided based on the information I have learned so far, I wish that will be helpful to you. If your problem still cannot be solved by these steps, you could tell me the specific situation in the next reply. I will continue to assist you in solving the problem.

    Best Regards,

    Mosken- MSFT | Microsoft Community Support Specialist

    Was this answer helpful?

    30+ people found this answer helpful.
    0 comments No comments
  2. Anonymous
    2022-06-07T03:34:26+00:00

    Hi EBFoster,

    I'm glad your issue was resolved.

    But according to your last reply, 1 service failed to start successfully. So it is recommended that you try to run the following command to try to repair the corrupt system files that may exist.

    Please run Command Prompt as an administrator ("Win" logo key + "Q", enter "cmd", select "Run as administrator"), and enter the following commands one by one.

    sfc /scannow 
    
    DISM /Online /Cleanup-Image /RestoreHealth
    

    If you found the suggestions in the above reply helpful, you can rate the reply as "Helpful" to help others with the same problem.

    Best Regards,

    Mosken- MSFT | Microsoft Community Support Specialist

    Was this answer helpful?

    20+ people found this answer helpful.
    0 comments No comments
  3. Anonymous
    2022-06-04T22:48:40+00:00

    Ok this is really strange, but now everything is working. I did those things, watched a YouTube video, and then opened up the most recent version of Powershell. It didn't throw an error, VSCode's terminal didn't, and everything seems to be working fine. I ran the start -> stop -> start commands you suggested just to make sure it would work but everything seems to be fine. I still have no clue why, but hopefully this is the end of my problems. Thanks for all your help!

    Was this answer helpful?

    7 people found this answer helpful.
    0 comments No comments
  4. Anonymous
    2022-06-04T21:56:51+00:00

    I was only able to complete some of the commands you suggested I enter. "netsh winsock reset" worked just fine. When I tried to run "net start HvHost", it said it was starting and then the terminal exited with the same code as usual, not allowing the start process to finish. When I tried to run "net stop HvHost", it said it had not started. When I ran the "bcdedit" edit command, it said it executed fine, before the terminal threw its code. But I was unable to run all of those commands. Any ideas for how to either run them or find alternative ways of doing the same thing?

    Was this answer helpful?

    7 people found this answer helpful.
    0 comments No comments