Vista SP1: Windows Process Activation Service fails

After installing Vista SP1 on 64 bit Vista Enterprise the World Wide Web
Publishing service failed to start because a required service (the Windows
Process Activation Service) could not be started. When I attempted to start
that service I received the error: "Error 1168: Element not found".
Uninstalling and reinstalling the WPAS service did not fix the error. When I
uninstalled SP1, the service was able to start successfully and I can use IIS
again.

Any ideas? Thanks.

http://support.microsoft.com/oas/def...4&gprid=500921

> Free unlimited installation and compatibility support is available for Windows Vista, but only for
> Service Pack 1 (SP1). This support for SP1 is valid until March 18, 2009. Chat and e-mail support is
> available only in the United States and Canada.

Free phone support is offered, too.

MowGreen [MVP 2003-2008]
===============
*-343-* FDNY
Never Forgotten
===============


JoeD wrote:

> After installing Vista SP1 on 64 bit Vista Enterprise the World Wide Web
> Publishing service failed to start because a required service (the Windows
> Process Activation Service) could not be started. When I attempted to start
> that service I received the error: "Error 1168: Element not found".
> Uninstalling and reinstalling the WPAS service did not fix the error. When I
> uninstalled SP1, the service was able to start successfully and I can use IIS
> again.
>
> Any ideas? Thanks.

I have the very same problem that the first "Joe" has, except that I am working on Windows Vista Ultimate 32-bit. When I try to start the Windows Process Activation Service, I get error 1168. The verbiage is "Error 1168: Element not found."

Anybody have any ideas?

<Joe Sater> wrote in message
news:...
>I have the very same problem that the first "Joe" has, except that I am working on Windows Vista Ultimate 32-bit. When I try to
>start the Windows Process Activation Service, I get error 1168. The verbiage is "Error 1168: Element not found."
>
> Anybody have any ideas?


Search the diagnostics logs the update always creates or writes to
for context for that error code.


---