Microsoft Windows Vista Community Forums - Vistaheads
Recommended Download



Welcome to the Microsoft Windows Vista Community Forums - Vistaheads, YOUR Largest Resource for Windows Vista related information.

You are currently viewing our boards as a guest which gives you limited access to view most discussions and access our other features. By joining our free community you will have access to post topics, communicate privately with other members (PM), respond to polls, upload content and access many other special features. Registration is fast, simple and absolutely free so , join our community today!

If you have any problems with the registration process or your account login, please contact us.

Driver Scanner

Update for Windows Vista KB941649 fails with error 80041002

microsoft.public.windowsupdate






Speedup My PC
Reply
  #1 (permalink)  
Old 12-14-2007
Conley Read
 

Posts: n/a
Update for Windows Vista KB941649 fails with error 80041002
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
Reply With Quote
Sponsored Links
  #2 (permalink)  
Old 12-14-2007
MowGreen [MVP]
 

Posts: n/a
Re: Update for Windows Vista KB941649 fails with error 80041002
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

Reply With Quote
  #3 (permalink)  
Old 12-15-2007
GoGeisel
 

Posts: n/a
Re: Update for Windows Vista KB941649 fails with error 80041002
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

>

Reply With Quote
  #4 (permalink)  
Old 12-18-2007
Conley Read
 

Posts: n/a
Re: Update for Windows Vista KB941649 fails with error 80041002
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

> >

Reply With Quote
  #5 (permalink)  
Old 12-18-2007
Conley Read
 

Posts: n/a
Re: Update for Windows Vista KB941649 fails with error 80041002
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@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@2007/12/13:02:26:51.707 CMIADAPTER: Starting install...

2007-12-12 18:26:51, Info CSI
000000a1@2007/12/13:02:26:51.827 CMIADAPTER: Invoking AI for install...

2007-12-12 18:26:51, Info CSI
000000a2@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@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@2007/12/13:02:26:51.827 CMIADAPTER: AI succeeded.

2007-12-12 18:26:51, Info CSI
000000a5@2007/12/13:02:26:51.827 CMIADAPTER: Exiting with HRESULT code = S_OK.

2007-12-12 18:26:51, Info CSI
00000078@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@2007/12/13:02:26:51.827 CMIADAPTER: Starting install...

2007-12-12 18:26:51, Info CSI
000000a7@2007/12/13:02:26:51.887 CMIADAPTER: Invoking AI for install...

2007-12-12 18:26:51, Info CSI
000000a8@2007/12/13:02:26:51.887 [45]"MOF (install online)
$(runtime.wbem)\wlan.mof"

2007-12-12 18:26:52, Error CSI
000000a9@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@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@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@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@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@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_3ca 54b9fb3dfa6cb"
pid: 5dc starttime: 128419863916085856 (0x01c83d2f92d28260)
2007-12-12 18:27:04, Info CSI
000000ad@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@2007/12/13:02:27:04.946 CMIADAPTER: AI succeeded.

2007-12-12 18:27:04, Info CSI
000000af@2007/12/13:02:27:04.946 CMIADAPTER: Exiting with HRESULT code = S_OK.

2007-12-12 18:27:04, Info CSI
00000083@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

>

Reply With Quote
  #6 (permalink)  
Old 12-18-2007
Conley Read
 

Posts: n/a
Re: Update for Windows Vista KB941649 fails with error 80041002
Fixed.

These are the steps that i used to fix the problem:

Go to Start | Run and open cmd.exe
type: net stop wuauserv
hit ENTER
Navigate to C:\Windows
Rename SoftwareDistribution to SoftwareDistributionOld
In the CMD window type: net start wuauserv
hit ENTER

Open the Windows Update control panel applet and check for updates. Install
any required updates. Make sure that you again install Microsoft Update.

Conley


"Conley Read" wrote:

