Ok, so I figured this out sorta. There's actually a dependency tab on each service if you view the properties of it (damned helpful that is, heh). Anyway, it relies on two services I didn't have enabled, I attempted to enable those, they had a dependency, so I then looked at those and figured it out.
Basically, I had disabled a service called HTTP a month ago, because I wanted to run Apache on this system for some development work and I wanted to use port 80 by default. This service, HTTP, uses port 80 and wouldn't let Apache run on it then. So, I disabled it. That fixed that problem.
Unfortunately, this means I only have a few options, none of which I like.
- Develop on something other than port 80 (really fun typing in a port number on every request...) and turn the service back on.
- Leave it off and don't use the homegroup stuff (sucks, but I can deal with it).
Anyway, just lame of MS to make a service dependent on port 80 being open, when many people use port 80 themselves...
