|
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:
Thanks for the tips, but none of these suggestions have helped yet. I've tried:
If you have other suggestions, please post them! I've tried the first two given, but I haven't fixed this yet.
(comments are locked)
|
|
FINALLY figured out the solution: had to create a DEP exception for Unity. Runs without a hitch now! I'm having the same problem. How do you create a DEP exception for Unity?
Aug 24 '11 at 08:49 PM
joycecIL
I would really like to know as well. How did you do this?
Oct 12 '11 at 01:13 AM
sabliao
As Microsoft Says:
Feb 20 '12 at 01:08 AM
CC Inc
Thank you so much, the program runs for me now!
Jul 24 '12 at 07:36 PM
mahari
Sure thing, glad I could help!
Jul 25 '12 at 01:38 AM
CC Inc
(comments are locked)
|
|
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.
Mar 14 '10 at 09:05 PM
Jen Grier
(comments are locked)
|
|
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.
Mar 14 '10 at 09:06 PM
Jen Grier
(comments are locked)
|
|
my DEP is protecting OS services only and i have this problem, is there something i missed here
(comments are locked)
|
|
you can isolate the scene that has the problem, in my case, i have to do, and i found a Particule Animator in one of my objects, so I remove it and everything run fine. Make backup of the problematic scene and delete one by one of objects that have particule animator.
(comments are locked)
|
1 2 next page »

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.