> 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@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@2007/12/13:02:26:51.707 CMIADAPTER: Starting install...
>
> 2007-12-12 18:26:51, Info CSI
> 000000a1@2007/12/13:02:26:51.827 CMIADAPTER: Invoking AI for install...
>
> 2007-12-12 18:26:51, Info CSI
> 000000a2@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@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@2007/12/13:02:26:51.827 CMIADAPTER: AI succeeded.
>
> 2007-12-12 18:26:51, Info CSI
> 000000a5@2007/12/13:02:26:51.827 CMIADAPTER: Exiting with HRESULT code = S_OK.
>
> 2007-12-12 18:26:51, Info CSI
> 00000078@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@2007/12/13:02:26:51.827 CMIADAPTER: Starting install...
>
> 2007-12-12 18:26:51, Info CSI
> 000000a7@2007/12/13:02:26:51.887 CMIADAPTER: Invoking AI for install...
>
> 2007-12-12 18:26:51, Info CSI
> 000000a8@2007/12/13:02:26:51.887 [45]"MOF (install online)
> $(runtime.wbem)\wlan.mof"
>
> 2007-12-12 18:26:52, Error CSI
> 000000a9@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@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@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@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@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@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_3ca 54b9fb3dfa6cb"
> pid: 5dc starttime: 128419863916085856 (0x01c83d2f92d28260)
> 2007-12-12 18:27:04, Info CSI
> 000000ad@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@2007/12/13:02:27:04.946 CMIADAPTER: AI succeeded.
>
> 2007-12-12 18:27:04, Info CSI
> 000000af@2007/12/13:02:27:04.946 CMIADAPTER: Exiting with HRESULT code = S_OK.
>
> 2007-12-12 18:27:04, Info CSI
> 00000083@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

> >

Reply With Quote
  #7 (permalink)  
Old 12-19-2007
Conley Read
 

Posts: n/a
Re: Update for Windows Vista KB941649 fails with error 80041002
Nevermind. Not fixed.

Just two hours later, Windows Update prompted me to download 941649 again.

The log notes that 941649 failed with error 800F0826 indicating that another
package is keeping 941649 from installing. However, all other updates are
listed as having installed successfully.

Conley

"Conley Read" wrote:

> Fixed.
>
> These are the steps that i used to fix the problem:
>
> Go to Start | Run and open cmd.exe
> type: net stop wuauserv
> hit ENTER
> Navigate to C:\Windows
> Rename SoftwareDistribution to SoftwareDistributionOld
> In the CMD window type: net start wuauserv
> hit ENTER
>
> Open the Windows Update control panel applet and check for updates. Install
> any required updates. Make sure that you again install Microsoft Update.
>
> Conley
>
>
> "Conley Read" wrote:
>
> > 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@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@2007/12/13:02:26:51.707 CMIADAPTER: Starting install...
> >
> > 2007-12-12 18:26:51, Info CSI
> > 000000a1@2007/12/13:02:26:51.827 CMIADAPTER: Invoking AI for install...
> >
> > 2007-12-12 18:26:51, Info CSI
> > 000000a2@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@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@2007/12/13:02:26:51.827 CMIADAPTER: AI succeeded.
> >
> > 2007-12-12 18:26:51, Info CSI
> > 000000a5@2007/12/13:02:26:51.827 CMIADAPTER: Exiting with HRESULT code = S_OK.
> >
> > 2007-12-12 18:26:51, Info CSI
> > 00000078@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@2007/12/13:02:26:51.827 CMIADAPTER: Starting install...
> >
> > 2007-12-12 18:26:51, Info CSI
> > 000000a7@2007/12/13:02:26:51.887 CMIADAPTER: Invoking AI for install...
> >
> > 2007-12-12 18:26:51, Info CSI
> > 000000a8@2007/12/13:02:26:51.887 [45]"MOF (install online)
> > $(runtime.wbem)\wlan.mof"
> >
> > 2007-12-12 18:26:52, Error CSI
> > 000000a9@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@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@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@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@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@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_3ca 54b9fb3dfa6cb"
> > pid: 5dc starttime: 128419863916085856 (0x01c83d2f92d28260)
> > 2007-12-12 18:27:04, Info CSI
> > 000000ad@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@2007/12/13:02:27:04.946 CMIADAPTER: AI succeeded.
> >
> > 2007-12-12 18:27:04, Info CSI
> > 000000af@2007/12/13:02:27:04.946 CMIADAPTER: Exiting with HRESULT code = S_OK.
> >
> > 2007-12-12 18:27:04, Info CSI
> > 00000083@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
> > >

