I have been using Unity 3.0 with windows 7 pro 32 bit and it was working with no issues. Once I upgraded to Unity 3.4 I started having a problem. When I start Unity it exits silently with no errors. There is nothing in the log and I have made an exception in DEP. I have admin access and I disabled the virus protection. I also upgraded my Nvidia 5200 drivers. Still it will not start. I never even get to the splash screen.
I filled out a bug report but didn’t receive any help there. Has anyone had any success getting 3.4 to work with windows 7? Nothing on PC has changed except Unity was upgraded.
I rolled back the drivers but still have the same problem. Something in the new version is causing this. I ran the old version of unity just fine. I have googled this problem but there doesn’t seem to be a solution. It either works on your PC or it doesn’t when it comes to Windows 7. If I had an error message that would at least give me a direction to go but right now I have no direction.
normally if you get no error message shown its always the security solution or DEP. I’m not aware of anything else that can cause it.
UAC errors would allow it to startup to crash directly, other kind of errors would make it fail at runtime.
Its only DEP that checks before it can execute at all and security can cause it cause if they mess with the threads at runtime (disabling security often does not help as most of them have guards running that makes it perma present) during startup it can lead to clashes before the core is even. its though very rare, saw it once or so in the past 5 years, normally I got to see consequences of that when entering play mode
there is btw one major change in 3.4 vs 3.3: 3.4 supports the Windows 7 tablet support too, so did you perhaps have some hack driver installed on that end or alike in the past? that could now mess it? (should cause a fail out but a crash too though normally)
I have added Unity to the exception list in the DEP tab but that doesn’t do anything. So I guess I will just go back to using the previous version of Unity since it actually works. Thanks for all the suggestions.
Since I don’t see it mentioned, you could also try “Run As Administrator” from the right click menu, when over the executable icon.
Having Admin rights can still need the confirmation at least once to actually give full privileged to the program.
I had same problem when I first downloaded and tried to run Unity3.4, After contacting Unity and spending several minutes trying to figure it out. I did the same thing, tried as admin, even tried to run in compatibility mode, nothing worked.
Finally found a solution in the forums. (Thanks to the great staff at Unity that took the time to help…Kudos)
Windows7 - Make double sure DEP is turned off.
Somehow mine got turned back on for some game or other.
Remove DEP completely from the running processes, ie disable it entirely. You will need to google for that, to disable the process. I had to do this: merely adding an exception for unity was not enough.
I spend most of my time on the macs these days since I’m just plain tired of windows trying it’s best to cause a problem. Luckily both operating systems are fairly unobtrusive and I quickly forget I’m using a pc or mac on either when buried deep inside unity.
I never removed it.
What I would recommend instead is set it to protect important services only instead of protecting it all with exceptions. That way you will never have problems with any form of normal program
Reasons is that if you use exceptions with a tool like unity you will add 5 exceptions at least: Unity.exe, Mono.exe, beast process, umbra pvs process and potentially a model format converter
Thats more than just pain and often gives you ugly phantom errors
Not had any noticeable problems crashing with 3.4 other than the usual strained memory finally causing a weakened Unity to give up.
I ran Unity once using the Run As Administrator and not had problems (win 7 64 bit).
Hehe no, its related to http://feedback.unity3d.com/forums/15792-unity/suggestions/1096957-platforms-64-bit-unity and was an avatar created by someone else. I decided to pick it up cause that feature suggestion is the one of highest priority to me and the projects I’ve been working on since early 2010 due to umbra - beast memory problems and “laughable restrictions”
I’m also having problems with Unity 3.4 on Windows 7 (64-bit). It crashes a whole lot more than 3.2 which was the last version I used. Actually, I can’t remember the older versions crashing like this a single time.
3.4 crashes randomly when I move assets, open scripts, change values, drag windows, when I do anything at all more or less. It crashes about once a day. It doesn’t exit silently though, I get a runtime exception every time.
Tonight I reset my DEP settings to their default (DEP on for essential Windows programs and services only) and my random crashes stopped completely.
I had changed those settings a long time ago with previous versions of Unity and had never reverted those changes. Anyway thus far tonight, no crashes. I’ll keep these settings for the next few days and see if this makes my Windows 7 - 64bit crashes go away.
