AU found no suitable session to launch client in.

On a company network where none of the users are administrators of
their local pc, I've started to get the "AU found no suitable session
to launch client in." (ever since I removed admin rights) and WSUS(3)
shows the computer with errors. In one particular case I have 11
failed to install - every single one of them are office patches
(although other office patches have installed. -
920103,919029,923097,925251,942571,940602,914455,9 34180,936048,924085,934181

If I log on as an administrator I am offered the patches and I can
then install them. However that defeats the point of an enterprise
patching system if I have to log into the pc's individually. Giving
users admin rights is not an option and shouldn't be necessary either.

As an example, the 934180 is installed on 36 machines, but failed on 5
- the same 5 machines that have failed on each of the patches.
What am I missing to get this working?

I have the log file if required (just todays entries were 64k so I
didn't want to post here)

Andy Helsby wrote:
> On a company network where none of the users are administrators of
> their local pc, I've started to get the "AU found no suitable
> session to launch client in." (ever since I removed admin rights)
> and WSUS(3) shows the computer with errors. In one particular case
> I have 11 failed to install - every single one of them are office
> patches (although other office patches have installed. -
> 920103,919029,923097,925251,942571,940602,914455,9 34180,936048,924085,934181
>
> If I log on as an administrator I am offered the patches and I can
> then install them. However that defeats the point of an enterprise
> patching system if I have to log into the pc's individually. Giving
> users admin rights is not an option and shouldn't be necessary
> either.
>
> As an example, the 934180 is installed on 36 machines, but failed
> on 5 - the same 5 machines that have failed on each of the patches.
> What am I missing to get this working?
>
> I have the log file if required (just todays entries were 64k so I
> didn't want to post here)

In some cases, but not all, this can be due to group policy not being
configured properly or a corruption of the wuaueng.dll file/registration of
said file.

Try these commands on the machine:
regsvr32 /u wuaueng.dll
regsvr32 wuaueng.dll

Reboot - try again.

If that doesn't work - go a bit more to the extreme:

These commands...
net stop wuauserv
regsvr32 /u wuaueng.dll

Then delete the folder c:\windows\softwaredistibution and delete
c:\windows\windowsupdate.log (or move it.)

Then these commands...
regsvr32 wuaueng.dll
net start wuauserv
wuauclt.exe /resetauthorization /detectnow

Let us know!

--
Shenan Stanley
MS-MVP
--
How To Ask Questions The Smart Way
http://www.catb.org/~esr/faqs/smart-questions.html