KB898461 successfull but keeps wanting to do it again

I have installed the new permanent package installer probably 60 times over
the last few weeks. It always says it's successful, however automatic
updates AND windows update always says I need to install it.

I have tried every suggestion I can find, deleteing and/or renameing files
and folders. Re-registering dlls. I have tried it beofre and after SP2
intall. I even completely reinstalled windows (xp pro) from scratch and
began updates and it got me to the same place. Need to install
kb898461...... I do it, it works... then It says I need to do it again, so I
can't get any of the other updates I need. My update history shows all were
successful.

It's driving me crazy. It all started with needing/wanting to install .net
framework and I needed to do it through windows update, yada yada yada....

Please help if you can.

msiebels wrote:

> I have installed the new permanent package installer probably 60 times over
> the last few weeks. It always says it's successful, however automatic
> updates AND windows update always says I need to install it.
>
> I have tried every suggestion I can find, deleteing and/or renameing files
> and folders.

Have you renamed spupdsvc.exe?

Herr_Mord found that renaming c:\windows\system32\spupdsvc.exe
solved the KB898461 install problem for him:

http://groups.google.co.uk/group/mic...9e8e589?hl=en&


Also see if the install log file for kb898461 give you any tip:

From Start/Run:

notepad.exe %windir%\kb898461.log


> Re-registering dlls. I have tried it beofre and after SP2
> intall. I even completely reinstalled windows (xp pro) from scratch and
> began updates and it got me to the same place. Need to install
> kb898461...... I do it, it works... then It says I need to do it again, so I
> can't get any of the other updates I need. My update history shows all were
> successful.
>
> It's driving me crazy. It all started with needing/wanting to install .net
> framework and I needed to do it through windows update, yada yada yada....
>
> Please help if you can.


--
torgeir, Microsoft MVP Scripting, Porsgrunn Norway
Administration scripting examples and an ONLINE version of
the 1328 page Scripting Guide:
http://www.microsoft.com/technet/scr...r/default.mspx

Yep, no good. I've also downloaded the (can't remember the exact
terminology) "stand alone" install file, same thing.

I tried to post my update log here, but copied too much. I haven't looked
at the kb898461 specific log, I'll do that and try and post some of it back
here.

Thanks

"Torgeir Bakken (MVP)" wrote:

> msiebels wrote:
>
> > I have installed the new permanent package installer probably 60 times over
> > the last few weeks. It always says it's successful, however automatic
> > updates AND windows update always says I need to install it.
> >
> > I have tried every suggestion I can find, deleteing and/or renameing files
> > and folders.
>
> Have you renamed spupdsvc.exe?
>
> Herr_Mord found that renaming c:\windows\system32\spupdsvc.exe
> solved the KB898461 install problem for him:
>
> http://groups.google.co.uk/group/mic...9e8e589?hl=en&
>
>
> Also see if the install log file for kb898461 give you any tip:
>
> From Start/Run:
>
> notepad.exe %windir%\kb898461.log
>
>
> > Re-registering dlls. I have tried it beofre and after SP2
> > intall. I even completely reinstalled windows (xp pro) from scratch and
> > began updates and it got me to the same place. Need to install
> > kb898461...... I do it, it works... then It says I need to do it again, so I
> > can't get any of the other updates I need. My update history shows all were
> > successful.
> >
> > It's driving me crazy. It all started with needing/wanting to install .net
> > framework and I needed to do it through windows update, yada yada yada....
> >
> > Please help if you can.
>
>
> --
> torgeir, Microsoft MVP Scripting, Porsgrunn Norway
> Administration scripting examples and an ONLINE version of
> the 1328 page Scripting Guide:
> http://www.microsoft.com/technet/scr...r/default.mspx
>

Here's part of my kb898461 log. I see it says someing about update.ver file
not correct? I believe my windows key is valid and have done that windows
uodate verification tool nd it worked fine. But could that be the problem?
This is a Development box, and I'm useing a key from my MSDN subscription. I
haven't installed it more then 10 times (the MSDN limit) I don't think.
Anyway here is part of my Log, thanks for your help.

Oh yea, the other thing is KB898461 shows up in my add and remove programs
as installed (I guess), but it dosn't have the "normal" info, like last used,
when it was installed, ect. it just says "this update cannot be removed"? My
only other update is "windows installer 3.1", medeia player, and SP2. Again
thanks

1.344: 2005/10/11 20:03:08.281 (local)
1.344:
C:\WINDOWS\SoftwareDistribution\Download\126638ad8 0a740243aeee66683d803a7\update\update.exe (version 6.1.22.4)
1.344: Failed To Enable SE_SHUTDOWN_PRIVILEGE
1.344: Hotfix started with following command line: -q -z -er
/ParentInfo:9ba538a098383943a9aea8d0d7eb7cb6
2.734: In Function TestVolatileFlag, line 11660, RegOpenKeyEx failed with
error 0x2
2.734: In Function TestVolatileFlag, line 11692, RegOpenKeyEx failed with
error 0x2
2.734: DoInstallation: CleanPFR failed: 0x2
2.734: SetProductTypes: InfProductBuildType=BuildType.IP
2.734: SetAltOsLoaderPath: No section uses DirId 65701; done.
2.765: DoInstallation: FetchSourceURL for
c:\windows\softwaredistribution\download\126638ad8 0a740243aeee66683d803a7\update\update_SP2GDR.inf failed
2.765: CreateUninstall = 0,Directory = C:\WINDOWS\$NtUninstallKB898461$
2.765: LoadFileQueues: UpdSpGetSourceFileLocation for halaacpi.dll failed:
0xe0000102
2.859: BuildCabinetManifest: update.url absent
2.859: Starting AnalyzeComponents
2.859: AnalyzePhaseZero used 0 ticks
2.875: No c:\windows\INF\updtblk.inf file.
2.875: OEM file scan used 0 ticks
5.031: GetTargetExists: GetFileAttributesEx(
c:\windows\system32\preinstall\winse\wxp_x86_0409_ v1\spcustom.dll.ref )
failed (23)
9.156: GetTargetExists: GetFileAttributesEx(
c:\windows\system32\preinstall\winse\wxp_x86_0409_ v1\spcustom.dll.ref )
failed (23)
10.281: AnalyzePhaseOne: used 7422 ticks
10.281: AnalyzeComponents: Hotpatch analysis disabled; skipping.
10.281: AnalyzeComponents: Hotpatching is disabled.
10.281: FindFirstFile c:\windows\$hf_mig$\*.*
10.328: KB898461 Setup encountered an error: The update.ver file is not
correct.
10.437: KB898461 Setup encountered an error: The update.ver file is not
correct.
10.531: KB898461 Setup encountered an error: The update.ver file is not
correct.
10.578: KB898461 Setup encountered an error: The update.ver file is not
correct.
10.609: KB898461 Setup encountered an error: The update.ver file is not
correct.
10.656: KB898461 Setup encountered an error: The update.ver file is not
correct.
10.703: KB898461 Setup encountered an error: The update.ver file is not
correct.
10.765: KB898461 Setup encountered an error: The update.ver file is not
correct.
10.765: KB898461 Setup encountered an error: The update.ver file is not
correct.
10.812: KB898461 Setup encountered an error: The update.ver file is not
correct.
10.859: KB898461 Setup encountered an error: The update.ver file is not
correct.
10.859: KB898461 Setup encountered an error: The update.ver file is not
correct.
10.859: KB898461 Setup encountered an error: The update.ver file is not
correct.
10.922: KB898461 Setup encountered an error: The update.ver file is not
correct.
10.953: KB898461 Setup encountered an error: The update.ver file is not
correct.
10.969: KB898461 Setup encountered an error: The update.ver file is not
correct.
10.984: KB898461 Setup encountered an error: The update.ver file is not
correct.
11.015: KB898461 Setup encountered an error: The update.ver file is not
correct.
11.031: KB898461 Setup encountered an error: The update.ver file is not
correct.
11.062: KB898461 Setup encountered an error: The update.ver file is not
correct.
11.062: KB898461 Setup encountered an error: The update.ver file is not
correct.
11.078: KB898461 Setup encountered an error: The update.ver file is not
correct.
11.078: KB898461 Setup encountered an error: The update.ver file is not
correct.
11.094: KB898461 Setup encountered an error: The update.ver file is not
correct.
11.125: KB898461 Setup encountered an error: The update.ver file is not
correct.
11.125: KB898461 Setup encountered an error: The update.ver file is not
correct.
11.156: KB898461 Setup encountered an error: The update.ver file is not
correct.
11.156: KB898461 Setup encountered an error: The update.ver file is not
correct.
11.172: KB898461 Setup encountered an error: The update.ver file is not
correct.
11.172: KB898461 Setup encountered an error: The update.ver file is not
correct.
11.187: KB898461 Setup encountered an error: The update.ver file is not
correct.
11.203: KB898461 Setup encountered an error: The update.ver file is not
correct.
12.531: AnalyzeForBranching used 1328 ticks.
12.531: AnalyzePhaseTwo used 0 ticks
12.531: AnalyzePhaseThree used 0 ticks
12.562: AnalyzePhaseFive used 0 ticks
12.703: AnalyzePhaseSix used 141 ticks
12.703: AnalyzeComponents used 9844 ticks
12.703: Downloading 0 files
12.703: bPatchMode = FALSE
12.703: Inventory complete: ReturnStatus=0, 9938 ticks
12.719: Num Ticks for invent : 9954
12.734: VerifySize: Unable to verify size: Source = NULL:
c:\windows\inf\HFX9D.tmp
12.734: Copied file: c:\windows\inf\branches.inf
13.875: Allocation size of drive C: is 4096 bytes, free space = 6782951424
bytes
15.219: GetTargetExists: GetFileAttributesEx(
c:\windows\system32\preinstall\winse\wxp_x86_0409_ v1\spcustom.dll.ref )
failed (23)
16.578: GetTargetExists: GetFileAttributesEx(
c:\windows\system32\preinstall\winse\wxp_x86_0409_ v1\spcustom.dll.ref )
failed (23)
16.687: Drive C: free 6468MB req: 5MB w/uninstall 0MB
16.703: CabinetBuild complete
16.703: Num Ticks for Cabinet build : 3984
16.703: DynamicStrings section not defined or empty.
16.797: FileInUse:: need to restart already, turn off
17.859: LoadFileQueues: UpdSpGetSourceFileLocation for halaacpi.dll failed:
0xe0000102
17.922: System Restore Point set.
18.062: Copied file: C:\WINDOWS\system32\spmsg.dll
18.078: PFE2: Not avoiding Per File Exceptions.
18.297: ProcessSetupContentSection: PROCESS_SETUP_CONTENT_OP_INSTALL: Copied
c:\windows\softwaredistribution\download\126638ad8 0a740243aeee66683d803a7\update\update_SP2QFE.inf -> c:\windows\$hf_mig$\KB898461\update\update_SP2QFE. inf.
18.344: ProcessSetupContentSection: PROCESS_SETUP_CONTENT_OP_INSTALL: Copied
c:\windows\softwaredistribution\download\126638ad8 0a740243aeee66683d803a7\spuninst.exe -> c:\windows\$hf_mig$\KB898461\spuninst.exe.
18.406: ProcessSetupContentSection: PROCESS_SETUP_CONTENT_OP_INSTALL: Copied
c:\windows\softwaredistribution\download\126638ad8 0a740243aeee66683d803a7\spmsg.dll -> c:\windows\$hf_mig$\KB898461\spmsg.dll.
18.453: ProcessSetupContentSection: PROCESS_SETUP_CONTENT_OP_INSTALL: Copied
c:\windows\softwaredistribution\download\126638ad8 0a740243aeee66683d803a7\update\spcustom.dll -> c:\windows\$hf_mig$\KB898461\update\spcustom.dll.
18.453: ProcessSetupContentSection: PROCESS_SETUP_CONTENT_OP_INSTALL: Copied
c:\windows\softwaredistribution\download\126638ad8 0a740243aeee66683d803a7\update\KB898461.CAT -> c:\windows\$hf_mig$\KB898461\update\KB898461.CAT.
18.562: ProcessSetupContentSection: PROCESS_SETUP_CONTENT_OP_INSTALL: Copied
c:\windows\softwaredistribution\download\126638ad8 0a740243aeee66683d803a7\update\update.exe -> c:\windows\$hf_mig$\KB898461\update\update.exe.
18.734: ProcessSetupContentSection: PROCESS_SETUP_CONTENT_OP_INSTALL: Copied
c:\windows\softwaredistribution\download\126638ad8 0a740243aeee66683d803a7\update\updspapi.dll -> c:\windows\$hf_mig$\KB898461\update\updspapi.dll.
18.734: ProcessSetupContentSection: PROCESS_SETUP_CONTENT_OP_INSTALL: Copied
c:\windows\softwaredistribution\download\126638ad8 0a740243aeee66683d803a7\update\update.ver -> c:\windows\$hf_mig$\KB898461\update\update.ver.
18.734: ProcessSetupContentSection: PROCESS_SETUP_CONTENT_OP_INSTALL: Copied
c:\windows\softwaredistribution\download\126638ad8 0a740243aeee66683d803a7\update\updatebr.inf -> c:\windows\$hf_mig$\KB898461\update\updatebr.inf.
18.765: ProcessSetupContentSection: PROCESS_SETUP_CONTENT_OP_INSTALL: Copied
c:\windows\softwaredistribution\download\126638ad8 0a740243aeee66683d803a7\update\eula.txt -> c:\windows\$hf_mig$\KB898461\update\eula.txt.
18.765: ProcessSetupContentSection: PROCESS_SETUP_CONTENT_OP_INSTALL: Copied
c:\windows\softwaredistribution\download\126638ad8 0a740243aeee66683d803a7\update\branches.inf -> c:\windows\$hf_mig$\KB898461\update\branches.inf.
20.094: Copied file:
C:\WINDOWS\system32\PreInstall\WinSE\wxp_x86_0409_ v1\spcustom.dll.ref
27.828: Copied file (delayed):
C:\WINDOWS\system32\PreInstall\WinSE\wxp_x86_0409_ v1\SETA1.tmp
28.422: DoInstallation: Installing assemblies with source root path:
c:\windows\softwaredistribution\download\126638ad8 0a740243aeee66683d803a7\
28.422: Num Ticks for Copying files : 11719
28.422: Num Ticks for Reg update and deleting 0 size files : 0
28.437: ---- Old Information In The Registry ------
29.812:
Source:C:\WINDOWS\system32\PreInstall\WinSE\wxp_x8 6_0409_v1\SETA1.tmp
(6.1.22.4)
31.156:
Destination:C:\WINDOWS\system32\PreInstall\WinSE\w xp_x86_0409_v1\spcustom.dll.ref
31.156: ---- New Information In The Registry ------
31.156:
Source:C:\WINDOWS\system32\PreInstall\WinSE\wxp_x8 6_0409_v1\SETA1.tmp
(6.1.22.4)
32.515:
Destination:C:\WINDOWS\system32\PreInstall\WinSE\w xp_x86_0409_v1\spcustom.dll.ref
32.531: UpdateSpUpdSvcInf: Source [ProcessesToRunAfterReboot] section is
empty; nothing to do.
32.531: IsRebootRequiredForFileQueue: At least one file operation was
delayed; reboot is required.
If none are listed below, check above for
delayed deletes.
32.531: IsRebootRequiredForFileQueue:
c:\windows\system32\preinstall\winse\wxp_x86_0409_ v1\spcustom.dll.ref was
delayed; reboot is required.
32.531: DoInstallation: A reboot is required to complete the installation of
one or more files.
32.531: In Function SetVolatileFlag, line 11576, RegOpenKeyEx failed with
error 0x2
32.531: In Function SetVolatileFlag, line 11593, RegOpenKeyEx failed with
error 0x2
32.531: UpdateSpUpdSvcInf: Source
[ProcessesToRunAfterReboot.RebootNotRequired] section is empty; nothing to do.
32.594: RebootNecessary = 1,WizardInput = 1 , DontReboot = 1, ForceRestart = 0

