I just switched to visual studio professional from express (thank you ISIC). Anyway, i keep getting this error when i run my project. Google said that i should enable the Application Experience service, except windows 8 gives me this error when i try to do that:

Same problem. Works at first but when i change something and recompile, i get the same error.

Edit: So i just restarted the laptop and the problem went away (why didn't i do that before i don't know). Which is weird since no related processes were open in the task manager.

Same problem. Works at first but when i change something and recompile, i get the same err

As BitMaster pointed out, this error is usually caused from the application running. The reason it is still happening after a recompile is because something is wrong with your code. Is this a Win32 project? If so, when you run it under a debugger and close the window with the "x" button, does the debugger release? If no, how is your window class created? How does your message proc look?

This tends to happen a lot with Win32 code.

I rather doubt it's a win32 problem since i've been working on this project for 3 months and the problem just appeared. (All i changed was the speed of the player lol)

Well, you can either check to see if this is what's causing the problem and let us know, or we can keep telling you the same thing.

I rather doubt it's a win32 problem since i've been working on this project for 3 months and the problem just appeared. (All i changed was the speed of the player lol)

Regardless of what has happened, the cause is usually the same. Your program is staying in an endless loop and is preventing the release of the program by the operating system upon exit. I don't know why it just started happing, however, I can take a few wild guesses depending on what language you are using. For example, one cause I have witnessed in beginner Win32 code done in C is when a game system (player stats in your case) is implemented using pointers. The pointer is initialized somewhere, the pointer is *usually* deleted somewhere. However, somewhere in program execution, the pointer gets reassigned to an object like the window handle. In this scenario, if you reassigned the pointer to the window handle, you will delete the window handle, the Win32 API does not get the chance to delete the handle and release it, and you are stuck in the endless loop RobTheBloke described. This, of course, is one of many, many reasons that causes this, but they usually always relate to an endless loop.