Windows Process Activation Service Could Not Be Started

I began today by starting a different post about publishing an app to localhost. Things soon went sideways. That post will have to wait while I peel back this onion:

Localhost can't be reached

When I open up IIS, I can see that the Default Site and the DefaultAppPool are stopped. No problem, let’s start them.

App Pools Cannot Be Started

You knew it wasn’t going to be that simple, right? From an admin command prompt:

Now, WAS and IIS are both installed, so I follow the recommendation from iis.net to go ahead and reinstall them, but save yourself the restart. That didn’t do it.

Windows FeaturesI’m not eager to Regedit based on a StackOverflow answer, but it’s simply removing a file and Scott Hanselman’s foray into PerfMon lead me to several errors, but they did not get me closer to a resolution. I’ve reinstalled WAS once, so I deleted NanoSetup.

WAS Parameters

Now the App Pool can be started, but we’re missing one last step to turn on the DefaultSite.

Manage Website Start

W3SVC Is Stopped

One more Admin Command Prompt later and we’re there.

Now, we can navigate to localhost in the browser.

Welcome IIS