"Torgeir Bakken (MVP)" wrote:

> msiebels wrote:
>
> > I have installed the new permanent package installer probably 60 times over
> > the last few weeks. It always says it's successful, however automatic
> > updates AND windows update always says I need to install it.
> >
> > I have tried every suggestion I can find, deleteing and/or renameing files
> > and folders.
>
> Have you renamed spupdsvc.exe?
>
> Herr_Mord found that renaming c:\windows\system32\spupdsvc.exe
> solved the KB898461 install problem for him:
>
> http://groups.google.co.uk/group/mic...9e8e589?hl=en&
>
>
> Also see if the install log file for kb898461 give you any tip:
>
> From Start/Run:
>
> notepad.exe %windir%\kb898461.log
>
>
> > Re-registering dlls. I have tried it beofre and after SP2
> > intall. I even completely reinstalled windows (xp pro) from scratch and
> > began updates and it got me to the same place. Need to install
> > kb898461...... I do it, it works... then It says I need to do it again, so I
> > can't get any of the other updates I need. My update history shows all were
> > successful.
> >
> > It's driving me crazy. It all started with needing/wanting to install .net
> > framework and I needed to do it through windows update, yada yada yada....
> >
> > Please help if you can.
>
>
> --
> torgeir, Microsoft MVP Scripting, Porsgrunn Norway
> Administration scripting examples and an ONLINE version of
> the 1328 page Scripting Guide:
> http://www.microsoft.com/technet/scr...r/default.mspx
>

