Simon May

Client and cloud

WSUS Service fails to start with error 193, WSUS Service is not a valid Win32 application

WSUS Service fails to start with error 193, WSUS Service is not a valid Win32 application

  • Comments 7
  • Likes

As I continue to build my System Center Configuration Manager 2012 (CM12) lab I continue to shoot myself in the foot in a number of ways.  Over the weekend I discovered that my WSUS service was unable to start and was logging “WSUS Service is not a valid Win32 application” in the event log.

After some digging around I found this great post by David Obrien (and great Config Manager blog by the way) that points to the issue:

Essentially a file had been created called c:\program and it was stopping the service from starting and renaming it worked a charm.  I’ll have to dig around a little more to work out what really happened here down the line. But thanks David!

  • Hi Simon,

    thanks for mentioning my blog and I'm glad I could be of help!

    Best regards,


  • Thanks Simon

    This post really helped, was struggling with this one.

    I know what you mean about SCCM 2012, this is my first experience with any version of config manager and it seems everything I try takes a lot of research to why it isn't working.


  • Great catch... I had the error too :(

  • Thanks for the article it solved my issue...getting frustrated without the amount of time spent bug fixing SCCM 2012 now though (SP1 or not) :(

  • Awesome job guys, I just had this issue and you saved me hours of research!

  • Thanks Simon,

    Was just about to start pulling my hair out over this one until I found this file on the C: drive.

    All working again


  • I had this happen in a lab box I had just upgraded to Win 2012 Server R2. Looks like a log file - probably the process that created it got the file name truncated.

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment