The main reason behind this issue is due to name of this file. You could also delete the file if it’s not required. The next step is to rename the file from program to something else. There was no information about who created the file. I have no idea why this file was created on the C: drive. Opening the file with notepad++ revealed that this file logged information about the client agent setup. In addition checking the C: drive on the server showed up a rogue file called Program. So something was blocking the service from starting. There is nothing much you can understand from the given error. WSUS service is not a valid Win32 application. The error was The WSUS Service service failed to start due to the following error. In the event viewer, under log name System i found the event ID 7000. The next step was to get into event viewer and look for right event. Nothing much can be understood from the error. So upon starting the WSUS service from services console, I saw the below error. Windows could not start WSUS service on local computer Error 193 There were errors logged in wsyncmgr.log and wsusctrl.log files. I also noticed that the under Monitoring, SUP component status was critical. The error was Windows could not start WSUS service on local computer Error 193. On my SCCM server the WSUS service failed to start. While things were working fine, I got an error related to WSUS service. Recently I installed cumulative update 4 on SCCM 2012 R2 SP1.

Error oxc1