Search Unity

  1. Welcome to the Unity Forums! Please take the time to read our Code of Conduct to familiarize yourself with the forum rules and how to post constructively.
  2. We have updated the language to the Editor Terms based on feedback from our employees and community. Learn more.
    Dismiss Notice

Failed because this command failed to write the following output files error in new project

Discussion in 'Editor & General Support' started by Boz0r, Jun 8, 2022.

  1. Boz0r

    Boz0r

    Joined:
    Feb 27, 2014
    Posts:
    419
    I'm trying to get back to Unity, but every time I open a project I get a boatload of errors, even with a completely new project, both 2D and 3D.

    The only possible solution I've found online is this one. All other solutions seems to be on mac.

    I've tried uninstalling everything Unity related, cleaned up AppData and ProgramData, and used CCleaner to clean up regedit before reinstalling. I've also tried installing it both on an HDD and an SSD, with projects on both drives.
     
  2. CodeSmile

    CodeSmile

    Joined:
    Apr 10, 2014
    Posts:
    4,191
    „Failed to write“ errors always make me suspect file/folder permission issues first, secondly not enough disk space second or possibly restricted folders (such as C:\Program Files or Windows).

    Try create projects under the current user‘s Documents folder and do no run Unity (Hub) with elevated access (ie not „Run as Administrator“).
     
  3. Boz0r

    Boz0r

    Joined:
    Feb 27, 2014
    Posts:
    419
    Pretty sure I've already tried that, but I'll give it another shot later. I'm in the process of deleting everything Unity-related right now.
     
  4. Boz0r

    Boz0r

    Joined:
    Feb 27, 2014
    Posts:
    419
    I tried it, and it didn't make any difference. I tried installing the 2019 LTS version and made a new project with that, which gave me some other errors instead:

    So it looks like some kind of permission issue.
     
  5. Boz0r

    Boz0r

    Joined:
    Feb 27, 2014
    Posts:
    419
    I finally fixed it by using regedit. The following key had some gibberish values that I removed:

    Computer\HKEY_CURRENT_USER\SOFTWARE\Microsoft\Command Processor\Autorun

    Doing so, though, caused Windows to not start up explorer.exe on startup. It gave me a command prompt instead, so I could easily start it up. I fixed that problem by adding 'explorer.exe' to the following key.

    Computer\HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\Shell

    I hope others can use this information.
     
  6. unity_r5HlRUDMk1OExA

    unity_r5HlRUDMk1OExA

    Joined:
    Sep 14, 2022
    Posts:
    1
    Your a life saver bro Thx!