Windows Update Could Not Search for new Updates; Error WindowsUpdate_8000FFFF

Running Vista Ultimate on a pentiumD system in a workgroup with a fuly
patched XP box (so Active Directory and DC issues are eliminated). The
administrative template "specify intranet Microsoft update service location"
is set to "not configured", as it should be. System in daily use with
nearly daily manual update queries since the final version of Vista was
released (February?). Updates worked great until mid-June. The system
consistently found the language packs I chose not to install

Since then I get a WindowsUpdate_8000FFFF error and a red dialog box titled
"Windows
could not search for new updates" almost all of the time. Defender updates
come down automatically at 3 a.m. Six updates for the most recent patch
Tuesday came
down manually on the 13th of July. I went through the Vista updates listed
on downloads.microsoft.com and
tried to install each one inturn from June 18 to date. None would take.
System reprted that update not needed on
this system.

It is hard to know what might be missing. On the 13th of July Windows Update
indicated
other updates were available once but refused to list or download them. Then
it went
back to complaining "Windows could not search for new updates" giving the
error WindowsUpdate_8000FFFF .

I have been following multiple threads hoping to find a solution with no
luck. What I find odd is that if I review the update history, the
installation dates for updates appear to be accurate. Updates installed on
13 July show that date, for instance. When, however, I check for updates,
the
"most recent check for updates" date is stuck at June 18, 2007.

The system time and date are correct. I have tried uninstalling all updates
installed
on June 18. I tried creating a new user with Admin rights and running
Windows Update as that user. I have stoped the Windows update service,
renamed the directory and restarted the service. I checked the WMI
repository for consistency. No problems there. I have even run Windows
update via Run As Administrator. None of this has changed
the system's behavior.

Running all five phases of CHKDSK makes the following attempt to check for
updates take longer to fail, but beyond that, I have not seen any consistant
improvement. Is that date difference important or trivial?

Any help understanding and resolving this issue would be greatly
appreciated.

I have almost exactly the same issue, except for the 'Error(s) found: Code 8024D00A' instead of the 8000FFFF that you recieved.

My Windows Defender also is able to pull updates, prior to that my most recent update was 6/23/2007. I am not able to find much on this issue.

Thanks!

J.

EggHeadCafe.com - .NET Developer Portal of Choice
http://www.eggheadcafe.com

Some steps you can try and I am sure it will resolve the issue.

1.From admin command prompt type net stop wuauserv and net stop cryptsvc and
then delete the softwaredistribution and catroot2 folder under c:\windows and
c:\windows\system32 respectively.

2.Look for these files under c:\windows\winsxs
Pending.xml and Pending.grl
Take the ownership of these files and delete them.
Along with this also check if you have these values undre registry

• PendingXmldentifier
• NextQueueEntryIndex
• AdvancedInstallersNeedResolving

in the location HKLM/Components

If present delete them as well.

Restart the computer and try updating again.

If issue still remains try these

1.Install WindowsUpdateAgent30-x86.exe
from
http://download.windowsupdate.com/v7...gent30-x86.exe
save to the desktop, and run from an elevated command prompt, adding
/wuforce to the end of the command


2.Uninstall any antivirus or firewall software.

3.try running sfc scan in the WinRE ( sfc /scannow /offbootdir=C:\
/offwindir=C:\windows )

All the Best!!

"Scott" wrote:

> Running Vista Ultimate on a pentiumD system in a workgroup with a fuly
> patched XP box (so Active Directory and DC issues are eliminated). The
> administrative template "specify intranet Microsoft update service location"
> is set to "not configured", as it should be. System in daily use with
> nearly daily manual update queries since the final version of Vista was
> released (February?). Updates worked great until mid-June. The system
> consistently found the language packs I chose not to install
>
> Since then I get a WindowsUpdate_8000FFFF error and a red dialog box titled
> "Windows
> could not search for new updates" almost all of the time. Defender updates
> come down automatically at 3 a.m. Six updates for the most recent patch
> Tuesday came
> down manually on the 13th of July. I went through the Vista updates listed
> on downloads.microsoft.com and
> tried to install each one inturn from June 18 to date. None would take.
> System reprted that update not needed on
> this system.
>
> It is hard to know what might be missing. On the 13th of July Windows Update
> indicated
> other updates were available once but refused to list or download them. Then
> it went
> back to complaining "Windows could not search for new updates" giving the
> error WindowsUpdate_8000FFFF .
>
> I have been following multiple threads hoping to find a solution with no
> luck. What I find odd is that if I review the update history, the
> installation dates for updates appear to be accurate. Updates installed on
> 13 July show that date, for instance. When, however, I check for updates,
> the
> "most recent check for updates" date is stuck at June 18, 2007.
>
> The system time and date are correct. I have tried uninstalling all updates
> installed
> on June 18. I tried creating a new user with Admin rights and running
> Windows Update as that user. I have stoped the Windows update service,
> renamed the directory and restarted the service. I checked the WMI
> repository for consistency. No problems there. I have even run Windows
> update via Run As Administrator. None of this has changed
> the system's behavior.
>
> Running all five phases of CHKDSK makes the following attempt to check for
> updates take longer to fail, but beyond that, I have not seen any consistant
> improvement. Is that date difference important or trivial?
>
> Any help understanding and resolving this issue would be greatly
> appreciated.
>
>