msiebels wrote:
> Here's part of my kb898461 log. I see it says someing about update.ver file
> not correct? I believe my windows key is valid and have done that windows
> uodate verification tool nd it worked fine. But could that be the problem?
> This is a Development box, and I'm useing a key from my MSDN subscription. I
> haven't installed it more then 10 times (the MSDN limit) I don't think.
> Anyway here is part of my Log, thanks for your help.
>
> Oh yea, the other thing is KB898461 shows up in my add and remove programs
> as installed (I guess), but it dosn't have the "normal" info, like last used,
> when it was installed, ect. it just says "this update cannot be removed"? My
> only other update is "windows installer 3.1", medeia player, and SP2. Again
> thanks
>
> (snip log)
Hi,

The update.ver issue have nothing to do with your windows key, and the
update is supposed to be uninstallable, so there is for sure something
wrong here.

I would think it is update.ver in the $hf_mig$\KB898461 folder that
gives it trouble.

Try this from Start/Run (a black command prompt will flash by):

%comspec% /c rmdir /s /q %windir%\$hf_mig$\KB898461

Then see if the KB898461 installs successfully.


--
torgeir, Microsoft MVP Scripting, Porsgrunn Norway
Administration scripting examples and an ONLINE version of
the 1328 page Scripting Guide:
http://www.microsoft.com/technet/scr...r/default.mspx

Nope. Here's what I did. (FYI - I had attempted to install 89461 in safe
mode just prior to posting here, after that the auto update won't pop up and
tell me to install it, but windows update still said I needed too)

-I ran your comand.
-Went to windows update, and sure enough it said install kb898461
-I did
-Then restarted (btw - I've notice that most of the time the update process
won't restart the computer, I have to click on restart for it to do it, would
there be something ogin on there?)

Anyway, now auto update says I need to install KB898461.


Thanks agaion for all you help.

