Update for Windows Vista KB941649 fails with error 80041002
in [Windows Update]
|
Prev: 0x13EC Error
Next: why cant i get windows update
From: Conley Read Conley on 14 Dec 2007 00:24 The update for Windows Vista KB941649 repeatedly fails to install with the error code 80041002. Since the update has been available on Windows Update, Vista has continued to remind me to install the update, yet, each time i proceed with the installation, the update appears to successfully install and requests reboot. After reboot, Vista reports "Configuring Updates..." during startup. When 2 minutes pass with the startup message still showing "Configuring Updates...", my computer reboots again. This time, the login screen appears but after logging in, Windows Update reports that the last update installation was unsuccessful. Occasionally, this update fails to install with the code 800F0826. This error indicates that another update may be preventing the installation of 841649. However, all other updates to date have installed successfully. Update 941649 continues to reappear after each reboot, leading me to believe that if my windows update settings allowed updates to automatically install, my machine would be stuck in an endless loop? I have tried updating using the file from KB941649 article for 32bit Windows Vista but i get the same scenario and failed installation. This occurs on a IBM T42p with 2GB Ram and ATI 128MB with Vista Business - more details on request. I also have a desktop that experienced a Blue Screen Error when first installing 941649, but it then installed successfully. I have to note that that was the first Blue Screen i ever encountered on that machine... I think this update brought more problems than resolutions... Conley
From: MowGreen [MVP] on 14 Dec 2007 04:31 If you dare to ... open the CBS.log located at %windir%\logs\CBS\cbs.log I suspect that an update included in the package failed to install properly. Start at the bottom of the log and work your way back up until you find an xml entry. That *should* give you an idea of the component that failed to install. MowGreen [MVP 2003-2008] =============== *-343-* FDNY Never Forgotten =============== Conley Read wrote: > The update for Windows Vista KB941649 repeatedly fails to install with the > error code 80041002. > > Since the update has been available on Windows Update, Vista has continued > to remind me to install the update, yet, each time i proceed with the > installation, the update appears to successfully install and requests reboot. > After reboot, Vista reports "Configuring Updates..." during startup. When 2 > minutes pass with the startup message still showing "Configuring Updates...", > my computer reboots again. This time, the login screen appears but after > logging in, Windows Update reports that the last update installation was > unsuccessful. > > Occasionally, this update fails to install with the code 800F0826. This > error indicates that another update may be preventing the installation of > 841649. However, all other updates to date have installed successfully. > > Update 941649 continues to reappear after each reboot, leading me to believe > that if my windows update settings allowed updates to automatically install, > my machine would be stuck in an endless loop? > > I have tried updating using the file from KB941649 article for 32bit Windows > Vista but i get the same scenario and failed installation. > > This occurs on a IBM T42p with 2GB Ram and ATI 128MB with Vista Business - > more details on request. > > I also have a desktop that experienced a Blue Screen Error when first > installing 941649, but it then installed successfully. I have to note that > that was the first Blue Screen i ever encountered on that machine... > > I think this update brought more problems than resolutions... > > Conley
From: GoGeisel on 14 Dec 2007 19:01 i am working in vista and when I try to open this file it says "access denied" I am the administrator so whats the deal with that. Everyone has this problem, will it be resolved with Vista SP1? "MowGreen [MVP]" wrote: > If you dare to ... open the CBS.log located at > %windir%\logs\CBS\cbs.log > I suspect that an update included in the package failed to install > properly. > Start at the bottom of the log and work your way back up until you find > an xml entry. That *should* give you an idea of the component that > failed to install. > > MowGreen [MVP 2003-2008] > =============== > *-343-* FDNY > Never Forgotten > =============== > > > > Conley Read wrote: > > > The update for Windows Vista KB941649 repeatedly fails to install with the > > error code 80041002. > > > > Since the update has been available on Windows Update, Vista has continued > > to remind me to install the update, yet, each time i proceed with the > > installation, the update appears to successfully install and requests reboot. > > After reboot, Vista reports "Configuring Updates..." during startup. When 2 > > minutes pass with the startup message still showing "Configuring Updates...", > > my computer reboots again. This time, the login screen appears but after > > logging in, Windows Update reports that the last update installation was > > unsuccessful. > > > > Occasionally, this update fails to install with the code 800F0826. This > > error indicates that another update may be preventing the installation of > > 841649. However, all other updates to date have installed successfully. > > > > Update 941649 continues to reappear after each reboot, leading me to believe > > that if my windows update settings allowed updates to automatically install, > > my machine would be stuck in an endless loop? > > > > I have tried updating using the file from KB941649 article for 32bit Windows > > Vista but i get the same scenario and failed installation. > > > > This occurs on a IBM T42p with 2GB Ram and ATI 128MB with Vista Business - > > more details on request. > > > > I also have a desktop that experienced a Blue Screen Error when first > > installing 941649, but it then installed successfully. I have to note that > > that was the first Blue Screen i ever encountered on that machine... > > > > I think this update brought more problems than resolutions... > > > > Conley >
From: Conley Read on 18 Dec 2007 16:55 You are likely being denied access to the log file because it is being accessed by another application. Try closing the Windows Update control panel applet and trying to access the file again. Conley "GoGeisel" wrote: > i am working in vista and when I try to open this file it says "access > denied" I am the administrator so whats the deal with that. > Everyone has this problem, will it be resolved with Vista SP1? > > "MowGreen [MVP]" wrote: > > > If you dare to ... open the CBS.log located at > > %windir%\logs\CBS\cbs.log > > I suspect that an update included in the package failed to install > > properly. > > Start at the bottom of the log and work your way back up until you find > > an xml entry. That *should* give you an idea of the component that > > failed to install. > > > > MowGreen [MVP 2003-2008] > > =============== > > *-343-* FDNY > > Never Forgotten > > =============== > > > > > > > > Conley Read wrote: > > > > > The update for Windows Vista KB941649 repeatedly fails to install with the > > > error code 80041002. > > > > > > Since the update has been available on Windows Update, Vista has continued > > > to remind me to install the update, yet, each time i proceed with the > > > installation, the update appears to successfully install and requests reboot. > > > After reboot, Vista reports "Configuring Updates..." during startup. When 2 > > > minutes pass with the startup message still showing "Configuring Updates...", > > > my computer reboots again. This time, the login screen appears but after > > > logging in, Windows Update reports that the last update installation was > > > unsuccessful. > > > > > > Occasionally, this update fails to install with the code 800F0826. This > > > error indicates that another update may be preventing the installation of > > > 841649. However, all other updates to date have installed successfully. > > > > > > Update 941649 continues to reappear after each reboot, leading me to believe > > > that if my windows update settings allowed updates to automatically install, > > > my machine would be stuck in an endless loop? > > > > > > I have tried updating using the file from KB941649 article for 32bit Windows > > > Vista but i get the same scenario and failed installation. > > > > > > This occurs on a IBM T42p with 2GB Ram and ATI 128MB with Vista Business - > > > more details on request. > > > > > > I also have a desktop that experienced a Blue Screen Error when first > > > installing 941649, but it then installed successfully. I have to note that > > > that was the first Blue Screen i ever encountered on that machine... > > > > > > I think this update brought more problems than resolutions... > > > > > > Conley > >
From: Conley Read on 18 Dec 2007 17:16
MowGreen, Thanks for the direction. I took a look at the log file. A few things look problematic to me. There appears to be a successful installation of the package before the failed installation. Then, the package that is listed as "new" is a lower version than the "old." Note: Old component: Microsoft-Windows-Wlansvc, Version = 6.0.6000.16551, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral New component: Microsoft-Windows-Wlansvc, Version = 6.0.6000.16386, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral The package causing the error is "Microsoft-Windows-Wlansvc." Is it possible that the package successfully installed, but that an error is causing the package to be listed in windows update anyway? Or, is the package corrupted and caught in an install loop or something similar? Here is the error line: 2007-12-12 18:26:52, Error CSI 000000a9(a)2007/12/13:02:26:52.598 (F) CMIADAPTER: Inner Error Message from AI HRESULT = 80041002 [Error,Facility=FACILITY_ITF,Code=4098 (0x1002)] [ [138]"An error occurred while creating object 1 defined on lines 14 - 67: 0X80041002 Class, instance, or property 'EventTrace' was not found. " I have included more context from the log below. Conley --- 2007-12-12 18:26:51, Info CSI 00000077 Begin executing advanced installer phase 32 (0x00000020) index 54 (0x00000036) (sequence 87) Old component: Microsoft-Windows-Wlansvc, Version = 6.0.6000.16551, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral New component: Microsoft-Windows-Wlansvc, Version = 6.0.6000.16386, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral Install mode: install Installer ID: {51d813ef-83f1-42de-a2ee-89ee4633a7c9} Installer name: [15]"Registry Key SD" 2007-12-12 18:26:51, Info CSI 000000a0(a)2007/12/13:02:26:51.707 CMIADAPTER: Starting install... 2007-12-12 18:26:51, Info CSI 000000a1(a)2007/12/13:02:26:51.827 CMIADAPTER: Invoking AI for install... 2007-12-12 18:26:51, Info CSI 000000a2(a)2007/12/13:02:26:51.827 [123]"Computing EffectiveSddl for registry key MACHINE\SYSTEM\CurrentControlSet\Control\Winlogon\Notifications\Components\Wlansvc" 2007-12-12 18:26:51, Info CSI 000000a3(a)2007/12/13:02:26:51.827 [153]"Applying ACL D:P(A;;GRGX;;;BU)(A;;GA;;;BA)(A;;GA;;;SY) to registry key MACHINE\SYSTEM\CurrentControlSet\Control\Winlogon\Notifications\Components\Wlansvc" 2007-12-12 18:26:51, Info CSI 000000a4(a)2007/12/13:02:26:51.827 CMIADAPTER: AI succeeded. 2007-12-12 18:26:51, Info CSI 000000a5(a)2007/12/13:02:26:51.827 CMIADAPTER: Exiting with HRESULT code = S_OK. 2007-12-12 18:26:51, Info CSI 00000078(a)2007/12/13:02:26:51.827 CSI Advanced installer perf trace: CSIPERF:AIDONE;{51d813ef-83f1-42de-a2ee-89ee4633a7c9};Microsoft-Windows-Wlansvc, Version = 6.0.6000.16386, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral;140072 2007-12-12 18:26:51, Info CSI 00000079 End executing advanced installer (sequence 87) Completion status: S_OK --- 2007-12-12 18:26:51, Info CSI 0000007a Begin executing advanced installer phase 32 (0x00000020) index 55 (0x00000037) (sequence 88) Old component: Microsoft-Windows-Wlansvc, Version = 6.0.6000.16551, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral New component: Microsoft-Windows-Wlansvc, Version = 6.0.6000.16386, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral Install mode: install Installer ID: {9f4ec79f-3a97-4772-b635-2899468900a2} Installer name: [3]"Mof" 2007-12-12 18:26:51, Info CSI 000000a6(a)2007/12/13:02:26:51.827 CMIADAPTER: Starting install... 2007-12-12 18:26:51, Info CSI 000000a7(a)2007/12/13:02:26:51.887 CMIADAPTER: Invoking AI for install... 2007-12-12 18:26:51, Info CSI 000000a8(a)2007/12/13:02:26:51.887 [45]"MOF (install online) $(runtime.wbem)\wlan.mof" 2007-12-12 18:26:52, Error CSI 000000a9(a)2007/12/13:02:26:52.598 (F) CMIADAPTER: Inner Error Message from AI HRESULT = 80041002 [Error,Facility=FACILITY_ITF,Code=4098 (0x1002)] [ [138]"An error occurred while creating object 1 defined on lines 14 - 67: 0X80041002 Class, instance, or property 'EventTrace' was not found. " ] [gle=0x80004005] 2007-12-12 18:26:52, Error CSI 000000aa(a)2007/12/13:02:26:52.598 (F) CMIADAPTER: AI failed. HRESULT = 80041002 [Error,Facility=FACILITY_ITF,Code=4098 (0x1002)] Element: [80]"<mof xmlns="urn:schemas-microsoft-com:asm.v3" name="$(runtime.wbem)\wlan.mof" />" [gle=0x80004005] 2007-12-12 18:26:52, Error CSI 000000ab(a)2007/12/13:02:26:52.598 (F) CMIADAPTER: Exiting with HRESULT code = 80041002 [Error,Facility=FACILITY_ITF,Code=4098 (0x1002)]. [gle=0x80004005] 2007-12-12 18:26:52, Info CSI 0000007b(a)2007/12/13:02:26:52.598 CSI Advanced installer perf trace: CSIPERF:AIDONE;{9f4ec79f-3a97-4772-b635-2899468900a2};Microsoft-Windows-Wlansvc, Version = 6.0.6000.16386, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral;918103 2007-12-12 18:26:52, Error CSI 0000007c (F) Failed execution of queue item Installer: Mof ({9f4ec79f-3a97-4772-b635-2899468900a2}) with HRESULT 80041002 [Error,Facility=FACILITY_ITF,Code=4098 (0x1002)]. Failure will be ignored: The failure was encountered during rollback; installer is reliable (2)[gle=0x80004005] 2007-12-12 18:27:04, Info CSI 0000007d End executing advanced installer (sequence 88) Completion status: S_OK --- 2007-12-12 18:27:04, Info CSI 0000007e Begin executing advanced installer phase 32 (0x00000020) index 56 (0x00000038) (sequence 89) Old component: Microsoft-Windows-Wlansvc, Version = 6.0.6000.16551, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral New component: Microsoft-Windows-Wlansvc, Version = 6.0.6000.16386, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral Install mode: delta Installer ID: {188cac44-e174-4170-ab26-a475e3106f3b} Installer name: [7]"File SD" 2007-12-12 18:27:04, Info CSI 0000007f(a)2007/12/13:02:27:04.906 CSI Advanced installer perf trace: CSIPERF:AIDONE;{188cac44-e174-4170-ab26-a475e3106f3b};Microsoft-Windows-Wlansvc, Version = 6.0.6000.16386, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral;15503 2007-12-12 18:27:04, Info CSI 00000080 End executing advanced installer (sequence 89) Completion status: S_OK --- 2007-12-12 18:27:04, Info CSI 00000081 Begin executing advanced installer phase 32 (0x00000020) index 57 (0x00000039) (sequence 90) Old component: Microsoft-Windows-Wlansvc, Version = 6.0.6000.16551, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral New component: Microsoft-Windows-Wlansvc, Version = 6.0.6000.16386, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral Install mode: install Installer ID: {8303bcc9-58cb-4a37-b9fc-9c34bc30d85c} Installer name: [3]"SMI" 2007-12-12 18:27:04, Info CSI 000000ac(a)2007/12/13:02:27:04.906 CMIADAPTER: Starting install... 2007-12-12 18:27:04, Info CSI 00000082 Performing 1 operations; 1 are not lock/unlock and follow: LockComponentPath (10): flags: 0 comp: {l:16 b:9079b1a62f3dc8013d000000dc058405} pathid: {l:16 b:9079b1a62f3dc8013e000000dc058405} path: [l:216{108}]"\SystemRoot\WinSxS\x86_microsoft-windows-smi-installer_1122334455667788_6.0.6000.16386_none_3ca54b9fb3dfa6cb" pid: 5dc starttime: 128419863916085856 (0x01c83d2f92d28260) 2007-12-12 18:27:04, Info CSI 000000ad(a)2007/12/13:02:27:04.946 CMIADAPTER: Invoking AI for install... 2007-12-12 18:27:04, Info CSI 00000009 done 2007-12-12 18:27:04, Info CSI 000000ae(a)2007/12/13:02:27:04.946 CMIADAPTER: AI succeeded. 2007-12-12 18:27:04, Info CSI 000000af(a)2007/12/13:02:27:04.946 CMIADAPTER: Exiting with HRESULT code = S_OK. 2007-12-12 18:27:04, Info CSI 00000083(a)2007/12/13:02:27:04.946 CSI Advanced installer perf trace: CSIPERF:AIDONE;{8303bcc9-58cb-4a37-b9fc-9c34bc30d85c};Microsoft-Windows-Wlansvc, Version = 6.0.6000.16386, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral;48036 2007-12-12 18:27:04, Info CSI 00000084 End executing advanced installer (sequence 90) Completion status: S_OK "MowGreen [MVP]" wrote: > If you dare to ... open the CBS.log located at > %windir%\logs\CBS\cbs.log > I suspect that an update included in the package failed to install > properly. > Start at the bottom of the log and work your way back up until you find > an xml entry. That *should* give you an idea of the component that > failed to install. > > MowGreen [MVP 2003-2008] > =============== > *-343-* FDNY > Never Forgotten > =============== > > > > Conley Read wrote: > > > The update for Windows Vista KB941649 repeatedly fails to install with the > > error code 80041002. > > > > Since the update has been available on Windows Update, Vista has continued > > to remind me to install the update, yet, each time i proceed with the > > installation, the update appears to successfully install and requests reboot. > > After reboot, Vista reports "Configuring Updates..." during startup. When 2 > > minutes pass with the startup message still showing "Configuring Updates...", > > my computer reboots again. This time, the login screen appears but after > > logging in, Windows Update reports that the last update installation was > > unsuccessful. > > > > Occasionally, this update fails to install with the code 800F0826. This > > error indicates that another update may be preventing the installation of > > 841649. However, all other updates to date have installed successfully. > > > > Update 941649 continues to reappear after each reboot, leading me to believe > > that if my windows update settings allowed updates to automatically install, > > my machine would be stuck in an endless loop? > > > > I have tried updating using the file from KB941649 article for 32bit Windows > > Vista but i get the same scenario and failed installation. > > > > This occurs on a IBM T42p with 2GB Ram and ATI 128MB with Vista Business - > > more details on request. > > > > I also have a desktop that experienced a Blue Screen Error when first > > installing 941649, but it then installed successfully. I have to note that > > that was the first Blue Screen i ever encountered on that machine... > > > > I think this update brought more problems than resolutions... > > > > Conley > |