Back when I first installed Windows 7 x64 on my Dell Core 2 Duo laptop, I also installed Avast Home antivirus. As I found out yesterday, Avast false flagged TrustedInstaller.exe, in the C:\Windows\Servicing folder, as a malicious file, and deleted it. Up until trying to install the Service Pack 1 update, I hadn't noticed this file was missing. The SP1 update wouldn't show up in Windows Updates, so I downloaded the manual update and tried it. It would always error out with a Missing File Error. I tried to run SFC /SCANNOW and it errored out also. SFC also depends on the TrustedInstaller.exe service to run. Luckily my HP Core i5 laptop also running Windows 7 x64 still had it's TrustedInstaller.exe file, so I copied it over to the Dell, ran Windows Updates, and had 30 critical updates that had never installed. I installed all the criticals, then SP1, and everything is running fine again.
-
Old addage shut off Virus scanner before operating system updates seems to fit nicely here.
Cheers
3Fees -
Avast deleted the TrustedInstaller.exe file a while back, not yesterday when I tried to install SP1. I stopped using Avast about 6 months ago. If you are having similar issues, the easiest way to do is to check your C:\Windows\Servicing folder to see if this file is present. If not, then that's your issue.
-
Interesting WackyT, thanks for sharing.
Kind of reminiscent of the svchost deletion by McAfee last summer. Wonder why more people are not reporting this trustedinstaller issue. Surely there are a lot of avast users downloading sp1 -
this is really nasty
Michael -
One question...what version of avast were you using?
In possible fairness to Avast, version 6 just came out of beta yesterday.
Clearly, you were using an earlier version of Avast--was it the beta, or was it version 5? And what caused the deletion? A virus definition update or heuristic detection? -
It was the standard Avast Home free edition, not the beta. I tend to shy away from pre-release versions of software. I think it was the version 5.
Doing a Google search on this, it looks like this happened in both versions 4 (2008) & 5 (2010). -
That's why my AV of choice is MSE, zero conflicts.
-
That's what I'm also using now, hatcher.
-
-
Ahbeyvuhgehduh Lost in contemplation....
I would presume (hope?) that MSE would be designed to be as compatible as possible with MS installers ... I didn't have any problems with installing Win 7 SP1 on any of our machines, even with the anti virus app running. (We use F-Secure.)
-
My 3 personal Win 7 systems, 2 x64 & 1 x86, all running MSE, updated fine with SP1 with MSE running. My work laptop running Win 7 x86 & Symantec Endpoint Protection updated with SP1 fine with SEP running. The only issue I had was that missing file on my Dell laptop, and once replaced, updated fine.
My "Adventure" Installing Windows 7 Service Pack 1
Discussion in 'Windows OS and Software' started by WackyT, Feb 26, 2011.