En iyi yanıtlayıcılar
Windows Update fails with error code 8000FFFF
Soru
-
Hello to you all,
today I've checked whether my system has been updated in the last days. After having opened Windows Update, it showed that the last update has been done on Febr. 19, 2009 (KB961367) and last time it checked for updates was Febr. 22, 2009.
I've started the search by clicking on "Search for new updates" but after a few seconds of activity I've received an error message saying that an unknown error occured while searching for new updates (error code 8000FFFF). Since I couldn't find any related posting in the Windows 7 forums I'm now asking you for any help on that...
Thanks in advance and greetings from Germany,
norisron
Yanıtlar
-
Well folks. it appears that there are only 2 ways to resolve this issue:
1) An in place 'upgrade'
2) A format and reinstall
@ Wolfie: I'm well aware of how to extract .cab files. The issue was centered on extracting their contents and getting the files installed so that information was being stored in the registry and WinSxS.
This thread is done. If anyone comes across the same or similar issue, please start a new thread.
MowGreen MVP Data Center Management - Update Services Consumer Security- Yanıt Olarak İşaretleyen MowGreenEditor 7 Nisan 2009 Salı 15:46
Tüm Yanıtlar
-
You can try the 'fix it button' for that
When I open Windows Update in Control Panel, I receive an error code of 8000FFFF:Rating posts helps other usersMark L. Ferguson MS-MVP -
I'm having an identical error. Unfortunately, Mark, the fix you describe is for Vista and doesn't work on Win7. Furthermore, the equivalent manual fix (deleting some keys under HKLM/COMPONENTS) appears to be irrelevant to this problem as those keys (PendingXmlIdentifier etc) don't exist on my system anyway (Win7 build 7000 x64).
Interestingly, a search through my logs shows that the problem started on 19 Feb for me as well. I only actually noticed it today when I decided to run Windows Update manually because of the test that's going on.
Here are some relevant lines from the logs which relate to the point at which this error first appears there:
WindowsUpdate.log:
2009-02-19 14:42:28:828 648 9e4 Misc =========== Logging initialized (build: 7.3.7000.0, tz: -0000) ===========
2009-02-19 14:42:28:968 648 9e4 Misc = Process: C:\Windows\system32\svchost.exe
2009-02-19 14:42:28:968 648 9e4 Misc = Module: c:\windows\system32\wuaueng.dll
2009-02-19 14:42:28:828 648 9e4 Service *************
2009-02-19 14:42:29:031 648 9e4 Service ** START ** Service: Service startup
2009-02-19 14:42:29:031 648 9e4 Service *********
2009-02-19 14:42:29:171 648 9e4 Agent * WU client version 7.3.7000.0
2009-02-19 14:42:29:187 648 9e4 Agent * Base directory: C:\Windows\SoftwareDistribution
2009-02-19 14:42:29:203 648 9e4 Agent * Access type: No proxy
2009-02-19 14:42:29:218 648 9e4 Agent * Network state: Connected
2009-02-19 14:43:16:871 648 9e4 Agent *********** Agent: Initializing Windows Update Agent ***********
2009-02-19 14:43:16:871 648 9e4 Agent *********** Agent: Initializing global settings cache ***********
2009-02-19 14:43:16:871 648 9e4 Agent * WSUS server: <NULL>
2009-02-19 14:43:16:871 648 9e4 Agent * WSUS status server: <NULL>
2009-02-19 14:43:16:871 648 9e4 Agent * Target group: (Unassigned Computers)
2009-02-19 14:43:16:871 648 9e4 Agent * Windows Update access disabled: No
2009-02-19 14:43:16:871 648 9e4 DnldMgr Download manager restoring 0 downloads
2009-02-19 14:43:16:886 648 9e4 AU ########### AU: Initializing Automatic Updates ###########
2009-02-19 14:43:16:902 648 9e4 AU AU setting next detection timeout to 2009-02-19 14:43:16
2009-02-19 14:43:16:902 648 9e4 AU AU setting next sqm report timeout to 2009-02-19 14:43:16
2009-02-19 14:43:16:917 648 9e4 AU # Approval type: Pre-install notify (User preference)
2009-02-19 14:43:16:917 648 9e4 AU # Auto-install minor updates: No (User preference)
2009-02-19 14:43:16:917 648 9e4 AU # Will interact with non-admins (Non-admins are elevated (User preference))
2009-02-19 14:43:16:917 648 9e4 AU # Will display featured updates notifications (User preference)
2009-02-19 14:43:16:933 648 9e4 AU Initializing featured updates
2009-02-19 14:43:16:933 648 9e4 AU Found 0 cached featured updates
2009-02-19 14:43:17:417 648 9e4 Report *********** Report: Initializing static reporting data ***********
2009-02-19 14:43:17:417 648 9e4 Report * OS Version = 6.1.7000.0.0.65792
2009-02-19 14:43:17:417 648 9e4 Report * OS Product Type = 0x00000001
2009-02-19 14:43:17:433 648 9e4 Report * Computer Brand = System Manufacter
2009-02-19 14:43:17:433 648 9e4 Report * Computer Model = System Product Name
2009-02-19 14:43:17:449 648 9e4 Report * Bios Revision = 6.00 PG
2009-02-19 14:43:17:449 648 9e4 Report * Bios Name = Phoenix - AwardBIOS v6.00PG
2009-02-19 14:43:17:449 648 9e4 Report * Bios Release Date = 2008-02-29T00:00:00
2009-02-19 14:43:17:449 648 9e4 Report * Locale ID = 2057
2009-02-19 14:43:17:480 648 9e4 AU Successfully wrote event for AU health state:0
2009-02-19 14:43:17:480 648 9e4 AU AU finished delayed initialization
2009-02-19 14:43:17:496 648 9e4 AU AU setting next sqm report timeout to 2009-02-20 14:43:17
2009-02-19 14:43:17:496 648 9e4 AU #############
2009-02-19 14:43:17:496 648 9e4 AU ## START ## AU: Search for updates
2009-02-19 14:43:17:496 648 9e4 AU #########
2009-02-19 14:43:17:574 648 9e4 AU <<## SUBMITTED ## AU: Search for updates [CallId = {47523E66-6380-4080-87A3-8E0FC4642B38}]
2009-02-19 14:43:17:714 648 1050 Agent *************
2009-02-19 14:43:17:714 648 1050 Agent ** START ** Agent: Finding updates [CallerId = AutomaticUpdates]
2009-02-19 14:43:17:714 648 1050 Agent *********
2009-02-19 14:43:17:714 648 1050 Agent * Online = Yes; Ignore download priority = No
2009-02-19 14:43:17:714 648 1050 Agent * Criteria = "IsInstalled=0 and DeploymentAction='Installation' or IsPresent=1 and DeploymentAction='Uninstallation' or IsInstalled=1 and DeploymentAction='Installation' and RebootRequired=1 or IsInstalled=0 and DeploymentAction='Uninstallation' and RebootRequired=1"
2009-02-19 14:43:17:714 648 1050 Agent * ServiceID = {7971F918-A847-4430-9279-4A52D1EFE18D} Third party service
2009-02-19 14:43:17:714 648 1050 Agent * Search Scope = {Machine}
2009-02-19 14:43:17:714 648 1050 Setup Checking for agent SelfUpdate
2009-02-19 14:43:17:714 648 1050 Setup Client version: Core: 7.3.7000.0 Aux: 7.3.7000.0
2009-02-19 14:43:17:761 648 1050 Misc Validating signature for C:\Windows\SoftwareDistribution\WuRedir_prerelease\9482F4B4-E343-43B6-B170-9A65BC822C77\win7wuredir.cab:
2009-02-19 14:43:17:839 648 1050 Misc Microsoft signed: Yes
2009-02-19 14:43:21:058 648 1050 Misc Validating signature for C:\Windows\SoftwareDistribution\WuRedir_prerelease\9482F4B4-E343-43B6-B170-9A65BC822C77\win7wuredir.cab:
2009-02-19 14:43:21:058 648 1050 Misc Microsoft signed: Yes
2009-02-19 14:43:21:089 648 1050 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
2009-02-19 14:43:21:121 648 1050 Misc Microsoft signed: Yes
2009-02-19 14:43:24:074 648 1050 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
2009-02-19 14:43:24:074 648 1050 Misc Microsoft signed: Yes
2009-02-19 14:43:26:777 648 1050 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:
2009-02-19 14:43:26:777 648 1050 Misc Microsoft signed: Yes
2009-02-19 14:43:26:855 648 1050 Setup Determining whether a new setup handler needs to be downloaded
2009-02-19 14:43:26:855 648 1050 Setup SelfUpdate handler is not found. It will be downloaded
2009-02-19 14:43:26:855 648 1050 Setup Evaluating applicability of setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.4.7000.81"
2009-02-19 14:43:28:886 648 1050 Handler FATAL: UH: 0x8000ffff: EvaluateApplicability failed in CCbs::EvaluateApplicability
2009-02-19 14:43:28:886 648 1050 Setup WARNING: CBS EvaluateApplicability returned error, error = 0x8000FFFF
2009-02-19 14:43:28:886 648 1050 Setup FATAL: Applicability evaluation for setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.4.7000.81" failed, error = 0x8000FFFF
2009-02-19 14:43:28:886 648 1050 Setup FATAL: SelfUpdate check failed, err = 0x8000FFFF
2009-02-19 14:43:28:886 648 1050 Agent * WARNING: Skipping scan, self-update check returned 0x8000FFFF
2009-02-19 14:43:28:917 648 1050 Agent * WARNING: Exit code = 0x8000FFFF
2009-02-19 14:43:28:917 648 1050 Agent *********
2009-02-19 14:43:28:917 648 1050 Agent ** END ** Agent: Finding updates [CallerId = AutomaticUpdates]
2009-02-19 14:43:28:917 648 1050 Agent *************
2009-02-19 14:43:28:917 648 1050 Agent WARNING: WU client failed Searching for update with error 0x8000ffff
2009-02-19 14:43:28:917 648 110c AU >>## RESUMED ## AU: Search for updates [CallId = {47523E66-6380-4080-87A3-8E0FC4642B38}]
2009-02-19 14:43:28:917 648 110c AU # WARNING: Search callback failed, result = 0x8000FFFF
2009-02-19 14:43:28:917 648 110c AU # WARNING: Failed to find updates with error code 8000FFFF
2009-02-19 14:43:28:917 648 110c AU #########
2009-02-19 14:43:28:917 648 110c AU ## END ## AU: Search for updates [CallId = {47523E66-6380-4080-87A3-8E0FC4642B38}]
2009-02-19 14:43:28:917 648 110c AU #############
2009-02-19 14:43:28:917 648 110c AU Successfully wrote event for AU health state:0
2009-02-19 14:43:28:917 648 110c AU AU setting next detection timeout to 2009-02-19 19:43:28
2009-02-19 14:43:33:886 648 1050 Report REPORT EVENT: {B9E7431D-7C5E-4EF3-964D-4D2F8BE156A0} 2009-02-19 14:43:28:886-0000 1 148 101 {61CA813A-7585-442E-A66B-B0D15CE6BDC0} 1 8000ffff SelfUpdate Failure Software Synchronization Windows Update Client failed to detect with error 0x8000ffff.
ReportingEvents.log:
{26214055-9394-445C-97F3-531386A74A7B} 2009-02-17 14:12:31:749-0000 1 189 102 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Content Install Installation Ready: The following updates are downloaded and ready for installation. To install the updates, an administrator should log on to this computer and Windows will prompt with further instructions: - Definition Update for Windows Defender - KB915597 (Definition 1.51.627.0)
{DC97B062-F363-49B6-955E-75438EE3D976} 2009-02-17 14:16:29:601-0000 1 183 101 {137A7A35-3451-409E-828E-A085259D9E2E} 100 0 AutomaticUpdates Success Content Install Installation Successful: Windows successfully installed the following update: Definition Update for Windows Defender - KB915597 (Definition 1.51.627.0)
{5C8A701C-7251-404E-A297-B8D874CADADB} 2009-02-17 14:17:28:907-0000 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 ChkWuDrv Success Software Synchronization Windows Update Client successfully detected 0 updates.
{A42FF2B8-D199-44F3-B079-E5222D469A19} 2009-02-17 14:17:30:918-0000 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 ChkWuDrv Success Software Synchronization Windows Update Client successfully detected 0 updates.
{37862602-94FC-4A8F-A9AE-58A9EE61B4F8} 2009-02-17 14:17:33:481-0000 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 ChkWuDrv Success Software Synchronization Windows Update Client successfully detected 0 updates.
{1C46F463-BCFF-405B-9526-36058BA49B5B} 2009-02-18 14:21:48:100-0000 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software Synchronization Windows Update Client successfully detected 0 updates.
{B9E7431D-7C5E-4EF3-964D-4D2F8BE156A0} 2009-02-19 14:43:28:886-0000 1 148 101 {61CA813A-7585-442E-A66B-B0D15CE6BDC0} 1 8000ffff SelfUpdate Failure Software Synchronization Windows Update Client failed to detect with error 0x8000ffff.
CBS.log:
2009-02-19 14:43:27, Info CBS Starting TrustedInstaller initialization.
2009-02-19 14:43:27, Info CBS Loaded Servicing Stack v6.1.7000.0 with Core: C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7000.0_none_d5e7e2f8bb9f807a\cbscore.dll
2009-02-19 14:43:27, Info CSI 00000001@2009/2/19:14:43:27.683 WcpInitialize (wcp.dll version 0.0.0.6) called (stack @0x7fee9add39d @0x7fee9df4761 @0x7fee9dc053e @0xff35e382 @0xff35d1a1 @0xff35d537)
2009-02-19 14:43:27, Info CSI 00000002@2009/2/19:14:43:27.683 WcpInitialize (wcp.dll version 0.0.0.6) called (stack @0x7fee9add39d @0x7fee9e3cfb4 @0x7fee9e0cdc2 @0x7fee9dc061b @0xff35e382 @0xff35d1a1)
2009-02-19 14:43:27, Info CBS SQM: Initializing online with Windows opt-in: True
2009-02-19 14:43:27, Info CBS SQM: Cleaning up report files older than 10 days.
2009-02-19 14:43:27, Info CBS SQM: Requesting upload of all unsent reports.
2009-02-19 14:43:27, Info CBS SQM: Queued 0 file(s) for upload with pattern: C:\Windows\servicing\sqm\*_std.sqm, flags: 0x2
2009-02-19 14:43:27, Info CBS SQM: Queued 0 file(s) for upload with pattern: C:\Windows\servicing\sqm\*_all.sqm, flags: 0x6
2009-02-19 14:43:27, Info CSI 00000003@2009/2/19:14:43:27.699 WcpInitialize (wcp.dll version 0.0.0.6) called (stack @0x7fee9add39d @0x7fee99886ec @0x7fee998881a @0xff35deac @0xff35d1e6 @0xff35d537)
2009-02-19 14:43:27, Info CBS Ending TrustedInstaller initialization.
2009-02-19 14:43:27, Info CBS Starting the TrustedInstaller main loop.
2009-02-19 14:43:27, Info CBS No startup processing required, TrustedInstaller service was not set as autostart, or else a reboot is still pending.
2009-02-19 14:43:27, Info CBS NonStart: Checking to ensure startup processing was not required.
2009-02-19 14:43:27, Info CSI 00000004 IAdvancedInstallerAwareStore_ResolvePendingTransactions (call 1) (flags = 00000004, progress = NULL, phase = 0, pdwDisposition = @0x137fb20
2009-02-19 14:43:27, Info CBS NonStart: Success, startup processing not required as expected.
2009-02-19 14:43:27, Info CBS Startup processing thread terminated normally
2009-02-19 14:43:27, Info CSI 00000005 CSI Store 1494432 (0x000000000016cda0) initialized
2009-02-19 14:43:27, Info CBS Session: 29987488_1828268489 initialized by client WindowsUpdateAgent.
2009-02-19 14:43:27, Info CBS Appl: detect Parent, Package: WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.4.7000.81, Parent: Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~6.0.6000.16386, Disposition = Detect, VersionComp: EQ, ServiceComp: EQ, BuildComp: EQ, DistributionComp: GE, RevisionComp: GE, Exist: present
2009-02-19 14:43:27, Info CBS Appl: detectParent: package: WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.4.7000.81, parent found: Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~6.1.7000.0, state: Installed
2009-02-19 14:43:27, Info CBS Appl: detect Parent, Package: WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.4.7000.81, disposition state from detectParent: Installed
2009-02-19 14:43:27, Info CBS Appl: Evaluating package applicability for package WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.4.7000.81, applicable state: Installed
2009-02-19 14:43:27, Info CSI 00000006 Pending transaction content must be resolved, cannot begin another transaction yet
2009-02-19 14:43:27, Error CSI 00000007 (F) E_UNEXPECTED #135# from Windows::COM::CComponentStore::InternalTransact(...)[gle=0x8000ffff]
2009-02-19 14:43:27, Error CSI 00000008@2009/2/19:14:43:27.871 (F) d:\win7beta\base\wcp\componentstore\com\store.cpp(4209): Error E_UNEXPECTED originated in function Windows::COM::CComponentStore::InternalTransact expression: ((HRESULT)0x8000FFFFL)
[gle=0x80004005]
2009-02-19 14:43:28, Error CSI 00000009 (F) E_UNEXPECTED #134# from Windows::ServicingAPI::CCSIStore_ICSIStore2::BeginTransaction(flags = (ICSISTORE2_BEGINTRANSACTION_FLAG_ALLOW_NO_KTM|ICSISTORE2_BEGINTRANSACTION_FLAG_DONT_FAIL_IF_TX_MERGE_IMPOSSIBLE), de = {d16d444c-56d8-11d5-882d-0080c847b195}, cti = [26]"TI5.29987488_1828268489:1/", riid = {16b07adc-182f-4fe3-bc9b-e53991770f25}, ppt = ppt, disp = disp)
[gle=0x8000ffff]
2009-02-19 14:43:28, Info CBS Failed to create CSI transaction with id: TI5.29987488_1828268489:1/. [HRESULT = 0x8000ffff - Unknown Error]
2009-02-19 14:43:28, Info CBS Failed to create CSI transaction to get inventory. [HRESULT = 0x8000ffff - Unknown Error]
2009-02-19 14:43:28, Info CBS Failed to get inventory [HRESULT = 0x8000ffff - Unknown Error]
2009-02-19 14:43:28, Info CBS Failed to load current component state [HRESULT = 0x8000ffff - Unknown Error]
2009-02-19 14:43:28, Info CBS Failed to find or add the component family [HRESULT = 0x8000ffff - Unknown Error]
2009-02-19 14:43:28, Info CBS ComponentAnalyzerEvaluateSelfUpdate call failed. [HRESULT = 0x8000ffff - Unknown Error]
2009-02-19 14:43:28, Info CBS Failed to evaluate self update [HRESULT = 0x8000ffff - Unknown Error]
2009-02-19 14:43:28, Info CBS Failed to evaluate non detect parent update [HRESULT = 0x8000ffff - Unknown Error]
2009-02-19 14:43:28, Info CBS Failed to evaluate non parent [HRESULT = 0x8000ffff - Unknown Error]
2009-02-19 14:43:28, Info CBS failed to evaluate single applicability [HRESULT = 0x8000ffff - Unknown Error]
2009-02-19 14:43:28, Info CBS Failed to evaluate applicability [HRESULT = 0x8000ffff - Unknown Error]
2009-02-19 14:43:28, Info CBS Failed to get applicability on updates [HRESULT = 0x8000ffff - Unknown Error]
2009-02-19 14:43:28, Info CBS Failed to call external evaluate applicability on package: WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.4.7000.81, Update: ActiveX [HRESULT = 0x8000ffff - Unknown Error]
Note the line :
2009-02-19 14:43:27, Info CSI 00000006 Pending transaction content must be resolved, cannot begin another transaction yet
I'm no Windows system engineer, but that looks a bit suspicious to me. :)
Anyway, I hope someone who knows how to interpret these logs properly manages to take a look at them, as right now Windows Update is completely inoperative on my machine, and has been for the past week. -
Hi Mark,thanks a lot for your hint!Unfortunately these keys are not existing here so that fix couldn't work (before I've posted here I have checked that error message via Google and there were some results leading to the same "solution" which surely works on Vista machines but not on mine)...Since charleski is reporting the same problem which has obviously started on the same day (the only difference is that I'm working on a 32-bit Windows 7 system) I could imagine that a fix/patch by Microsoft is necessary to get back the automatic update functionality...Thanks again (also to charleski for his very detailed report!),norisron
-
I too have this problem, the difference here is, I only installed win7 yesterday. Build 7000, with legit key.I've tried all sorts, and am stumped...BTW as I said this is a fresh install and I was just running win update for the first time.On my other machine, also win7 there is no problem at all...BTW are you the others having this problem over wifi or wired connections? I'm on wifi.Stewart
-
Hi of users,
the same Probelm had a few days ago, however, it could not solve. Has sent feedback to MS.The only solution to the Probelm is an Instal new, from Windows 7. Has ascertained afterwards itself also the users - Control has changed. Have weider an Admin user as well as two accounts.
Sorry for bad English
-
I ended up restoring my Vista Image and forgetting about Windows 7 on this system. I'm still testing on a desktop machine with no problems. I will try again with the next release.
Using HP Lappy. 9728CA. It was also a problem with SP1 of Vista so it could be hardware.
-
Hi all,
this story seems to become a real issue... Could it be related to the Windows Update tests which have been announced for Febr. 24, 2009?
@SGilray: I'm using wired connections only so I don't think the issue is related to that.
@Profster: here Windows 7 is installed on a HP laptop, too (but mine is a much older one, a NC6000). The laptop's performance is much better than with MS Vista which was installed before...
After having checked the Windows Update log on my machine I've found something strange (see the extract of the log file where I've marked the disputable sections boldly):
Client version: Core: 7.3.7000.0 Aux: 7.3.7000.0
2009-02-28 05:31:51:618 1096 11910 Misc Validating signature for C:\Windows\SoftwareDistribution\WuRedir_prerelease\9482F4B4-E343-43B6-B170-9A65BC822C77\win7wuredir.cab:
2009-02-28 05:31:51:626 1096 11910 Misc Microsoft signed: Yes
2009-02-28 05:31:52:117 1096 11910 Misc Validating signature for C:\Windows\SoftwareDistribution\WuRedir_prerelease\9482F4B4-E343-43B6-B170-9A65BC822C77\win7wuredir.cab:
2009-02-28 05:31:52:131 1096 11910 Misc Microsoft signed: Yes
2009-02-28 05:31:52:138 1096 11910 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
2009-02-28 05:31:52:162 1096 11910 Misc Microsoft signed: Yes
2009-02-28 05:31:52:599 1096 11910 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
2009-02-28 05:31:52:606 1096 11910 Misc Microsoft signed: Yes
2009-02-28 05:31:52:611 1096 11910 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:
2009-02-28 05:31:52:619 1096 11910 Misc Microsoft signed: Yes
2009-02-28 05:31:52:785 1096 11910 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:
2009-02-28 05:31:52:793 1096 11910 Misc Microsoft signed: Yes
2009-02-28 05:31:52:919 1096 11910 Setup Determining whether a new setup handler needs to be downloaded
2009-02-28 05:31:52:919 1096 11910 Setup SelfUpdate handler is not found. It will be downloaded
2009-02-28 05:31:52:941 1096 11910 Setup Evaluating applicability of setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~x86~~7.4.7000.81"
2009-02-28 05:31:54:185 1096 11910 Handler FATAL: UH: 0x8000ffff: EvaluateApplicability failed in CCbs::EvaluateApplicability
2009-02-28 05:31:54:185 1096 11910 Setup WARNING: CBS EvaluateApplicability returned error, error = 0x8000FFFF
2009-02-28 05:31:54:185 1096 11910 Setup FATAL: Applicability evaluation for setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~x86~~7.4.7000.81" failed, error = 0x8000FFFF
2009-02-28 05:31:54:186 1096 11910 Setup FATAL: SelfUpdate check failed, err = 0x8000FFFF
2009-02-28 05:31:54:186 1096 11910 Agent * WARNING: Skipping scan, self-update check returned 0x8000FFFF
2009-02-28 05:31:54:204 1096 11910 Agent * WARNING: Exit code = 0x8000FFFF
2009-02-28 05:31:54:204 1096 11910 Agent *********
2009-02-28 05:31:54:204 1096 11910 Agent ** END ** Agent: Finding updates [CallerId = AutomaticUpdates]
2009-02-28 05:31:54:204 1096 11910 Agent *************
2009-02-28 05:31:54:204 1096 11910 Agent WARNING: WU client failed Searching for update with error 0x8000ffff
2009-02-28 05:31:54:206 1096 120fc AU >>## RESUMED ## AU: Search for updates [CallId = {66948460-7AE8-42C0-90FE-055E93131476}]
2009-02-28 05:31:54:206 1096 120fc AU # WARNING: Search callback failed, result = 0x8000FFFF
2009-02-28 05:31:54:206 1096 120fc AU # WARNING: Failed to find updates with error code 8000FFFF"
I'm not convinced but pretty sure that there was a change of the self-update mechanism which lead to this issue. Either the registry has become defect in that point or the Windows Update created some changes before (during the last succesful update) which are preventing me from getting further updates right now...
Of course I used the feedback feature to inform the Windows 7 programming team. Since we will get no feedback from MS here, we will have to wait for further information or help (patch or fix). Reinstalling Windows 7 would surely solve the issue for now but I believe it would reoccur after a while as long as the root cause is not identified...
Good luck and keep on testing,
norisron
-
norisron said:
2009-02-28 05:31:52:919 1096 11910 Setup Determining whether a new setup handler needs to be downloaded
2009-02-28 05:31:52:919 1096 11910 Setup SelfUpdate handler is not found. It will be downloaded
2009-02-28 05:31:52:941 1096 11910 Setup Evaluating applicability of setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~x86~~7.4.7000.81"
2009-02-28 05:31:54:185 1096 11910 Handler FATAL: UH: 0x8000ffff: EvaluateApplicability failed in CCbs::EvaluateApplicability
2009-02-28 05:31:54:185 1096 11910 Setup WARNING: CBS EvaluateApplicability returned error, error = 0x8000FFFF
2009-02-28 05:31:54:185 1096 11910 Setup FATAL: Applicability evaluation for setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~x86~~7.4.7000.81" failed, error = 0x8000FFFF
2009-02-28 05:31:54:186 1096 11910 Setup FATAL: SelfUpdate check failed, err = 0x8000FFFF
2009-02-28 05:31:54:186 1096 11910 Agent * WARNING: Skipping scan, self-update check returned 0x8000FFFF
Yes, this appears to be an indicator of this error. What might be helpful is if you could post the same period (2009-02-28 05:31 and thereabouts) from your CBS.log.
To access CBS.log (which is dynamically updated and can't be viewed normally), open a command window with admin privileges and then type
xcopy %windir%\logs\CBS\CBS.log C:\CBS-diag.log
(type F when it asks you if the target is a File or Directory)
You will then be able to browse the contents of C:\CBS-diag.log freely. I'd be interested to know if CBS.log exhibits the same behaviour I found, since you seem to be experiencing the same error with CBS EvaluateApplicability. I'm referring to the following lines from my own CBS.log:
2009-02-19 14:43:27, Info CBS Appl: Evaluating package applicability for package WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.4.7000.81, applicable state: Installed
2009-02-19 14:43:27, Info CSI 00000006 Pending transaction content must be resolved, cannot begin another transaction yet
2009-02-19 14:43:27, Error CSI 00000007 (F) E_UNEXPECTED #135# from Windows::COM::CComponentStore::InternalTransact(...)[gle=0x8000ffff]
2009-02-19 14:43:27, Error CSI 00000008@2009/2/19:14:43:27.871 (F) d:\win7beta\base\wcp\componentstore\com\store.cpp(4209): Error E_UNEXPECTED originated in function Windows::COM::CComponentStore::InternalTransact expression: ((HRESULT)0x8000FFFFL)
If those lines match, then it would seem that we have a similar problem with a package that thinks it's installed when in fact it isn't. Or at least, that's my best guess as to what's happening.
And yeah, it would be nice to have some MSFT input on this, even if it's just, "OK, we see something's gone wrong that we need to fix." :) I've tried to dig as deep as I can into the logs to work out what's happening here. If anyone from MSFT needs more info, I'll be happy to provide it.
[I don't want this to seem a slur on Mark Ferguson's excellent input - his replies on this thread and many others that I've looked at have been very useful in narrowing down the problem. It seems right now that this is a technical Win7 beta problem, but I spent a while trying the fixes he described here and in other threads to make sure this wasn't a more general issue related to the Vista codebase of Win7. Narrowing down the field of issues is always a good idea, and thanks to Mark for suggesting several fixes (here and elsewhere) that needed to be ruled out.] -
Hi charleski,
thanks a lot for following up on that and for your hints about how to find out more information!!!
Here is the extract of the CBS.log timely related to the update log I've posted before:
2009-02-28 05:31:53, Info CBS Starting TrustedInstaller initialization.
2009-02-28 05:31:53, Info CBS Loaded Servicing Stack v6.1.7000.0 with Core: C:\Windows\winsxs\x86_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7000.0_none_79c9477503420f44\cbscore.dll
2009-02-28 05:31:53, Info CSI 00000001@2009/2/28:04:31:53.098 WcpInitialize (wcp.dll version 0.0.0.6) called (stack @0x5e41b9d2 @0x5e60222a @0x5e5df1e4 @0x2b1ed1 @0x2b1224 @0x7518742d)
2009-02-28 05:31:53, Info CSI 00000002@2009/2/28:04:31:53.107 WcpInitialize (wcp.dll version 0.0.0.6) called (stack @0x5e41b9d2 @0x5e63fe6e @0x5e61657c @0x2b1ed1 @0x2b1224 @0x7518742d)
2009-02-28 05:31:53, Info CBS SQM: Initializing online with Windows opt-in: True
2009-02-28 05:31:53, Info CBS SQM: Cleaning up report files older than 10 days.
2009-02-28 05:31:53, Info CBS SQM: Requesting upload of all unsent reports.
2009-02-28 05:31:53, Info CBS SQM: Queued 0 file(s) for upload with pattern: C:\Windows\servicing\sqm\*_std.sqm, flags: 0x2
2009-02-28 05:31:53, Info CBS SQM: Queued 0 file(s) for upload with pattern: C:\Windows\servicing\sqm\*_all.sqm, flags: 0x6
2009-02-28 05:31:53, Info CSI 00000003@2009/2/28:04:31:53.157 WcpInitialize (wcp.dll version 0.0.0.6) called (stack @0x5e41b9d2 @0x73384b68 @0x73385461 @0x2b1368 @0x2b1233 @0x7518742d)
2009-02-28 05:31:53, Info CBS Ending TrustedInstaller initialization.
2009-02-28 05:31:53, Info CBS Starting the TrustedInstaller main loop.
2009-02-28 05:31:53, Info CBS No startup processing required, TrustedInstaller service was not set as autostart, or else a reboot is still pending.
2009-02-28 05:31:53, Info CBS NonStart: Checking to ensure startup processing was not required.
2009-02-28 05:31:53, Info CSI 00000004 IAdvancedInstallerAwareStore_ResolvePendingTransactions (call 1) (flags = 00000004, progress = NULL, phase = 0, pdwDisposition = @0xaffa60
2009-02-28 05:31:53, Info CBS NonStart: Success, startup processing not required as expected.
2009-02-28 05:31:53, Info CBS Startup processing thread terminated normally
2009-02-28 05:31:53, Info CSI 00000005 CSI Store 666704 (0x000a2c50) initialized
2009-02-28 05:31:53, Info CBS Session: 29989213_2064025877 initialized by client WindowsUpdateAgent.
2009-02-28 05:31:53, Info CBS Appl: detect Parent, Package: WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~x86~~7.4.7000.81, Parent: Microsoft-Windows-Foundation-Package~31bf3856ad364e35~x86~~6.0.6000.16386, Disposition = Detect, VersionComp: EQ, ServiceComp: EQ, BuildComp: EQ, DistributionComp: GE, RevisionComp: GE, Exist: present
2009-02-28 05:31:53, Info CBS Appl: detectParent: package: WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~x86~~7.4.7000.81, parent found: Microsoft-Windows-Foundation-Package~31bf3856ad364e35~x86~~6.1.7000.0, state: Installed
2009-02-28 05:31:53, Info CBS Appl: detect Parent, Package: WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~x86~~7.4.7000.81, disposition state from detectParent: Installed
2009-02-28 05:31:53, Info CBS Appl: Evaluating package applicability for package WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~x86~~7.4.7000.81, applicable state: Installed
2009-02-28 05:31:53, Info CSI 00000006 Pending transaction content must be resolved, cannot begin another transaction yet
2009-02-28 05:31:53, Error CSI 00000007 (F) E_UNEXPECTED #132# from Windows::COM::CComponentStore::InternalTransact(...)[gle=0x8000ffff]
2009-02-28 05:31:53, Error CSI 00000008@2009/2/28:04:31:53.191 (F) d:\win7beta\base\wcp\componentstore\com\store.cpp(4209): Error E_UNEXPECTED originated in function Windows::COM::CComponentStore::InternalTransact expression: ((HRESULT)0x8000FFFFL)
[gle=0x80004005]
2009-02-28 05:31:54, Error CSI 00000009 (F) E_UNEXPECTED #131# from Windows::ServicingAPI::CCSIStore_ICSIStore2::BeginTransaction(flags = (ICSISTORE2_BEGINTRANSACTION_FLAG_ALLOW_NO_KTM|ICSISTORE2_BEGINTRANSACTION_FLAG_DONT_FAIL_IF_TX_MERGE_IMPOSSIBLE), de = {d16d444c-56d8-11d5-882d-0080c847b195}, cti = [26]"TI5.29989213_2064025877:1/", riid = {16b07adc-182f-4fe3-bc9b-e53991770f25}, ppt = ppt, disp = disp)
[gle=0x8000ffff]
2009-02-28 05:31:54, Info CBS Failed to create CSI transaction with id: TI5.29989213_2064025877:1/. [HRESULT = 0x8000ffff - Unknown Error]
2009-02-28 05:31:54, Info CBS Failed to create CSI transaction to get inventory. [HRESULT = 0x8000ffff - Unknown Error]
2009-02-28 05:31:54, Info CBS Failed to get inventory [HRESULT = 0x8000ffff - Unknown Error]
2009-02-28 05:31:54, Info CBS Failed to load current component state [HRESULT = 0x8000ffff - Unknown Error]
2009-02-28 05:31:54, Info CBS Failed to find or add the component family [HRESULT = 0x8000ffff - Unknown Error]
2009-02-28 05:31:54, Info CBS ComponentAnalyzerEvaluateSelfUpdate call failed. [HRESULT = 0x8000ffff - Unknown Error]
2009-02-28 05:31:54, Info CBS Failed to evaluate self update [HRESULT = 0x8000ffff - Unknown Error]
2009-02-28 05:31:54, Info CBS Failed to evaluate non detect parent update [HRESULT = 0x8000ffff - Unknown Error]
2009-02-28 05:31:54, Info CBS Failed to evaluate non parent [HRESULT = 0x8000ffff - Unknown Error]
2009-02-28 05:31:54, Info CBS failed to evaluate single applicability [HRESULT = 0x8000ffff - Unknown Error]
2009-02-28 05:31:54, Info CBS Failed to evaluate applicability [HRESULT = 0x8000ffff - Unknown Error]
2009-02-28 05:31:54, Info CBS Failed to get applicability on updates [HRESULT = 0x8000ffff - Unknown Error]
2009-02-28 05:31:54, Info CBS Failed to call external evaluate applicability on package: WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~x86~~7.4.7000.81, Update: ActiveX [HRESULT = 0x8000ffff - Unknown Error]
2009-02-28 05:41:54, Info CBS Scavenge: Starts
2009-02-28 05:41:54, Info CSI 0000000a Pending transaction content must be resolved, cannot begin another transaction yet
2009-02-28 05:41:54, Error CSI 0000000b (F) E_UNEXPECTED #150# from Windows::COM::CComponentStore::InternalTransact(...)[gle=0x8000ffff]
2009-02-28 05:41:54, Error CSI 0000000c@2009/2/28:04:41:54.259 (F) d:\win7beta\base\wcp\componentstore\com\store.cpp(4209): Error E_UNEXPECTED originated in function Windows::COM::CComponentStore::InternalTransact expression: ((HRESULT)0x8000FFFFL)
[gle=0x80004005]
2009-02-28 05:41:56, Error CSI 0000000d (F) E_UNEXPECTED #149# from Windows::ServicingAPI::CCSIStore_ICSIStore2::BeginTransaction(flags = (ICSISTORE2_BEGINTRANSACTION_FLAG_ALLOW_NO_KTM|ICSISTORE2_BEGINTRANSACTION_FLAG_DONT_FAIL_IF_TX_MERGE_IMPOSSIBLE), de = {d16d444c-56d8-11d5-882d-0080c847b195}, cti = [10]"TI6.0_0:0/", riid = {16b07adc-182f-4fe3-bc9b-e53991770f25}, ppt = ppt, disp = disp)
[gle=0x8000ffff]
2009-02-28 05:41:56, Info CBS Failed to create CSI transaction with id: TI6.0_0:0/. [HRESULT = 0x8000ffff - Unknown Error]
2009-02-28 05:41:56, Info CBS Scavenge: Failed to create CSI transaction for scavenging. [HRESULT = 0x8000ffff - Unknown Error]
2009-02-28 05:41:56, Info CBS Warning: Failed to scavenge CSI store. [HRESULT = 0x8000ffff - Unknown Error]
2009-02-28 05:41:56, Info CBS Warning: Failed while executing service idle processing. [HRESULT = 0x8000ffff - Unknown Error]
2009-02-28 05:41:56, Info CBS Warning: Failed to execute service idle processing. Error code: 0X8000ffff [HRESULT = 0x8000ffff - Unknown Error]
2009-02-28 05:41:56, Info CBS Ending the TrustedInstaller main loop.
2009-02-28 05:41:56, Info CBS Starting TrustedInstaller finalization.
2009-02-28 05:41:56, Info CBS Ending TrustedInstaller finalization.
To me it seems to be an absolutely identical issue (see bold text)...
I keep the fingers crossed for us!
Thanks again to all which have contributed their knowledge and their experience up to now!
Greetings from Germany,
norisron
-
This is a Pentium 4 3.2GHz running 32-bit Windows 7 Beta build 7000.
Automatic updates are turned on, so I've not been looking to see if it's working.
I noticed this evening that there haven't been any updates for some weeks, so I tried to update manually.
I get Error 8000FFFF every time. The only report on this I can find is from 2006, with a Vista installation.
Separately, but possibly related, the Windows Time update isn't working (although the clock is within seconds of correct).
Internet access seems fine, with Firefox, Thunderbird, and Avast all working fine.
Any suggestions?- Taşıyan Ronnie VernonMVP, Moderator 12 Mart 2009 Perşembe 04:39 (Moved from Windows 7 Installation, Setup, and Deployment to Windows 7 Miscellaneous)
- Birleştiren Ronnie VernonMVP, Moderator 1 Nisan 2009 Çarşamba 18:39 Same Issue
-
-
-
flayofish said:
http://support.microsoft.com/default.aspx/kb/946414
That should fix your problem.
Thanks, but that's the fix for Vista-based computers. I'm running Windows 7 Beta.
The "fix it" tells me it's not for this version when I run it.
None of the registry entries mentioned in the KB article are present in my computer. -
Robinson Zhang - MSFT said:Thanks for that, but no joy.
Based on some customers’ feedback, third party software/IE add-ons can cause the problem.
I suggest resetting IE settings/removing IE toolbar/doing a clean boot to troubleshoot the problem.
Thanks.
I don't use IE - I'm a Mozilla/Firefox user of many years. IE may be on the machine, but I don't use it and I've certainly never added anything on to it.
I tried a clean boot, but got the same problem (except that it took longer to decide).
It doesn't recognise that it's tried to update recently. It says "Most recent check for updates: 18/2/2009 at 23:24".
As far as I recall, I've not added anything or changed anything since 18/2. -
I just checked: there are two software items installed since 18/2 (both on 20/2).
One was Drive Image XML (which didn't work anyway). I removed that. Still no updates.
The other is AESEUS Partition Manager, which hasn't done anything to this drive - it partitioned a third hard drive that I added to the machine.
Would adding a SATA drive to a machine with two IDE drives cause Windows Update to fail?
-
The Fatal error, 0x8000ffff, is being caused by the installation failure of the new version of the Windows Update Agent's [WUA] ActiveX component.
Interference by an antivirus/security suite/or a 3rd party firewall may be the cause.
2009-02-28 05:31:54, Info CBS Failed to call external evaluate applicability on package: WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~x86~~7.4.7000.81, Update: ActiveX [HRESULT = 0x8000ffff - Unknown Error]
See if WuSetupV.exe exists at this location
Windows\SoftwareDistribution\SelfUpdate\Handler
If it does, you could try clean booting the system and running wusetupv.exe from an Elevated Command Prompt to see if that gets the WUA installed properly. Restart the system afterwards as the issue could also stem from a lack of a service restart when it initially attempted to install.
MowGreen MVP Data Center Management - Update Services Consumer Security -
Unfortunately Windows\SoftwareDistribution\SelfUpdate\Handler is empty, though Windows\SoftwareDistribution\SelfUpdate\ contains several .mum files:
WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.4.7000.81.mum
WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.4.7000.81.mum
WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.4.7000.81.mum
These appear to be xml files describing the assemblies to be applied to differing versions and regions. There's no evidence that the package has actually been downloaded, however.
Update still fails after deactivating my 3rd-party AV/firewall (Kaspersky).
-
charleski said:
Unfortunately Windows\SoftwareDistribution\SelfUpdate\Handler is empty, though Windows\SoftwareDistribution\SelfUpdate\ contains several .mum files:
WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.4.7000.81.mum
WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.4.7000.81.mum
WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.4.7000.81.mum
These appear to be xml files describing the assemblies to be applied to differing versions and regions. There's no evidence that the package has actually been downloaded, however.
Update still fails after deactivating my 3rd-party AV/firewall (Kaspersky).
Please check the ReportingEvents.log located in WINDOWS\SoftwareDistribution
The Date will be 2009-02-28. See if there are Error entries for the installation of
Windows Update ActiveX
Windows Update Core
Disabling the Kaspersky firewall will not put the system in the same state as a clean boot.
Suggest you try clean booting and see if the required software components can be successfully downloaded and installed.
How to troubleshoot a problem by performing a clean boot in Windows Vista
Do Step 1 and restart. See if the Windows Update Agent can be updated properly while in the clean boot state.
MowGreen MVP Data Center Management - Update Services Consumer Security -
KeithjUK said:
I just checked: there are two software items installed since 18/2 (both on 20/2).
One was Drive Image XML (which didn't work anyway). I removed that. Still no updates.
The other is AESEUS Partition Manager, which hasn't done anything to this drive - it partitioned a third hard drive that I added to the machine.
Would adding a SATA drive to a machine with two IDE drives cause Windows Update to fail?
Normally, it won’t cause Windows Update problem.
At this time, I suggest you take the following steps to troubleshoot the issue.
1. Close all the open windows.
2. Click the "Start" Button, click "All programs", and click "Accessories".
3. Right-click "Command Prompt", and click "Run as administrator".
4. In "Administrator: Command Prompt" window, type in "net stop WuAuServ" (without the quotes) and press Enter.5. Click the "Start" Button, in the "Start Search" box, type in "%windir%" (without the quotes) and press Enter.
6. In the opened folder, look for the folder named "SoftwareDistribution".
7. Right-click on the folder, select "Rename" and type "SDold" (without the quotes) to rename this folder.
8. Still in "Administrator: Command Prompt" window, type the command "net start WuAuServ" (without the quotes) in the opened window to restart the Windows Updates service.After completing the above steps, please restart the computer and try to run Windows Update again.
Hope it helps.
-
Thanks - I did all that. It removed the "last update was..." from the update screen, but it still bombs out with the 8000FFFF error.
I don't think this site accepts [img] tags, but the screengrab of the relevant bit is here:
http://www.kirbycane.plus.com/8000FFFF.jpg
-
I would suggest (in this order):
- stopping the Windows Update Service
- deleting the contents of the Software Distribution folder
- starting the Windows Udpate Service
While I haven't tried this in Win7, it has saved my bacon several times in Vista.
In Vista you:
- Open an elevated (Run as Administrator) Command Prompt and type "net stop wuauserv" (without the quotes) and press Enter.
- Once the service has stopped, open an elevated Windows Explorer window and delete the contents of the Software Distribution folder (in C:\Windows). Do not delete the folder itself.
- Once that's done, go back to the elevated Command Prompt window and type "net start wuauserv" (without the quotes) and press Enter.
- John -
-
Thank you.
ZoneAlarm said it wouldn't work with Windows 7, so is not installed.
The anti-virus on the machine is Avira. It was OK for several weeks - the problem is more recent. I'm away from home at the moment, but will try at the weekend with Avira turned off to see if that changes anything. -
KeithjUK said:
Thanks - I did all that. It removed the "last update was..." from the update screen, but it still bombs out with the 8000FFFF error.
I don't think this site accepts [img] tags, but the screengrab of the relevant bit is here:
http://www.kirbycane.plus.com/8000FFFF.jpgHi Keith
You can embed an image in a post here.
Click the <> button at the bottom/left corner of the Compose window and add this:
<img src="URL TO IMAGE GOES HERE" />
Remove the obvious and paste the URL between the 2 quotation marks.
Make sure that the spaces between img src and " /> stay intact.
Click the Pencil Icon to see the results and finish the message, before clicking Submit.
Hope this helps.
Thank You for testing Windows 7 Beta
Ronnie Vernon MVP -
-
Sometimes the update log will give a clue as to the reason/error.
Go to the Windows Orb (Start), type %windir%\windowsupdate.log and press Enter. To find the error(s), go to the end of the file (Ctrl+End) then use ‘Find’ (Ctrl+F) to check for the word 'fatal', use search ‘Up’ to search upwards from the end of the file. -
This is what the log shows for today. I don't know enough about the workings of Windows 7 to know which event caused the failure.
Any suggestions?
___________________________________________________________________
2009-03-15 05:33:19:374 964 308 AU #############
2009-03-15 05:33:19:385 964 308 AU ## START ## AU: Search for updates
2009-03-15 05:33:19:386 964 308 AU #########
2009-03-15 05:33:19:466 964 308 AU <<## SUBMITTED ## AU: Search for updates [CallId = {168A5C71-77E7-45D6-B3A1-2CE35E35D019}]
2009-03-15 05:33:19:467 964 598 Agent *************
2009-03-15 05:33:19:467 964 598 Agent ** START ** Agent: Finding updates [CallerId = AutomaticUpdates]
2009-03-15 05:33:19:467 964 598 Agent *********
2009-03-15 05:33:19:467 964 598 Agent * Online = Yes; Ignore download priority = No
2009-03-15 05:33:19:467 964 598 Agent * Criteria = "IsInstalled=0 and DeploymentAction='Installation' or IsPresent=1 and DeploymentAction='Uninstallation' or IsInstalled=1 and DeploymentAction='Installation' and RebootRequired=1 or IsInstalled=0 and DeploymentAction='Uninstallation' and RebootRequired=1"
2009-03-15 05:33:19:467 964 598 Agent * ServiceID = {9482F4B4-E343-43B6-B170-9A65BC822C77} Windows Update
2009-03-15 05:33:19:467 964 598 Agent * Search Scope = {Machine}
2009-03-15 05:33:19:476 964 598 Setup Checking for agent SelfUpdate
2009-03-15 05:33:19:504 964 598 Setup Client version: Core: 7.3.7000.0 Aux: 7.3.7000.0
2009-03-15 05:33:19:552 964 598 Misc Validating signature for C:\Windows\SoftwareDistribution\WuRedir_prerelease\9482F4B4-E343-43B6-B170-9A65BC822C77\win7wuredir.cab:
2009-03-15 05:33:19:590 964 598 Misc Microsoft signed: Yes
2009-03-15 05:33:33:590 964 598 Misc Validating signature for C:\Windows\SoftwareDistribution\WuRedir_prerelease\9482F4B4-E343-43B6-B170-9A65BC822C77\win7wuredir.cab:
2009-03-15 05:33:33:604 964 598 Misc Microsoft signed: Yes
2009-03-15 05:33:33:632 964 598 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
2009-03-15 05:33:33:651 964 598 Misc Microsoft signed: Yes
2009-03-15 05:33:36:587 964 598 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
2009-03-15 05:33:36:600 964 598 Misc Microsoft signed: Yes
2009-03-15 05:33:36:651 964 598 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:
2009-03-15 05:33:36:677 964 598 Misc Microsoft signed: Yes
2009-03-15 05:33:39:485 964 598 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:
2009-03-15 05:33:39:502 964 598 Misc Microsoft signed: Yes
2009-03-15 05:33:39:650 964 598 Setup Determining whether a new setup handler needs to be downloaded
2009-03-15 05:33:39:651 964 598 Setup SelfUpdate handler is not found. It will be downloaded
2009-03-15 05:33:39:685 964 598 Setup Evaluating applicability of setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~x86~~7.4.7000.81"
2009-03-15 05:33:43:836 964 598 Handler FATAL: UH: 0x8000ffff: EvaluateApplicability failed in CCbs::EvaluateApplicability
2009-03-15 05:33:43:837 964 598 Setup WARNING: CBS EvaluateApplicability returned error, error = 0x8000FFFF
2009-03-15 05:33:43:837 964 598 Setup FATAL: Applicability evaluation for setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~x86~~7.4.7000.81" failed, error = 0x8000FFFF
2009-03-15 05:33:43:838 964 598 Setup FATAL: SelfUpdate check failed, err = 0x8000FFFF
2009-03-15 05:33:43:858 964 598 Agent * WARNING: Skipping scan, self-update check returned 0x8000FFFF
2009-03-15 05:33:44:244 964 598 Agent * WARNING: Exit code = 0x8000FFFF
2009-03-15 05:33:44:245 964 598 Agent *********
2009-03-15 05:33:44:245 964 598 Agent ** END ** Agent: Finding updates [CallerId = AutomaticUpdates]
2009-03-15 05:33:44:245 964 598 Agent *************
2009-03-15 05:33:44:245 964 598 Agent WARNING: WU client failed Searching for update with error 0x8000ffff
2009-03-15 05:33:44:247 964 1658 AU >>## RESUMED ## AU: Search for updates [CallId = {168A5C71-77E7-45D6-B3A1-2CE35E35D019}]
2009-03-15 05:33:44:247 964 1658 AU # WARNING: Search callback failed, result = 0x8000FFFF
2009-03-15 05:33:44:247 964 1658 AU # WARNING: Failed to find updates with error code 8000FFFF
2009-03-15 05:33:44:247 964 1658 AU #########
2009-03-15 05:33:44:247 964 1658 AU ## END ## AU: Search for updates [CallId = {168A5C71-77E7-45D6-B3A1-2CE35E35D019}]
2009-03-15 05:33:44:247 964 1658 AU #############
2009-03-15 05:33:44:259 964 1658 AU Successfully wrote event for AU health state:0
2009-03-15 05:33:44:260 964 1658 AU AU setting next detection timeout to 2009-03-15 10:33:44
2009-03-15 05:33:44:260 964 1658 AU Setting AU scheduled install time to 2009-03-16 04:00:00
2009-03-15 05:33:48:865 964 598 Report REPORT EVENT: {7714FE3D-6954-4397-9E77-9CF181FD667E} 2009-03-15 05:33:43:858-0000 1 148 101 {61CA813A-7585-442E-A66B-B0D15CE6BDC0} 1 8000ffff SelfUpdate Failure Software Synchronization Windows Update Client failed to detect with error 0x8000ffff.
2009-03-15 08:55:52:108 964 10e0 Misc Validating signature for C:\Windows\SoftwareDistribution\WuRedir_prerelease\9482F4B4-E343-43B6-B170-9A65BC822C77\wuredir.cab:
2009-03-15 08:55:52:152 964 10e0 Misc Microsoft signed: Yes
2009-03-15 08:55:52:183 964 10e0 Misc Validating signature for C:\Windows\SoftwareDistribution\WuRedir_prerelease\9482F4B4-E343-43B6-B170-9A65BC822C77\wuredir.cab:
2009-03-15 08:55:52:196 964 10e0 Misc Microsoft signed: Yes
2009-03-15 08:55:52:207 964 10e0 Report Uploading 1 events using cached cookie, reporting URL = http://test.stats.update.microsoft.com/ReportingWebService/ReportingWebService.asmx
2009-03-15 08:56:06:312 964 10e0 Report Reporter successfully uploaded 1 events.
2009-03-15 10:33:44:304 964 308 AU #############
2009-03-15 10:33:44:326 964 308 AU ## START ## AU: Search for updates
2009-03-15 10:33:44:326 964 308 AU #########
2009-03-15 10:33:44:445 964 308 AU <<## SUBMITTED ## AU: Search for updates [CallId = {B26E7BE2-28C0-4078-AD56-91B8F750DF29}]
2009-03-15 10:33:44:458 964 1450 Agent *************
2009-03-15 10:33:44:462 964 1450 Agent ** START ** Agent: Finding updates [CallerId = AutomaticUpdates]
2009-03-15 10:33:44:470 964 1450 Agent *********
2009-03-15 10:33:44:470 964 1450 Agent * Online = Yes; Ignore download priority = No
2009-03-15 10:33:44:470 964 1450 Agent * Criteria = "IsInstalled=0 and DeploymentAction='Installation' or IsPresent=1 and DeploymentAction='Uninstallation' or IsInstalled=1 and DeploymentAction='Installation' and RebootRequired=1 or IsInstalled=0 and DeploymentAction='Uninstallation' and RebootRequired=1"
2009-03-15 10:33:44:471 964 1450 Agent * ServiceID = {9482F4B4-E343-43B6-B170-9A65BC822C77} Windows Update
2009-03-15 10:33:44:472 964 1450 Agent * Search Scope = {Machine}
2009-03-15 10:33:44:490 964 1450 Setup Checking for agent SelfUpdate
2009-03-15 10:33:44:528 964 1450 Setup Client version: Core: 7.3.7000.0 Aux: 7.3.7000.0
2009-03-15 10:33:44:606 964 1450 Misc Validating signature for C:\Windows\SoftwareDistribution\WuRedir_prerelease\9482F4B4-E343-43B6-B170-9A65BC822C77\win7wuredir.cab:
2009-03-15 10:33:44:624 964 1450 Misc Microsoft signed: Yes
2009-03-15 10:33:59:358 964 1450 Misc Validating signature for C:\Windows\SoftwareDistribution\WuRedir_prerelease\9482F4B4-E343-43B6-B170-9A65BC822C77\win7wuredir.cab:
2009-03-15 10:33:59:371 964 1450 Misc Microsoft signed: Yes
2009-03-15 10:33:59:453 964 1450 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
2009-03-15 10:33:59:512 964 1450 Misc Microsoft signed: Yes
2009-03-15 10:34:02:793 964 1450 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
2009-03-15 10:34:02:805 964 1450 Misc Microsoft signed: Yes
2009-03-15 10:34:02:956 964 1450 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:
2009-03-15 10:34:02:973 964 1450 Misc Microsoft signed: Yes
2009-03-15 10:34:06:046 964 1450 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:
2009-03-15 10:34:06:082 964 1450 Misc Microsoft signed: Yes
2009-03-15 10:34:06:515 964 1450 Setup Determining whether a new setup handler needs to be downloaded
2009-03-15 10:34:06:525 964 1450 Setup SelfUpdate handler is not found. It will be downloaded
2009-03-15 10:34:06:587 964 1450 Setup Evaluating applicability of setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~x86~~7.4.7000.81"
2009-03-15 10:34:19:352 964 1450 Handler FATAL: UH: 0x8000ffff: EvaluateApplicability failed in CCbs::EvaluateApplicability
2009-03-15 10:34:19:354 964 1450 Setup WARNING: CBS EvaluateApplicability returned error, error = 0x8000FFFF
2009-03-15 10:34:19:366 964 1450 Setup FATAL: Applicability evaluation for setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~x86~~7.4.7000.81" failed, error = 0x8000FFFF
2009-03-15 10:34:19:366 964 1450 Setup FATAL: SelfUpdate check failed, err = 0x8000FFFF
2009-03-15 10:34:19:410 964 1450 Agent * WARNING: Skipping scan, self-update check returned 0x8000FFFF
2009-03-15 10:34:20:107 964 1450 Agent * WARNING: Exit code = 0x8000FFFF
2009-03-15 10:34:20:107 964 1450 Agent *********
2009-03-15 10:34:20:107 964 1450 Agent ** END ** Agent: Finding updates [CallerId = AutomaticUpdates]
2009-03-15 10:34:20:107 964 1450 Agent *************
2009-03-15 10:34:20:107 964 1450 Agent WARNING: WU client failed Searching for update with error 0x8000ffff
2009-03-15 10:34:20:110 964 1538 AU >>## RESUMED ## AU: Search for updates [CallId = {B26E7BE2-28C0-4078-AD56-91B8F750DF29}]
2009-03-15 10:34:20:110 964 1538 AU # WARNING: Search callback failed, result = 0x8000FFFF
2009-03-15 10:34:20:110 964 1538 AU # WARNING: Failed to find updates with error code 8000FFFF
2009-03-15 10:34:20:110 964 1538 AU #########
2009-03-15 10:34:20:110 964 1538 AU ## END ## AU: Search for updates [CallId = {B26E7BE2-28C0-4078-AD56-91B8F750DF29}]
2009-03-15 10:34:20:110 964 1538 AU #############
2009-03-15 10:34:20:111 964 1538 AU Successfully wrote event for AU health state:0
2009-03-15 10:34:20:112 964 1538 AU AU setting next detection timeout to 2009-03-15 15:34:20
2009-03-15 10:34:20:113 964 1538 AU Setting AU scheduled install time to 2009-03-16 04:00:00
2009-03-15 10:34:24:453 964 1450 Report REPORT EVENT: {2332DDF7-C7E9-4A9D-8C1A-0E95E4C908D4} 2009-03-15 10:34:19:410-0000 1 148 101 {61CA813A-7585-442E-A66B-B0D15CE6BDC0} 1 8000ffff SelfUpdate Failure Software Synchronization Windows Update Client failed to detect with error 0x8000ffff.
2009-03-15 13:56:27:829 964 11f0 Misc Validating signature for C:\Windows\SoftwareDistribution\WuRedir_prerelease\9482F4B4-E343-43B6-B170-9A65BC822C77\wuredir.cab:
2009-03-15 13:56:27:884 964 11f0 Misc Microsoft signed: Yes
2009-03-15 13:56:27:932 964 11f0 Misc Validating signature for C:\Windows\SoftwareDistribution\WuRedir_prerelease\9482F4B4-E343-43B6-B170-9A65BC822C77\wuredir.cab:
2009-03-15 13:56:27:950 964 11f0 Misc Microsoft signed: Yes
2009-03-15 13:56:27:955 964 11f0 Report Uploading 1 events using cached cookie, reporting URL = http://test.stats.update.microsoft.com/ReportingWebService/ReportingWebService.asmx
2009-03-15 13:56:42:082 964 11f0 Report Reporter successfully uploaded 1 events.
-
1. I don’t think it’s affecting the Windows update but put the date/time right first. There are a list of servers here
http://support.microsoft.com/kb/2626802. Go to Internet Options > Security Tab > 'Trusted sites' icon > click Sites then uncheck 'Require server verification' and add these two entries
http://*.windowsupdate.microsoft.com and http://*.windowsupdate.com.
Click Close, Apply and OK. Then try IE to get the updates. -
-
1. Click the time display in the system tray > Change date and time settings > Internet Time Tab > Change Settings and replace the name in the Server box with Europe.pool.ntp.org.
2. You should be pasting (one at a time) the two links in the box named ‘Add this website to the Zone‘ and click Add.
-
Done both of those.
Still the same 8000FFFF error, I'm afraid.
I told it to try again after the first failure (which took a couple of minutes).
Here's the log:
2009-03-15 19:29:14:550 964 1034 AU Triggering AU detection through DetectNow API
2009-03-15 19:29:14:550 964 1034 AU Triggering Online detection (interactive)
2009-03-15 19:29:14:568 964 308 AU #############
2009-03-15 19:29:14:568 964 308 AU ## START ## AU: Search for updates
2009-03-15 19:29:14:568 964 308 AU #########
2009-03-15 19:29:14:686 964 308 AU <<## SUBMITTED ## AU: Search for updates [CallId = {71FF1613-D663-4364-866E-064FF1A25442}]
2009-03-15 19:29:14:707 964 11ac Agent *************
2009-03-15 19:29:14:707 964 11ac Agent ** START ** Agent: Finding updates [CallerId = AutomaticUpdates]
2009-03-15 19:29:14:707 964 11ac Agent *********
2009-03-15 19:29:14:708 964 11ac Agent * Online = Yes; Ignore download priority = No
2009-03-15 19:29:14:708 964 11ac Agent * Criteria = "IsInstalled=0 and DeploymentAction='Installation' or IsPresent=1 and DeploymentAction='Uninstallation' or IsInstalled=1 and DeploymentAction='Installation' and RebootRequired=1 or IsInstalled=0 and DeploymentAction='Uninstallation' and RebootRequired=1"
2009-03-15 19:29:14:708 964 11ac Agent * ServiceID = {9482F4B4-E343-43B6-B170-9A65BC822C77} Windows Update
2009-03-15 19:29:14:708 964 11ac Agent * Search Scope = {Machine}
2009-03-15 19:29:14:720 964 11ac Setup Checking for agent SelfUpdate
2009-03-15 19:29:14:757 964 11ac Setup Client version: Core: 7.3.7000.0 Aux: 7.3.7000.0
2009-03-15 19:29:14:832 964 11ac Misc Validating signature for C:\Windows\SoftwareDistribution\WuRedir_prerelease\9482F4B4-E343-43B6-B170-9A65BC822C77\win7wuredir.cab:
2009-03-15 19:29:14:970 964 11ac Misc Microsoft signed: Yes
2009-03-15 19:29:33:999 964 308 AU AU was unable to detect updates for more than 48 hours
2009-03-15 19:30:47:143 964 11ac Misc Validating signature for C:\Windows\SoftwareDistribution\WuRedir_prerelease\9482F4B4-E343-43B6-B170-9A65BC822C77\win7wuredir.cab:
2009-03-15 19:30:47:160 964 11ac Misc Microsoft signed: Yes
2009-03-15 19:30:47:185 964 11ac Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
2009-03-15 19:30:47:200 964 11ac Misc Microsoft signed: Yes
2009-03-15 19:31:02:292 964 11ac Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
2009-03-15 19:31:02:304 964 11ac Misc Microsoft signed: Yes
2009-03-15 19:31:02:334 964 11ac Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:
2009-03-15 19:31:02:351 964 11ac Misc Microsoft signed: Yes
2009-03-15 19:31:05:185 964 11ac Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:
2009-03-15 19:31:05:195 964 11ac Misc Microsoft signed: Yes
2009-03-15 19:31:05:362 964 11ac Setup Determining whether a new setup handler needs to be downloaded
2009-03-15 19:31:05:363 964 11ac Setup SelfUpdate handler is not found. It will be downloaded
2009-03-15 19:31:05:369 964 11ac Setup Evaluating applicability of setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~x86~~7.4.7000.81"
2009-03-15 19:31:09:355 964 11ac Handler FATAL: UH: 0x8000ffff: EvaluateApplicability failed in CCbs::EvaluateApplicability
2009-03-15 19:31:09:357 964 11ac Setup WARNING: CBS EvaluateApplicability returned error, error = 0x8000FFFF
2009-03-15 19:31:09:357 964 11ac Setup FATAL: Applicability evaluation for setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~x86~~7.4.7000.81" failed, error = 0x8000FFFF
2009-03-15 19:31:09:357 964 11ac Setup FATAL: SelfUpdate check failed, err = 0x8000FFFF
2009-03-15 19:31:09:358 964 11ac Agent * WARNING: Skipping scan, self-update check returned 0x8000FFFF
2009-03-15 19:31:09:396 964 11ac Agent * WARNING: Exit code = 0x8000FFFF
2009-03-15 19:31:09:397 964 11ac Agent *********
2009-03-15 19:31:09:397 964 11ac Agent ** END ** Agent: Finding updates [CallerId = AutomaticUpdates]
2009-03-15 19:31:09:397 964 11ac Agent *************
2009-03-15 19:31:09:397 964 11ac Agent WARNING: WU client failed Searching for update with error 0x8000ffff
2009-03-15 19:31:09:409 964 400 AU >>## RESUMED ## AU: Search for updates [CallId = {71FF1613-D663-4364-866E-064FF1A25442}]
2009-03-15 19:31:09:409 964 400 AU # WARNING: Search callback failed, result = 0x8000FFFF
2009-03-15 19:31:09:409 964 400 AU # WARNING: Failed to find updates with error code 8000FFFF
2009-03-15 19:31:09:409 964 400 AU #########
2009-03-15 19:31:09:409 964 400 AU ## END ## AU: Search for updates [CallId = {71FF1613-D663-4364-866E-064FF1A25442}]
2009-03-15 19:31:09:409 964 400 AU #############
2009-03-15 19:31:09:414 964 11ac Report REPORT EVENT: {2045CEEE-DE2E-4ABF-ACE7-5B16A2276A78} 2009-03-15 19:29:34:009-0000 1 149 102 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Failure Software Synchronization Unable to Connect: Windows is unable to connect to the automatic updates service and therefore cannot download and install updates according to the set schedule. Windows will continue to try to establish a connection.
2009-03-15 19:31:09:431 964 400 AU Successfully wrote event for AU health state:0
2009-03-15 19:31:09:431 964 400 AU AU setting next detection timeout to 2009-03-16 00:31:09
2009-03-15 19:31:09:432 964 400 AU Setting AU scheduled install time to 2009-03-16 04:00:00
2009-03-15 19:31:14:358 964 11ac Report REPORT EVENT: {F6ED97CC-F8CB-4DAD-B9C7-032CEF468818} 2009-03-15 19:31:09:358-0000 1 148 101 {61CA813A-7585-442E-A66B-B0D15CE6BDC0} 1 8000ffff SelfUpdate Failure Software Synchronization Windows Update Client failed to detect with error 0x8000ffff.
2009-03-15 19:31:46:357 964 1034 AU Triggering AU detection through DetectNow API
2009-03-15 19:31:46:357 964 1034 AU Triggering Online detection (interactive)
2009-03-15 19:31:46:357 964 308 AU #############
2009-03-15 19:31:46:358 964 308 AU ## START ## AU: Search for updates
2009-03-15 19:31:46:358 964 308 AU #########
2009-03-15 19:31:46:368 964 308 AU <<## SUBMITTED ## AU: Search for updates [CallId = {222E66D6-E0A5-4E84-9BC1-9678AB8CACF6}]
2009-03-15 19:31:46:369 964 11ac Agent *************
2009-03-15 19:31:46:369 964 11ac Agent ** START ** Agent: Finding updates [CallerId = AutomaticUpdates]
2009-03-15 19:31:46:369 964 11ac Agent *********
2009-03-15 19:31:46:369 964 11ac Agent * Online = Yes; Ignore download priority = No
2009-03-15 19:31:46:370 964 11ac Agent * Criteria = "IsInstalled=0 and DeploymentAction='Installation' or IsPresent=1 and DeploymentAction='Uninstallation' or IsInstalled=1 and DeploymentAction='Installation' and RebootRequired=1 or IsInstalled=0 and DeploymentAction='Uninstallation' and RebootRequired=1"
2009-03-15 19:31:46:370 964 11ac Agent * ServiceID = {9482F4B4-E343-43B6-B170-9A65BC822C77} Windows Update
2009-03-15 19:31:46:370 964 11ac Agent * Search Scope = {Machine}
2009-03-15 19:31:46:370 964 11ac Setup Checking for agent SelfUpdate
2009-03-15 19:31:46:372 964 11ac Setup Client version: Core: 7.3.7000.0 Aux: 7.3.7000.0
2009-03-15 19:31:46:385 964 11ac Misc Validating signature for C:\Windows\SoftwareDistribution\WuRedir_prerelease\9482F4B4-E343-43B6-B170-9A65BC822C77\win7wuredir.cab:
2009-03-15 19:31:46:415 964 11ac Misc Microsoft signed: Yes
2009-03-15 19:31:46:638 964 11ac Misc Validating signature for C:\Windows\SoftwareDistribution\WuRedir_prerelease\9482F4B4-E343-43B6-B170-9A65BC822C77\win7wuredir.cab:
2009-03-15 19:31:46:648 964 11ac Misc Microsoft signed: Yes
2009-03-15 19:31:46:675 964 11ac Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
2009-03-15 19:31:46:686 964 11ac Misc Microsoft signed: Yes
2009-03-15 19:31:46:882 964 11ac Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
2009-03-15 19:31:46:895 964 11ac Misc Microsoft signed: Yes
2009-03-15 19:31:46:903 964 11ac Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:
2009-03-15 19:31:46:911 964 11ac Misc Microsoft signed: Yes
2009-03-15 19:31:47:012 964 11ac Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:
2009-03-15 19:31:47:021 964 11ac Misc Microsoft signed: Yes
2009-03-15 19:31:47:110 964 11ac Setup Determining whether a new setup handler needs to be downloaded
2009-03-15 19:31:47:110 964 11ac Setup SelfUpdate handler is not found. It will be downloaded
2009-03-15 19:31:47:111 964 11ac Setup Evaluating applicability of setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~x86~~7.4.7000.81"
2009-03-15 19:31:47:899 964 11ac Handler FATAL: UH: 0x8000ffff: EvaluateApplicability failed in CCbs::EvaluateApplicability
2009-03-15 19:31:47:921 964 11ac Setup WARNING: CBS EvaluateApplicability returned error, error = 0x8000FFFF
2009-03-15 19:31:47:921 964 11ac Setup FATAL: Applicability evaluation for setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~x86~~7.4.7000.81" failed, error = 0x8000FFFF
2009-03-15 19:31:47:922 964 11ac Setup FATAL: SelfUpdate check failed, err = 0x8000FFFF
2009-03-15 19:31:47:922 964 11ac Agent * WARNING: Skipping scan, self-update check returned 0x8000FFFF
2009-03-15 19:31:47:926 964 11ac Agent * WARNING: Exit code = 0x8000FFFF
2009-03-15 19:31:47:927 964 11ac Agent *********
2009-03-15 19:31:47:927 964 11ac Agent ** END ** Agent: Finding updates [CallerId = AutomaticUpdates]
2009-03-15 19:31:47:927 964 11ac Agent *************
2009-03-15 19:31:47:927 964 11ac Agent WARNING: WU client failed Searching for update with error 0x8000ffff
2009-03-15 19:31:47:928 964 400 AU >>## RESUMED ## AU: Search for updates [CallId = {222E66D6-E0A5-4E84-9BC1-9678AB8CACF6}]
2009-03-15 19:31:47:928 964 400 AU # WARNING: Search callback failed, result = 0x8000FFFF
2009-03-15 19:31:47:928 964 400 AU # WARNING: Failed to find updates with error code 8000FFFF
2009-03-15 19:31:47:928 964 400 AU #########
2009-03-15 19:31:47:929 964 400 AU ## END ## AU: Search for updates [CallId = {222E66D6-E0A5-4E84-9BC1-9678AB8CACF6}]
2009-03-15 19:31:47:929 964 400 AU #############
2009-03-15 19:31:47:929 964 400 AU Successfully wrote event for AU health state:0
2009-03-15 19:31:47:930 964 400 AU AU setting next detection timeout to 2009-03-16 00:31:47
2009-03-15 19:31:47:930 964 400 AU Setting AU scheduled install time to 2009-03-16 04:00:00
2009-03-15 19:31:52:931 964 11ac Report REPORT EVENT: {F08C1412-0BFB-4326-B1B6-15B9AFB4305D} 2009-03-15 19:31:47:922-0000 1 148 101 {61CA813A-7585-442E-A66B-B0D15CE6BDC0} 1 8000ffff SelfUpdate Failure Software Synchronization Windows Update Client failed to detect with error 0x8000ffff. -
{sigh} Doesn't anyone bother reading log files any more...? The log file doesn't have any issues with time. It appears to be an issue with a file or applet.
The relevant portion is as follows:
-------------------------------------------------------------------------------------------------------------------------------------------
2009-03-15 19:31:05:362 964 11ac Setup Determining whether a new setup handler needs to be downloaded
2009-03-15 19:31:05:363 964 11ac Setup SelfUpdate handler is not found. It will be downloaded
2009-03-15 19:31:05:369 964 11ac Setup Evaluating applicability of setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~x86~~7.4.7000.81"
2009-03-15 19:31:09:355 964 11ac Handler FATAL: UH: 0x8000ffff: EvaluateApplicability failed in CCbs::EvaluateApplicability
2009-03-15 19:31:09:357 964 11ac Setup WARNING: CBS EvaluateApplicability returned error, error = 0x8000FFFF
2009-03-15 19:31:09:357 964 11ac Setup FATAL: Applicability evaluation for setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~x86~~7.4.7000.81" failed, error = 0x8000FFFF
2009-03-15 19:31:09:357 964 11ac Setup FATAL: SelfUpdate check failed, err = 0x8000FFFF
2009-03-15 19:31:09:358 964 11ac Agent * WARNING: Skipping scan, self-update check returned 0x8000FFFF
2009-03-15 19:31:09:396 964 11ac Agent * WARNING: Exit code = 0x8000FFFF
-------------------------------------------------------------------------------------------------------------------------------------------
Now then, have you tried an "in place upgrade"? That is, installing Win 7 on top of itself? From some of the things I've found on similar issues on Vista, one solution was to do the upgrade on top of itself. This will preserve your existing setup, but will install a fresh copy of the OS. I'm guessing something in the WU got corrupted somewhere along the line and that's what's causing the problem. For Vista, there's an option of downloading the Windows Update modules as a stand alone app - but I kinda doubt they'd work with Win 7 just yet. -
I'm too apprehensive to risk running a reinstall. The time is past for installing Win 7 Beta, so I can see it refusing, and leaving me stuck. I'd hate to lose the functionality of it right now. I'll live without the updates if that's the alternative.
The "48 hours ago" thing is a default: it's been saying that all along. I don't think it indicates a specific time when the problem first occurred.
I was hoping there would be a registry entry to delete or a file to download/install. It looks as if there isn't, yet. Maybe this is exactly the sort of thing the Win7 Beta was meant to find and fix, in which case I've done my thing for the test programme. -
Well, I've continued to search, and try to update. Always the same result.
Windows 7 was initially much faster than XP, but is now slowing down badly. I wonder if the two are connected.
Does anyone know if there's a fix yet? It seems that update isn't connecting to the MS server, but I can't see why it wouldn't. -
Well... I dunno what to tell you. I still think you may have something whacked with the Windows Update files - and an "In Place Upgrade" may fix it. An In place upgrade simply refreshes what you've got - without wiping out everything else you've got installed. 30 to 45 minutes and it's back up and running.
My installation of Win 7 seems to be as fast, if not a bit faster than it was originally. There HAVE been a few patches shipped out over the past few months that have improved speed. The Windows Live login helper alone seems to have doubled IE 8's speed when it comes to accessing MS related sites that require a log in. -
I've been posting on a separate thread. I have the same problem with error 8000FFFF. There is no Wusetupv.exe on my machine.
Has anyone found a solution? The only meaningful suggestion I've had is to reinstall Win 7, but I'm worried that will trigger the "time expired" for new installations and leave me high and dry. I'd rather find the specific problem and fix it.
This must be a major concern for Microsoft - it can't be a satisfactory way for the updater to behave. -
Still haven't found a solution yet, Keith. I'll post some things to try on your original thread.
MowGreen MVP Data Center Management - Update Services Consumer Security -
Keith ... in your first post you mention Avast being installed. In a later post you mention Avira. Was that just a mistake or was the AV switched from Avast to Avira ?
Updates are failing because the system is 'stuck' installing the latest release of the Windows Update Agent [WUA], specifically, the ActiveX component, as Wolfie has already pointed out:
2009-03-15 19:29:14:757 964 11ac Setup Client version: Core: 7.3.7000.0 Aux: 7.3.7000.0
2009-03-15 19:31:47:110 964 11ac Setup Determining whether a new setup handler needs to be downloaded
2009-03-15 19:31:47:110 964 11ac Setup SelfUpdate handler is not found. It will be downloaded
2009-03-15 19:31:47:111 964 11ac Setup Evaluating applicability of setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~x86~~7.4.7000.81"
2009-03-15 19:31:47:899 964 11ac Handler FATAL: UH: 0x8000ffff: EvaluateApplicability failed in CCbs::EvaluateApplicability
2009-03-15 19:31:47:921 964 11ac Setup WARNING: CBS EvaluateApplicability returned error, error = 0x8000FFFF
2009-03-15 19:31:47:921 964 11ac Setup FATAL: Applicability evaluation for setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~x86~~7.4.7000.81" failed, error = 0x8000FFFF
2009-03-15 19:31:47:922 964 11ac Setup FATAL: SelfUpdate check failed, err = 0x8000FFFF
2009-03-15 19:31:47:922 964 11ac Agent * WARNING: Skipping scan, self-update check returned 0x8000FFFF
2009-03-15 19:31:47:928 964 400 AU # WARNING: Search callback failed, result = 0x8000FFFF
2009-03-15 19:31:47:928 964 400 AU # WARNING: Failed to find updates with error code 8000FFFF
8000FFFF signifies a catastrophic error, which is not really useful. Either the system is unable to evaluate the applicability of the WUA due to restrictions caused by the installed AV or there's file corruption in WinSxS that is preventing the evaluation.
If Wusetupv.exe is not present, there's a strong likelihood that the installed AV is preventing it from being downloaded.
Renaming/deleting the SoftwareDistribution folder accomplishes nothing in this situation except deleting the updating history stored in DataStore.ebd. What's needed is a method to force the installation of the WUA.
You can try running sfc /scannow from an Elevated Command Prompt or do an 'inplace' upgrade and hope the system reverts to the original version of the WUA, 7.3.7000.0. The first solution rarely resolves the error but, give it a shot.
Two questions:
1) Are there any WUCLIENT-SelfUpdate___.cat or .mum files in WINDOWS\servicing\Packages ?
2) In the servicing\Sessions subfolder, are there any .xml files Modified on 2/18 ?
Just checked the ones on my system and they appear to log the WUA's package staging
<?xml version='1.0' encoding='utf-8'?>
<Session version="1.0" id="29988518_2170731486" client="WindowsUpdateAgent" options="560" currentPhase="1" lastSuccessfulState="Complete" pendingFollower="false" retry="false" Started="2009/02/24/09:37:05" Complete="2009/02/24/09:37:10" status="0x0">
<Tasks>
<Phase seq="1">
<package id="WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~x86~~7.4.7000.81" name="WindowsUpdateClient-SelfUpdate-ActiveX-Package" targetState="Staged" options="4"/>
</Phase>
</Tasks>
<Actions>
<Phase seq="1" rebootRequired="false" Resolved="2009/02/24/09:37:08" Staged="2009/02/24/09:37:08">
<Resolve package="WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~x86~~7.4.7000.81" update="ActiveX"/>
<Stage package="WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~x86~~7.4.7000.81" update="ActiveX"/>
</Phase>
</Actions>
</Session>
At the very least, we'll see if the WUA was actually downloaded or not by the system.
BTW, does the WindowsUpdate.log go back to February ? If it does, then suggest you check around the middle of the month,
maybe even 2/18, as that was around the time the latest release of the WUA came out automatically via Windows Update for Win7. That's when the 8000FFFF error should have first appeared.
MowGreen MVP Data Center Management - Update Services Consumer Security -
I tried the first step: stopped Avast (it's that, not Avira).
Then opened an Admin CMD window and typed: sfc /scannow
The response was
"Beginning system scan. This process will take some time."
followed almost immediately by
"Windows Resource Protection could not perform the requested operation."
and back to the C:\Windows\system32 prompt.
There are 370 items in C:\Windows\servicing\Packages but none of them have WUCLIENT in the name.
There are no .xml files in servicing\Sessions that show Feb 18 as the date. A snip of the folder contents (below, if I've linked it correctly) shows the dates are all December 12 and 13, January 14, and March 31.
<img src="http://www.kirbycane.plus.com/servicing_sessions.jpg" />
The WindowsUpdate.log earliest entry is 2009-02-09
When I first reported the problem, there was a log entry that said "Most recent check for updates: 18/2/2009 at 23:24".
That log has gone now - it disappeared with the renaming of SoftwareDistribution to SDold above. -
I tried the first step: stopped Avast (it's that, not Avira).
Then the WUA packages were never staged for download. Since the WindowsUpdate.log goes back to 2009-02-09, then it should show the first attempt at downloading the WUA and the should include the first instance of the 8000FFFF error code.
Then opened an Admin CMD window and typed: sfc /scannow
The response was
"Beginning system scan. This process will take some time."
followed almost immediately by
"Windows Resource Protection could not perform the requested operation."
and back to the C:\Windows\system32 prompt.
There are 370 items in C:\Windows\servicing\Packages but none of them have WUCLIENT in the name.
There are no .xml files in servicing\Sessions that show Feb 18 as the date. A snip of the folder contents (below, if I've linked it correctly) shows the dates are all December 12 and 13, January 14, and March 31.
<img src="http://www.kirbycane.plus.com/servicing_sessions.jpg" />
The WindowsUpdate.log earliest entry is 2009-02-09
When I first reported the problem, there was a log entry that said "Most recent check for updates: 18/2/2009 at 23:24".
That log has gone now - it disappeared with the renaming of SoftwareDistribution to SDold above.
Open it, click Edit, Find, enter 8000FFFF in the Find what: field and then click Find Next.
Please include the entries just prior to and after the first instance of 8000FFFF up to where it shows
WARNING: Failed to find updates with error code 8000FFFF
The Sessions.xml appears to include all of the .xml files that should be present in the Sessions subfolder.
Key word being should.
Sessions.xml is also located in WINDOWS\servicing\Sessions
Right click Sessions.xml, choose Edit.
Scroll all the way to the bottom and copy&paste all entries that were created today, 3/31, please .
In the meantime, I'll see if I can come up with a URL to the latest version of the WUA that doesn't involve downloading .cab files and installing them using WUSetupV.exe.
MowGreen MVP Data Center Management - Update Services Consumer Security -
Thanks for your patience! Here's the WindowsUpdate.log from a fair way before to just after the 8000FFFF error on Feb 11.
2009-02-10 22:27:04:574 976 fa8 Misc =========== Logging initialized (build: 7.3.7000.0, tz: -0000) ===========
2009-02-10 22:27:04:591 976 fa8 Misc = Process: C:\Windows\system32\svchost.exe
2009-02-10 22:27:04:591 976 fa8 Misc = Module: c:\windows\system32\wuaueng.dll
2009-02-10 22:27:04:574 976 fa8 Service *************
2009-02-10 22:27:04:593 976 fa8 Service ** START ** Service: Service startup
2009-02-10 22:27:04:593 976 fa8 Service *********
2009-02-10 22:27:04:875 976 fa8 Agent * WU client version 7.3.7000.0
2009-02-10 22:27:04:876 976 fa8 Agent * Base directory: C:\Windows\SoftwareDistribution
2009-02-10 22:27:04:880 976 fa8 Agent * Access type: No proxy
2009-02-10 22:27:04:890 976 fa8 Agent * Network state: Connected
2009-02-10 22:27:50:996 976 fa8 Agent *********** Agent: Initializing Windows Update Agent ***********
2009-02-10 22:27:50:996 976 fa8 Agent *********** Agent: Initializing global settings cache ***********
2009-02-10 22:27:50:996 976 fa8 Agent * WSUS server: <NULL>
2009-02-10 22:27:50:996 976 fa8 Agent * WSUS status server: <NULL>
2009-02-10 22:27:50:996 976 fa8 Agent * Target group: (Unassigned Computers)
2009-02-10 22:27:50:996 976 fa8 Agent * Windows Update access disabled: No
2009-02-10 22:27:51:019 976 fa8 DnldMgr Download manager restoring 0 downloads
2009-02-10 22:27:51:031 976 fa8 AU ########### AU: Initializing Automatic Updates ###########
2009-02-10 22:27:51:033 976 fa8 AU # Approval type: Scheduled (User preference)
2009-02-10 22:27:51:033 976 fa8 AU # Scheduled install day/time: Every day at 3:00
2009-02-10 22:27:51:033 976 fa8 AU # Auto-install minor updates: Yes (User preference)
2009-02-10 22:27:51:033 976 fa8 AU # Will interact with non-admins (Non-admins are elevated (User preference))
2009-02-10 22:27:51:033 976 fa8 AU # Will display featured updates notifications (User preference)
2009-02-10 22:27:51:085 976 fa8 AU Setting AU scheduled install time to 2009-02-11 03:00:00
2009-02-10 22:27:51:085 976 fa8 AU Initializing featured updates
2009-02-10 22:27:51:085 976 fa8 AU Found 0 cached featured updates
2009-02-10 22:27:51:925 976 fa8 Report *********** Report: Initializing static reporting data ***********
2009-02-10 22:27:51:925 976 fa8 Report * OS Version = 6.1.7000.0.0.65792
2009-02-10 22:27:51:925 976 fa8 Report * OS Product Type = 0x00000001
2009-02-10 22:27:51:984 976 fa8 Report * Computer Brand = P4iCB
2009-02-10 22:27:51:984 976 fa8 Report * Computer Model = P4 COMBO
2009-02-10 22:27:51:996 976 fa8 Report * Bios Revision = P1.60
2009-02-10 22:27:51:996 976 fa8 Report * Bios Name = Default System BIOS
2009-02-10 22:27:51:996 976 fa8 Report * Bios Release Date = 2005-01-24T00:00:00
2009-02-10 22:27:51:996 976 fa8 Report * Locale ID = 2057
2009-02-10 22:27:52:021 976 fa8 AU Successfully wrote event for AU health state:0
2009-02-10 22:27:52:039 976 fa8 AU AU finished delayed initialization
2009-02-11 03:00:10:035 976 fa8 AU Forced install timer expired for scheduled install
2009-02-11 03:00:10:064 976 fa8 AU UpdateDownloadProperties: 0 download(s) are still in progress.
2009-02-11 03:00:10:128 976 fa8 AU Setting AU scheduled install time to 2009-02-12 03:00:00
2009-02-11 12:59:36:134 976 fa8 AU #############
2009-02-11 12:59:36:162 976 fa8 AU ## START ## AU: Search for updates
2009-02-11 12:59:36:162 976 fa8 AU #########
2009-02-11 12:59:36:421 976 fa8 AU <<## SUBMITTED ## AU: Search for updates [CallId = {B874C524-6477-403E-960F-63238267A0AF}]
2009-02-11 12:59:36:445 976 f5c Agent *************
2009-02-11 12:59:36:445 976 f5c Agent ** START ** Agent: Finding updates [CallerId = AutomaticUpdates]
2009-02-11 12:59:36:445 976 f5c Agent *********
2009-02-11 12:59:36:445 976 f5c Agent * Online = Yes; Ignore download priority = No
2009-02-11 12:59:36:445 976 f5c Agent * Criteria = "IsInstalled=0 and DeploymentAction='Installation' or IsPresent=1 and DeploymentAction='Uninstallation' or IsInstalled=1 and DeploymentAction='Installation' and RebootRequired=1 or IsInstalled=0 and DeploymentAction='Uninstallation' and RebootRequired=1"
2009-02-11 12:59:36:449 976 f5c Agent * ServiceID = {9482F4B4-E343-43B6-B170-9A65BC822C77} Windows Update
2009-02-11 12:59:36:449 976 f5c Agent * Search Scope = {Machine}
2009-02-11 12:59:36:464 976 f5c Setup Checking for agent SelfUpdate
2009-02-11 12:59:36:498 976 f5c Setup Client version: Core: 7.3.7000.0 Aux: 7.3.7000.0
2009-02-11 12:59:36:615 976 f5c Misc Validating signature for C:\Windows\SoftwareDistribution\WuRedir_prerelease\9482F4B4-E343-43B6-B170-9A65BC822C77\win7wuredir.cab:
2009-02-11 12:59:36:785 976 f5c Misc Microsoft signed: Yes
2009-02-11 12:59:50:933 976 f5c Misc Validating signature for C:\Windows\SoftwareDistribution\WuRedir_prerelease\9482F4B4-E343-43B6-B170-9A65BC822C77\win7wuredir.cab:
2009-02-11 12:59:50:941 976 f5c Misc Microsoft signed: Yes
2009-02-11 12:59:50:955 976 f5c Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
2009-02-11 12:59:50:972 976 f5c Misc Microsoft signed: Yes
2009-02-11 12:59:51:154 976 f5c Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
2009-02-11 12:59:51:166 976 f5c Misc Microsoft signed: Yes
2009-02-11 12:59:51:230 976 f5c Setup Skipping SelfUpdate check based on the /SKIP directive in wuident
2009-02-11 12:59:51:230 976 f5c Setup SelfUpdate check completed. SelfUpdate is NOT required.
2009-02-11 12:59:52:171 976 f5c Misc Validating signature for C:\Windows\SoftwareDistribution\WuRedir_prerelease\9482F4B4-E343-43B6-B170-9A65BC822C77\win7wuredir.cab:
2009-02-11 12:59:52:179 976 f5c Misc Microsoft signed: Yes
2009-02-11 12:59:52:361 976 f5c Misc Validating signature for C:\Windows\SoftwareDistribution\WuRedir_prerelease\9482F4B4-E343-43B6-B170-9A65BC822C77\win7wuredir.cab:
2009-02-11 12:59:52:369 976 f5c Misc Microsoft signed: Yes
2009-02-11 12:59:52:380 976 f5c PT +++++++++++ PT: Synchronizing server updates +++++++++++
2009-02-11 12:59:52:382 976 f5c PT + ServiceId = {9482F4B4-E343-43B6-B170-9A65BC822C77}, Server URL = https://beta.update.microsoft.com/v6/ClientWebService/client.asmx
2009-02-11 13:00:06:256 976 f5c Driver DriverUtil marking {2E947818-8771-4A6F-B5B4-DEBE0C7E7FBD}.101 e_detectionStateInstallable
2009-02-11 13:00:06:258 976 f5c Driver Matched driver to device PCI\VEN_10EC&DEV_8139&SUBSYS_81391849&REV_10
2009-02-11 13:00:06:258 976 f5c Driver Status: 0x180200a, ProblemNumber: 00000000
2009-02-11 13:00:06:258 976 f5c Driver Calculated driver attributes as 0x00000000
2009-02-11 13:00:06:258 976 f5c Driver DriverUtil marking {24E23AA7-EC29-4731-80CF-A166742A1810}.100 e_detectionStateInstallable
2009-02-11 13:00:06:258 976 f5c Driver Matched driver to device PCI\VEN_10DE&DEV_02E0&SUBSYS_00000000&REV_A2
2009-02-11 13:00:06:258 976 f5c Driver Status: 0x180200a, ProblemNumber: 00000000
2009-02-11 13:00:06:258 976 f5c Driver Calculated driver attributes as 0x00000000
2009-02-11 13:00:06:258 976 f5c Driver DriverUtil marking {C06B56BD-2128-494A-962F-3BEC48B800C7}.101 e_detectionStateInstallable
2009-02-11 13:00:06:258 976 f5c Driver Matched driver to device HID\VID_06A3&PID_0464&REV_0110
2009-02-11 13:00:06:258 976 f5c Driver Status: 0x180200a, ProblemNumber: 00000000
2009-02-11 13:00:06:258 976 f5c Driver Calculated driver attributes as 0x00000000
2009-02-11 13:00:06:258 976 f5c Driver DriverUtil marking {B3CB9AC2-9B25-444D-B54C-FB697B2E1BB1}.101 e_detectionStateInstallable
2009-02-11 13:00:06:258 976 f5c Driver Matched driver to device USB\VID_0A12&PID_0001&REV_1958
2009-02-11 13:00:06:258 976 f5c Driver Status: 0x180600a, ProblemNumber: 00000000
2009-02-11 13:00:06:260 976 f5c Driver Calculated driver attributes as 0x00000000
2009-02-11 13:00:06:260 976 f5c Driver DriverUtil marking {109E7CC5-7CE5-4129-A068-5DDEADE85DB9}.101 e_detectionStateInstallable
2009-02-11 13:00:06:260 976 f5c Driver Matched driver to device USB\VID_06A3&PID_0464&REV_0110
2009-02-11 13:00:06:260 976 f5c Driver Status: 0x180600a, ProblemNumber: 00000000
2009-02-11 13:00:06:260 976 f5c Driver Calculated driver attributes as 0x00000000
2009-02-11 13:00:08:135 976 f5c Handler FATAL: UH: 0x8000ffff: EvaluateApplicability failed in CCbs::EvaluateApplicability
2009-02-11 13:00:08:135 976 f5c Agent WARNING: Failed to evaluate Installed rule, updateId = {16BF8D76-6649-4FA4-B611-C5C1FF6C6B1F}.100, hr = 8000FFFF
2009-02-11 13:00:08:323 976 f5c Handler FATAL: UH: 0x8000ffff: EvaluateApplicability failed in CCbs::EvaluateApplicability
2009-02-11 13:00:08:338 976 f5c Agent WARNING: Failed to evaluate Installable rule, updateId = {16BF8D76-6649-4FA4-B611-C5C1FF6C6B1F}.100, hr = 8000FFFF
2009-02-11 13:00:08:536 976 f5c Handler FATAL: UH: 0x8000ffff: EvaluateApplicability failed in CCbs::EvaluateApplicability
2009-02-11 13:00:08:581 976 f5c Misc Validating signature for C:\Windows\SoftwareDistribution\WuRedir_prerelease\9482F4B4-E343-43B6-B170-9A65BC822C77\win7wuredir.cab:
2009-02-11 13:00:08:594 976 f5c Misc Microsoft signed: Yes
2009-02-11 13:00:08:778 976 f5c Misc Validating signature for C:\Windows\SoftwareDistribution\WuRedir_prerelease\9482F4B4-E343-43B6-B170-9A65BC822C77\win7wuredir.cab:
2009-02-11 13:00:08:791 976 f5c Misc Microsoft signed: Yes
2009-02-11 13:00:08:811 976 f5c PT +++++++++++ PT: Synchronizing extended update info +++++++++++
2009-02-11 13:00:08:811 976 f5c PT + ServiceId = {9482F4B4-E343-43B6-B170-9A65BC822C77}, Server URL = https://beta.update.microsoft.com/v6/ClientWebService/client.asmx
2009-02-11 13:00:09:073 976 f5c Agent * Added update {C06B56BD-2128-494A-962F-3BEC48B800C7}.101 to search result
2009-02-11 13:00:09:073 976 f5c Agent * Added update {109E7CC5-7CE5-4129-A068-5DDEADE85DB9}.101 to search result
2009-02-11 13:00:09:073 976 f5c Agent * Added update {B3CB9AC2-9B25-444D-B54C-FB697B2E1BB1}.101 to search result
2009-02-11 13:00:09:073 976 f5c Agent * Added update {2E947818-8771-4A6F-B5B4-DEBE0C7E7FBD}.101 to search result
2009-02-11 13:00:09:073 976 f5c Agent * Added update {24E23AA7-EC29-4731-80CF-A166742A1810}.100 to search result
2009-02-11 13:00:09:073 976 f5c Agent * Found 5 updates and 15 categories in search; evaluated appl. rules of 145 out of 149 deployed entities
2009-02-11 13:00:09:088 976 f5c Agent *********
2009-02-11 13:00:09:088 976 f5c Agent ** END ** Agent: Finding updates [CallerId = AutomaticUpdates]
2009-02-11 13:00:09:088 976 f5c Agent *************
_______________________________________________________________________________________________
Sessions.xml entries: I'm intrigued - it shows last successful being on 2009/01/14 and the very next as 2009/03/31 with 8000FFFF. Here are the last few lines of the file:
<Session version="1.0" id="29980244_3773081729" client="WindowsUpdateAgent" options="816" currentPhase="1" lastSuccessfulState="Complete" pendingFollower="false" retry="true" Started="2009/01/14/14:32:09" Complete="2009/01/14/14:36:25" status="0x0">
<Tasks>
<Phase seq="1">
<package id="Package_for_KB961367~31bf3856ad364e35~x86~~6.1.1.1" name="" targetState="Installed" options="4"/>
</Phase>
</Tasks>
<Actions>
<Phase seq="1" rebootRequired="true" Staged="2009/01/14/14:32:10" Installed="2009/01/14/14:32:14" ShutdownStart="2009/01/14/14:34:35" ShutdownFinish="2009/01/14/14:34:51" Startup="2009/01/14/14:36:14" StartupFinish="2009/01/14/14:36:25">
<Stage package="Package_1_for_KB961367~31bf3856ad364e35~x86~~6.1.1.1" update="961367-1_neutral_LDR"/>
<Stage package="Package_1_for_KB961367~31bf3856ad364e35~x86~~6.1.1.1" update="961367-2_neutral_GDR"/>
<Stage package="Package_1_for_KB961367~31bf3856ad364e35~x86~~6.1.1.1" update="961367-3_neutral_LDR"/>
<Stage package="Package_1_for_KB961367~31bf3856ad364e35~x86~~6.1.1.1" update="961367-4_neutral_GDR"/>
<Stage package="Package_1_for_KB961367~31bf3856ad364e35~x86~~6.1.1.1" update="961367-5_neutral_LDR"/>
<Stage package="Package_1_for_KB961367~31bf3856ad364e35~x86~~6.1.1.1" update="961367-6_neutral_GDR"/>
<Stage package="Package_1_for_KB961367~31bf3856ad364e35~x86~~6.1.1.1" update="961367-7_neutral_LDR"/>
<Stage package="Package_1_for_KB961367~31bf3856ad364e35~x86~~6.1.1.1" update="961367-8_neutral_GDR"/>
<Stage package="Package_2_for_KB961367~31bf3856ad364e35~x86~~6.1.1.1" update="961367-9_neutral_LDR"/>
<Stage package="Package_2_for_KB961367~31bf3856ad364e35~x86~~6.1.1.1" update="961367-10_neutral_GDR"/>
<Install package="Package_1_for_KB961367~31bf3856ad364e35~x86~~6.1.1.1" update="961367-2_neutral_GDR"/>
<Install package="Package_1_for_KB961367~31bf3856ad364e35~x86~~6.1.1.1" update="961367-4_neutral_GDR"/>
<Install package="Package_1_for_KB961367~31bf3856ad364e35~x86~~6.1.1.1" update="961367-6_neutral_GDR"/>
<Install package="Package_1_for_KB961367~31bf3856ad364e35~x86~~6.1.1.1" update="961367-8_neutral_GDR"/>
<Install package="Package_2_for_KB961367~31bf3856ad364e35~x86~~6.1.1.1" update="961367-10_neutral_GDR"/>
</Phase>
</Actions>
</Session>
<Session version="1.0" id="29995403_3058079165" client="WindowsUpdateAgent" options="816" currentPhase="1" lastSuccessfulState="Started" pendingFollower="false" retry="true" Started="2009/03/31/00:03:33" Complete="2009/03/31/00:03:33" status="0x8000ffff">
<Tasks>
<Phase seq="1">
<package id="Package_for_KB962921~31bf3856ad364e35~x86~~6.1.1.0" name="KB962921" targetState="Installed" options="4"/>
</Phase>
</Tasks>
<Actions>
<Phase seq="1" rebootRequired="false">
</Phase>
</Actions>
</Session>
</Sessions>
___________________________________________________________________________________________
Looking at the first one, it seems the hiccup came right after "updating USB VID". Should I try uninstalling the USB webcam, to see if that's the cause of the problem? -
I unplugged and uninstalled the webcam. That made no difference.
I notice in ReportingEvents.log it has these lines:
{18F6FFEB-CD1C-449D-A006-184742F35C2F} 2009-03-31 20:29:42:026+0100 1 149 102 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Failure Software Synchronization Unable to Connect: Windows is unable to connect to the automatic updates service and therefore cannot download and install updates according to the set schedule. Windows will continue to try to establish a connection.
{A5101B06-2E5C-4375-9F96-BF0E400FCDFD} 2009-03-31 22:35:43:943+0100 1 148 101 {61CA813A-7585-442E-A66B-B0D15CE6BDC0} 1 8000ffff SelfUpdate Failure Software Synchronization Windows Update Client failed to detect with error 0x8000ffff.
{F44BEAF0-F6CE-4B49-A7BC-A9747F2C95EF} 2009-04-01 01:35:33:758+0100 1 148 101 {61CA813A-7585-442E-A66B-B0D15CE6BDC0} 1 8000ffff SelfUpdate Failure Software Synchronization Windows Update Client failed to detect with error 0x8000ffff.
{FCDA7DD4-B240-4426-81D9-9CC0D25C753C} 2009-04-01 01:35:39:436+0100 1 148 101 {61CA813A-7585-442E-A66B-B0D15CE6BDC0} 1 8000ffff SelfUpdate Failure Software Synchronization Windows Update Client failed to detect with error 0x8000ffff.
I can't see why Windows is unable to connect to the automatic updates service. The only firewall on here is the Windows one (ZoneAlarm won't install with Win7). I'd turned off Avast, so that wasn't it. The modem/router isn't set to block Windows, as far as I recall. -
I just went into the SDold folder (the previous SoftwareDistribution files), and browsed ReportingEvents.log in there.
I can see the precise instance of the first 8000FFFF:
{AD49ACF2-04DC-4D5C-9BCC-6C8BAE89D7B9} 2009-02-20 02:08:58:166-0000 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 ChkWuDrv Success Software Synchronization Windows Update Client successfully detected 0 updates.
{3B0EAF18-640B-4A71-8E3D-6A8BA90F5711} 2009-02-20 02:09:03:575-0000 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 ChkWuDrv Success Software Synchronization Windows Update Client successfully detected 0 updates.
{03072AC0-0425-4C51-8640-3DDA55D7C12E} 2009-02-20 02:09:09:862-0000 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 ChkWuDrv Success Software Synchronization Windows Update Client successfully detected 0 updates.
{9D032A06-1122-475B-97A8-68B2CB7CB6B2} 2009-02-20 02:09:21:303-0000 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 ChkWuDrv Success Software Synchronization Windows Update Client successfully detected 1 updates.
{C553A07A-9955-4F8C-9943-8A8E5054AAE4} 2009-02-20 02:09:25:673-0000 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 ChkWuDrv Success Software Synchronization Windows Update Client successfully detected 0 updates.
{AB5E17B9-821F-4972-87B6-FE83D0653995} 2009-02-20 02:21:13:928-0000 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 ChkWuDrv Success Software Synchronization Windows Update Client successfully detected 1 updates.
{5FD77E96-B982-4AF5-A047-DF724FAA4453} 2009-02-20 02:21:25:727-0000 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 ChkWuDrv Success Software Synchronization Windows Update Client successfully detected 0 updates.
{8D486CEF-F3DA-4369-90EC-7039FD41B0E2} 2009-02-20 02:21:30:749-0000 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 ChkWuDrv Success Software Synchronization Windows Update Client successfully detected 0 updates.
{6429E13D-E94F-43FE-B054-B899F5634DAD} 2009-02-20 02:21:35:833-0000 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 ChkWuDrv Success Software Synchronization Windows Update Client successfully detected 0 updates.
{07796464-6074-4EF1-B00A-881485969532} 2009-02-20 02:21:46:482-0000 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 ChkWuDrv Success Software Synchronization Windows Update Client successfully detected 1 updates.
{2AF7D900-56F3-4D77-AAA7-F20D79C5375A} 2009-02-20 02:21:50:557-0000 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 ChkWuDrv Success Software Synchronization Windows Update Client successfully detected 0 updates.
{60956D66-209A-4AAC-B726-A095DAACCBB8} 2009-02-20 05:32:20:425-0000 1 148 101 {61CA813A-7585-442E-A66B-B0D15CE6BDC0} 1 8000ffff SelfUpdate Failure Software Synchronization Windows Update Client failed to detect with error 0x8000ffff.
{8244ACF2-A275-4D7C-9F98-9090AEFBDAC9} 2009-02-20 10:32:46:895-0000 1 148 101 {61CA813A-7585-442E-A66B-B0D15CE6BDC0} 1 8000ffff SelfUpdate Failure Software Synchronization Windows Update Client failed to detect with error 0x8000ffff.
{52909CBE-17C0-4327-BD42-958A9B650D58} 2009-02-20 15:33:16:297-0000 1 148 101 {61CA813A-7585-442E-A66B-B0D15CE6BDC0} 1 8000ffff SelfUpdate Failure Software Synchronization Windows Update Client failed to detect with error 0x8000ffff.
{1B03BF63-125F-4431-AF24-8933AD52F444} 2009-02-20 20:33:44:873-0000 1 148 101 {61CA813A-7585-442E-A66B-B0D15CE6BDC0} 1 8000ffff SelfUpdate Failure Software Synchronization Windows Update Client failed to detect with error 0x8000ffff.
{3D5271F4-B38B-4572-ACF3-C2F8155BD7D5} 2009-02-21 00:31:31:081-0000 1 202 102 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Content Install Reboot completed.
{E41017FF-B94F-4DD3-875F-9080692B2210} 2009-02-21 01:34:08:791-0000 1 148 101 {61CA813A-7585-442E-A66B-B0D15CE6BDC0} 1 8000ffff SelfUpdate Failure Software Synchronization Windows Update Client failed to detect with error 0x8000ffff.
{E3E377F8-1ED9-4862-8E81-105D6E5BC6D0} 2009-02-21 06:34:38:487-0000 1 148 101 {61CA813A-7585-442E-A66B-B0D15CE6BDC0} 1 8000ffff SelfUpdate Failure Software Synchronization Windows Update Client failed to detect with error 0x8000ffff.
{4DC50B70-B96F-4666-8F6B-6A2D136B5D47} 2009-02-21 11:35:03:208-0000 1 148 101 {61CA813A-7585-442E-A66B-B0D15CE6BDC0} 1 8000ffff SelfUpdate Failure Software Synchronization Windows Update Client failed to detect with error 0x8000ffff.
{B39F8665-40C1-45D4-9DD2-B74E0784FD90} 2009-02-21 16:35:28:918-0000 1 148 101 {61CA813A-7585-442E-A66B-B0D15CE6BDC0} 1 8000ffff SelfUpdate Failure Software Synchronization Windows Update Client failed to detect with error 0x8000ffff.
{5F46FDDF-D62F-4F0F-9C83-DA8AEC04A49F} 2009-02-21 19:29:23:110-0000 1 149 102 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Failure Software Synchronization Unable to Connect: Windows is unable to connect to the automatic updates service and therefore cannot download and install updates according to the set schedule. Windows will continue to try to establish a connection.
{F25A7106-78B4-455D-B9DD-3FF23FFB950C} 2009-02-21 21:35:54:108-0000 1 148 101 {61CA813A-7585-442E-A66B-B0D15CE6BDC0} 1 8000ffff SelfUpdate Failure Software Synchronization Windows Update Client failed to detect with error 0x8000ffff.
{3E6F4934-EA96-4AFF-BFD2-96E63FE58150} 2009-02-22 02:36:26:700-0000 1 148 101 {61CA813A-7585-442E-A66B-B0D15CE6BDC0} 1 8000ffff SelfUpdate Failure Software Synchronization Windows Update Client failed to detect with error 0x8000ffff.
{E91A48F6-9119-4389-91C6-3B91BB755C75} 2009-02-22 07:36:57:684-0000 1 148 101 {61CA813A-7585-442E-A66B-B0D15CE6BDC0} 1 8000ffff SelfUpdate Failure Software Synchronization Windows Update Client failed to detect with error 0x8000ffff.
{121F3698-878A-4B94-B2D9-9ED737646A14} 2009-02-22 12:37:30:721-0000 1 148 101 {61CA813A-7585-442E-A66B-B0D15CE6BDC0} 1 8000ffff SelfUpdate Failure Software Synchronization Windows Update Client failed to detect with error 0x8000ffff.
{1334F6CE-A1AA-48A0-8C0D-922C8352D4E4} 2009-02-22 17:37:54:437-0000 1 148 101 {61CA813A-7585-442E-A66B-B0D15CE6BDC0} 1 8000ffff SelfUpdate Failure Software Synchronization Windows Update Client failed to detect with error 0x8000ffff.
{B7B708EC-695A-4051-A3AE-344410093030} 2009-02-22 22:38:19:951-0000 1 148 101 {61CA813A-7585-442E-A66B-B0D15CE6BDC0} 1 8000ffff SelfUpdate Failure Software Synchronization Windows Update Client failed to detect with error 0x8000ffff.
{E28AE2C4-A4CB-45A6-B487-773DB0C3E03C} 2009-02-23 03:38:56:931-0000 1 148 101 {61CA813A-7585-442E-A66B-B0D15CE6BDC0} 1 8000ffff SelfUpdate Failure Software Synchronization Windows Update Client failed to detect with error 0x8000ffff.
{7DBC9639-BD9F-4403-9754-E501AC043FBB} 2009-02-23 08:41:36:070-0000 1 148 101 {61CA813A-7585-442E-A66B-B0D15CE6BDC0} 1 8000ffff SelfUpdate Failure Software Synchronization Windows Update Client failed to detect with error 0x8000ffff.
{138FB5A5-8DD4-4C9A-BAA4-CE8CB053CFA5} 2009-02-23 13:42:18:411-0000 1 148 101 {61CA813A-7585-442E-A66B-B0D15CE6BDC0} 1 8000ffff SelfUpdate Failure Software Synchronization Windows Update Client failed to detect with error 0x8000ffff.
{DD08B2BD-123F-45B2-9FC4-0A25F129D2E6} 2009-02-23 18:42:44:810-0000 1 148 101 {61CA813A-7585-442E-A66B-B0D15CE6BDC0} 1 8000ffff SelfUpdate Failure Software Synchronization Windows Update Client failed to detect with error 0x8000ffff.
{35CCE569-89A6-4AE9-B7F4-7FCCF5FD8C04} 2009-02-23 19:29:24:157-0000 1 149 102 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Failure Software Synchronization Unable to Connect: Windows is unable to connect to the automatic updates service and therefore cannot download and install updates according to the set schedule. Windows will continue to try to establish a connection.
{477D3B1D-556B-4B16-8C10-4358EB91B4EE} 2009-02-23 22:29:43:330-0000 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 ChkWuDrv Success Software Synchronization Windows Update Client successfully detected 1 updates.
{374C7B2D-3141-4526-B2E2-EF0A8A7709C6} 2009-02-23 23:43:08:083-0000 1 148 101 {61CA813A-7585-442E-A66B-B0D15CE6BDC0} 1 8000ffff SelfUpdate Failure Software Synchronization Windows Update Client failed to detect with error 0x8000ffff.
{819C80BF-04D3-4753-826A-D032141602C4} 2009-02-24 04:43:35:512-0000 1 148 101 {61CA813A-7585-442E-A66B-B0D15CE6BDC0} 1 8000ffff SelfUpdate Failure Software Synchronization Windows Update Client failed to detect with error 0x8000ffff.
{50F7F36C-EB5F-4222-962F-F67260435823} 2009-02-24 09:43:59:975-0000 1 148 101 {61CA813A-7585-442E-A66B-B0D15CE6BDC0} 1 8000ffff SelfUpdate Failure Software Synchronization Windows Update Client failed to detect with error 0x8000ffff.
{A543EFA6-C8A5-42AA-9D28-9512222D96A7} 2009-02-24 14:44:25:016-0000 1 148 101 {61CA813A-7585-442E-A66B-B0D15CE6BDC0} 1 8000ffff SelfUpdate Failure Software Synchronization Windows Update Client failed to detect with error 0x8000ffff.
{7BCCB477-6A46-46AD-A6FA-5717A94034B2} 2009-02-24 19:44:52:448-0000 1 148 101 {61CA813A-7585-442E-A66B-B0D15CE6BDC0} 1 8000ffff SelfUpdate Failure Software Synchronization Windows Update Client failed to detect with error 0x8000ffff.
That shows that the problem happened between 2am and 5am GMT (which was also local time here) on Feb 20. There is no way I was at the computer at that time, so whatever happened was "automatic".
There was then one success on Feb 21, and everything failed thereafter.
This is too deep for me to know whether those are significant or not. -
I've been posting on a separate thread. I have the same problem with error 8000FFFF. There is no Wusetupv.exe on my machine.
Hi
Has anyone found a solution? The only meaningful suggestion I've had is to reinstall Win 7, but I'm worried that will trigger the "time expired" for new installations and leave me high and dry. I'd rather find the specific problem and fix it.
This must be a major concern for Microsoft - it can't be a satisfactory way for the updater to behave.
I merged both of these threads concerning this same Windows Update fails with error code 8000FFFF issue.
Hopefully, this will make it easier to track the progress.
Thank You for testing Windows 7 Beta
Ronnie Vernon MVP
Forum Moderator -
Let's do a little rummaging around, Keith ... I think the driver downloaded just happened to coincide with the updating failure. Open the registry editor and navigate to
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing
*Right* click Component Based Servicing and choose Permissions.
Check that these are the Permissions for -
SYSTEM Read
Adminstrators (Win7-PC\Administrators) Read
Users (Win7-PC\Users) Read
TrustedInstaller Full Control; Read
Under Component Based Servicing, expand ApplicabilityEvaluationCache
At the bottom of the list are there any WUClient entries listed ?
If yes, what are they ?
Now expand UpdateDetect
Are these listed ?
Adm
Aux
Core
UI
If they are, in the right frame there should be Value Names listed under Default.
*Right* click them and choose Modify.
Copy the Value Name and paste them into your reply.
DO NOT make any registry changes at the present time. Click Cancel to close the window.
Please check this subkey
HKEY_LOCAL_MACHINE\COMPONENTS
Click on COMPONENTS
Are any of these ValueName listed in the right frame ?
PendingXmlIndentifier
NextQueueEntryIndex
AdvancedInstallersNeedResolving
IF the answer is yes, then right click and delete them.
Close the registry editor.
Open the Services console or, right click Computer on the Desktop, choose Manage.
Expand Services and Applications and then open Services.
Please check these Services and their Startup type.
Also, be sure that services listed as Automatic are in a running state.
Background Intelligent Transfer Service Default setting: Manual (can be set to Manual or Automatic)
DCOM Server Process Launcher Default: Automatic
Interactive Services Detection Default: Manual
Remote Procedure Call (RPC) Default: Automatic
Remote Registry Default: Manual
Windows Modules Installer Default: Manual [TrustedInstaller.exe]
Windows Update Default: Automatic (Delayed Start)
MowGreen MVP Data Center Management - Update Services Consumer Security -
I have noticed that this problem goes way back to february, and people are blaming all sorts of things for their problems. I have just been given a new laptop without any o/s. I decided today to install windows 7 to see how it would perform on this machine. After almost 2 hours installing, with only the drivers for the soundcard not being found,I was ready to go. The first thing I did was to go to windows update, and surprise, suprise ERROR code 8000FFFF. There are no other programs or software packages installed on this machine, just W7. Therefore the problem must be with the O/S.
Please post the entire WindowsUpdate.log, located in WINDOWS.
Thanks.
MowGreen MVP Data Center Management - Update Services Consumer Security -
Thanks again, MowGreen. It goes like this:
System permissions - all exactly as you said.
Under ApplicabilityEvaluationCache: no WUClient entries.
There is Microsoft-Windows-Winhelp-Update...
and five entries of Package_for_KB...
Under UpdateDetect
Adm, Aux, Core and UI are not listed.
HKLM\COMPONENTS
Those three are not listed.
Services:
All the Automatics were showing "Started" except for "SoftwareProtection". I started that one.
The services you list are all there, set as you said, except for WindowsModulesInstaller which shows as "Manual" but doesn't have the remark [TrustedInstaller.exe]. -
You're welcome, Keith and thanks for sticking with this. I'm learning here, too. <w>
[TrustedInstaller.exe] was added on by me to indicate that WindowsModuleInstaller is TrustedInstaller.exe. It should not be appended to WindowsModuleInstaller .
I think that the missing Adm, Aux, Core, and UI under UpdateDetect indicates that the WUA is completely unregistered and it's files are no longer present. Since the System File Checker can't run ... short of an 'in place upgrade' or a format/reinstall, this is going to be a tough nut to crack.
But what the heck ... I'm game.
There is no URL that is able to download the previous Version of the WUA that was present and I think that forcing an install of the lastest Version will not resolve this error since there are files and registry entries missing. Thus, Win7 can not evalulate applicability or installed rules nor contact the update servers.
Let me sleep on this and I'll get back to you tomorrow morning.
MowGreen MVP Data Center Management - Update Services Consumer Security -
Please check to see if these files are present at %windir%\System32 and if they are, what Version level are they at ?
wuapi.dll
wuapp.dll
wuauclt.exe
wuaueng.dll
wucltux.dll
wudriver.dll
wups2.dll
wups.dll
wuwebv.dll
MowGreen MVP Data Center Management - Update Services Consumer Security -
-
-
You said in an earlier post that you did not want to re-install W7 as the time had passed for installing the beta. Have you tried to to a clean install. By that I mean completely erasing your hard drive and starting from scratch without any other O/S on seperate partitions, and do a fresh install of 7. I was having the same problem with the updates and last night I done a full format on my laptop and freshly installed 7 and it is working perfectly.(except that there are no drivers for my on board graphics). Unless you have lots of files and stuff that you really need, a clean install would be quicker than all the posts that you have made. -
You said in an earlier post that you did not want to re-install W7 as the time had passed for installing the beta. Have you tried to to a clean install. By that I mean completely erasing your hard drive and starting from scratch without any other O/S on seperate partitions, and do a fresh install of 7. I was having the same problem with the updates and last night I done a full format on my laptop and freshly installed 7 and it is working perfectly.(except that there are no drivers for my on board graphics). Unless you have lots of files and stuff that you really need, a clean install would be quicker than all the posts that you have made.Hi nm6174
Thanks for the feedback.
Reinstalling is the last option and should only be used after everythong else has been tried.
The folks in this thread are trying to troubleshoot and document a fix for this common and very difficult problem. The question that needs to be answered is "what happens during the reinstall that fixes this problem"?
Thanks for understanding.
Regards,
Thank You for testing Windows 7 Beta
Ronnie Vernon MVP -
Sorry,but I am not very technically minded when it comes to reading all the techy stuff in the log files and I really don't understand most of it. I installed the beta on my desktop PC when it was first released and it performed quite well for about two weeks. I installed all the updates as they were made available, and then all of a sudden I got the aforementioned error. After reading all the posts and not being able to find a solution for the problem, I decided to uninstall. A couple of days ago I was given a laptop without an operating system on it. I installed XP and then done an upgrade to vista and everything was ok. I then decided to see if 7 would run on the laptop, so I done an upgrade to 7, and when I done the first scan for updates it failed with 8000ffff error. As requested I tried to submit the log file, but it was far too big to be submitted. After looking at all the posts on this page and with the prospects of no solution in sight(it's been 5 weeks now) I decided to go for the easy option and done a full clean install. Since I have done this I have had no problems. As you have quite rightly stated that this forum will help others(technically minded) diagnose the faults and find a solution. Sorry but I am not one of them.
-
I also have the same error, and the same date and time stamp in windows update and CBS Log has identical errors. My computer is a new HP with Vista Ultimate 64 8 gig of memory and two 1TB sata drives. One drive is for Vista and the other is for Windows 7. I am just using Windows firewall and VIPRE anti-virus on the windows 7 OS. The only programs running on this computer are Microsoft Office 2007, CorelDraw Office Suit X3, and Monzilla Firefox. I left IE as default so there would be no issues with updates. I did have several issues with IE not opening pages after you were connected to different sites, so on came Monzilla. I did happen to note that the update on the 19th of Feb started on its own and of course attempted a restart. I know my duel boot system defaults to Windows Vista and if not opened it will login to Vista. I also tried the clean boot theory and still had the same issue. Stopped service cleared SD folder started service still same error. I have two theroies that could have happened. 1st the update test that was previously mentioned was set to turn off updates to Windows 7 Beta and was tested on random updates. The 2nd, theory is that the update got corrupted due to Windows 7 doing an automatic restart and loading Vista instead. The only thing that I have read that fixed this issue is reinstall. I hope that this is not the issue. Thanks to everyone for all the information. I can say that I did not even think about the CBS-diag.log. I am sure it will help MSFT and other users in the future. I have just about given up hope on saving this installation of Windows 7. You guys are ausome. Keep up the good work. We will prevail.
John -
Please check to see if these files are present at %windir%\System32 and if they are, what Version level are they at ?
I'm back from rural parts. The Win7 machine had crashed on Thursday evening at a time when I was away, and not using the VPN, and there's no indication of what caused it. A separate problem (maybe/probably) to be worried about later if it does it more often.
wuapi.dll
wuapp.dll
wuauclt.exe
wuaueng.dll
wucltux.dll
wudriver.dll
wups2.dll
wups.dll
wuwebv.dll
MowGreen MVP Data Center Management - Update Services Consumer Security
Here's the information on those files:
wuapi.dll - version 7.3.7000.0 dated 13/12/2008 05:03
wuapp.dll -same version, same date, 05:00
wuauclt.exe - same version, same date, 03:30
wuaueng.dll - same version, same date, 03:32
wucltux.dll - same version, same date, 03:32
wudriver.dll - same version, same date, 03:29
wups2.dll - same version, same date, 03:30
wups.dll - same version, same date, 03:30
wuwebv.dll - same version, same date, 03:29
-
Just for the heck of it, I checked the versions on my Win 7 installation and I got the following:
WUAPI.DLL v 7.4.7000.81 Date Modified: 12/17/2008 6:49pm Date Created: 2/18/2009 3:22am
wuapp.dll v 7.4.7000.81 Date Modified: 12/17/2008 6:31pm Date Created: 2/18/2009 3:22am
wuauclt.exe v 7.4.7000.81 Date Modified: 12/17/2008 6:49pm Date Created: 2/18/2009 3:22am
wuaueng.dll v 7.4.7000.81 Date Modified: 12/17/2008 6:49pm Date Created: 2/18/2009 3:22am
wucltux.dll v 7.4.7000.81 Date Modified: 12/17/2008 6:32pm Date Created: 2/18/2009 3:22am
wudriver.dll v 7.4.7000.81 Date Modified: 12/17/2008 6:31pm Date Created: 2/18/2009 3:22am
wups2.dll v 7.4.7000.81 Date Modified: 12/17/2008 6:49pm Date Created: 2/18/2009 3:22am
wups.dll v 7.4.7000.81 Date Modified: 12/17/2008 6:49pm Date Created: 2/18/2009 3:22am
wuwebv.dll v 7.4.7000.81 Date Modified: 12/17/2008 6:44pm Date Created: 2/18/2009 3:21am -
-
-
Might be a little late but here are the registry information on mine:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\UpdateDetect\CoreClientCollectionUltimate
Microsoft-Windows-Help-CoreClientUAUE-Package~31bf3856ad364e35~amd64~en-US~6.1.7000.0HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\UpdateDetect\Aux
WUClient-SelfUpdate-Aux-AuxComp~31bf3856ad364e35~amd64~en-US~7.4.7000.81HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\UpdateDetect\CoreClientUltimate
Microsoft-Windows-Help-CoreClientUAUE-Package~31bf3856ad364e35~amd64~en-US~6.1.7000.0No Adm
No UI -
Something just caught my eye after reading your post. My versions are all 7.3.7000.0 and yours are 7.4.7000.81. I checked the update log again and this is what I found. Where the error started and it states version 7.4.7000.81 see below in black.
2009-02-20 20:34:07:100 944 f1c Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\Handler\WuSetupV.exe:
2009-02-20 20:34:07:100 944 f1c Misc Microsoft signed: Yes
2009-02-20 20:34:07:100 944 f1c Setup SelfUpdate handler update NOT required: Current version: 7.4.7000.81, required version: 7.4.7000.81
2009-02-20 20:34:07:100 944 f1c Setup Evaluating applicability of setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.4.7000.81"
2009-02-20 20:34:11:109 944 f1c Handler FATAL: UH: 0x8000ffff:
-
Ah HA! I think we're onto something here...
Just chcked my Windows Update log and on Feb 18th, there was one listed as:
Windows Update Agent 7.4.7000.81Installation date: 2/18/2009 3:23 AM
Installation status: Successful
Update type: Important
The Windows Update Agent enables your computer to search for and install updates from an update service. The agent can automatically update itself as needed to communicate with the update service when Windows searches for new updates.
More information:
http://go.microsoft.com/fwlink/?LinkID=118000Help and Support:
http://go.microsoft.com/fwlink/?LinkID=117301
So it would seem that those machines getting this error either got a failure on the update to the 7.4 version or it never arrived on their system. Now all we need to do is figure out why - and how to fix it. -
I also did a search on my computer and the only update on my C drive dated 2/19/2009 was the winsxs directory. This directory is hugh and does a side by side copy of every install. nothing else in the windows directory or updates go to that date. This could be want a reinstall cleans up and repairs to allow the updates to sart again. It has been noted that if this file is moved or corrupted that updates will fail.
-
It's entirely possible. Can you check your Windows Update log to see if there were any updates to the Windows Update Agent done ever? If so, can you see what the status of that update was and post the contents of the details of said update record?
By this, I mean launch Windows Update and click on View Update History. Look for one titled "Windows Update Agent 7.4.7000.81" -
There was a download of the selfupdate and update handler on the 18th log states update was refused on shut down. Needless to say No, that did not happen. Down hill from there. My question is why http://download.windowsupdate.com/muv4/windowsupdate/a/selfupdate/WSUS3/x64/Vista
There has to be an issue here.
2009-02-18 16:39:08:500 988 fcc AU AU deferring detection until wake-up from hibernation
2009-02-18 16:39:08:500 988 fcc AU Forced install timer expired for scheduled install
2009-02-18 16:39:08:500 988 fcc AU UpdateDownloadProperties: 0 download(s) are still in progress.
2009-02-18 16:39:08:515 988 fcc AU Setting AU scheduled install time to 2009-02-19 11:00:00
2009-02-18 16:39:08:515 988 fcc AU AU setting next sqm report timeout to 2009-02-20 00:39:08
2009-02-18 16:39:08:952 988 fcc AU Triggering Online detection (non-interactive)
2009-02-18 16:49:23:226 988 fcc AU #############
2009-02-18 16:49:23:226 988 fcc AU ## START ## AU: Search for updates
2009-02-18 16:49:23:226 988 fcc AU #########
2009-02-18 16:49:23:226 988 fcc AU <<## SUBMITTED ## AU: Search for updates [CallId = {073AE716-7427-493B-8BA9-210B38A24BA1}]
2009-02-18 16:49:23:226 988 1f4 Agent *************
2009-02-18 16:49:23:226 988 1f4 Agent ** START ** Agent: Finding updates [CallerId = AutomaticUpdates]
2009-02-18 16:49:23:226 988 1f4 Agent *********
2009-02-18 16:49:23:226 988 1f4 Agent * Online = Yes; Ignore download priority = No
2009-02-18 16:49:23:226 988 1f4 Agent * Criteria = "IsInstalled=0 and DeploymentAction='Installation' or IsPresent=1 and DeploymentAction='Uninstallation' or IsInstalled=1 and DeploymentAction='Installation' and RebootRequired=1 or IsInstalled=0 and DeploymentAction='Uninstallation' and RebootRequired=1"
2009-02-18 16:49:23:226 988 1f4 Agent * ServiceID = {7971F918-A847-4430-9279-4A52D1EFE18D} Third party service
2009-02-18 16:49:23:226 988 1f4 Agent * Search Scope = {Machine}
2009-02-18 16:49:23:226 988 1f4 Setup Checking for agent SelfUpdate
2009-02-18 16:49:23:226 988 1f4 Setup Client version: Core: 7.3.7000.0 Aux: 7.3.7000.0
2009-02-18 16:49:23:228 988 1f4 Misc Validating signature for C:\Windows\SoftwareDistribution\WuRedir_prerelease\9482F4B4-E343-43B6-B170-9A65BC822C77\win7wuredir.cab:
2009-02-18 16:49:23:233 988 1f4 Misc Microsoft signed: Yes
2009-02-18 16:49:26:498 988 1f4 Misc Validating signature for C:\Windows\SoftwareDistribution\WuRedir_prerelease\9482F4B4-E343-43B6-B170-9A65BC822C77\win7wuredir.cab:
2009-02-18 16:49:26:501 988 1f4 Misc Microsoft signed: Yes
2009-02-18 16:49:26:503 988 1f4 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
2009-02-18 16:49:26:506 988 1f4 Misc Microsoft signed: Yes
2009-02-18 16:49:29:299 988 1f4 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
2009-02-18 16:49:29:301 988 1f4 Misc Microsoft signed: Yes
2009-02-18 16:49:34:509 988 1f4 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:
2009-02-18 16:49:34:511 988 1f4 Misc Microsoft signed: Yes
2009-02-18 16:49:34:549 988 1f4 Setup Determining whether a new setup handler needs to be downloaded
2009-02-18 16:49:34:549 988 1f4 Setup SelfUpdate handler is not found. It will be downloaded
2009-02-18 16:49:34:549 988 1f4 Setup Evaluating applicability of setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.4.7000.81"
2009-02-18 16:49:34:609 988 1f4 Setup Setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.4.7000.81" is applicable and needs to be downloaded.
2009-02-18 16:49:34:609 988 1f4 Setup Evaluating applicability of setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.4.7000.81"
2009-02-18 16:49:35:496 988 1f4 Setup Setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.4.7000.81" is applicable and needs to be downloaded.
2009-02-18 16:49:35:496 988 1f4 Setup Evaluating applicability of setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.4.7000.81"
2009-02-18 16:49:36:414 988 1f4 Setup Setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.4.7000.81" is applicable and needs to be downloaded.
2009-02-18 16:49:36:414 988 1f4 Setup SelfUpdate check completed. SelfUpdate is required.
2009-02-18 16:49:36:414 988 1f4 Setup Downloading binaries required for SelfUpdate
2009-02-18 16:49:36:414 988 1f4 Setup Downloading SelfUpdate handler WuSetupHandler.cab from http://download.windowsupdate.com/muv4/windowsupdate/a/selfupdate/WSUS3/x64/Vista
2009-02-18 16:49:36:869 988 1f4 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\Handler\WuSetupHandler.cab:
2009-02-18 16:49:36:874 988 1f4 Misc Microsoft signed: Yes
2009-02-18 16:49:36:874 988 1f4 Setup Successfully downloaded SelfUpdate handler
2009-02-18 16:49:36:876 988 1f4 Setup Downloading setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.4.7000.81"
2009-02-18 16:49:36:876 988 1f4 Setup Downloading setup package WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.4.7000.81.cab from http://download.windowsupdate.com/muv4/windowsupdate/a/selfupdate/WSUS3/x64/Vista
2009-02-18 16:49:39:249 988 1f4 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\Packages\WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.4.7000.81\WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.4.7000.81.cab:
2009-02-18 16:49:39:254 988 1f4 Misc Microsoft signed: Yes
2009-02-18 16:49:39:254 988 1f4 Setup Downloading setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.4.7000.81"
2009-02-18 16:49:39:254 988 1f4 Setup Downloading setup package WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.4.7000.81.cab from http://download.windowsupdate.com/muv4/windowsupdate/a/selfupdate/WSUS3/x64/Vista
2009-02-18 16:49:49:024 988 1f4 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\Packages\WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.4.7000.81\WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.4.7000.81.cab:
2009-02-18 16:49:49:029 988 1f4 Misc Microsoft signed: Yes
2009-02-18 16:49:49:031 988 1f4 Setup Downloading setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.4.7000.81"
2009-02-18 16:49:49:031 988 1f4 Setup Downloading setup package WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.4.7000.81.cab from http://download.windowsupdate.com/muv4/windowsupdate/a/selfupdate/WSUS3/x64/Vista
2009-02-18 16:50:02:109 988 1f4 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\Packages\WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.4.7000.81\WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.4.7000.81.cab:
2009-02-18 16:50:02:124 988 1f4 Misc Microsoft signed: Yes
2009-02-18 16:50:06:867 988 1f4 Setup Staging setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.4.7000.81"
2009-02-18 16:50:14:850 988 1f4 Setup Successfully staged setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.4.7000.81"
2009-02-18 16:50:14:850 988 1f4 Setup Staging setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.4.7000.81"
2009-02-18 16:50:25:428 988 1f4 Setup Successfully staged setup package "WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.4.7000.81"
2009-02-18 16:50:25:443 988 1f4 Setup Staging setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.4.7000.81"
2009-02-18 16:50:25:537 988 fcc Shutdwn user declined update at shutdown
2009-02-18 16:50:25:537 988 fcc AU AU initiates service shutdown
2009-02-18 16:50:25:537 988 fcc AU ########### AU: Uninitializing Automatic Updates ###########
2009-02-18 16:50:26:286 988 1f4 Setup FATAL: Failed to stage setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.4.7000.81", error = 0x8024000B
2009-02-18 16:50:26:286 988 1f4 Setup WARNING: Failed to stage applicable setup packages, error = 0x8024000B
2009-02-18 16:50:26:286 988 1f4 Setup FATAL: Downloading binaries for SelfUpdate failed, err = 0x8024000B
2009-02-18 16:50:26:286 988 1f4 Agent * WARNING: Skipping scan, self-update check returned 0x8024000B
2009-02-18 16:50:26:317 988 1f4 Agent * WARNING: Exit code = 0x8024000B
2009-02-18 16:50:26:317 988 1f4 Agent *********
2009-02-18 16:50:26:317 988 1f4 Agent ** END ** Agent: Finding updates [CallerId = AutomaticUpdates]
2009-02-18 16:50:26:317 988 1f4 Agent *************
2009-02-18 16:50:26:317 988 1f4 Agent WARNING: WU client failed Searching for update with error 0x8024000b
2009-02-18 16:50:26:317 988 fcc Report REPORT EVENT: {692BF52E-9C43-4580-8AB2-3F6F343001DB} 2009-02-18 16:50:26:286-0800 1 161 101 {E2FF4526-97D7-4926-8E75-295DBA39C6BF} 1 8024000b SelfUpdate Failure Content Download Error: Download failed.
2009-02-18 16:50:26:348 988 fcc Service *********
2009-02-18 16:50:26:348 988 fcc Service ** END ** Service: Service exit [Exit code = 0x240001]
2009-02-18 16:50:26:348 988 fcc Service *************
2009-02-18 20:13:43:493 996 5b8 Misc =========== Logging initialized (build: 7.3.7000.0, tz: -0800) ===========
2009-02-18 20:13:43:508 996 5b8 Misc = Process: C:\Windows\system32\svchost.exe
2009-02-18 20:13:43:508 996 5b8 Misc = Module: c:\windows\system32\wuaueng.dll
2009-02-18 20:13:43:493 996 5b8 Service *************
2009-02-18 20:13:43:508 996 5b8 Service ** START ** Service: Service startup
2009-02-18 20:13:43:508 996 5b8 Service *********
2009-02-18 20:13:43:571 996 5b8 Agent * WU client version 7.3.7000.0
2009-02-18 20:13:43:571 996 5b8 Agent * Base directory: C:\Windows\SoftwareDistribution
2009-02-18 20:13:43:586 996 5b8 Agent * Access type: No proxy
2009-02-18 20:13:43:586 996 5b8 Agent * Network state: Connected
2009-02-18 20:13:44:803 996 5b8 Setup WARNING: SelfUpdate is in an error state
2009-02-18 20:14:29:778 996 5b8 Agent *********** Agent: Initializing Windows Update Agent ***********
2009-02-18 20:14:29:778 996 5b8 Agent *********** Agent: Initializing global settings cache ***********
2009-02-18 20:14:29:778 996 5b8 Agent * WSUS server: <NULL>
2009-02-18 20:14:29:794 996 5b8 Agent * WSUS status server: <NULL>
2009-02-18 20:14:29:794 996 5b8 Agent * Target group: (Unassigned Computers)
2009-02-18 20:14:29:794 996 5b8 Agent * Windows Update access disabled: No
2009-02-18 20:14:29:825 996 5b8 DnldMgr Download manager restoring 0 downloads
2009-02-18 20:14:29:825 996 5b8 AU ########### AU: Initializing Automatic Updates ###########
2009-02-18 20:14:29:840 996 5b8 AU AU setting next detection timeout to 2009-02-19 04:14:29
2009-02-18 20:14:29:840 996 5b8 AU # Approval type: Scheduled (User preference)
2009-02-18 20:14:29:840 996 5b8 AU # Scheduled install day/time: Every day at 3:00
2009-02-18 20:14:29:840 996 5b8 AU # Auto-install minor updates: Yes (User preference)
2009-02-18 20:14:29:840 996 5b8 AU # Will interact with non-admins (Non-admins are elevated (User preference))
2009-02-18 20:14:29:840 996 5b8 AU # Will display featured updates notifications (User preference)
2009-02-18 20:14:29:887 996 5b8 AU Setting AU scheduled install time to 2009-02-19 11:00:00
2009-02-18 20:14:29:887 996 5b8 AU Initializing featured updates
2009-02-18 20:14:29:887 996 5b8 AU Found 0 cached featured updates
2009-02-18 20:14:30:433 996 5b8 Report *********** Report: Initializing static reporting data ***********
2009-02-18 20:14:30:433 996 5b8 Report * OS Version = 6.1.7000.0.0.65792
2009-02-18 20:14:30:433 996 5b8 Report * OS Product Type = 0x00000001
2009-02-18 20:14:30:464 996 5b8 Report * Computer Brand = HP-Pavilion
2009-02-18 20:14:30:464 996 5b8 Report * Computer Model = KT608AAR-ABA d5000t
2009-02-18 20:14:30:496 996 5b8 Report * Bios Revision = 5.14
2009-02-18 20:14:30:496 996 5b8 Report * Bios Name = BIOS Date: 04/25/08 17:21:14 Ver: 5.14
2009-02-18 20:14:30:496 996 5b8 Report * Bios Release Date = 2008-04-25T00:00:00
2009-02-18 20:14:30:496 996 5b8 Report * Locale ID = 1033
2009-02-18 20:14:30:511 996 5b8 AU Successfully wrote event for AU health state:0
2009-02-18 20:14:30:511 996 5b8 AU AU finished delayed initialization
2009-02-18 20:14:30:527 996 5b8 AU #############
2009-02-18 20:14:30:527 996 5b8 AU ## START ## AU: Search for updates
2009-02-18 20:14:30:527 996 5b8 AU #########
2009-02-18 20:14:30:589 996 5b8 AU <<## SUBMITTED ## AU: Search for updates [CallId = {92BFC2B1-EF71-400C-9524-C9A49EAC5450}]
2009-02-18 20:14:30:636 996 9b8 Agent *************
2009-02-18 20:14:30:636 996 9b8 Agent ** START ** Agent: Finding updates [CallerId = AutomaticUpdates]
2009-02-18 20:14:30:652 996 9b8 Agent *********
2009-02-18 20:14:30:652 996 9b8 Agent * Online = Yes; Ignore download priority = No
2009-02-18 20:14:30:652 996 9b8 Agent * Criteria = "IsInstalled=0 and DeploymentAction='Installation' or IsPresent=1 and DeploymentAction='Uninstallation' or IsInstalled=1 and DeploymentAction='Installation' and RebootRequired=1 or IsInstalled=0 and DeploymentAction='Uninstallation' and RebootRequired=1"
2009-02-18 20:14:30:652 996 9b8 Agent * ServiceID = {7971F918-A847-4430-9279-4A52D1EFE18D} Third party service
2009-02-18 20:14:30:652 996 9b8 Agent * Search Scope = {Machine}
2009-02-18 20:14:30:652 996 9b8 Setup Checking for agent SelfUpdate
2009-02-18 20:14:30:652 996 9b8 Setup Client version: Core: 7.3.7000.0 Aux: 7.3.7000.0
2009-02-18 20:14:30:683 996 9b8 Misc Validating signature for C:\Windows\SoftwareDistribution\WuRedir_prerelease\9482F4B4-E343-43B6-B170-9A65BC822C77\win7wuredir.cab:
2009-02-18 20:14:30:698 996 9b8 Misc Microsoft signed: Yes
2009-02-18 20:14:33:600 996 9b8 Misc Validating signature for C:\Windows\SoftwareDistribution\WuRedir_prerelease\9482F4B4-E343-43B6-B170-9A65BC822C77\win7wuredir.cab:
2009-02-18 20:14:33:600 996 9b8 Misc Microsoft signed: Yes
2009-02-18 20:14:33:600 996 9b8 Misc Validating signature for C:\Windows\SoftwareDistribution\WuRedir_prerelease\9482F4B4-E343-43B6-B170-9A65BC822C77\win7wuredir.cab:
2009-02-18 20:14:33:600 996 9b8 Misc Microsoft signed: Yes
2009-02-18 20:14:33:694 996 9b8 Misc Validating signature for C:\Windows\SoftwareDistribution\WuRedir_prerelease\9482F4B4-E343-43B6-B170-9A65BC822C77\win7wuredir.cab:
2009-02-18 20:14:33:694 996 9b8 Misc Microsoft signed: Yes
2009-02-18 20:14:33:694 996 9b8 Misc Validating signature for C:\Windows\SoftwareDistribution\WuRedir_prerelease\9482F4B4-E343-43B6-B170-9A65BC822C77\win7wuredir.cab:
2009-02-18 20:14:33:694 996 9b8 Misc Microsoft signed: Yes
2009-02-18 20:14:33:850 996 9b8 Misc Validating signature for C:\Windows\SoftwareDistribution\WuRedir_prerelease\9482F4B4-E343-43B6-B170-9A65BC822C77\win7wuredir.cab:
2009-02-18 20:14:33:850 996 9b8 Misc Microsoft signed: Yes
2009-02-18 20:14:33:865 996 9b8 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
2009-02-18 20:14:33:865 996 9b8 Misc Microsoft signed: Yes
2009-02-18 20:14:36:486 996 9b8 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
2009-02-18 20:14:36:486 996 9b8 Misc Microsoft signed: Yes
2009-02-18 20:14:36:517 996 9b8 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:
2009-02-18 20:14:36:564 996 9b8 Misc Microsoft signed: Yes
2009-02-18 20:14:39:138 996 9b8 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:
2009-02-18 20:14:39:138 996 9b8 Misc Microsoft signed: Yes
2009-02-18 20:14:39:200 996 9b8 Setup Determining whether a new setup handler needs to be downloaded
2009-02-18 20:14:39:216 996 9b8 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\Handler\WuSetupV.exe:
2009-02-18 20:14:39:216 996 9b8 Misc Microsoft signed: Yes
2009-02-18 20:14:39:216 996 9b8 Setup SelfUpdate handler update NOT required: Current version: 7.4.7000.81, required version: 7.4.7000.81
2009-02-18 20:14:39:232 996 9b8 Setup Evaluating applicability of setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.4.7000.81"
2009-02-18 20:14:40:901 996 9b8 Handler FATAL: UH: 0x8000ffff: EvaluateApplicability failed in CCbs::EvaluateApplicability
2009-02-18 20:14:40:901 996 9b8 Setup WARNING: CBS EvaluateApplicability returned error, error = 0x8000FFFF
2009-02-18 20:14:40:901 996 9b8 Setup FATAL: Applicability evaluation for setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.4.7000.81" failed, error = 0x8000FFFF
2009-02-18 20:14:40:901 996 9b8 Setup FATAL: SelfUpdate check failed, err = 0x8000FFFF
2009-02-18 20:14:40:901 996 9b8 Agent * WARNING: Skipping scan, self-update check returned 0x8000FFFF
2009-02-18 20:14:40:963 996 9b8 Agent * WARNING: Exit code = 0x8000FFFF
2009-02-18 20:14:40:963 996 9b8 Agent *********
2009-02-18 20:14:40:963 996 9b8 Agent ** END ** Agent: Finding updates [CallerId = AutomaticUpdates]
2009-02-18 20:14:40:963 996 9b8 Agent *************
2009-02-18 20:14:40:963 996 9b8 Agent WARNING: WU client failed Searching for update with error 0x8000ffff
2009-02-18 20:14:40:963 996 bb8 AU >>## RESUMED ## AU: Search for updates [CallId = {92BFC2B1-EF71-400C-9524-C9A49EAC5450}]
2009-02-18 20:14:40:963 996 bb8 AU # WARNING: Search callback failed, result = 0x8000FFFF
2009-02-18 20:14:40:963 996 bb8 AU # WARNING: Failed to find updates with error code 8000FFFF
2009-02-18 20:14:40:963 996 bb8 AU #########
2009-02-18 20:14:40:963 996 bb8 AU ## END ## AU: Search for updates [CallId = {92BFC2B1-EF71-400C-9524-C9A49EAC5450}]
2009-02-18 20:14:40:963 996 bb8 AU #############
2009-02-18 20:14:40:963 996 bb8 AU Successfully wrote event for AU health state:0
2009-02-18 20:14:40:963 996 bb8 AU AU setting next detection timeout to 2009-02-19 09:14:40
2009-02-18 20:14:40:963 996 bb8 AU Setting AU scheduled install time to 2009-02-19 11:00:00
2009-02-18 20:14:45:908 996 9b8 Report REPORT EVENT: {CE54D025-524E-4FD5-B9B0-CC0EC476442C} 2009-02-18 20:14:40:901-0800 1 148 101 {61CA813A-7585-442E-A66B-B0D15CE6BDC0} 1 8000ffff SelfUpdate Failure Software Synchronization Windows Update Client failed to detect with error 0x8000ffff.
2009-02-18 20:22:26:585 996 5b8 Shutdwn user declined update at shutdown
2009-02-18 20:22:26:585 996 5b8 AU AU initiates service shutdown
2009-02-18 20:22:26:585 996 5b8 AU ########### AU: Uninitializing Automatic Updates ###########
2009-02-18 20:22:26:835 996 5b8 Service *********
2009-02-18 20:22:26:835 996 5b8 Service ** END ** Service: Service exit [Exit code = 0x240001]
2009-02-18 20:22:26:835 996 5b8 Service *************
2009-02-18 20:26:47:196 940 30c Misc =========== Logging initialized (build: 7.3.7000.0, tz: -0800) ===========
2009-02-18 20:26:47:259 940 30c Misc = Process: C:\Windows\system32\svchost.exe
2009-02-18 20:26:47:259 940 30c Misc = Module: c:\windows\system32\wuaueng.dll
2009-02-18 20:26:47:196 940 30c Service *************
2009-02-18 20:26:47:259 940 30c Service ** START ** Service: Service startup
2009-02-18 20:26:47:259 940 30c Service *********
2009-02-18 20:26:47:508 940 30c Agent * WU client version 7.3.7000.0
2009-02-18 20:26:47:508 940 30c Agent * Base directory: C:\Windows\SoftwareDistribution
2009-02-18 20:26:47:508 940 30c Agent * Access type: No proxy
2009-02-18 20:26:47:586 940 30c Agent * Network state: Connected
2009-02-18 20:26:49:706 940 30c Setup WARNING: SelfUpdate is in an error state
2009-02-18 20:27:05:026 940 30c AU AU initiates service shutdown
2009-02-18 20:27:05:790 940 30c Report *********** Report: Initializing static reporting data ***********
2009-02-18 20:27:05:790 940 30c Report * OS Version = 6.1.7000.0.0.65792
2009-02-18 20:27:05:790 940 30c Report * OS Product Type = 0x00000001
2009-02-18 20:27:05:806 940 30c Report * Computer Brand = HP-Pavilion
2009-02-18 20:27:05:806 940 30c Report * Computer Model = KT608AAR-ABA d5000t
2009-02-18 20:27:05:822 940 30c Report * Bios Revision = 5.14
2009-02-18 20:27:05:822 940 30c Report * Bios Name = BIOS Date: 04/25/08 17:21:14 Ver: 5.14
2009-02-18 20:27:05:822 940 30c Report * Bios Release Date = 2008-04-25T00:00:00
2009-02-18 20:27:05:822 940 30c Report * Locale ID = 1033
2009-02-18 20:27:05:853 940 30c AU ########### AU: Uninitializing Automatic Updates ###########
2009-02-18 20:27:05:884 940 30c Report WARNING: Reporter failed to upload events with hr = 8024000c.
2009-02-18 20:27:05:915 940 30c Service *********
2009-02-18 20:27:05:915 940 30c Service ** END ** Service: Service exit [Exit code = 0x240001]
2009-02-18 20:27:05:915 940 30c Service *************
2009-02-18 20:30:32:698 1008 cfc Misc =========== Logging initialized (build: 7.3.7000.0, tz: -0800) ===========
2009-02-18 20:30:32:714 1008 cfc Misc = Process: C:\Windows\system32\svchost.exe
2009-02-18 20:30:32:714 1008 cfc Misc = Module: c:\windows\system32\wuaueng.dll
2009-02-18 20:30:32:698 1008 cfc Service *************
2009-02-18 20:30:32:714 1008 cfc Service ** START ** Service: Service startup
2009-02-18 20:30:32:714 1008 cfc Service *********
2009-02-18 20:30:33:135 1008 cfc Agent * WU client version 7.3.7000.0
2009-02-18 20:30:33:135 1008 cfc Agent * Base directory: C:\Windows\SoftwareDistribution
2009-02-18 20:30:33:151 1008 cfc Agent * Access type: No proxy
2009-02-18 20:30:33:151 1008 cfc Agent * Network state: Connected
2009-02-18 20:30:34:758 1008 cfc Setup WARNING: SelfUpdate is in an error state
2009-02-18 20:31:19:748 1008 cfc Agent *********** Agent: Initializing Windows Update Agent ***********
2009-02-18 20:31:19:764 1008 cfc Agent *********** Agent: Initializing global settings cache ***********
2009-02-18 20:31:19:764 1008 cfc Agent * WSUS server: <NULL>
2009-02-18 20:31:19:764 1008 cfc Agent * WSUS status server: <NULL>
2009-02-18 20:31:19:764 1008 cfc Agent * Target group: (Unassigned Computers)
2009-02-18 20:31:19:764 1008 cfc Agent * Windows Update access disabled: No
2009-02-18 20:31:19:779 1008 cfc DnldMgr Download manager restoring 0 downloads
2009-02-18 20:31:19:810 1008 cfc AU ########### AU: Initializing Automatic Updates ###########
2009-02-18 20:31:19:810 1008 cfc AU # Approval type: Scheduled (User preference)
2009-02-18 20:31:19:810 1008 cfc AU # Scheduled install day/time: Every day at 3:00
2009-02-18 20:31:19:810 1008 cfc AU # Auto-install minor updates: Yes (User preference)
2009-02-18 20:31:19:810 1008 cfc AU # Will interact with non-admins (Non-admins are elevated (User preference))
2009-02-18 20:31:19:810 1008 cfc AU # Will display featured updates notifications (User preference)
2009-02-18 20:31:19:826 1008 cfc AU Setting AU scheduled install time to 2009-02-19 11:00:00
2009-02-18 20:31:19:826 1008 cfc AU Initializing featured updates
2009-02-18 20:31:19:826 1008 cfc AU Found 0 cached featured updates
2009-02-18 20:31:21:012 1008 cfc Report *********** Report: Initializing static reporting data ***********
2009-02-18 20:31:21:012 1008 cfc Report * OS Version = 6.1.7000.0.0.65792
2009-02-18 20:31:21:012 1008 cfc Report * OS Product Type = 0x00000001
2009-02-18 20:31:21:058 1008 cfc Report * Computer Brand = HP-Pavilion
2009-02-18 20:31:21:058 1008 cfc Report * Computer Model = KT608AAR-ABA d5000t
2009-02-18 20:31:21:074 1008 cfc Report * Bios Revision = 5.14
2009-02-18 20:31:21:074 1008 cfc Report * Bios Name = BIOS Date: 04/25/08 17:21:14 Ver: 5.14
2009-02-18 20:31:21:074 1008 cfc Report * Bios Release Date = 2008-04-25T00:00:00
2009-02-18 20:31:21:074 1008 cfc Report * Locale ID = 1033
2009-02-18 20:31:21:105 1008 cfc AU Successfully wrote event for AU health state:0
2009-02-18 20:31:21:105 1008 cfc AU AU finished delayed initialization
2009-02-18 20:31:21:292 1008 d80 Misc Validating signature for C:\Windows\SoftwareDistribution\WuRedir_prerelease\9482F4B4-E343-43B6-B170-9A65BC822C77\wuredir.cab:
2009-02-18 20:31:21:324 1008 d80 Misc Microsoft signed: Yes
2009-02-18 20:31:21:339 1008 d80 PT WARNING: Cached cookie has expired or new PID is available
2009-02-18 20:31:21:339 1008 d80 PT WARNING: PTWarn: Anonymous plug-in skipped for WU
2009-02-18 20:31:24:475 1008 d80 PT WARNING: GetCookie failure, error = 0x8024400D, soap client error = 7, soap error code = 300, HTTP status code = 200
2009-02-18 20:31:24:475 1008 d80 PT WARNING: SOAP Fault: 0x00012c
2009-02-18 20:31:24:475 1008 d80 PT WARNING: faultstring:Fault occurred
2009-02-18 20:31:24:475 1008 d80 PT WARNING: ErrorCode:ServerChanged(4)
2009-02-18 20:31:24:475 1008 d80 PT WARNING: Message:(null)
2009-02-18 20:31:24:475 1008 d80 PT WARNING: Method:"http://www.microsoft.com/SoftwareDistribution/Server/ClientWebService/GetCookie"
2009-02-18 20:31:24:475 1008 d80 PT WARNING: ID:d17327f2-e7fa-4a2e-b69a-a996b12db952
2009-02-18 20:31:24:475 1008 d80 PT WARNING: PTError: 0x80244015
2009-02-18 20:31:24:475 1008 d80 PT WARNING: GetCookie_WithRecovery failed : 0x80244015
2009-02-18 20:31:24:475 1008 d80 PT WARNING: RefreshCookie failed: 0x80244015
2009-02-18 20:31:24:475 1008 d80 PT WARNING: RefreshPTState failed: 0x80244015
2009-02-18 20:31:24:631 1008 d80 PT WARNING: Cached cookie has expired or new PID is available
2009-02-18 20:31:24:631 1008 d80 PT WARNING: PTWarn: Anonymous plug-in skipped for WU
2009-02-18 20:31:25:894 1008 d80 Misc Validating signature for C:\Windows\SoftwareDistribution\WuRedir_prerelease\9482F4B4-E343-43B6-B170-9A65BC822C77\wuredir.cab:
2009-02-18 20:31:25:910 1008 d80 Misc Microsoft signed: Yes
2009-02-18 20:31:25:910 1008 d80 Report Uploading 2 events using cached cookie, reporting URL = http://test.stats.update.microsoft.com/ReportingWebService/ReportingWebService.asmx
2009-02-18 20:31:28:702 1008 d80 Report Reporter successfully uploaded 2 events.
2009-02-19 01:14:39:999 1008 cfc AU #############
2009-02-19 01:14:39:999 1008 cfc AU ## START ## AU: Search for updates
2009-02-19 01:14:39:999 1008 cfc AU #########
2009-02-19 01:14:39:999 1008 cfc AU <<## SUBMITTED ## AU: Search for updates [CallId = {57A6A797-347E-4EE9-B451-0A79CDA417B9}]
2009-02-19 01:14:39:999 1008 d48 Agent *************
2009-02-19 01:14:39:999 1008 d48 Agent ** START ** Agent: Finding updates [CallerId = AutomaticUpdates]
2009-02-19 01:14:39:999 1008 d48 Agent *********
2009-02-19 01:14:39:999 1008 d48 Agent * Online = Yes; Ignore download priority = No
2009-02-19 01:14:39:999 1008 d48 Agent * Criteria = "IsInstalled=0 and DeploymentAction='Installation' or IsPresent=1 and DeploymentAction='Uninstallation' or IsInstalled=1 and DeploymentAction='Installation' and RebootRequired=1 or IsInstalled=0 and DeploymentAction='Uninstallation' and RebootRequired=1"
2009-02-19 01:14:39:999 1008 d48 Agent * ServiceID = {7971F918-A847-4430-9279-4A52D1EFE18D} Third party service
2009-02-19 01:14:39:999 1008 d48 Agent * Search Scope = {Machine}
2009-02-19 01:14:39:999 1008 d48 Setup Checking for agent SelfUpdate
2009-02-19 01:14:39:999 1008 d48 Setup Client version: Core: 7.3.7000.0 Aux: 7.3.7000.0
2009-02-19 01:14:40:015 1008 d48 Misc Validating signature for C:\Windows\SoftwareDistribution\WuRedir_prerelease\9482F4B4-E343-43B6-B170-9A65BC822C77\win7wuredir.cab:
2009-02-19 01:14:40:031 1008 d48 Misc Microsoft signed: Yes
2009-02-19 01:14:43:166 1008 d48 Misc Validating signature for C:\Windows\SoftwareDistribution\WuRedir_prerelease\9482F4B4-E343-43B6-B170-9A65BC822C77\win7wuredir.cab:
2009-02-19 01:14:43:182 1008 d48 Misc Microsoft signed: Yes
2009-02-19 01:14:43:197 1008 d48 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
2009-02-19 01:14:43:197 1008 d48 Misc Microsoft signed: Yes
2009-02-19 01:14:45:803 1008 d48 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
2009-02-19 01:14:45:803 1008 d48 Misc Microsoft signed: Yes
2009-02-19 01:14:45:834 1008 d48 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:
2009-02-19 01:14:45:849 1008 d48 Misc Microsoft signed: Yes
2009-02-19 01:14:48:299 1008 d48 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:
2009-02-19 01:14:48:299 1008 d48 Misc Microsoft signed: Yes
2009-02-19 01:14:48:345 1008 d48 Setup Determining whether a new setup handler needs to be downloaded
2009-02-19 01:14:48:361 1008 d48 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\Handler\WuSetupV.exe:
2009-02-19 01:14:48:361 1008 d48 Misc Microsoft signed: Yes
2009-02-19 01:14:48:361 1008 d48 Setup SelfUpdate handler update NOT required: Current version: 7.4.7000.81, required version: 7.4.7000.81
2009-02-19 01:14:48:361 1008 d48 Setup Evaluating applicability of setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.4.7000.81"
2009-02-19 01:14:49:391 1008 d48 Handler FATAL: UH: 0x8000ffff: EvaluateApplicability failed in CCbs::EvaluateApplicability
2009-02-19 01:14:49:391 1008 d48 Setup WARNING: CBS EvaluateApplicability returned error, error = 0x8000FFFF
2009-02-19 01:14:49:391 1008 d48 Setup FATAL: Applicability evaluation for setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.4.7000.81" failed, error = 0x8000FFFF
2009-02-19 01:14:49:391 1008 d48 Setup FATAL: SelfUpdate check failed, err = 0x8000FFFF
2009-02-19 01:14:49:391 1008 d48 Agent * WARNING: Skipping scan, self-update check returned 0x8000FFFF
2009-02-19 01:14:51:138 1008 d48 Agent * WARNING: Exit code = 0x8000FFFF
2009-02-19 01:14:51:138 1008 d48 Agent *********
2009-02-19 01:14:51:138 1008 d48 Agent ** END ** Agent: Finding updates [CallerId = AutomaticUpdates]
2009-02-19 01:14:51:138 1008 d48 Agent *************
2009-02-19 01:14:51:138 1008 d48 Agent WARNING: WU client failed Searching for update with error 0x8000ffff
2009-02-19 01:14:51:138 1008 bf0 AU >>## RESUMED ## AU: Search for updates [CallId = {57A6A797-347E-4EE9-B451-0A79CDA417B9}]
2009-02-19 01:14:51:138 1008 bf0 AU # WARNING: Search callback failed, result = 0x8000FFFF
2009-02-19 01:14:51:138 1008 bf0 AU # WARNING: Failed to find updates with error code 8000FFFF
2009-02-19 01:14:51:138 1008 bf0 AU #########
2009-02-19 01:14:51:138 1008 bf0 AU ## END ## AU: Search for updates [CallId = {57A6A797-347E-4EE9-B451-0A79CDA417B9}]
2009-02-19 01:14:51:138 1008 bf0 AU #############
2009-02-19 01:14:51:138 1008 bf0 AU Successfully wrote event for AU health state:0
2009-02-19 01:14:51:138 1008 bf0 AU AU setting next detection timeout to 2009-02-19 14:14:51
2009-02-19 01:14:51:138 1008 bf0 AU Setting AU scheduled install time to 2009-02-19 11:00:00
2009-02-19 01:14:54:414 1008 d48 Report REPORT EVENT: {95DB254F-4E05-46F1-9461-5D1A0DF6C40B} 2009-02-19 01:14:49:391-0800 1 148 101 {61CA813A-7585-442E-A66B-B0D15CE6BDC0} 1 8000ffff SelfUpdate Failure Software Synchronization Windows Update Client failed to detect with error 0x8000ffff.
2009-02-19 16:57:49:531 1008 cfc AU Forced install timer expired for scheduled install
2009-02-19 16:57:49:531 1008 cfc AU UpdateDownloadProperties: 0 download(s) are still in progress.
2009-02-19 16:57:49:531 1008 cfc AU Setting AU scheduled install time to 2009-02-20 11:00:00
2009-02-19 16:57:49:531 1008 cfc AU AU deferring detection until wake-up from hibernation
2009-02-19 16:57:49:562 1008 cfc AU AU setting next sqm report timeout to 2009-02-21 00:57:49
2009-02-19 16:57:57:549 1008 cfc AU Triggering Online detection (non-interactive)
2009-02-19 16:58:04:257 1008 eb8 Report WARNING: Reporter failed to upload events with hr = 8024000c.
2009-02-19 16:58:05:817 1008 eb8 Misc Validating signature for C:\Windows\SoftwareDistribution\WuRedir_prerelease\9482F4B4-E343-43B6-B170-9A65BC822C77\wuredir.cab:
2009-02-19 16:58:05:817 1008 eb8 Misc Microsoft signed: Yes
2009-02-19 16:58:07:221 1008 eb8 Misc Validating signature for C:\Windows\SoftwareDistribution\WuRedir_prerelease\9482F4B4-E343-43B6-B170-9A65BC822C77\wuredir.cab:
2009-02-19 16:58:07:221 1008 eb8 Misc Microsoft signed: Yes
2009-02-19 16:58:07:221 1008 eb8 Report Uploading 1 events using cached cookie, reporting URL = http://test.stats.update.microsoft.com/ReportingWebService/ReportingWebService.asmx
2009-02-19 16:58:11:386 1008 eb8 Report Reporter successfully uploaded 1 events.
2009-02-19 17:08:04:234 1008 cfc AU #############
2009-02-19 17:08:04:234 1008 cfc AU ## START ## AU: Search for updates
2009-02-19 17:08:04:234 1008 cfc AU #########
2009-02-19 17:08:04:234 1008 cfc AU <<## SUBMITTED ## AU: Search for updates [CallId = {D186ECFA-4B38-4131-862F-AC13BAD50303}]
2009-02-19 17:08:04:234 1008 eb8 Agent *************
2009-02-19 17:08:04:234 1008 eb8 Agent ** START ** Agent: Finding updates [CallerId = AutomaticUpdates]
2009-02-19 17:08:04:234 1008 eb8 Agent *********
2009-02-19 17:08:04:234 1008 eb8 Agent * Online = Yes; Ignore download priority = No
2009-02-19 17:08:04:234 1008 eb8 Agent * Criteria = "IsInstalled=0 and DeploymentAction='Installation' or IsPresent=1 and DeploymentAction='Uninstallation' or IsInstalled=1 and DeploymentAction='Installation' and RebootRequired=1 or IsInstalled=0 and DeploymentAction='Uninstallation' and RebootRequired=1"
2009-02-19 17:08:04:234 1008 eb8 Agent * ServiceID = {7971F918-A847-4430-9279-4A52D1EFE18D} Third party service
2009-02-19 17:08:04:234 1008 eb8 Agent * Search Scope = {Machine}
2009-02-19 17:08:04:234 1008 eb8 Setup Checking for agent SelfUpdate
2009-02-19 17:08:04:234 1008 eb8 Setup Client version: Core: 7.3.7000.0 Aux: 7.3.7000.0
2009-02-19 17:08:04:234 1008 eb8 Misc Validating signature for C:\Windows\SoftwareDistribution\WuRedir_prerelease\9482F4B4-E343-43B6-B170-9A65BC822C77\win7wuredir.cab:
2009-02-19 17:08:04:250 1008 eb8 Misc Microsoft signed: Yes
2009-02-19 17:08:07:089 1008 eb8 Misc Validating signature for C:\Windows\SoftwareDistribution\WuRedir_prerelease\9482F4B4-E343-43B6-B170-9A65BC822C77\win7wuredir.cab:
2009-02-19 17:08:07:105 1008 eb8 Misc Microsoft signed: Yes
2009-02-19 17:08:07:105 1008 eb8 Misc Validating signature for C:\Windows\SoftwareDistribution\WuRedir_prerelease\9482F4B4-E343-43B6-B170-9A65BC822C77\win7wuredir.cab:
2009-02-19 17:08:07:105 1008 eb8 Misc Microsoft signed: Yes
2009-02-19 17:08:07:229 1008 eb8 Misc Validating signature for C:\Windows\SoftwareDistribution\WuRedir_prerelease\9482F4B4-E343-43B6-B170-9A65BC822C77\win7wuredir.cab:
2009-02-19 17:08:07:245 1008 eb8 Misc Microsoft signed: Yes
2009-02-19 17:08:07:245 1008 eb8 Misc Validating signature for C:\Windows\SoftwareDistribution\WuRedir_prerelease\9482F4B4-E343-43B6-B170-9A65BC822C77\win7wuredir.cab:
2009-02-19 17:08:07:245 1008 eb8 Misc Microsoft signed: Yes
2009-02-19 17:08:07:385 1008 eb8 Misc Validating signature for C:\Windows\SoftwareDistribution\WuRedir_prerelease\9482F4B4-E343-43B6-B170-9A65BC822C77\win7wuredir.cab:
2009-02-19 17:08:07:385 1008 eb8 Misc Microsoft signed: Yes
2009-02-19 17:08:07:401 1008 eb8 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
2009-02-19 17:08:07:401 1008 eb8 Misc Microsoft signed: Yes
2009-02-19 17:08:10:037 1008 eb8 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wuident.cab:
2009-02-19 17:08:10:037 1008 eb8 Misc Microsoft signed: Yes
2009-02-19 17:08:10:053 1008 eb8 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:
2009-02-19 17:08:10:053 1008 eb8 Misc Microsoft signed: Yes
2009-02-19 17:08:12:533 1008 eb8 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\wsus3setup.cab:
2009-02-19 17:08:12:533 1008 eb8 Misc Microsoft signed: Yes
2009-02-19 17:08:12:580 1008 eb8 Setup Determining whether a new setup handler needs to be downloaded
2009-02-19 17:08:12:580 1008 eb8 Misc Validating signature for C:\Windows\SoftwareDistribution\SelfUpdate\Handler\WuSetupV.exe:
2009-02-19 17:08:12:580 1008 eb8 Misc Microsoft signed: Yes
2009-02-19 17:08:12:580 1008 eb8 Setup SelfUpdate handler update NOT required: Current version: 7.4.7000.81, required version: 7.4.7000.81
2009-02-19 17:08:12:580 1008 eb8 Setup Evaluating applicability of setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.4.7000.81"
2009-02-19 17:08:12:939 1008 eb8 Handler FATAL: UH: 0x8000ffff: EvaluateApplicability failed in CCbs::EvaluateApplicability
2009-02-19 17:08:12:939 1008 eb8 Setup WARNING: CBS EvaluateApplicability returned error, error = 0x8000FFFF
2009-02-19 17:08:12:939 1008 eb8 Setup FATAL: Applicability evaluation for setup package "WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.4.7000.81" failed, error = 0x8000FFFF
2009-02-19 17:08:12:939 1008 eb8 Setup FATAL: SelfUpdate check failed, err = 0x8000FFFF
2009-02-19 17:08:12:939 1008 eb8 Agent * WARNING: Skipping scan, self-update check returned 0x8000FFFF
2009-02-19 17:08:13:407 1008 eb8 Agent * WARNING: Exit code = 0x8000FFFF
2009-02-19 17:08:13:407 1008 eb8 Agent *********
2009-02-19 17:08:13:407 1008 eb8 Agent ** END ** Agent: Finding updates [CallerId = AutomaticUpdates]
2009-02-19 17:08:13:407 1008 eb8 Agent *************
2009-02-19 17:08:13:407 1008 eb8 Agent WARNING: WU client failed Searching for update with error 0x8000ffff
2009-02-19 17:08:13:407 1008 b00 AU >>## RESUMED ## AU: Search for updates [CallId = {D186ECFA-4B38-4131-862F-AC13BAD50303}]
2009-02-19 17:08:13:407 1008 b00 AU # WARNING: Search callback failed, result = 0x8000FFFF
2009-02-19 17:08:13:407 1008 b00 AU # WARNING: Failed to find updates with error code 8000FFFF -
I also just checked and found these cab files on the computer. I wonder if the OS would get a little fussy.
WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.4.7000.81
WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.4.7000.81
WUClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~amd64~~7.4.7000.81 -
Ok.. There were a couple of items I found to be troubling following the section you put made BOLD...
2009-02-18 16:50:25:537 988 fcc Shutdwn user declined update at shutdown
2009-02-18 16:50:25:537 988 fcc AU AU initiates service shutdown
2009-02-18 16:50:25:537 988 fcc AU ########### AU: Uninitializing Automatic Updates ###########
2009-02-18 16:50:26:286 988 1f4 Setup FATAL: Failed to stage setup package "WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~amd64~~7.4.7000.81", error = 0x8024000B
2009-02-18 16:50:26:286 988 1f4 Setup WARNING: Failed to stage applicable setup packages, error = 0x8024000B
2009-02-18 16:50:26:286 988 1f4 Setup FATAL: Downloading binaries for SelfUpdate failed, err = 0x8024000B
First off, Shutdwn user declined update at shutdown... Do you recall if you perhaps maybe told Windows Update NOT to reboot your system following an update? Eh... That doesn't make much sense - it would have installed the update the next time you shut down and restarted. But the last item I quoted - the Setup FATAL: Downloading binaries for Self Update failed one...
That one makes no sense. You found the cab files on your hard drive. Unless... Maybe there was a CRC or other error in the files you downloaded. -
I do not believe that I have ever refused an update, especially at shutdown. If I was shutting it down I was leaving, especially at 1659. I have refused shut down if I was doing something on line and it was downloading an update. What I saw was interesting was it was waiting to wake from hibernation to down load then this refused to accept update at shut down. Since Windows XP I have never let my computers hibernate. I either leave them running or completely shutdown.
I noticed that keith also had another issue, which I have also had several times, and that is locked p and had to force a shut down, by rebooting. This could have happened. I was also wondering if I used the wusa to extract these files if it would screw up the system? Never have tried to extract windows files, since windows 98. I dont even know if wusa is the appropriate appt. to do this with. -
Let's see what happens when you attempt to register the updating.dll files.Please check to see if these files are present at %windir%\System32 and if they are, what Version level are they at ?
I'm back from rural parts. The Win7 machine had crashed on Thursday evening at a time when I was away, and not using the VPN, and there's no indication of what caused it. A separate problem (maybe/probably) to be worried about later if it does it more often.
wuapi.dll
wuapp.dll
wuauclt.exe
wuaueng.dll
wucltux.dll
wudriver.dll
wups2.dll
wups.dll
wuwebv.dll
MowGreen MVP Data Center Management - Update Services Consumer Security
Here's the information on those files:
wuapi.dll - version 7.3.7000.0 dated 13/12/2008 05:03
wuapp.dll -same version, same date, 05:00
wuauclt.exe - same version, same date, 03:30
wuaueng.dll - same version, same date, 03:32
wucltux.dll - same version, same date, 03:32
wudriver.dll - same version, same date, 03:29
wups2.dll - same version, same date, 03:30
wups.dll - same version, same date, 03:30
wuwebv.dll - same version, same date, 03:29
Open an Elevated Command Prompt.
At the prompt, enter these commands pressing Enter after each one
net stop wuauserv
regsvr32 msxml3.dll
regsvr32 wuapi.dll
regsvr32 wuapp.dll
regsvr32 wuaueng.dll
regsvr32 wucltux.dll
regsvr32 wudriver.dll
regsvr32 wups2.dll
regsvr32 wups.dll
regsvr32 wuwebv.dll
exit
Please note any messages that indicate the registering of the .dll failed.
Now restart the system and try to update.
MowGreen MVP Data Center Management - Update Services Consumer Security -
There are 4 .cab files involved in updating the Windows Update Agent:
WuSetupHandler.cab
WuClient-SelfUpdate-ActiveX.cab
WuClient-SelfUpdate-Aux-TopLevel.cab
WuClient-SelfUpdate-Core-TopLevel.cab
I'm not sure how one would go about extracting and installing the contents of the .cab files.
The operation involves checking previous files versions to evaluate applicability. Said information is located in the registry, WinSxS, and possibly, in Windows\servicing\Packages.
There's no URL to download the latest Version of the WUA that was installed around the middle of February in Win7.
In fact, I doubt it would install due to missing or corrupted file versions in the previously mentioned locations.
Thus, the only recourse at this point in time is:
1) Figure out a method to restore the missing/corrupted files in the previously mentioned locations.
2) Attempt an 'in place' upgrade, which will reinstall the previous Version of the WIndows Update Agent [WUA].
3) Format and reinstall Win7, which will then leave the system with the previous Version of the WUA.
Unfortunately, until someone can figure out why this issue is occurring in the first place, when the next Version of the WUA installs, the issue will reoccur.
Here's the URLs for the 4 .cab files from the WU.log if anyone wants to attempt to figure out how they get installed:
WuSetupHandler.cab
http://download.windowsupdate.com/muv4/windowsupdate/a/selfupdate/WSUS3/x86/Vista/WuSetupHandler.cab
WuClient-SelfUpdate-ActiveX.cab
http://download.windowsupdate.com/muv4/windowsupdate/a/selfupdate/WSUS3/x86/Vista/WuClient-SelfUpdate-ActiveX~31bf3856ad364e35~x86~~7.4.7000.81.cab
WuClient-SelfUpdate-Aux-TopLevel.cab
http://download.windowsupdate.com/muv4/windowsupdate/a/selfupdate/WSUS3/x86/Vista/WuClient-SelfUpdate-Aux-TopLevel~31bf3856ad364e35~x86~~7.4.7000.81.cab
WuClient-SelfUpdate-Core-TopLevel.cab
http://download.windowsupdate.com/muv4/windowsupdate/a/selfupdate/WSUS3/x86/Vista/WUClient-SelfUpdate-Core-TopLevel~31bf3856ad364e35~x86~~7.4.7000.81.cab
The above .cab files were downloaded to the rootdrive's SoftwareDistribution\SelfUpdate\Packages subfolder
If the rootdrive is C:\
C:\SoftwareDistribution\SelfUpdate\Packages
One would have to create the Packages subfolder in SelfUpdate. I *think* that WuSetupV.exe, Windows Update Setup, is the mechanism that downloads the other .cab files. Once they are downloaded, I'm not sure if Windows Module Installer [TrustedInstaller.exe] is what actually performs the extraction and installation or if it's Windows Update Setup that does it.
I suspect the former.
I tried running WuSetupV.exe from an Elevated Command Prompt and it opened an IE instance which informs one that to access Windows Update one must use either the Start Menu shortcut or the WU applet in Control Panel.
That's why I concluded that WuSetupV.exe is the downloading mechanism for the .cabs.
MowGreen MVP Data Center Management - Update Services Consumer Security -
[quote]
At the prompt, enter these commands pressing Enter after each one
net stop wuauserv
regsvr32 msxml3.dll
regsvr32 wuapi.dll
regsvr32 wuapp.dll
regsvr32 wuaueng.dll
regsvr32 wucltux.dll
regsvr32 wudriver.dll
regsvr32 wups2.dll
regsvr32 wups.dll
regsvr32 wuwebv.dll
exit
Please note any messages that indicate the registering of the .dll failed.[/quote]
For some reason, the site won't let me reply to your post - it tells me the site is updating and please try later.
Anyway, all but two of those were successful. I got these messages:
The module "wuapp.dll" failed to load.
Make sure the binary is stored at the specified path or debug it to check for problems with the binary or dependent .DLL files.
The specified module could not be found.
The module "wudriver.dll" was loaded but the entry point DllRegisterServer was not found.
Make sure that "wudriver.dll" is a valid DLL or OCX file and then try again.
There isn't a wuapp.dll in System32, so I tried with wuapi.dll, which worked OK.
I still got the error message with wudriver.dll, which is there. Same error.
I'm now off to reboot the system and see what happens... -
I had some fun restarting the PC (different problem, now sorted).
However, "Update" still delivered the same 8000FFFF error message.
Can someone pm or e-mail me the two files - wuapp.dll and wudriver.dll, or give me a link where I can download them?
If the problem is caused by a glitch in one of those, it makes for a relatively simple fix. -
Sorry, Keith, I made a mistake in a previous post. There is a wuapp.exe, there is no .dll file by that name.
wudriver.dll is the Windows Update WUDriver Stub. That's the .dll the system needs. It has to be the same Version as the other
update files on your system, 7.3.7000.0. That's the original .dll that Win7 installed.
I'm aware of only one method [ besides sfc /scannow, system restore, and reformat/reinstall ] that can do that:
Access Vista Install DVD Files
At this point in time, whether you want to go through all that or not, is entirely up to you. I'm really hoping that this issue is fixed in later builds but, since no one from MS will acknowledge it's an issue, am not holding my breath.
MowGreen MVP Data Center Management - Update Services Consumer Security -
Well, I give up. I attempted to force the cap files to load, but could not get it to respond as it should. I was able to open and extract the cab files and I put them where they belong, but needless to say , I still could not update. I now have reinstalled windows 7 as an update, and everything updated as it should. There where no lost files and the only issue that I had was a driver that Microsoft installed that does not work properly with my wireless card. I gave this information to Microsoft when I first installed Windows 7, but I guess they have not fixed that issue yet. Hopefully it will get fixed with the final version. I have placed that information in another forum. By the way the last update it made was the 7.4.7000.81 version of the Loader. Thanks for everones help, I learned a lot.
-
A while ago I added a SATA drive to this machine (because I had one lying around), and cloned the Win 7 drive to it. I hoped that would predate the problem and provide "clean" versions of those files, but...
a) it didn't (the new drive was installed on Feb 22), and
b) the system wouldn't let me replace the wudriver.dll with the one from the clone anyway. I couldn't even replace it with the machine booted to XP.
I made a copy called wudriver2.dll (no problem doing that) and tried regsvr32 wudriver2.dll but got the same error message about the entry point not being found.
sfc /scannow brings up an error message, and won't run.
Googling revealed quite a few sites offering downloadable versions of wudriver.dll at various levels for Vista machines, so it sounds as if there are ongoing problems with that file.
I'm going to leave it and live without updates, unless anyone has any more ideas (not including reinstalling Win 7, unless it's certain that it won't then tell me it's too late in the Beta testing to install it).
The whole process worries me about the robustness of Win 7. I've been very impressed with it, compared with XP and Vista, apart from this one issue. -
Well, I give up. I attempted to force the cap files to load, but could not get it to respond as it should. I was able to open and extract the cab files and I put them where they belong, but needless to say , I still could not update. I now have reinstalled windows 7 as an update, and everything updated as it should. There where no lost files and the only issue that I had was a driver that Microsoft installed that does not work properly with my wireless card. I gave this information to Microsoft when I first installed Windows 7, but I guess they have not fixed that issue yet. Hopefully it will get fixed with the final version. I have placed that information in another forum. By the way the last update it made was the 7.4.7000.81 version of the Loader. Thanks for everones help, I learned a lot.
@ jpw -
Then the "In Place" upgrade fixed the issue. Cool. Looks like that may very well be quick and easy fix for this issue. And you're welcome for the assitance.
@ KeithjUK -
Yes, I know, you don't want to do it, but looks to me like an "In Place" Upgrade probably will take care of your update woes. Insert the DVD, boot from it, and do an UPGRADE the OS. Given the amount of time you've spent on this. 30 to 45 minutes doing this can't hurt. It will likely save what hair you have left.
@ MowGreen -
You can open .CAB files with utilities like WinZip and WinRAR and extract their contents. -
Well folks. it appears that there are only 2 ways to resolve this issue:
1) An in place 'upgrade'
2) A format and reinstall
@ Wolfie: I'm well aware of how to extract .cab files. The issue was centered on extracting their contents and getting the files installed so that information was being stored in the registry and WinSxS.
This thread is done. If anyone comes across the same or similar issue, please start a new thread.
MowGreen MVP Data Center Management - Update Services Consumer Security- Yanıt Olarak İşaretleyen MowGreenEditor 7 Nisan 2009 Salı 15:46
-
I'm sure Microsoft will likely make the Windows Update files available for Windows 7 (as they did for Vista). Eventually.
@ MowGreen: My bad. I got stuck on one sentence in one of your posts - the bit about extracting from Cab files. Didn't quite finish reading the rest of it.. -
NP, Wolfie. I've seen this issue on Vista systems, too. Even a manual attempt at installing the WUA fails and the User is left with no recourse except the 2 in my previous posts. So, it appears the issue will continue in Win7 until someone can come up with another method to resolve it since MS apparently is under the impression that it's a non-issue.
The method described in KB946414 does not resolve the 8000FFFF error in the situations that I've recently encountered.
I'm done trying to convince anyone that it this is an issue that will have eventually have a major impact.
MowGreen MVP Data Center Management - Update Services Consumer Security -
MowGreen:
I agree. You've given it your best shot. I've tried everything short of reinstalling (which in my view is an admission of defeat). I shall wait quietly, not updating, for the Win 7 Beta to stop working. Then I will have to decide whether to buy the released version or to go back to XP Pro, which "just works".
If Microsoft don't realise 8000FFFF is a problem that needs urgent attention, then they are indeed in trouble. When I was in the world of work, I would by now have put a hand-picked team on an issue like this.
Thanks for your suggestions - I've learned a lot as we've gone along. -
-
Well it seems that you have given up now and decided that the best solution is for a re-install. I would suggest a format and re-install because I have found that if you upgrade you still get the same problems. I tried twice the upgrade path and still got the error. After a full clean install, it went smoothly and has been running about a week now and updates are all installing perfectly. I am running 32 bit on an Emachine laptop and the 64 bit on my desktop. I installed the 64 bit from scratch on the desktop on a seperate drive and I run XP from the other drive, and there are no conflicts. Could the problem have something to do with doing an upgrade rather than a fresh install, possibly causing conflicts between the operating systems. After the length of time that this thread has been open you would have thought that microsoft would have come up with a fix by now ?.
- Düzenleyen nm6174 9 Nisan 2009 Perşembe 02:26 Wasn't complete.
-
I would suggest that anyone that has this issue and wants to salvage their files and programs that are loaded, to at least try an upgrade first. I did and it solved all my problems. I did not even have to go find the drivers for my wireless card. When I went to update the drivers, there were two, Microsofts and my loaded drivers to choose from. That was a neat feature that I did not know about. Windows 7 is much easier to upgrade to itself than XP or Vista. I would say nothing ventured nothing gained. I have a duel boot system with Vista64 and Windows 7. The only suggestion that I have is after the upgrade downloads and gets ready to restart, remove the disk from your dvd drive. I did not and almost did a complete re-install. Windows 7 thanks, "Microsoft", when I went to install it asked again full install or upgrade. I choose upgrade and it gave, must have a version of windows running to perform an upgrade. Removing the disk and restarting Windows 7 found the correct path and upgraded my OS. This is the first time that I have not had driver issues, blue screens, and paths not found, when doing an upgrade. ALL UPDATES WORKED AFTER THE UPGRADE!!!
-
I gave up on this a month ago and just did an in-place upgrade, which fixed it as has been described. I hope that MS is taking this bug seriously, though I highly doubt that there's any chance on getting any feedback on that.
The proof will be in the proverbial pudding - when the RC hits the download servers. If we don't see a rash of 8000FFFF errors on Windows Update, then it's probably fixed. If we do... Well...
Only time will tell. -
Wolfie2k6:
I agree, this fixed this issue, but there will always be another error that will crop up that people like Moe, you, KeithJ, and I will spend several days trying to resolve and it will just go bye, bye. and just because the upgrade fixed it this time, does not mean that it wont comeback again, later down the road. There was an update error on vista, that I got into and I an several others found ways to correct it, but the correction did not work on all machines, and many had to upgrade, or re-install to solve the issue. These type of errors will haunt techs forever. No one wants to give up on an error that will come back and bite them. Again my thanks to MoeGreen, KeithJUK, Wolie2k6 and all the others that make this forum the best place to fix an error on the internet.
John W. -
JPW -
Yeah.. Well... IF and when another issue does pop up, we'll be back to hash the problem out... Keep in mind that an OS the size of Win 7 is a fairly complicated pile of code. There's NO such thing as 100% bug free code when you get as complex as this. That's what we're here for: finding, reporting and squashing bugs.
You're welcome! -
On the basis diminishing returns said we're not going to get to the root of the problem this time around, I did a reinstall - in some trepidation. I chose the "update" route: a fresh install from scratch would have tried my patience too far.
No problems whatever: it installed, went off and got a bunch of updates I'd not had previously, and all is working fine including the update routine. Case closed this time around.
The wu* files are version 7.4.7000.81 dated 9/4/09. The previous ones were 7.3.7000.0 (as above). I have suspicions about the cause of the problem.
If it does it again, I'll start a new thread and put a reference in here. -
-
go to action center, click the drop-down maintenance menu and click check for solutions. do what it says. i had Ox800FFF and it fixed it. it was a registry edit.
What was altered in the registry? It is possible that MS has pushed out a fix, but without details this isn't very helpful. -
Hi charleski
I think RossWiM is referring to the same article that Mark referred to in the 3rd message of this thread.
When I open Windows Update in Control Panel, I receive an error code of 8000FFFF
The only solution seems to be the reinstall.
Regards,
Thank You for testing Windows 7 Beta
Ronnie Vernon MVP -
I suspected as much. That fix, as we all know, is only targeted at Vista.Hi charleski
I think RossWiM is referring to the same article that Mark referred to in the 3rd message of this thread.
When I open Windows Update in Control Panel, I receive an error code of 8000FFFF
The only solution seems to be the reinstall.
The generic 8000FFFF error quite possibly covers a few different underlying faults, however. So it might be interesting to know if removing an errant PendingXmlIdentifier fixes the problem for some people. Without details, though, such a report ('I clicked a button and it fixed it') is no help to anyone.- Yanıt Olarak Öneren jpw-engineer 23 Nisan 2009 Perşembe 15:18
