Client Self Update has stopped working

Hello, I have a WSUS server that was working great up until a power outage
last week. Since then any new clients pointed to the WSUS server won't
receive the client update software correctly (existing clients still receive
windows updates and communicate no problem). These are all brand new XP SP2
installs so the wuaueng.dll file passes the client diag. They will show up
in the WSUS console but never change state from 'Not Yet Reported'.

If I manually install WindowsUpdateAgent20-x86.exe /wuforce on the clients
and then run wuauclt /detectnow updates will pop immediately and all is fine
after that.
Any ideas on how to get the client self update working again?
--
Chris
Rochester, NY

Chris,

How long have the XPSP2 machine been reporting as "Not Yet Reported" Has it
been more than a full detection cycle?
--
This posting is provided "AS IS" with no warranties, and confers no rights.


"Chris" wrote:

> Hello, I have a WSUS server that was working great up until a power outage
> last week. Since then any new clients pointed to the WSUS server won't
> receive the client update software correctly (existing clients still receive
> windows updates and communicate no problem). These are all brand new XP SP2
> installs so the wuaueng.dll file passes the client diag. They will show up
> in the WSUS console but never change state from 'Not Yet Reported'.
>
> If I manually install WindowsUpdateAgent20-x86.exe /wuforce on the clients
> and then run wuauclt /detectnow updates will pop immediately and all is fine
> after that.
> Any ideas on how to get the client self update working again?
> --
> Chris
> Rochester, NY

Hi Cecil, I believe so but I will put a new build together today and let it
sit for the weekend to confirm.
--
Chris
Rochester, NY


"Cecil (MSFT)" wrote:

> Chris,
>
> How long have the XPSP2 machine been reporting as "Not Yet Reported" Has it
> been more than a full detection cycle?
> --
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
>
> "Chris" wrote:
>
> > Hello, I have a WSUS server that was working great up until a power outage
> > last week. Since then any new clients pointed to the WSUS server won't
> > receive the client update software correctly (existing clients still receive
> > windows updates and communicate no problem). These are all brand new XP SP2
> > installs so the wuaueng.dll file passes the client diag. They will show up
> > in the WSUS console but never change state from 'Not Yet Reported'.
> >
> > If I manually install WindowsUpdateAgent20-x86.exe /wuforce on the clients
> > and then run wuauclt /detectnow updates will pop immediately and all is fine
> > after that.
> > Any ideas on how to get the client self update working again?
> > --
> > Chris
> > Rochester, NY

Well, I setup a PC Friday afternoon and it is still showing up as 'Not Yet
Reported' in the WSUS console. Looking through the Windows update log I am
seeing some errors.

Some snippets include

selfupdate Failure software synchronization Error: Agent failed detecting
with reason 0x80072efd

Automaticupdates Failure software synchronization Error: Agent failed
detecting with reason 0x80248008

Failed to obtain cached cookie with hr = 80248008
Failed to upload events with hr = 80248008
--
Chris
Rochester, NY


"Cecil (MSFT)" wrote:

> Chris,
>
> How long have the XPSP2 machine been reporting as "Not Yet Reported" Has it
> been more than a full detection cycle?
> --
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
>
> "Chris" wrote:
>
> > Hello, I have a WSUS server that was working great up until a power outage
> > last week. Since then any new clients pointed to the WSUS server won't
> > receive the client update software correctly (existing clients still receive
> > windows updates and communicate no problem). These are all brand new XP SP2
> > installs so the wuaueng.dll file passes the client diag. They will show up
> > in the WSUS console but never change state from 'Not Yet Reported'.
> >
> > If I manually install WindowsUpdateAgent20-x86.exe /wuforce on the clients
> > and then run wuauclt /detectnow updates will pop immediately and all is fine
> > after that.
> > Any ideas on how to get the client self update working again?
> > --
> > Chris
> > Rochester, NY

