The following sections explain how to troubleshoot and prevent problems with the Unity editor in different situations. In general, make sure your computer meets all the system requirements, it’s up-to-date, and you have the required user permissions in your system. Also make backups regularly to protect your projects.
You can install different versions of the editor in different folders. However, make sure you backup your projects as these might be upgraded by a newer version, and you won’t be able to open them in an older version of Unity. See the manual page on installing Unity for further information.
Licenses of add-ons are valid only for the Unity versions that share the same major number, for example 3.x and 4.x. If you upgrade to a minor version of Unity, for example 4.0 to 4.1, the add-ons will be kept.
Internet Activation is the preferred method to generate your license of Unity. But if you are having problems follow these steps:
If you still have problems with registering or logging in to your user account please contact email@example.com.
If Unity crashes when starting then firstly make sure that your computer meets the minimal system requirements. Also update to the latest graphic and sound drivers.
If you get disk write errors, you should check your user account restrictions. When in MacOS, note the “root user” is not recommended and Unity hasn’t been tested in this mode. Unity should always have write permissions for its folders, but if you are granting them manually check these folders:
%AllUsersProfile%\Unity (typically C:\ProgramData\Unity)
C:\Documents and Settings\<user>\Local Settings\Application Data\Unity
Some users have experienced difficulties when using hard disks formated with non-native partitions, and using certain software to translate data between storage devices.
Corrupt fonts can crash Unity, you can find damaged files following these steps:
The system might have resources constrained, for example running in a virtual machine. Use the Task Manager to find processes consuming lots of memory.
Unity could try to open a project that is corrupt, this might include the default sample project. In such case rename or move the folder of the project. After Unity starts correctly you can restore the project’s folder if wished.
In the event of a corrupt installation, you may need to reinstall Unity - see the instructions below.
In Windows, there could be problems like installation errors, registry corruption, conflicts, etc. For example, error 0xC0000005 means the program has attempted to access memory that it shouldn’t. If you added new hardware or drivers recently, remove and replace the hardware to determine if it’s causing the problem. Run diagnostics software and check information on trouble-shooting the operating system.
If the editor runs slowly or crashes, particularly on builds, this might be caused by all of the available system resources being consumed. Close all other applications when you build the project. Clean up the system using its utilities, and consult the Task Manager (Windows) or Activity Monitor (MacOS) to find out if there are processes using lots of resources, for example memory. Sometimes virus protection software can slow down or even block the file system with its scanning process.
There are many factors that can destroy a project, you should constantly backup your projects to prevent unfortunate accidents. When in MacOS, activate the TimeMachine using an external hard disk reserved for this sole purpose. After a loss you can try any of the file recovery utilities that exist, but sometimes this is irreversible.
Follow these steps to reinstall the editor:
Uninstall Unity. When in MacOS, drag the Unity app to trash.
Delete these files if present:
%AllUsersProfile%\Unity\ (typically C:\ProgramData\Unity)
Restart the computer.
Download the latest version from our website, since your original install might be corrupt: http://unity3d.com/unity/download/archive