If I manually stop the Windows Update service, I can install the RSAT (it's installing now). I guess I will try manually installing the latest cumulative update the same way, after I manage to update PowerShell.
On Thu, Dec 29, 2016 at 2:54 PM, Michael Leone <[email protected]> wrote: > This is weird. My work PC got corrupted, and I got a new hard drive of > our WIn 7 SP1 image. And I'm trying to install RSAT on it, and it seems to > just be hanging on "Searching for updates on this computer". Looking into > WindowsUpdate.log I see this: > > > 7756 1dcc Misc =========== Logging initialized (build: 7.6.7600.320, tz: > -0500) =========== > 7756 1dcc Misc = Process: C:\Windows\system32\wusa.exe > 7756 1dcc Misc = Module: C:\Windows\system32\wuapi.dll > 7756 1dcc COMAPI ----------- COMAPI: > IUpdateServiceManager::AddScanPackageService > ----------- > 7756 1dcc COMAPI - ServiceName = Windows Update Standalone Installer > 7756 1dcc COMAPI - ScanFileLocation = C:\5801e7aa26267eca7c\wsusscan.cab > 1152 a74 Misc Validating signature for C:\Windows\ > SoftwareDistribution\ScanFile\f9550e7e-d05e-4ef0-9643-29723ef36353\Source.cab > with dwProvFlags 0x00000080: > 1152 a74 Misc Microsoft signed: Yes > 1152 a74 DtaStor Default service for AU is {7971F918-A847-4430-9279- > 4A52D1EFE18D} > 7756 1dcc COMAPI - Added scan package service, ServiceID = > {F9550E7E-D05E-4EF0-9643-29723EF36353} Third party service > 7756 1dcc COMAPI ------------- > 7756 1dcc COMAPI -- START -- COMAPI: Search [ClientId = wusa] > 7756 1dcc COMAPI --------- > 7756 1dcc COMAPI <<-- SUBMITTED -- COMAPI: Search [ClientId = wusa] > > And now it's just sitting there. > > I see nothing in the Event log. > > Any ideas? The image shows last Windows Update was April 2015 (don't say > anything, I have nothing to do with workstation imaging). I did install the > April 2015 Servicing Stack Update, and updated from IE10 to IE11 > (successfully). > > Ideas? I'll be off for the New Year's holiday, so I won't be able to > really do anything about it for a few days, but any ideas for when I get > back? > > (saw the same issue when I tried to update my Powershell v2; just sat > there at "searching for updates"). > > Thanks > >
