Gamemaker:Studio is broken, again

[RandomFangamer]

HeyGuys, 
So, for the past week I have been unable to open Gamemaker:Studio and I have no idea why
When ever I open the application it takes a very long time (about 1-2 minutes) and then pops up a box with the message "Gamemaker:Studio has stopped working"
I have un-installed  and re-installed it multiple times yet it keeps giving me this message
Does anyone have any idea what could be causing this?
Thanks,
Random Fangamer
btw, I am currently using Windows 10, could this be causing this bug?

[Habluka]

Reverting the most recent windows update should fix it.

[pieceofcheese87]

Klazen told me they were having issues downloading a flash object from their homepage recently. I think if you disconnect from the internet and then reconnect after opening studio you should be able to use it again.

[RandomFangamer]

Thanks Piece, I would have never thought that was the problem.
I actually thought I did something, and was wondering why reinstalling Studio didn't work

EDIT:

I have another problem
When ever I try to play my game, this error pops up:

[patrickgh3]

1. If you edit your post, people that browse the most recent posts are probably not going to see it. Consider making a separate post instead if you have important information to add.

2. The error message says "Please check the Compile window for any additional information." Obviously, you should do that, and if you still need help, post a screenshot of that too. Always thoroughly read your error messages before asking for help. If you don't, then people will think you're not putting in any effort yourself and won't want to help you.

Cheers!

[RandomFangamer]

Thanks patrickgh3, the compile window showed me the problem
Apparently when I was coding a custom trigger, I wrote instance_create with out the parenthesis and as the compile error form only checks for incomplete parenthesis and incorrect recourse names, it didn't find a problem.
After having the previous error I guess I just assumed it was Gamemaker:Studio's fault
Thanks again!