How to fix "Csc.exe" exited with code -1073741819

The error code -1073741819 typically indicates a problem with the execution of the C# compiler (csc.exe), which can be caused by various issues such as corrupted installations, missing dependencies, or conflicts with other software. Here are some steps you can try to troubleshoot and potentially resolve the issue:

1. Check for System Updates: Ensure that your operating system is fully updated, as missing updates can sometimes cause compatibility issues.
2. Run Visual Studio in Safe Mode: Start Visual Studio in Safe Mode to disable all extensions and see if the issue persists. You can do this by running the command devenv.exe /SafeMode from the command prompt.
3. Check Environment Variables: Ensure that your system's environment variables, particularly the PATH variable, are set correctly and do not contain any invalid paths that could interfere with the compiler.
4. Check for Conflicting Software: Sometimes, other software installed on your machine can conflict with Visual Studio. Consider temporarily uninstalling or disabling any recently installed software to see if it resolves the issue.
5. Use Dependency Walker: You can use a tool like Dependency Walker to check for missing dependencies that csc.exe might require. This can help identify if there are any DLLs that are not being found.
6. Check Event Viewer: Look in the Windows Event Viewer for any application errors that might provide more context about why csc.exe is failing.
7. Reinstall .NET SDKs: Since you mentioned reinstalling .NET, ensure that you have the correct versions of the .NET SDKs installed that are compatible with your projects.
8. Create a New User Profile: Sometimes, user profile corruption can lead to issues. Try creating a new user account on your machine and see if the problem persists when running Visual Studio from that account.

If none of these steps resolve the issue, consider reaching out to Microsoft support or checking the Visual Studio Developer Community for similar issues reported by other users.

References:

• Make code work in Visual Studio

Hi.

I've seen this problem popping up recently. As Viorel has stated, this could be a problem with the newest SDK.

You could try this check to confirm if this is the case, and also try the workaround below :

1. Confirm which SDK is actually being used In a normal command prompt (not VS):

   
      dotnet --list-sdks
   
   

   If you see .NET SDK 10.0.100 installed, try creating and building a minimal repro from the command line:

   
      mkdir C:\Temp\HelloTest
   
      cd C:\Temp\HelloTest
   
      dotnet new console -f net10.0 -n HelloTest
   
      cd HelloTest
   
      dotnet build -v n
   
   

   If this fails with the same MSB6006 / csc.exe -1073741819, the problem is the SDK/compiler itself.
2. Force projects to use a different SDK (workaround) Until the underlying issue is resolved on your machine, you can often get unblocked by pinning an earlier SDK version that works for you (for example 9.0.307):
   • In your solution folder, create a file called global.json with:

     
          {
     
            "sdk": {
     
              "version": "9.0.307",
     
              "rollForward": "latestMajor"
     
            }
     
          }
     
     

   • Then, in that same folder, run:

     
          dotnet --version
     
     

     and verify it prints 9.0.307.
   • After that, try dotnet build again, and also rebuild in Visual Studio.
   If builds start working again under 9.0.307, you at least have a practical workaround while you continue to troubleshoot the access violation with SDK 10.0.100.
3. Delete all build artifacts and do a command‑line build Even though you’ve reinstalled/repair VS/.NET, it’s still worth doing a completely clean build from the command line:
   • Close Visual Studio.
   • In your solution root, delete every bin and obj folder in all projects.
   • Open a command prompt in the solution folder and run:

     
          dotnet clean
     
          dotnet build -v n
     
     

   This helps rule out stale build artifacts and also shows whether the failure happens outside VS.

Hope this helps