Reply With Quote
  #8 (permalink)  
Old 12-19-2007
Robert Aldwinckle
 

Posts: n/a
Re: Update for Windows Vista KB941649 fails with error 80041002
"Conley Read" <ConleyRead@discussions.microsoft.com> wrote in message
news:9B39681D-CC63-4A60-AF97-13C0A3B73A4B@microsoft.com...
> Nevermind. Not fixed.
>
> Just two hours later, Windows Update prompted me to download 941649 again.
>
> The log notes that 941649 failed with error 800F0826 indicating that another
> package is keeping 941649 from installing. However, all other updates are
> listed as having installed successfully.



See if there are any clues in the Event log.
If you are running the update manually you could try activating its /verbose
logging option. If that isn't sufficient to understand which modules and
which apps are causing your problem you could also supplement that logging
by running ProcMon. E.g. that would capture any registry and file
operations which might be related to the log entries you do see.
Fortunately each separate write of a log record is recorded along with its
length, which allows us to infer a more accurate timestamp for each one.
Tip: use Notepad's Status bar with Word Wrap off and press End to see
the approximate length of a line. The length of its write usually would be
exactly 1 byte longer.

Looking at the list of modules being changed by that update
it may be a bit impractical to try checking them all manually but I think it could
be worthwhile to find out which one is the problem. Tip: when the modules
are loaded you can use tools such as msinfo32.exe and Process Explorer
and sort their module lists by the Version field to quickly check modules for
some particular version numbers.


Good luck

Robert Aldwinckle
---


>
> Conley
>
> "Conley Read" wrote:
>
>> Fixed.
>>
>> These are the steps that i used to fix the problem:
>>
>> Go to Start | Run and open cmd.exe
>> type: net stop wuauserv
>> hit ENTER
>> Navigate to C:\Windows
>> Rename SoftwareDistribution to SoftwareDistributionOld
>> In the CMD window type: net start wuauserv
>> hit ENTER
>>
>> Open the Windows Update control panel applet and check for updates. Install
>> any required updates. Make sure that you again install Microsoft Update.
>>
>> Conley
>>
>>
>> "Conley Read" wrote:
>>
>> > 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@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@2007/12/13:02:26:51.707 CMIADAPTER: Starting install...
>> >
>> > 2007-12-12 18:26:51, Info CSI
>> > 000000a1@2007/12/13:02:26:51.827 CMIADAPTER: Invoking AI for install...
>> >
>> > 2007-12-12 18:26:51, Info CSI
>> > 000000a2@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@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@2007/12/13:02:26:51.827 CMIADAPTER: AI succeeded.
>> >
>> > 2007-12-12 18:26:51, Info CSI
>> > 000000a5@2007/12/13:02:26:51.827 CMIADAPTER: Exiting with HRESULT code = S_OK.
>> >
>> > 2007-12-12 18:26:51, Info CSI
>> > 00000078@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@2007/12/13:02:26:51.827 CMIADAPTER: Starting install...
>> >
>> > 2007-12-12 18:26:51, Info CSI
>> > 000000a7@2007/12/13:02:26:51.887 CMIADAPTER: Invoking AI for install...
>> >
>> > 2007-12-12 18:26:51, Info CSI
>> > 000000a8@2007/12/13:02:26:51.887 [45]"MOF (install online)
>> > $(runtime.wbem)\wlan.mof"
>> >
>> > 2007-12-12 18:26:52, Error CSI
>> > 000000a9@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@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@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@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@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@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_3ca 54b9fb3dfa6cb"
>> > pid: 5dc starttime: 128419863916085856 (0x01c83d2f92d28260)
>> > 2007-12-12 18:27:04, Info CSI
>> > 000000ad@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@2007/12/13:02:27:04.946 CMIADAPTER: AI succeeded.
>> >
>> > 2007-12-12 18:27:04, Info CSI
>> > 000000af@2007/12/13:02:27:04.946 CMIADAPTER: Exiting with HRESULT code = S_OK.
>> >
>> > 2007-12-12 18:27:04, Info CSI
>> > 00000083@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
>> > >