The 0x80072efd error points to an infrastructure failure. Either a
misconfigured proxy client, a misconfigured proxy server, a nonexistent
proxy server for a configured proxy client, a nonconfigured proxy client
being routed to a proxy server, a misconfigured firewall, dysfunctional DNS,
or a routing table error.

Essentially 0x80072efd is what the client logs when it does not get a
response back from the web server. Ergo, the WSUS server is not receiving
the client's detection request.

"Chris" <Chris@discussions.microsoft.com> wrote in message
news:FF9B299C-E78E-4EA6-88FD-6CD6A57A7AF9@microsoft.com...
> Well, I setup a PC Friday afternoon and it is still showing up as 'Not Yet
> Reported' in the WSUS console. Looking through the Windows update log I
> am
> seeing some errors.
>
> Some snippets include
>
> selfupdate Failure software synchronization Error: Agent failed detecting
> with reason 0x80072efd
>
> Automaticupdates Failure software synchronization Error: Agent failed
> detecting with reason 0x80248008
>
> Failed to obtain cached cookie with hr = 80248008
> Failed to upload events with hr = 80248008
> --
> Chris
> Rochester, NY
>
>
> "Cecil (MSFT)" wrote:
>
>> Chris,
>>
>> How long have the XPSP2 machine been reporting as "Not Yet Reported" Has
>> it
>> been more than a full detection cycle?
>> --
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>>
>>
>> "Chris" wrote:
>>
>> > Hello, I have a WSUS server that was working great up until a power
>> > outage
>> > last week. Since then any new clients pointed to the WSUS server won't
>> > receive the client update software correctly (existing clients still
>> > receive
>> > windows updates and communicate no problem). These are all brand new
>> > XP SP2
>> > installs so the wuaueng.dll file passes the client diag. They will
>> > show up
>> > in the WSUS console but never change state from 'Not Yet Reported'.
>> >
>> > If I manually install WindowsUpdateAgent20-x86.exe /wuforce on the
>> > clients
>> > and then run wuauclt /detectnow updates will pop immediately and all is
>> > fine
>> > after that.
>> > Any ideas on how to get the client self update working again?
>> > --
>> > Chris
>> > Rochester, NY

Well, we do have a proxy server configured for Internet Access on the client
but I have an exception in the list for our local domain where the WSUS
server resides.
Perhaps I don't understand the whole process but going back to my original
post if I
manually install WindowsUpdateAgent20-x86.exe /wuforce on the client and
then run wuauclt detectnow updates will pop immediately and all is fine
(client updates and reports back to WSUS) so why all of a sudden if I
manually install the self update client does everything work?



--
Chris
Rochester, NY


"Lawrence Garvin (MVP)" wrote:

> The 0x80072efd error points to an infrastructure failure. Either a
> misconfigured proxy client, a misconfigured proxy server, a nonexistent
> proxy server for a configured proxy client, a nonconfigured proxy client
> being routed to a proxy server, a misconfigured firewall, dysfunctional DNS,
> or a routing table error.
>
> Essentially 0x80072efd is what the client logs when it does not get a
> response back from the web server. Ergo, the WSUS server is not receiving
> the client's detection request.
>
> "Chris" <Chris@discussions.microsoft.com> wrote in message
> news:FF9B299C-E78E-4EA6-88FD-6CD6A57A7AF9@microsoft.com...
> > Well, I setup a PC Friday afternoon and it is still showing up as 'Not Yet
> > Reported' in the WSUS console. Looking through the Windows update log I
> > am
> > seeing some errors.
> >
> > Some snippets include
> >
> > selfupdate Failure software synchronization Error: Agent failed detecting
> > with reason 0x80072efd
> >
> > Automaticupdates Failure software synchronization Error: Agent failed
> > detecting with reason 0x80248008
> >
> > Failed to obtain cached cookie with hr = 80248008
> > Failed to upload events with hr = 80248008
> > --
> > Chris
> > Rochester, NY
> >
> >
> > "Cecil (MSFT)" wrote:
> >
> >> Chris,
> >>
> >> How long have the XPSP2 machine been reporting as "Not Yet Reported" Has
> >> it
> >> been more than a full detection cycle?
> >> --
> >> This posting is provided "AS IS" with no warranties, and confers no
> >> rights.
> >>
> >>
> >> "Chris" wrote:
> >>
> >> > Hello, I have a WSUS server that was working great up until a power
> >> > outage
> >> > last week. Since then any new clients pointed to the WSUS server won't
> >> > receive the client update software correctly (existing clients still
> >> > receive
> >> > windows updates and communicate no problem). These are all brand new
> >> > XP SP2
> >> > installs so the wuaueng.dll file passes the client diag. They will
> >> > show up
> >> > in the WSUS console but never change state from 'Not Yet Reported'.
> >> >
> >> > If I manually install WindowsUpdateAgent20-x86.exe /wuforce on the
> >> > clients
> >> > and then run wuauclt /detectnow updates will pop immediately and all is
> >> > fine
> >> > after that.
> >> > Any ideas on how to get the client self update working again?
> >> > --
> >> > Chris
> >> > Rochester, NY
>
>
>