Here is the log:
18.718: Copied file:
C:\WINDOWS\system32\PreInstall\WinSE\wxp_x86_0409_ v1\spcustom.dll.ref
26.109: Copied file (delayed):
C:\WINDOWS\system32\PreInstall\WinSE\wxp_x86_0409_ v1\SET2A3.tmp
26.171: Copied file: c:\windows\$hf_mig$\KB898461\spmsg.dll
26.187: Copied file: c:\windows\$hf_mig$\KB898461\spuninst.exe
26.218: Copied file: c:\windows\$hf_mig$\KB898461\spupdsvc.exe
26.250: Copied file: c:\windows\$hf_mig$\KB898461\update\spcustom.dll
26.281: Copied file: c:\windows\$hf_mig$\KB898461\update\update.exe
26.328: Copied file: c:\windows\$hf_mig$\KB898461\update\updspapi.dll
26.375: DoInstallation: Installing assemblies with source root path:
c:\windows\softwaredistribution\download\126638ad8 0a740243aeee66683d803a7\
26.375: Num Ticks for Copying files : 11000
26.375: Num Ticks for Reg update and deleting 0 size files : 0
26.437: ---- Old Information In The Registry ------
27.796:
Source:C:\WINDOWS\system32\PreInstall\WinSE\wxp_x8 6_0409_v1\SET2A3.tmp
(6.1.22.4)
29.140:
Destination:C:\WINDOWS\system32\PreInstall\WinSE\w xp_x86_0409_v1\spcustom.dll.ref
29.140: ---- New Information In The Registry ------
29.140:
Source:C:\WINDOWS\system32\PreInstall\WinSE\wxp_x8 6_0409_v1\SET2A3.tmp
(6.1.22.4)
30.484:
Destination:C:\WINDOWS\system32\PreInstall\WinSE\w xp_x86_0409_v1\spcustom.dll.ref
30.484: UpdateSpUpdSvcInf: Source [ProcessesToRunAfterReboot] section is
empty; nothing to do.
30.515: IsRebootRequiredForFileQueue: At least one file operation was
delayed; reboot is required.
If none are listed below, check above for
delayed deletes.
30.515: IsRebootRequiredForFileQueue:
c:\windows\system32\preinstall\winse\wxp_x86_0409_ v1\spcustom.dll.ref was
delayed; reboot is required.
30.515: DoInstallation: A reboot is required to complete the installation of
one or more files.
30.515: In Function SetVolatileFlag, line 11576, RegOpenKeyEx failed with
error 0x2
30.515: In Function SetVolatileFlag, line 11593, RegOpenKeyEx failed with
error 0x2
30.625: UpdateSpUpdSvcInf: Source
[ProcessesToRunAfterReboot.RebootNotRequired] section is empty; nothing to do.
30.734: RebootNecessary = 1,WizardInput = 1 , DontReboot = 1, ForceRestart = 0

"Torgeir Bakken (MVP)" wrote:

> msiebels wrote:
> > Here's part of my kb898461 log. I see it says someing about update.ver file
> > not correct? I believe my windows key is valid and have done that windows
> > uodate verification tool nd it worked fine. But could that be the problem?
> > This is a Development box, and I'm useing a key from my MSDN subscription. I
> > haven't installed it more then 10 times (the MSDN limit) I don't think.
> > Anyway here is part of my Log, thanks for your help.
> >
> > Oh yea, the other thing is KB898461 shows up in my add and remove programs
> > as installed (I guess), but it dosn't have the "normal" info, like last used,
> > when it was installed, ect. it just says "this update cannot be removed"? My
> > only other update is "windows installer 3.1", medeia player, and SP2. Again
> > thanks
> >
> > (snip log)
> Hi,
>
> The update.ver issue have nothing to do with your windows key, and the
> update is supposed to be uninstallable, so there is for sure something
> wrong here.
>
> I would think it is update.ver in the $hf_mig$\KB898461 folder that
> gives it trouble.
>
> Try this from Start/Run (a black command prompt will flash by):
>
> %comspec% /c rmdir /s /q %windir%\$hf_mig$\KB898461
>
> Then see if the KB898461 installs successfully.
>
>
> --
> torgeir, Microsoft MVP Scripting, Porsgrunn Norway
> Administration scripting examples and an ONLINE version of
> the 1328 page Scripting Guide:
> http://www.microsoft.com/technet/scr...r/default.mspx
>

Hi,

Sorry to hear that, and I am out of ideas...

Microsoft offers unlimited free support for Windows Update, I suggest
you use that. At the URL

http://support.microsoft.com/ph/6527

Click on "Need More Help? Contact a Support Professional by Email,
Online, or Phone." in the upper right corner.


Regards,
Torgeir


msiebels wrote:

