WSUS is breaking my desktop

[Tripredacus]

A couple of weeks ago, my company implemented a WSUS to send along Windows Updates to all the employee workstations. My computer is one of those rare "false-positive" rogue computers that exists on the domain. By that I mean that I do not log into the domain every day (log in locally), although my domain account has the appropriate rights to join the computer to the domain (which it is). I do not use the Exchange Server (because I use Thunderbird) and have to manually log into the firewall every morning to get out. Prior to this computer being on the domain, it was not even on that network. Instead it used to bridge it and the production network. And this reason was that I not only needed internet access, but this PC also used to be a Domain Controller, WDS and WSUS server for testing. That was a long time ago. I have unpromoted this PC, unauthorized it in DHCP and WDS, and had uninstalled WSUS.

The problems seem to stem from the fact that WSUS used to be installed on the computer at one point, and the uninstaller did not remove everything. Our first clue that this was happening was when Updates tried to install a patch for WSUS and it failed. The fact that it did try to install the update means that my computer must still have some WSUS related files on it. I had confirmed that there was no service listed. I had run a tool to do a manual remove (ie a cleaner) on WSUS and it seems to be totally gone now. The only issue is I am still getting errors and some updates fail to install. I am also getting the "At least one service failed to load at startup" message on a reboot.

Prior to the corporate WSUS being used, there were no problems with this computer. For those interested, it is Windows Server 2003 Standard x32. Let me start with the Event Viewer, starting with last nights reboot until login.

Source: MSSQL$MICROSOFT##SSEE

Event ID: 17049

Description: Unable to cycle error log file from 'c:\WINDOWS\SYSMSI\SSEE\MSSQL.2005\MSSQL\LOG\ERRORLOG.5' to 'c:\WINDOWS\SYSMSI\SSEE\MSSQL.2005\MSSQL\LOG\ERRORLOG.6' due to OS error '5(Access is denied.)'. A process outside of SQL Server may be preventing SQL Server from reading the files. As a result, errorlog entries may be lost and it may not be possible to view some SQL Server errorlogs. Make sure no other processes have locked the file with write-only access."

The above also occurs to change 0 to 1, 1 to 2, 3 to 4, 4 to 5.

Source: MSSQL$MICROSOFT##SSEE

Event ID: 17207

Description: FCB::Open: Operating system error 5(Access is denied.) occurred while creating or opening file 'c:\WINDOWS\SYSMSI\SSEE\MSSQL.2005\MSSQL\DATA\master.mdf'. Diagnose and correct the operating system error, and retry the operation.

The above also occurs with mastlog.ldf.

Source: MSSQL$MICROSOFT##SSEE

Event ID: 17204

Description: FCB::Open failed: Could not open file c:\WINDOWS\SYSMSI\SSEE\MSSQL.2005\MSSQL\DATA\master.mdf for file number 1. OS error: 5(Access is denied.).

The above also occurs with mastlog.ldf. I am also getting what appears to be a Group Policy or Logon Script error from the domain regarding the inability to update the DST via a CMD. I will not be posting that for obvious reasons. The next one is an update that fails:

Source: MsiInstaller

Event ID: 10005

Description: Product: Windows Internal Database -- Error 29528. The setup has encountered an unexpected error while Setting Internal Properties. The error is: Fatal error during installation.

The following appear in the system log:

Source: Windows Update Agent

Event ID: 20

Description: Installation Failure: Windows failed to install the following update with error 0x80070643: Security Update for Windows Server 2003 and Windows Server 2008 (KB948109).

Source: DCOM

Event ID: 10005

Description: DCOM got error "The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. " attempting to start the service NMIndexingService with arguments "" in order to run the server:

{C6A811AB-F8FF-45A4-93E5-FC5CCB650BE7}

If anyone has any ideas on these specific errors, let me know. There were no warnings listed and all Infos seemed to be ok.