Reply With Quote
  #9 (permalink)  
Old 12-19-2007
vkrupach
 

Posts: n/a
Re: Update for Windows Vista KB941649 fails with error 80041002

Hello Conley,

Looks like I resolve the problem with patch 941649 failing with error
800F0826.

In the CBS.log I found that the 941649 because it can not find the
path to files from the C:\Windows\System32\wbem\. After I added the
C:\Windows\System32\wbem\ to the Path (Computer -> Properties ->
Advanced System Settings -> tab Advanced -> Environment Variables ->
System Variables list -> "Path" variable) the update was successfully
installed.

I compared my Path wit Path on my colleague's computer and found that
some bad bad installation (I suspect it was adobe ColdFusion) removed
system paths that should be like:
%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\Sy stem32\Wbem;

Hope this help!

Thank you,
Volodia


--
vkrupach
------------------------------------------------------------------------
vkrupach's Profile: http://forums.techarena.in/member.php?userid=37723
View this thread: http://forums.techarena.in/showthread.php?t=871357

http://forums.techarena.in

Reply With Quote
  #10 (permalink)  
Old 12-19-2007
MowGreen [MVP]
 

Posts: n/a
Re: Update for Windows Vista KB941649 fails with error 80041002
I agree with Robert about the Event log. Not having Vista installed,
let's see if I can remember where to look for this error :

2007-12-12 18:26:52, Error CSI
> 000000aa@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]


Eventvwr.msc > Applications and Services Log > Microsoft > Windows >
WindowsUpdateClient > Operational

Component Based Servicing is tricky to troubleshoot. Basically, the
entire update contains packages. When one package fails to install the
update can be repeatedly reoffered.

Suggest you first check the Environmental Variable as posted by Volodia.

If it isn't pertinent to this issue suggest you try to register
wmiutils.dll from an Elevated Command Prompt.

Click Start > type cmd in the Start Search box > right-click cmd in the
Programs list, and then click 'Run as administrator'.

User Account Control permission: If you are prompted for an
administrator password or confirmation, type the password or click
Continue if no password is in use.

At the Command Prompt type the following in, *pressing Enter* after each
command:

regsvr32 wmiutils.dll
exit

Restart the system and see if KB941649 installs now.


MowGreen [MVP 2003-2008]
===============
*-343-* FDNY
Never Forgotten
===============


Robert Aldwinckle wrote:

> "Conley Read" <ConleyRead@discussions.microsoft.com> wrote in message
> news:9B39681D-CC63-4A60-AF97-13C0A3B73A4B@microsoft.com...
>
>>Nevermind. Not fixed.
>>
>>Just two hours later, Windows Update prompted me to download 941649 again.
>>
>>The log notes that 941649 failed with error 800F0826 indicating that another
>>package is keeping 941649 from installing. However, all other updates are
>>listed as having installed successfully.