> Nope. Here's what I did. (FYI - I had attempted to install 89461 in safe
> mode just prior to posting here, after that the auto update won't pop up and
> tell me to install it, but windows update still said I needed too)
>
> -I ran your comand.
> -Went to windows update, and sure enough it said install kb898461
> -I did
> -Then restarted (btw - I've notice that most of the time the update process
> won't restart the computer, I have to click on restart for it to do it, would
> there be something ogin on there?)
>
> Anyway, now auto update says I need to install KB898461.
>
>
> Thanks agaion for all you help.
>
> Here is the log:
> 18.718: Copied file:
> C:\WINDOWS\system32\PreInstall\WinSE\wxp_x86_0409_ v1\spcustom.dll.ref
> 26.109: Copied file (delayed):
> C:\WINDOWS\system32\PreInstall\WinSE\wxp_x86_0409_ v1\SET2A3.tmp
> 26.171: Copied file: c:\windows\$hf_mig$\KB898461\spmsg.dll
> 26.187: Copied file: c:\windows\$hf_mig$\KB898461\spuninst.exe
> 26.218: Copied file: c:\windows\$hf_mig$\KB898461\spupdsvc.exe
> 26.250: Copied file: c:\windows\$hf_mig$\KB898461\update\spcustom.dll
> 26.281: Copied file: c:\windows\$hf_mig$\KB898461\update\update.exe
> 26.328: Copied file: c:\windows\$hf_mig$\KB898461\update\updspapi.dll
> 26.375: DoInstallation: Installing assemblies with source root path:
> c:\windows\softwaredistribution\download\126638ad8 0a740243aeee66683d803a7\
> 26.375: Num Ticks for Copying files : 11000
> 26.375: Num Ticks for Reg update and deleting 0 size files : 0
> 26.437: ---- Old Information In The Registry ------
> 27.796:
> Source:C:\WINDOWS\system32\PreInstall\WinSE\wxp_x8 6_0409_v1\SET2A3.tmp
> (6.1.22.4)
> 29.140:
> Destination:C:\WINDOWS\system32\PreInstall\WinSE\w xp_x86_0409_v1\spcustom.dll.ref
> 29.140: ---- New Information In The Registry ------
> 29.140:
> Source:C:\WINDOWS\system32\PreInstall\WinSE\wxp_x8 6_0409_v1\SET2A3.tmp
> (6.1.22.4)
> 30.484:
> Destination:C:\WINDOWS\system32\PreInstall\WinSE\w xp_x86_0409_v1\spcustom.dll.ref
> 30.484: UpdateSpUpdSvcInf: Source [ProcessesToRunAfterReboot] section is
> empty; nothing to do.
> 30.515: IsRebootRequiredForFileQueue: At least one file operation was
> delayed; reboot is required.
> If none are listed below, check above for
> delayed deletes.
> 30.515: IsRebootRequiredForFileQueue:
> c:\windows\system32\preinstall\winse\wxp_x86_0409_ v1\spcustom.dll.ref was
> delayed; reboot is required.
> 30.515: DoInstallation: A reboot is required to complete the installation of
> one or more files.
> 30.515: In Function SetVolatileFlag, line 11576, RegOpenKeyEx failed with
> error 0x2
> 30.515: In Function SetVolatileFlag, line 11593, RegOpenKeyEx failed with
> error 0x2
> 30.625: UpdateSpUpdSvcInf: Source
> [ProcessesToRunAfterReboot.RebootNotRequired] section is empty; nothing to do.
> 30.734: RebootNecessary = 1,WizardInput = 1 , DontReboot = 1, ForceRestart = 0
>
> "Torgeir Bakken (MVP)" wrote:
>
>
>>msiebels wrote:
>>
>>>Here's part of my kb898461 log. I see it says someing about update.ver file
>>>not correct? I believe my windows key is valid and have done that windows
>>>uodate verification tool nd it worked fine. But could that be the problem?
>>>This is a Development box, and I'm useing a key from my MSDN subscription. I
>>>haven't installed it more then 10 times (the MSDN limit) I don't think.
>>>Anyway here is part of my Log, thanks for your help.
>>>
>>>Oh yea, the other thing is KB898461 shows up in my add and remove programs
>>>as installed (I guess), but it dosn't have the "normal" info, like last used,
>>>when it was installed, ect. it just says "this update cannot be removed"? My
>>>only other update is "windows installer 3.1", medeia player, and SP2. Again
>>>thanks
>>>
>>>(snip log)
>>
>>Hi,
>>
>>The update.ver issue have nothing to do with your windows key, and the
>>update is supposed to be uninstallable, so there is for sure something
>>wrong here.
>>
>>I would think it is update.ver in the $hf_mig$\KB898461 folder that
>>gives it trouble.
>>
>>Try this from Start/Run (a black command prompt will flash by):
>>
>>%comspec% /c rmdir /s /q %windir%\$hf_mig$\KB898461
>>
>>Then see if the KB898461 installs successfully.
>>
>>


--
torgeir, Microsoft MVP Scripting, Porsgrunn Norway
Administration scripting examples and an ONLINE version of
the 1328 page Scripting Guide:
http://www.microsoft.com/technet/scr...r/default.mspx

Thanks anyway for your time.
Mark


"Torgeir Bakken (MVP)" wrote:

