Unity3d won't open anymore

I’ve been working with Unity3d for the past 9 months, since 3.4.0 version.
It was working, i had to stop during 2 months.
Yesterday i had the opportunity to work with it again, when suddenly i try to use Untiy3d.exe and i don’t know why it didn’t open at all.
A little “loading circle” appears by the cursor but it goes away after 1 second.
I checked “Task Manager” same thing happens a “Unity3d” process appears but it soon goes away and when i put to lead me to the “service” it just doesn’t lead me and the process closes…
I tried to uninstall and re-install Unity3d, maybe i was using an old version i don’t know it can happen…
I had to opportunity to download 3.5.2 latest version, but still it didn’t work, doesn’t even open.
Is there any way to find out what is happening with the program?
Has someone already had this problem and with did you do to make it work?
Is there a compatibility problem going on?
Some extra information: I am using Windows 7…
If someone could help me i would be more then thankful.

OnFight

I had a similar problem (except that the process didn’t go away). Turns out the reason was that I had plugged in an XBox controller. Plugged it out and it worked again.

Thought this might help someone.

Try to put the compatibility mode on like windows XP, and run as administrator. That’s all I can come up with. I’m using windows 7 and it’s working fine.

This is a stupid question…but I’m going to ask anyway: Did you restart you computer?

I am using compatibility WIndows XP (Service Pack 3).
And yes i did restart my computer.
Still does the same thing, little “loading circle” by the cursor.
I can even make a video and upload it to youtube if you want to check it out.

OnFight

Hey, I had the same problem as you. Spent hours searching up online and finally was pointed to this which worked :

I had to remove the USB cable that connected my U2713h monitor to the computer. I guess it was because of the SD Card reader but don’t exactly now the real reason. Maybe it created an unreadable drive and the developers didn’t take care of some timeout to abort read trials. :frowning: Seems to be a lame mistake.

Getting this at the moment with 5.3.5, it appears to be caused by AVG Anti-Virus as Unity will only boot if I temporarily turn this off and then boot.
It also works if I reboot my machine and then immediately open Unity, presumably before AVG gets chance to prevent it opening.

I just had the issue with 2017.1.1f1 and running unity.exe “as administrator” fixed it