Well after many good leads from other posts in this excellent community I was
finally able to hunt down the cause of my woes.

I have the WSUS configured on its own website using port 8530. I now
understand that the legacy clients still need to initially connect to the
WSUS selfupdate site over port 80 (under the default web site) to get the
latest update client to work with WSUS (okay I know this was probably in the
documentation). The default website had been shutdown for perceived security
enhancement thus breaking the required connection for the legacy clients. I
turned the site back on and bingo, back in business.
--
Chris
Rochester, NY


"Lawrence Garvin (MVP)" wrote:

> The 0x80072efd error points to an infrastructure failure. Either a
> misconfigured proxy client, a misconfigured proxy server, a nonexistent
> proxy server for a configured proxy client, a nonconfigured proxy client
> being routed to a proxy server, a misconfigured firewall, dysfunctional DNS,
> or a routing table error.
>
> Essentially 0x80072efd is what the client logs when it does not get a
> response back from the web server. Ergo, the WSUS server is not receiving
> the client's detection request.
>
> "Chris" <Chris@discussions.microsoft.com> wrote in message
> news:FF9B299C-E78E-4EA6-88FD-6CD6A57A7AF9@microsoft.com...
> > Well, I setup a PC Friday afternoon and it is still showing up as 'Not Yet
> > Reported' in the WSUS console. Looking through the Windows update log I
> > am
> > seeing some errors.
> >
> > Some snippets include
> >
> > selfupdate Failure software synchronization Error: Agent failed detecting
> > with reason 0x80072efd
> >
> > Automaticupdates Failure software synchronization Error: Agent failed
> > detecting with reason 0x80248008
> >
> > Failed to obtain cached cookie with hr = 80248008
> > Failed to upload events with hr = 80248008
> > --
> > Chris
> > Rochester, NY
> >
> >
> > "Cecil (MSFT)" wrote:
> >
> >> Chris,
> >>
> >> How long have the XPSP2 machine been reporting as "Not Yet Reported" Has
> >> it
> >> been more than a full detection cycle?
> >> --
> >> This posting is provided "AS IS" with no warranties, and confers no
> >> rights.
> >>
> >>
> >> "Chris" wrote:
> >>
> >> > Hello, I have a WSUS server that was working great up until a power
> >> > outage
> >> > last week. Since then any new clients pointed to the WSUS server won't
> >> > receive the client update software correctly (existing clients still
> >> > receive
> >> > windows updates and communicate no problem). These are all brand new
> >> > XP SP2
> >> > installs so the wuaueng.dll file passes the client diag. They will
> >> > show up
> >> > in the WSUS console but never change state from 'Not Yet Reported'.
> >> >
> >> > If I manually install WindowsUpdateAgent20-x86.exe /wuforce on the
> >> > clients
> >> > and then run wuauclt /detectnow updates will pop immediately and all is
> >> > fine
> >> > after that.
> >> > Any ideas on how to get the client self update working again?
> >> > --
> >> > Chris
> >> > Rochester, NY
>
>
>