> Hi,
>
> Sorry to hear that, and I am out of ideas...
>
> Microsoft offers unlimited free support for Windows Update, I suggest
> you use that. At the URL
>
> http://support.microsoft.com/ph/6527
>
> Click on "Need More Help? Contact a Support Professional by Email,
> Online, or Phone." in the upper right corner.
>
>
> Regards,
> Torgeir
>
>
> msiebels wrote:
>
> > Nope. Here's what I did. (FYI - I had attempted to install 89461 in safe
> > mode just prior to posting here, after that the auto update won't pop up and
> > tell me to install it, but windows update still said I needed too)
> >
> > -I ran your comand.
> > -Went to windows update, and sure enough it said install kb898461
> > -I did
> > -Then restarted (btw - I've notice that most of the time the update process
> > won't restart the computer, I have to click on restart for it to do it, would
> > there be something ogin on there?)
> >
> > Anyway, now auto update says I need to install KB898461.
> >
> >
> > Thanks agaion for all you help.
> >
> > Here is the log:
> > 18.718: Copied file:
> > C:\WINDOWS\system32\PreInstall\WinSE\wxp_x86_0409_ v1\spcustom.dll.ref
> > 26.109: Copied file (delayed):
> > C:\WINDOWS\system32\PreInstall\WinSE\wxp_x86_0409_ v1\SET2A3.tmp
> > 26.171: Copied file: c:\windows\$hf_mig$\KB898461\spmsg.dll
> > 26.187: Copied file: c:\windows\$hf_mig$\KB898461\spuninst.exe
> > 26.218: Copied file: c:\windows\$hf_mig$\KB898461\spupdsvc.exe
> > 26.250: Copied file: c:\windows\$hf_mig$\KB898461\update\spcustom.dll
> > 26.281: Copied file: c:\windows\$hf_mig$\KB898461\update\update.exe
> > 26.328: Copied file: c:\windows\$hf_mig$\KB898461\update\updspapi.dll
> > 26.375: DoInstallation: Installing assemblies with source root path:
> > c:\windows\softwaredistribution\download\126638ad8 0a740243aeee66683d803a7\
> > 26.375: Num Ticks for Copying files : 11000
> > 26.375: Num Ticks for Reg update and deleting 0 size files : 0
> > 26.437: ---- Old Information In The Registry ------
> > 27.796:
> > Source:C:\WINDOWS\system32\PreInstall\WinSE\wxp_x8 6_0409_v1\SET2A3.tmp
> > (6.1.22.4)
> > 29.140:
> > Destination:C:\WINDOWS\system32\PreInstall\WinSE\w xp_x86_0409_v1\spcustom.dll.ref
> > 29.140: ---- New Information In The Registry ------
> > 29.140:
> > Source:C:\WINDOWS\system32\PreInstall\WinSE\wxp_x8 6_0409_v1\SET2A3.tmp
> > (6.1.22.4)
> > 30.484:
> > Destination:C:\WINDOWS\system32\PreInstall\WinSE\w xp_x86_0409_v1\spcustom.dll.ref
> > 30.484: UpdateSpUpdSvcInf: Source [ProcessesToRunAfterReboot] section is
> > empty; nothing to do.
> > 30.515: IsRebootRequiredForFileQueue: At least one file operation was
> > delayed; reboot is required.
> > If none are listed below, check above for
> > delayed deletes.
> > 30.515: IsRebootRequiredForFileQueue:
> > c:\windows\system32\preinstall\winse\wxp_x86_0409_ v1\spcustom.dll.ref was
> > delayed; reboot is required.
> > 30.515: DoInstallation: A reboot is required to complete the installation of
> > one or more files.
> > 30.515: In Function SetVolatileFlag, line 11576, RegOpenKeyEx failed with
> > error 0x2
> > 30.515: In Function SetVolatileFlag, line 11593, RegOpenKeyEx failed with
> > error 0x2
> > 30.625: UpdateSpUpdSvcInf: Source
> > [ProcessesToRunAfterReboot.RebootNotRequired] section is empty; nothing to do.
> > 30.734: RebootNecessary = 1,WizardInput = 1 , DontReboot = 1, ForceRestart = 0
> >
> > "Torgeir Bakken (MVP)" wrote:
> >
> >
> >>msiebels wrote:
> >>
> >>>Here's part of my kb898461 log. I see it says someing about update.ver file
> >>>not correct? I believe my windows key is valid and have done that windows
> >>>uodate verification tool nd it worked fine. But could that be the problem?
> >>>This is a Development box, and I'm useing a key from my MSDN subscription. I
> >>>haven't installed it more then 10 times (the MSDN limit) I don't think.
> >>>Anyway here is part of my Log, thanks for your help.
> >>>
> >>>Oh yea, the other thing is KB898461 shows up in my add and remove programs
> >>>as installed (I guess), but it dosn't have the "normal" info, like last used,
> >>>when it was installed, ect. it just says "this update cannot be removed"? My
> >>>only other update is "windows installer 3.1", medeia player, and SP2. Again
> >>>thanks
> >>>
> >>>(snip log)
> >>
> >>Hi,
> >>
> >>The update.ver issue have nothing to do with your windows key, and the
> >>update is supposed to be uninstallable, so there is for sure something
> >>wrong here.
> >>
> >>I would think it is update.ver in the $hf_mig$\KB898461 folder that
> >>gives it trouble.
> >>
> >>Try this from Start/Run (a black command prompt will flash by):
> >>
> >>%comspec% /c rmdir /s /q %windir%\$hf_mig$\KB898461
> >>
> >>Then see if the KB898461 installs successfully.
> >>
> >>
>
>
> --
> torgeir, Microsoft MVP Scripting, Porsgrunn Norway
> Administration scripting examples and an ONLINE version of
> the 1328 page Scripting Guide:
> http://www.microsoft.com/technet/scr...r/default.mspx
>

"msiebels" <> wrote in message
news:C7A1DE71-5095-4B25-B6F4-...
> Here's part of my kb898461 log. I see it says someing about update.ver file
> not correct?


