Solved TrustedInstaller.exe -> system32/config/COMPONENTS

[cerpintaxt]

Hi,

I have a problem with a computer running Windows 7 Pro 64bit. A couple of seconds after windows has booted the process "TrustedInstaller.exe" is started and accessing the file "c:/Windows/system32/config/COMPONENTES" continously. While the task manager shows no cpu usage of said process the resource monitor does show disk activity (screenshot attached). The disk activity comes along with a regular "klack" noise of the harddisk (every 2-3 seconds). This behaviour goes on and on with only short breaks of disk activity and the "klack" noise. The system does work but responds pretty laggy.
I noticed the issue yesterday after I inserted an additional harddisk into the pc. I had to remove all harddrives for space reasons and put them back in (1 system drive, 4 additional drives). I have disconnected all additional drives from the power supply for now but the problem remains. It is possible that the system installed updates while shutting down before I removed all the drives. Maybe something got corrupted during the first boot up with the additional drive?

Any help or ideas are appreciated, thanks in advance.

Jan

 

[paul1149]

One possibility is that Windows sometimes uses the first empty partition to store update "temporary" installation files. Perhaps it did so, and looked for them after the reboot, only to find the partition letter switched to the new drive. You might try installing the drives as they were, or at least searching them to look for folders with GUID labels at the partition root that have the date of this problem. Or simply do a System Restore that predates the problem.

 

[cerpintaxt]

Thanks for your answer, Paul. I didn't find any temporary update files and unfortunately windows could not do a system restore due to some error message that it could not extract some files from the archive.
In the end I tried a scheduled disk check with both options checked and it looks like this has fixed the problem for now. Fingers crossed.

 

[paul1149]

Interesting, cerpintaxt. I should have caught that. In that case I would back up all data and test the drive using the utility from its maker. Or with a program such as gsmartcontrol, check the Attributes and then run the long generic test.