- Home /
Getting the Unity Editor to Work in Windows 7 64-Bit
Unfortunately, I've just done the install of the Unity Editor on Windows 7 64-bit and can't get it to open. I've tried running it "as an Administrator" and in multiple compatibility modes, including XP and Vista options. No dice! Any help is appreciated.
I get this error:
Problem signature:
Problem Event Name: APPCRASH
Application Name: Unity.exe
Application Version: 2.6.1.31223
Application Timestamp: 4b13e3a0
Fault Module Name: KERNELBASE.dll
Fault Module Version: 6.1.7600.16385
Fault Module Timestamp: 4a5bdbdf
Exception Code: e06d7363
Exception Offset: 0000b727
OS Version: 6.1.7600.2.0.0.256.48
Locale ID: 1033
Additional Information 1: 236e
Additional Information 2: 236e213616a19c43b9b4f484bab02c9e
Additional Information 3: f0fb
Additional Information 4: f0fb81261199e5edc1200c7838f5a558
Thanks for the tips, but none of these suggestions have helped yet. I've tried:
- Disabling antivirus (Panda Cloud AV)
- Multiple NVidia drivers
- Installing in a new user profile
- Making sure all Windows updates (optional as well) are installed, especially display drivers
- I reinstalled IE8 through the Programs-Features>Add/Remove Windows Services, then reinstalled Unity. Rather than crashing, Unity seems to start, then silently refuse to boot. Period. No APPCRASH, but also no Editor! Jen Grier 15 hours ago [delete this comment]
- As a temporary workaround, I've tried running Unity on Virtual PC and VirtualBox with Windows XP installs, but VPC doesn't have 3D acceleration support (blasted!). VirtualBox DOES get Unity to open, but the windows/panels appear in flashing colors. I can navigate around the Island demo project, but it's not a workable scenario.
If you have other suggestions, please post them! I've tried the first two given, but I haven't fixed this yet.
You didn't need to mark this as Community Wiki, and you could accept your own answer.
Sorry - just got the hang of it and have marked it. Thanks.
Answer by Jen Grier · Mar 15, 2010 at 05:28 PM
FINALLY figured out the solution: had to create a DEP exception for Unity. Runs without a hitch now!
FINALLY figured out the solution: had to create a DEP exception for Unity. Runs without a hitch now!
Thanks! Solved my problem too!
my DEP is protecting OS services only and i have this problem, is there something i missed here
I'm having the same problem. How do you create a DEP exception for Unity?
I would really like to know as well. How did you do this?
Answer by qJake · Mar 13, 2010 at 09:54 PM
I've been running Unity 2.6.x under Windows 7 64-bit for quite some time now with no problems.
My best guess would be that this is a problem specific to your particular setup. Sometimes bad or out-of-date drivers can cause these kinds of errors, or sometimes it's another program installed that conflicts with Unity (absurd as it sounds, I know).
The best advice I can give you is to update all your drivers (and make sure you aren't running any beta drivers). You could even try running Unity under a different account in Windows, and with no other programs running in the background.
Thanks for the answer - I'm glad to hear that this isn't inherent to Windows 7! I am fully up-to-date on drivers and have no beta drivers, but I will definitely try doing the install in a clean account to see if there is a conflict.
Answer by karl_ · Mar 13, 2010 at 10:18 PM
You could also try checking Windows Update for any new compatibility fixes, as most of the time they are marked as optional and might not install automatically.
However, as said earlier Drivers are typically the reason programs do not run properly. You may even try using an earlier version of a Driver. Occasionally the most up to date Driver will break programs that ran well under a previous version. This has been the case for me a number of times with ATI's updates.
Thanks for the tip! Yes, I'm up-to-date with all NVidia graphics drivers, so this could definitely be the culprit. I'll post back here if it is related.
Answer by Dreamora · Sep 28, 2010 at 04:32 AM
as developer its normally in your best interest to set DEP to what it should be outside a restricted environment anyway: set it to protect os services instead of having it running in paranoia mode.
This recommendation is one I give cause you will find out that there are applications that will malfunction and finding the issue then, get it into relation of DEP can be near impossible as you forgot about DEPs dark sides by then.
Answer by jhessler · Jun 10, 2011 at 12:26 AM
DEP Exception worked for me as well, Thanks. Windows 7 home premium 64bit, HP laptop