Do you have access to someone else's log for comparison?
Looking at mine there are many areas of significant differences.
Too many to attempt to discuss here, which could be a waste
of time anyway because I don't know which would be significant.


I think that you might benefit from trying the diagnostic technique
I have tried using with a few other posters. The idea is to use
use both RegMon and FileMon to capture details about the update
and use their much more precise timestamps to correlate what was
happening concurrently in all three logs. Unfortunately the differences
I see in our logs hints at either a problem with some files

<example>
5.031: GetTargetExists: GetFileAttributesEx(
c:\windows\system32\preinstall\winse\wxp_x86_0409_ v1\spcustom.dll.ref )
failed (23)
9.156: GetTargetExists: GetFileAttributesEx(
c:\windows\system32\preinstall\winse\wxp_x86_0409_ v1\spcustom.dll.ref )
failed (23)
</example>

or in the registry (e.g. near the end)

<example>
32.531: In Function SetVolatileFlag, line 11576, RegOpenKeyEx failed with
error 0x2
32.531: In Function SetVolatileFlag, line 11593, RegOpenKeyEx failed with
error 0x2
</example>


Unfortunately I suspect the file case (e.g. the first differences)
may be the most significant ones which could complicate the analysis
by requiring a loose filter on both tools.


Let's take the just the registry example though so you can see the power
of the technique. In that case you could filter in FileMon on just writes to
update*log since all we would want to see would be the writes to the install
log, including especially their lengths and most importantly the timestamp
down to the millesecond. By then matching that write with a record in the
install log (by the pattern of the lengths) we would have a timestamp for that
record accurate to within milleseconds. Then you could look in the RegMon
log which would have to be filtering much more loosely, say with just update
(e.g., assuming that that is the name of the executable which does the install)
and find precisely what was happening at the time that log record was written.

Note that the two key options on both tools Clock Time and Show Milleseconds
may not be checked by default, so make sure that you check those
on both tools for the above technique to succeed.


A similar analysis could be done with messages involving files using
FileMon only but then that tool's filter would have to be at least as loose
as just update (again, if that is what the executable for the patch is called)
and you could not restrict the monitoring to just file writes.


Good luck

Robert Aldwinckle
---

Hi all,
I have resolved the issue today, we can try to rename the file
(%windir%\System32\spupdsvc.exe) in Safe Mode and then try to install the
update manually.
finally, I have installed the package successfully.
good luck!

"Robert Aldwinckle" wrote:

> "msiebels" <> wrote in message
> news:C7A1DE71-5095-4B25-B6F4-...
> > Here's part of my kb898461 log. I see it says someing about update.ver file
> > not correct?
>
>
> Do you have access to someone else's log for comparison?
> Looking at mine there are many areas of significant differences.
> Too many to attempt to discuss here, which could be a waste
> of time anyway because I don't know which would be significant.
>
>
> I think that you might benefit from trying the diagnostic technique
> I have tried using with a few other posters. The idea is to use
> use both RegMon and FileMon to capture details about the update
> and use their much more precise timestamps to correlate what was
> happening concurrently in all three logs. Unfortunately the differences
> I see in our logs hints at either a problem with some files
>
> <example>
> 5.031: GetTargetExists: GetFileAttributesEx(
> c:\windows\system32\preinstall\winse\wxp_x86_0409_ v1\spcustom.dll.ref )
> failed (23)
> 9.156: GetTargetExists: GetFileAttributesEx(
> c:\windows\system32\preinstall\winse\wxp_x86_0409_ v1\spcustom.dll.ref )
> failed (23)
> </example>
>
> or in the registry (e.g. near the end)
>
> <example>
> 32.531: In Function SetVolatileFlag, line 11576, RegOpenKeyEx failed with
> error 0x2
> 32.531: In Function SetVolatileFlag, line 11593, RegOpenKeyEx failed with
> error 0x2
> </example>
>
>
> Unfortunately I suspect the file case (e.g. the first differences)
> may be the most significant ones which could complicate the analysis
> by requiring a loose filter on both tools.
>
>
> Let's take the just the registry example though so you can see the power
> of the technique. In that case you could filter in FileMon on just writes to
> update*log since all we would want to see would be the writes to the install
> log, including especially their lengths and most importantly the timestamp
> down to the millesecond. By then matching that write with a record in the
> install log (by the pattern of the lengths) we would have a timestamp for that
> record accurate to within milleseconds. Then you could look in the RegMon
> log which would have to be filtering much more loosely, say with just update
> (e.g., assuming that that is the name of the executable which does the install)
> and find precisely what was happening at the time that log record was written.
>
> Note that the two key options on both tools Clock Time and Show Milleseconds
> may not be checked by default, so make sure that you check those
> on both tools for the above technique to succeed.
>
>
> A similar analysis could be done with messages involving files using
> FileMon only but then that tool's filter would have to be at least as loose
> as just update (again, if that is what the executable for the patch is called)
> and you could not restrict the monitoring to just file writes.
>
>
> Good luck
>
> Robert Aldwinckle
> ---
>
>
>
>