>
>
>
> See if there are any clues in the Event log.
> If you are running the update manually you could try activating its /verbose
> logging option. If that isn't sufficient to understand which modules and
> which apps are causing your problem you could also supplement that logging
> by running ProcMon. E.g. that would capture any registry and file
> operations which might be related to the log entries you do see.
> Fortunately each separate write of a log record is recorded along with its
> length, which allows us to infer a more accurate timestamp for each one.
> Tip: use Notepad's Status bar with Word Wrap off and press End to see
> the approximate length of a line. The length of its write usually would be
> exactly 1 byte longer.
>
> Looking at the list of modules being changed by that update
> it may be a bit impractical to try checking them all manually but I think it could
> be worthwhile to find out which one is the problem. Tip: when the modules
> are loaded you can use tools such as msinfo32.exe and Process Explorer
> and sort their module lists by the Version field to quickly check modules for
> some particular version numbers.
>
>
> Good luck
>
> Robert Aldwinckle
> ---
>
>
>
>>Conley
>>
>>"Conley Read" wrote:
>>
>>
>>>Fixed.
>>>
>>>These are the steps that i used to fix the problem:
>>>
>>>Go to Start | Run and open cmd.exe
>>>type: net stop wuauserv
>>>hit ENTER
>>>Navigate to C:\Windows
>>>Rename SoftwareDistribution to SoftwareDistributionOld
>>>In the CMD window type: net start wuauserv
>>>hit ENTER
>>>
>>>Open the Windows Update control panel applet and check for updates. Install
>>>any required updates. Make sure that you again install Microsoft Update.
>>>
>>>Conley
>>>
>>>
>>>"Conley Read" wrote:
>>>
>>>
>>>>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@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@2007/12/13:02:26:51.707 CMIADAPTER: Starting install...
>>>>
>>>>2007-12-12 18:26:51, Info CSI
>>>>000000a1@2007/12/13:02:26:51.827 CMIADAPTER: Invoking AI for install...
>>>>
>>>>2007-12-12 18:26:51, Info CSI
>>>>000000a2@2007/12/13:02:26:51.827 [123]"Computing EffectiveSddl for registry
>>>>key
>>>>MACHINE\SYSTEM\CurrentControlSet\Control\Winlo gon\Notifications\Components\Wlansvc"
>>>>
>>>>2007-12-12 18:26:51, Info CSI
>>>>000000a3@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\Winlo gon\Notifications\Components\Wlansvc"
>>>>
>>>>2007-12-12 18:26:51, Info CSI
>>>>000000a4@2007/12/13:02:26:51.827 CMIADAPTER: AI succeeded.
>>>>
>>>>2007-12-12 18:26:51, Info CSI
>>>>000000a5@2007/12/13:02:26:51.827 CMIADAPTER: Exiting with HRESULT code = S_OK.
>>>>
>>>>2007-12-12 18:26:51, Info CSI
>>>>00000078@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@2007/12/13:02:26:51.827 CMIADAPTER: Starting install...
>>>>
>>>>2007-12-12 18:26:51, Info CSI
>>>>000000a7@2007/12/13:02:26:51.887 CMIADAPTER: Invoking AI for install...
>>>>
>>>>2007-12-12 18:26:51, Info CSI
>>>>000000a8@2007/12/13:02:26:51.887 [45]"MOF (install online)
>>>>$(runtime.wbem)\wlan.mof"
>>>>
>>>>2007-12-12 18:26:52, Error CSI
>>>>000000a9@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@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@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@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@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@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_3ca 54b9fb3dfa6cb"
>>>>pid: 5dc starttime: 128419863916085856 (0x01c83d2f92d28260)
>>>>2007-12-12 18:27:04, Info CSI
>>>>000000ad@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@2007/12/13:02:27:04.946 CMIADAPTER: AI succeeded.
>>>>
>>>>2007-12-12 18:27:04, Info CSI
>>>>000000af@2007/12/13:02:27:04.946 CMIADAPTER: Exiting with HRESULT code = S_OK.
>>>>
>>>>2007-12-12 18:27:04, Info CSI
>>>>00000083@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
>>>>>

>
>

Reply With Quote
Reply


Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off

Similar Threads
Thread Thread Starter Forum Replies Last Post
Update for Windows Vista (KB941649) failed Derek microsoft.public.windows.vista.general 3 12-15-2007 21:28
Error Code 8007007E Vista update KB941649 Rinaldo1961 microsoft.public.windowsupdate 2 12-10-2007 16:41
I cannot update 1 particular update - KB941649- Error Code 8007000 Shaunyboy microsoft.public.windowsupdate 11 11-29-2007 00:55
Update for Windows Vista (KB941649) digger microsoft.public.windows.vista.performance maintenance 1 11-26-2007 01:08
Windows update fails - Vista Home Premium Error 80040153 newschapmj1 microsoft.public.windows.vista.general 3 10-01-2007 07:54




All times are GMT +1. The time now is 09:46.




Driver Scanner - Free Scan Now

Vistaheads.com is part of the Heads Network. See also XPHeads.com , Win7Heads.com and Win8Heads.com.


Design by Vjacheslav Trushkin for phpBBStyles.com.
Powered by vBulletin® Version 3.6.7
Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Search Engine Optimization by vBSEO 3.6.0 RC 2

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120