Argh.. and the one on the list that I inadvertently left off (this time --
but you'd find listed on the several other similar answers I've provided to
this question), is 'the virtual server is stopped'.

Glad you found it; apologies for not including it in the original response.

"Chris" <Chris@discussions.microsoft.com> wrote in message
news:CDE41D10-9231-48AD-A68F-250BFAB2E41A@microsoft.com...
> Well after many good leads from other posts in this excellent community I
> was
> finally able to hunt down the cause of my woes.
>
> I have the WSUS configured on its own website using port 8530. I now
> understand that the legacy clients still need to initially connect to the
> WSUS selfupdate site over port 80 (under the default web site) to get the
> latest update client to work with WSUS (okay I know this was probably in
> the
> documentation). The default website had been shutdown for perceived
> security
> enhancement thus breaking the required connection for the legacy clients.
> I
> turned the site back on and bingo, back in business.
> --
> Chris
> Rochester, NY
>
>
> "Lawrence Garvin (MVP)" wrote:
>
>> The 0x80072efd error points to an infrastructure failure. Either a
>> misconfigured proxy client, a misconfigured proxy server, a nonexistent
>> proxy server for a configured proxy client, a nonconfigured proxy client
>> being routed to a proxy server, a misconfigured firewall, dysfunctional
>> DNS,
>> or a routing table error.
>>
>> Essentially 0x80072efd is what the client logs when it does not get a
>> response back from the web server. Ergo, the WSUS server is not receiving
>> the client's detection request.
>>
>> "Chris" <Chris@discussions.microsoft.com> wrote in message
>> news:FF9B299C-E78E-4EA6-88FD-6CD6A57A7AF9@microsoft.com...
>> > Well, I setup a PC Friday afternoon and it is still showing up as 'Not
>> > Yet
>> > Reported' in the WSUS console. Looking through the Windows update log
>> > I
>> > am
>> > seeing some errors.
>> >
>> > Some snippets include
>> >
>> > selfupdate Failure software synchronization Error: Agent failed
>> > detecting
>> > with reason 0x80072efd
>> >
>> > Automaticupdates Failure software synchronization Error: Agent failed
>> > detecting with reason 0x80248008
>> >
>> > Failed to obtain cached cookie with hr = 80248008
>> > Failed to upload events with hr = 80248008
>> > --
>> > Chris
>> > Rochester, NY
>> >
>> >
>> > "Cecil (MSFT)" wrote:
>> >
>> >> Chris,
>> >>
>> >> How long have the XPSP2 machine been reporting as "Not Yet Reported"
>> >> Has
>> >> it
>> >> been more than a full detection cycle?
>> >> --
>> >> This posting is provided "AS IS" with no warranties, and confers no
>> >> rights.
>> >>
>> >>
>> >> "Chris" wrote:
>> >>
>> >> > Hello, I have a WSUS server that was working great up until a power
>> >> > outage
>> >> > last week. Since then any new clients pointed to the WSUS server
>> >> > won't
>> >> > receive the client update software correctly (existing clients still
>> >> > receive
>> >> > windows updates and communicate no problem). These are all brand
>> >> > new
>> >> > XP SP2
>> >> > installs so the wuaueng.dll file passes the client diag. They will
>> >> > show up
>> >> > in the WSUS console but never change state from 'Not Yet Reported'.
>> >> >
>> >> > If I manually install WindowsUpdateAgent20-x86.exe /wuforce on the
>> >> > clients
>> >> > and then run wuauclt /detectnow updates will pop immediately and all
>> >> > is
>> >> > fine
>> >> > after that.
>> >> > Any ideas on how to get the client self update working again?
>> >> > --
>> >> > Chris
>> >> > Rochester, NY
>>
>>
>>