Leftover folders after Microsoft Update

I have 1 PC running Windows XP Pro SP3 and I regularly install the updates
released via Microsoft Update web site.
Sometimes, the Microsoft Update process creates one or more folders in root
(e.g.: C:\589727f66af640356a) which will be removed after the first
reboot... almost always.
I don't know why, but, sometimes, after the reboot, the folders are not
removed.
Currently I have a couple of that kind of folders and I would like to know
if it is safe to remove them manually.

PA
Wed Sep 24 06:47:12 PDT 2008

Leave well enough alone for the time being. If the folder's still present
after a week or so, run Disk Cleanup. If still no joy, yes, you can delete
it to Recycle Bin manually.
--
~Robear Dyer (PA Bear)
MS MVP-IE, Mail, Security, Windows Desktop Experience - since 2002
AumHa VSOP & Admin http://aumha.net
DTS-L http://dts-l.net/

mme000 wrote:
> I have 1 PC running Windows XP Pro SP3 and I regularly install the updates
> released via Microsoft Update web site.
> Sometimes, the Microsoft Update process creates one or more folders in
> root
> (e.g.: C:\589727f66af640356a) which will be removed after the first
> reboot... almost always.
> I don't know why, but, sometimes, after the reboot, the folders are not
> removed.
> Currently I have a couple of that kind of folders and I would like to know
> if it is safe to remove them manually.

MowGreen
Wed Sep 24 11:10:02 PDT 2008

Have you ever inspected the contents of the 'leftover' folders ?
The Windows Malicious Software Removal Tool runs from a temp folder
located on the drive with the most free space and they *should* be
deleted when it finishes running; security updates for MSMXL packages
also create these temp staging locations but, do not always clean them up.
So, until you post what's in those temp folders, we can't recommend a
course of action, mme000.

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

(add $1 million dollars to my nick and I'll give you my email address)


mme000 (add @yahoo.it to my nick) wrote:

> I have 1 PC running Windows XP Pro SP3 and I regularly install the
> updates released via Microsoft Update web site.
> Sometimes, the Microsoft Update process creates one or more folders in
> root (e.g.: C:\589727f66af640356a) which will be removed after the first
> reboot... almost always.
> I don't know why, but, sometimes, after the reboot, the folders are not
> removed.
> Currently I have a couple of that kind of folders and I would like to
> know if it is safe to remove them manually.
>
>
>

mme000
Thu Sep 25 01:53:30 PDT 2008

"MowGreen [MVP]" <mowgreen@nowandzen.com> wrote in message
news:#MAp$CnHJHA.1156@TK2MSFTNGP04.phx.gbl...
> Have you ever inspected the contents of the 'leftover' folders ?
> The Windows Malicious Software Removal Tool runs from a temp folder
> located on the drive with the most free space and they *should* be deleted
> when it finishes running; security updates for MSMXL packages also create
> these temp staging locations but, do not always clean them up.
> So, until you post what's in those temp folders, we can't recommend a
> course of action, mme000.

Hi MowGreen.

This is the content of the temp folder:

C:\589727f66af640356a\amd64
C:\589727f66af640356a\amd64\filterpipelineprintproc.dll
C:\589727f66af640356a\amd64\msxpsdrv.cat
C:\589727f66af640356a\amd64\msxpsdrv.inf
C:\589727f66af640356a\amd64\msxpsinc.gpd
C:\589727f66af640356a\amd64\msxpsinc.ppd
C:\589727f66af640356a\amd64\mxdwdrv.dll
C:\589727f66af640356a\amd64\xpssvcs.dll
C:\589727f66af640356a\i386
C:\589727f66af640356a\i386\filterpipelineprintproc.dll
C:\589727f66af640356a\i386\msxpsdrv.cat
C:\589727f66af640356a\i386\msxpsdrv.inf
C:\589727f66af640356a\i386\msxpsinc.gpd
C:\589727f66af640356a\i386\msxpsinc.ppd
C:\589727f66af640356a\i386\mxdwdrv.dll
C:\589727f66af640356a\i386\xpssvcs.dll

Looking at the info contained in "msxpsdrv.inf", I can read "Microsoft
system driver files for XPSDrv print drivers".

Thanks,

mme000

MowGreen
Thu Sep 25 09:51:57 PDT 2008

Delete the temp folder, 589727f66af640356a. Those files appear to be for
Vista, not XP.
Do you know specifically which update left that folder\files ?

Check the Creation date of the temp folder to see if it matches the
installation date of updates, shown in Add/Remove Programs or, since
this was done from the MU update site, in the ReportingEvents.log
located in WINDOWS\SoftwareDistribution.

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



mme000 (add @yahoo.it to my nick) wrote:

> "MowGreen [MVP]" <mowgreen@nowandzen.com> wrote in message
> news:#MAp$CnHJHA.1156@TK2MSFTNGP04.phx.gbl...
>
>> Have you ever inspected the contents of the 'leftover' folders ?
>> The Windows Malicious Software Removal Tool runs from a temp folder
>> located on the drive with the most free space and they *should* be
>> deleted when it finishes running; security updates for MSMXL packages
>> also create these temp staging locations but, do not always clean them
>> up.
>> So, until you post what's in those temp folders, we can't recommend a
>> course of action, mme000.
>
>
> Hi MowGreen.
>
> This is the content of the temp folder:
>
> C:\589727f66af640356a\amd64
> C:\589727f66af640356a\amd64\filterpipelineprintproc.dll
> C:\589727f66af640356a\amd64\msxpsdrv.cat
> C:\589727f66af640356a\amd64\msxpsdrv.inf
> C:\589727f66af640356a\amd64\msxpsinc.gpd
> C:\589727f66af640356a\amd64\msxpsinc.ppd
> C:\589727f66af640356a\amd64\mxdwdrv.dll
> C:\589727f66af640356a\amd64\xpssvcs.dll
> C:\589727f66af640356a\i386
> C:\589727f66af640356a\i386\filterpipelineprintproc.dll
> C:\589727f66af640356a\i386\msxpsdrv.cat
> C:\589727f66af640356a\i386\msxpsdrv.inf
> C:\589727f66af640356a\i386\msxpsinc.gpd
> C:\589727f66af640356a\i386\msxpsinc.ppd
> C:\589727f66af640356a\i386\mxdwdrv.dll
> C:\589727f66af640356a\i386\xpssvcs.dll
>
> Looking at the info contained in "msxpsdrv.inf", I can read "Microsoft
> system driver files for XPSDrv print drivers".
>
> Thanks,
>
> mme000

koawmfot
Fri Oct 24 15:54:00 PDT 2008

do we know what update this is from?
i have an integrated cd used to build a corp image with patches through oct
integrated. i did not have this problem previously with patches only through
sept. once the oct patches were added i have this issue with this exact
patch.
the problem is that in some of the scenarios where the integrated cd is used
to build the image, there is no automation to get rid of a randomly named
folder, and i don't feel like having to figure out any when i shouldn't have
to.

where did this come from and how do i avoid having it happen in the first
place?

"MowGreen [MVP]" wrote:

> Delete the temp folder, 589727f66af640356a. Those files appear to be for
> Vista, not XP.
> Do you know specifically which update left that folder\files ?
>
> Check the Creation date of the temp folder to see if it matches the
> installation date of updates, shown in Add/Remove Programs or, since
> this was done from the MU update site, in the ReportingEvents.log
> located in WINDOWS\SoftwareDistribution.
>
> MowGreen [MVP 2003-2008]
> ===============
> *-343-* FDNY
> Never Forgotten
> ===============
>
>
>
> mme000 (add @yahoo.it to my nick) wrote:
>
> > "MowGreen [MVP]" <mowgreen@nowandzen.com> wrote in message
> > news:#MAp$CnHJHA.1156@TK2MSFTNGP04.phx.gbl...
> >
> >> Have you ever inspected the contents of the 'leftover' folders ?
> >> The Windows Malicious Software Removal Tool runs from a temp folder
> >> located on the drive with the most free space and they *should* be
> >> deleted when it finishes running; security updates for MSMXL packages
> >> also create these temp staging locations but, do not always clean them
> >> up.
> >> So, until you post what's in those temp folders, we can't recommend a
> >> course of action, mme000.
> >
> >
> > Hi MowGreen.
> >
> > This is the content of the temp folder:
> >
> > C:\589727f66af640356a\amd64
> > C:\589727f66af640356a\amd64\filterpipelineprintproc.dll
> > C:\589727f66af640356a\amd64\msxpsdrv.cat
> > C:\589727f66af640356a\amd64\msxpsdrv.inf
> > C:\589727f66af640356a\amd64\msxpsinc.gpd
> > C:\589727f66af640356a\amd64\msxpsinc.ppd
> > C:\589727f66af640356a\amd64\mxdwdrv.dll
> > C:\589727f66af640356a\amd64\xpssvcs.dll
> > C:\589727f66af640356a\i386
> > C:\589727f66af640356a\i386\filterpipelineprintproc.dll
> > C:\589727f66af640356a\i386\msxpsdrv.cat
> > C:\589727f66af640356a\i386\msxpsdrv.inf
> > C:\589727f66af640356a\i386\msxpsinc.gpd
> > C:\589727f66af640356a\i386\msxpsinc.ppd
> > C:\589727f66af640356a\i386\mxdwdrv.dll
> > C:\589727f66af640356a\i386\xpssvcs.dll
> >
> > Looking at the info contained in "msxpsdrv.inf", I can read "Microsoft
> > system driver files for XPSDrv print drivers".
> >
> > Thanks,
> >
> > mme000
>

koawmfot
Tue Oct 28 08:22:08 PDT 2008

it appears to be from this update, 954550-v5.

here is the log. you can see below the directory deletion fails. returns
code 2. why all of the sudden is this an issue?

[KB954550-v5.log]
0.032:
================================================================================
0.032: 2008/10/24 16:45:59.906 (local)
0.032: c:\1ce0b44e820c91ab1928a85621\update\update.exe (version 6.3.13.0)
0.032: InitializeSvcPackLogWrapper: Unable to write to user-supplied log
path: c:\1ce0b44e820c91ab1928a85621\update\%TEMP%\dd_XPS.txt
0.032: Hotfix started with following command line: /quiet /norestart
/log:%TEMP%\dd_XPS.txt
0.032: In Function GetReleaseSet, line 1216, RegQueryValueEx failed with
error 0x2
0.032: In Function GetReleaseSet, line 1240, RegQueryValueEx failed with
error 0x2
0.204: ---- Old Information In The Registry ------
0.204: Source:C:\WINDOWS\System32\spool\DRIVERS\W32X86\3\New\jnwdui.dll
0.204: Destination:C:\WINDOWS\System32\spool\DRIVERS\W32X86\3\jnwdui.dll
(0.3.7.0)
0.204: Source:C:\pagefile.sys
0.204: Destination:
0.204: Source:C:\Config.Msi\52bfe.rbf (1.0.3705.6018)
0.204: Destination:
0.204: ---- New Information In The Registry ------
0.204: Source:C:\WINDOWS\System32\spool\DRIVERS\W32X86\3\New\jnwdui.dll
0.204: Destination:C:\WINDOWS\System32\spool\DRIVERS\W32X86\3\jnwdui.dll
(0.3.7.0)
0.204: Source:C:\pagefile.sys
0.204: Destination:
0.204: Source:C:\Config.Msi\52bfe.rbf (1.0.3705.6018)
0.204: Destination:
0.204: In Function GetReleaseSet, line 1216, RegQueryValueEx failed with
error 0x2
0.204: In Function GetReleaseSet, line 1240, RegQueryValueEx failed with
error 0x2
0.204: SetProductTypes: InfProductBuildType=BuildType.Sel
0.204: SetAltOsLoaderPath: No section uses DirId 65701; done.
0.235: DoInstallation: FetchSourceURL for
c:\1ce0b44e820c91ab1928a85621\update\update.inf failed
0.235: CreateUninstall = 0,Directory = C:\WINDOWS\$NtUninstallKB954550-v5$
0.235: LoadFileQueues: UpdSpGetSourceFileLocation for halaacpi.dll failed:
0xe0000102
0.235: BuildCabinetManifest: update.url absent
0.235: Starting AnalyzeComponents
0.235: AnalyzePhaseZero used 0 ticks
0.235: No c:\windows\INF\updtblk.inf file.
0.235: SetupFindFirstLine in LoadExclusionList Failed with error: 0xe0000102
0.235: SetupFindFirstLine in LoadExclusionList Failed with error: 0xe0000102
0.235: Enumerating Devices of printer, GUID
{4d36e979-e325-11ce-bfc1-08002be10318}
0.266: OEM file scan used 31 ticks
0.266: AnalyzePhaseOne: used 31 ticks
0.266: AnalyzeComponents: Hotpatch analysis disabled; skipping.
0.266: AnalyzeComponents: Hotpatching is disabled.
0.297: AnalyzePhaseTwo used 31 ticks
0.297: AnalyzePhaseThree used 0 ticks
0.297: AnalyzePhaseFive used 0 ticks
0.297: AnalyzePhaseSix used 0 ticks
0.297: AnalyzeComponents used 62 ticks
0.297: Downloading 0 files
0.297: bPatchMode = FALSE
0.297: Inventory complete: ReturnStatus=0, 62 ticks
0.297: Num Ticks for invent : 62
0.297: Allocation size of drive C: is 4096 bytes, free space = 11263389696
bytes
0.297: Drive C: free 10741MB req: 37MB w/uninstall 0MB
0.297: CabinetBuild complete
0.297: Num Ticks for Cabinet build : 0
0.297: DynamicStrings section not defined or empty.
0.297: FileInUse:: Detection disabled.
1.297: Registering Uninstall Program for -> KB954550-v5, KB954550-v5 , 0x0
1.297: LoadFileQueues: UpdSpGetSourceFileLocation for halaacpi.dll failed:
0xe0000102
1.313: Copied file: C:\WINDOWS\system32\spmsg.dll
1.344: PFE2: Not avoiding Per File Exceptions.
1.344: GetCatVersion: Failed to retrieve version information from
C:\WINDOWS\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\KB954550-v5.cat with error 0x57
1.360: MyMakePerFileExceptionA: MakePerFileException failed; error=0x6ba.
1.360: Copied file: c:\1ce0b44e820c91ab1928a85621\update\..\amd64\xpssvcs.dll
1.454: MyMakePerFileExceptionA: MakePerFileException failed; error=0x6ba.
1.454: Copied file: c:\1ce0b44e820c91ab1928a85621\update\..\amd64\mxdwdrv.dll
1.485: MyMakePerFileExceptionA: MakePerFileException failed; error=0x6ba.
1.485: Copied file:
c:\1ce0b44e820c91ab1928a85621\update\..\amd64\msxpsinc.ppd
1.485: MyMakePerFileExceptionA: MakePerFileException failed; error=0x6ba.
1.485: Copied file:
c:\1ce0b44e820c91ab1928a85621\update\..\amd64\msxpsinc.gpd
1.485: MyMakePerFileExceptionA: MakePerFileException failed; error=0x6ba.
1.485: Copied file:
c:\1ce0b44e820c91ab1928a85621\update\..\amd64\msxpsdrv.inf
1.500: MyMakePerFileExceptionA: MakePerFileException failed; error=0x6ba.
1.500: Copied file:
c:\1ce0b44e820c91ab1928a85621\update\..\amd64\msxpsdrv.cat
1.500: MyMakePerFileExceptionA: MakePerFileException failed; error=0x6ba.
1.500: Copied file:
c:\1ce0b44e820c91ab1928a85621\update\..\amd64\filterpipelineprintproc.dll
1.500: MyMakePerFileExceptionA: MakePerFileException failed; error=0x6ba.
1.500: Copied file:
C:\WINDOWS\System32\spool\PRTPROCS\W32X86\printfilterpipelinesvc.exe
1.532: MyMakePerFileExceptionA: MakePerFileException failed; error=0x6ba.
1.532: Copied file: c:\1ce0b44e820c91ab1928a85621\update\..\i386\xpssvcs.dll
1.579: MyMakePerFileExceptionA: MakePerFileException failed; error=0x6ba.
1.579: Copied file: c:\1ce0b44e820c91ab1928a85621\update\..\i386\mxdwdrv.dll
1.610: MyMakePerFileExceptionA: MakePerFileException failed; error=0x6ba.
1.610: Copied file: c:\1ce0b44e820c91ab1928a85621\update\..\i386\msxpsinc.ppd
1.610: MyMakePerFileExceptionA: MakePerFileException failed; error=0x6ba.
1.610: Copied file: c:\1ce0b44e820c91ab1928a85621\update\..\i386\msxpsinc.gpd
1.610: MyMakePerFileExceptionA: MakePerFileException failed; error=0x6ba.
1.610: Copied file: c:\1ce0b44e820c91ab1928a85621\update\..\i386\msxpsdrv.inf
1.625: MyMakePerFileExceptionA: MakePerFileException failed; error=0x6ba.
1.625: Copied file: c:\1ce0b44e820c91ab1928a85621\update\..\i386\msxpsdrv.cat
1.625: MyMakePerFileExceptionA: MakePerFileException failed; error=0x6ba.
1.625: Copied file:
c:\1ce0b44e820c91ab1928a85621\update\..\i386\filterpipelineprintproc.dll
1.625: MyMakePerFileExceptionA: MakePerFileException failed; error=0x6ba.
1.625: Copied file: C:\WINDOWS\system32\xpssvcs.dll
1.672: MyMakePerFileExceptionA: MakePerFileException failed; error=0x6ba.
1.672: Copied file: C:\WINDOWS\system32\xpsshhdr.dll
1.704: MyMakePerFileExceptionA: MakePerFileException failed; error=0x6ba.
1.704: Copied file: C:\WINDOWS\system32\prntvpt.dll
1.704: MyMakePerFileExceptionA: MakePerFileException failed; error=0x6ba.
1.704: Copied file: C:\WINDOWS\Driver Cache\i386\unires.dll
1.750: MyMakePerFileExceptionA: MakePerFileException failed; error=0x6ba.
1.750: Copied file: C:\WINDOWS\Driver Cache\i386\unidrvui.dll
1.766: MyMakePerFileExceptionA: MakePerFileException failed; error=0x6ba.
1.766: Copied file: C:\WINDOWS\Driver Cache\i386\unidrv.hlp
1.782: MyMakePerFileExceptionA: MakePerFileException failed; error=0x6ba.
1.782: Copied file: C:\WINDOWS\Driver Cache\i386\unidrv.dll
1.797: MyMakePerFileExceptionA: MakePerFileException failed; error=0x6ba.
1.797: Copied file: C:\WINDOWS\Driver Cache\i386\stdschmx.gdl
1.797: MyMakePerFileExceptionA: MakePerFileException failed; error=0x6ba.
1.797: Copied file: C:\WINDOWS\Driver Cache\i386\stdschem.gdl
1.797: MyMakePerFileExceptionA: MakePerFileException failed; error=0x6ba.
1.797: Copied file: C:\WINDOWS\Driver Cache\i386\stdnames.gpd
1.813: MyMakePerFileExceptionA: MakePerFileException failed; error=0x6ba.
1.813: Copied file: C:\WINDOWS\Driver Cache\i386\stddtype.gdl
1.813: MyMakePerFileExceptionA: MakePerFileException failed; error=0x6ba.
1.813: Copied file: C:\WINDOWS\Driver Cache\i386\mxdwdui.ini
1.813: MyMakePerFileExceptionA: MakePerFileException failed; error=0x6ba.
1.813: Copied file: C:\WINDOWS\Driver Cache\i386\mxdwdui.gpd
1.829: MyMakePerFileExceptionA: MakePerFileException failed; error=0x6ba.
1.829: Copied file: C:\WINDOWS\Driver Cache\i386\mxdwdui.dll
1.829: MyMakePerFileExceptionA: MakePerFileException failed; error=0x6ba.
1.829: Copied file: C:\WINDOWS\Driver Cache\i386\mxdwdrv.dll
1.860: MyMakePerFileExceptionA: MakePerFileException failed; error=0x6ba.
1.860: Copied file: C:\WINDOWS\Driver Cache\i386\msxpsinc.ppd
1.860: MyMakePerFileExceptionA: MakePerFileException failed; error=0x6ba.
1.860: Copied file: C:\WINDOWS\Driver Cache\i386\msxpsinc.gpd
1.875: MyMakePerFileExceptionA: MakePerFileException failed; error=0x6ba.
1.875: Copied file: C:\WINDOWS\Driver Cache\i386\msxpsdrv.inf
1.875: MyMakePerFileExceptionA: MakePerFileException failed; error=0x6ba.
1.875: Copied file: C:\WINDOWS\Driver Cache\i386\filterpipelineprintproc.dll
1.875: MyMakePerFileExceptionA: MakePerFileException failed; error=0x6ba.
1.875: Copied file: C:\WINDOWS\system32\DllCache\xpssvcs.dll
1.891: MyMakePerFileExceptionA: MakePerFileException failed; error=0x6ba.
1.891: Copied file: C:\WINDOWS\system32\DllCache\xpsshhdr.dll
1.891: MyMakePerFileExceptionA: MakePerFileException failed; error=0x6ba.
1.891: Copied file: C:\WINDOWS\system32\DllCache\printfilterpipelinesvc.exe
1.907: MyMakePerFileExceptionA: MakePerFileException failed; error=0x6ba.
1.907: Copied file: C:\WINDOWS\system32\DllCache\filterpipelineprintproc.dll
1.907: DoInstallation: Installing assemblies with source root path:
c:\1ce0b44e820c91ab1928a85621\
1.907: Num Ticks for Copying files : 1610
1.922: Num Ticks for Reg update and deleting 0 size files : 15
1.922: Starting process: C:\WINDOWS\system32\spupdsvc.exe /install
1.985: Return Code = 0
1.985: Starting process:
c:\1ce0b44e820c91ab1928a85621\update\..\printfilterpipelinesvc.exe /RegServer
c:\1ce0b44e820c91ab1928a85621\update
2.891: Return Code = 0
2.891: Starting process: C:\WINDOWS\system32\regsvr32 /s
C:\WINDOWS\system32\prntvpt.dll
2.938: Return Code = 0
2.938: Starting process: C:\WINDOWS\system32\regsvr32 /s
C:\WINDOWS\System32\spool\PRTPROCS\W32X86\FilterPipelinePrintProc.dll
2.985: Return Code = 0
2.985: Starting process: del /q
c:\1ce0b44e820c91ab1928a85621\update\..\i386\*
2.985: RunInfProcesses: SpawnProcessAndWaitForItToComplete on "del /q
c:\1ce0b44e820c91ab1928a85621\update\..\i386\*" in [ProcessesToRun] failed:
0x2
2.985: Return Code = 2
2.985: Starting process: del /q
c:\1ce0b44e820c91ab1928a85621\update\..\amd64\*
2.985: RunInfProcesses: SpawnProcessAndWaitForItToComplete on "del /q
c:\1ce0b44e820c91ab1928a85621\update\..\amd64\*" in [ProcessesToRun] failed:
0x2
2.985: Return Code = 2
2.985: Starting process: rmdir /q
c:\1ce0b44e820c91ab1928a85621\update\..\i386
2.985: RunInfProcesses: SpawnProcessAndWaitForItToComplete on "rmdir /q
c:\1ce0b44e820c91ab1928a85621\update\..\i386" in [ProcessesToRun] failed: 0x2
2.985: Return Code = 2
2.985: Starting process: rmdir /q
c:\1ce0b44e820c91ab1928a85621\update\..\amd64
2.985: RunInfProcesses: SpawnProcessAndWaitForItToComplete on "rmdir /q
c:\1ce0b44e820c91ab1928a85621\update\..\amd64" in [ProcessesToRun] failed:
0x2
2.985: Return Code = 2
2.985: ---- Old Information In The Registry ------
2.985: Source:C:\WINDOWS\System32\spool\DRIVERS\W32X86\3\New\jnwdui.dll
2.985: Destination:C:\WINDOWS\System32\spool\DRIVERS\W32X86\3\jnwdui.dll
(0.3.7.0)
2.985: Source:C:\pagefile.sys
2.985: Destination:
2.985: Source:C:\Config.Msi\52bfe.rbf (1.0.3705.6018)
2.985: Destination:
2.985: ---- New Information In The Registry ------
2.985: Source:C:\WINDOWS\System32\spool\DRIVERS\W32X86\3\New\jnwdui.dll
2.985: Destination:C:\WINDOWS\System32\spool\DRIVERS\W32X86\3\jnwdui.dll
(0.3.7.0)
2.985: Source:C:\pagefile.sys
2.985: Destination:
2.985: Source:C:\Config.Msi\52bfe.rbf (1.0.3705.6018)
2.985: Destination:
2.985: UpdateSpUpdSvcInf: Source [ProcessesToRunAfterReboot] section is
empty; nothing to do.
2.985: Starting process:
C:\WINDOWS\System32\spool\PRTPROCS\W32X86\printfilterpipelinesvc.exe
/RegServer c:\1ce0b44e820c91ab1928a85621\update
3.344: Return Code = 0
3.344: RebootNecessary = 0,WizardInput = 1 , DontReboot = 1, ForceRestart = 0

Robert
Sun Nov 02 14:00:45 PST 2008


"koawmfot" <koawmfot@discussions.microsoft.com> wrote in message news:259E83C5-C3BE-41EE-8AE3-51EE55118D18@microsoft.com...
> it appears to be from this update, 954550-v5.
>
> here is the log. you can see below the directory deletion fails. returns
> code 2.

No. Where?

> why all of the sudden is this an issue?


I don't think that specifically is an issue.
There are other more severe error symptoms later in your log.
It looks to me that too much is locked down to install this update
cleanly.

Also, you are getting this error code

<cmd_output OS="XPsp3">
E:\>set /a c =0x6ba
1722
E:\>net helpmsg %c%

The RPC server is unavailable.
</cmd_output>

I have no idea why the RPC server would be needed for an install
unless the product being updated was somehow incomplete.

Have you tried downloading this update and installing it manually?
Perhaps you would see different symptoms in the log then?
Also, then you could request verbose logging to at least supplement
what you have now. If that is not enough you could further supplement
those diagnostics by running ProcMon to trace all registry and file
accesses that the update attempts.

Hmm... what exactly is KB954550? A search of microsoft.com
yields no hits?


Good luck

Robert Aldwinckle
---


>
> [KB954550-v5.log]
> 0.032:
> ================================================================================
> 0.032: 2008/10/24 16:45:59.906 (local)
> 0.032: c:\1ce0b44e820c91ab1928a85621\update\update.exe (version 6.3.13.0)
> 0.032: InitializeSvcPackLogWrapper: Unable to write to user-supplied log
> path: c:\1ce0b44e820c91ab1928a85621\update\%TEMP%\dd_XPS.txt
> 0.032: Hotfix started with following command line: /quiet /norestart
> /log:%TEMP%\dd_XPS.txt
> 0.032: In Function GetReleaseSet, line 1216, RegQueryValueEx failed with
> error 0x2
> 0.032: In Function GetReleaseSet, line 1240, RegQueryValueEx failed with
> error 0x2
> 0.204: ---- Old Information In The Registry ------
> 0.204: Source:C:\WINDOWS\System32\spool\DRIVERS\W32X86\3\New\jnwdui.dll
> 0.204: Destination:C:\WINDOWS\System32\spool\DRIVERS\W32X86\3\jnwdui.dll
> (0.3.7.0)
> 0.204: Source:C:\pagefile.sys
> 0.204: Destination:
> 0.204: Source:C:\Config.Msi\52bfe.rbf (1.0.3705.6018)
> 0.204: Destination:
> 0.204: ---- New Information In The Registry ------
> 0.204: Source:C:\WINDOWS\System32\spool\DRIVERS\W32X86\3\New\jnwdui.dll
> 0.204: Destination:C:\WINDOWS\System32\spool\DRIVERS\W32X86\3\jnwdui.dll
> (0.3.7.0)
> 0.204: Source:C:\pagefile.sys
> 0.204: Destination:
> 0.204: Source:C:\Config.Msi\52bfe.rbf (1.0.3705.6018)
> 0.204: Destination:
> 0.204: In Function GetReleaseSet, line 1216, RegQueryValueEx failed with
> error 0x2
> 0.204: In Function GetReleaseSet, line 1240, RegQueryValueEx failed with
> error 0x2
> 0.204: SetProductTypes: InfProductBuildType=BuildType.Sel
> 0.204: SetAltOsLoaderPath: No section uses DirId 65701; done.
> 0.235: DoInstallation: FetchSourceURL for
> c:\1ce0b44e820c91ab1928a85621\update\update.inf failed
> 0.235: CreateUninstall = 0,Directory = C:\WINDOWS\$NtUninstallKB954550-v5$
> 0.235: LoadFileQueues: UpdSpGetSourceFileLocation for halaacpi.dll failed:
> 0xe0000102
> 0.235: BuildCabinetManifest: update.url absent
> 0.235: Starting AnalyzeComponents
> 0.235: AnalyzePhaseZero used 0 ticks
> 0.235: No c:\windows\INF\updtblk.inf file.
> 0.235: SetupFindFirstLine in LoadExclusionList Failed with error: 0xe0000102
> 0.235: SetupFindFirstLine in LoadExclusionList Failed with error: 0xe0000102
> 0.235: Enumerating Devices of printer, GUID
> {4d36e979-e325-11ce-bfc1-08002be10318}
> 0.266: OEM file scan used 31 ticks
> 0.266: AnalyzePhaseOne: used 31 ticks
> 0.266: AnalyzeComponents: Hotpatch analysis disabled; skipping.
> 0.266: AnalyzeComponents: Hotpatching is disabled.
> 0.297: AnalyzePhaseTwo used 31 ticks
> 0.297: AnalyzePhaseThree used 0 ticks
> 0.297: AnalyzePhaseFive used 0 ticks
> 0.297: AnalyzePhaseSix used 0 ticks
> 0.297: AnalyzeComponents used 62 ticks
> 0.297: Downloading 0 files
> 0.297: bPatchMode = FALSE
> 0.297: Inventory complete: ReturnStatus=0, 62 ticks
> 0.297: Num Ticks for invent : 62
> 0.297: Allocation size of drive C: is 4096 bytes, free space = 11263389696
> bytes
> 0.297: Drive C: free 10741MB req: 37MB w/uninstall 0MB
> 0.297: CabinetBuild complete
> 0.297: Num Ticks for Cabinet build : 0
> 0.297: DynamicStrings section not defined or empty.
> 0.297: FileInUse:: Detection disabled.
> 1.297: Registering Uninstall Program for -> KB954550-v5, KB954550-v5 , 0x0
> 1.297: LoadFileQueues: UpdSpGetSourceFileLocation for halaacpi.dll failed:
> 0xe0000102
> 1.313: Copied file: C:\WINDOWS\system32\spmsg.dll
> 1.344: PFE2: Not avoiding Per File Exceptions.
> 1.344: GetCatVersion: Failed to retrieve version information from
> C:\WINDOWS\system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\KB954550-v5.cat with error 0x57
> 1.360: MyMakePerFileExceptionA: MakePerFileException failed; error=0x6ba.
> 1.360: Copied file: c:\1ce0b44e820c91ab1928a85621\update\..\amd64\xpssvcs.dll
> 1.454: MyMakePerFileExceptionA: MakePerFileException failed; error=0x6ba.
> 1.454: Copied file: c:\1ce0b44e820c91ab1928a85621\update\..\amd64\mxdwdrv.dll
> 1.485: MyMakePerFileExceptionA: MakePerFileException failed; error=0x6ba.
> 1.485: Copied file:
> c:\1ce0b44e820c91ab1928a85621\update\..\amd64\msxpsinc.ppd
> 1.485: MyMakePerFileExceptionA: MakePerFileException failed; error=0x6ba.
> 1.485: Copied file:
> c:\1ce0b44e820c91ab1928a85621\update\..\amd64\msxpsinc.gpd
> 1.485: MyMakePerFileExceptionA: MakePerFileException failed; error=0x6ba.
> 1.485: Copied file:
> c:\1ce0b44e820c91ab1928a85621\update\..\amd64\msxpsdrv.inf
> 1.500: MyMakePerFileExceptionA: MakePerFileException failed; error=0x6ba.
> 1.500: Copied file:
> c:\1ce0b44e820c91ab1928a85621\update\..\amd64\msxpsdrv.cat
> 1.500: MyMakePerFileExceptionA: MakePerFileException failed; error=0x6ba.
> 1.500: Copied file:
> c:\1ce0b44e820c91ab1928a85621\update\..\amd64\filterpipelineprintproc.dll
> 1.500: MyMakePerFileExceptionA: MakePerFileException failed; error=0x6ba.
> 1.500: Copied file:
> C:\WINDOWS\System32\spool\PRTPROCS\W32X86\printfilterpipelinesvc.exe
> 1.532: MyMakePerFileExceptionA: MakePerFileException failed; error=0x6ba.
> 1.532: Copied file: c:\1ce0b44e820c91ab1928a85621\update\..\i386\xpssvcs.dll
> 1.579: MyMakePerFileExceptionA: MakePerFileException failed; error=0x6ba.
> 1.579: Copied file: c:\1ce0b44e820c91ab1928a85621\update\..\i386\mxdwdrv.dll
> 1.610: MyMakePerFileExceptionA: MakePerFileException failed; error=0x6ba.
> 1.610: Copied file: c:\1ce0b44e820c91ab1928a85621\update\..\i386\msxpsinc.ppd
> 1.610: MyMakePerFileExceptionA: MakePerFileException failed; error=0x6ba.
> 1.610: Copied file: c:\1ce0b44e820c91ab1928a85621\update\..\i386\msxpsinc.gpd
> 1.610: MyMakePerFileExceptionA: MakePerFileException failed; error=0x6ba.
> 1.610: Copied file: c:\1ce0b44e820c91ab1928a85621\update\..\i386\msxpsdrv.inf
> 1.625: MyMakePerFileExceptionA: MakePerFileException failed; error=0x6ba.
> 1.625: Copied file: c:\1ce0b44e820c91ab1928a85621\update\..\i386\msxpsdrv.cat
> 1.625: MyMakePerFileExceptionA: MakePerFileException failed; error=0x6ba.
> 1.625: Copied file:
> c:\1ce0b44e820c91ab1928a85621\update\..\i386\filterpipelineprintproc.dll
> 1.625: MyMakePerFileExceptionA: MakePerFileException failed; error=0x6ba.
> 1.625: Copied file: C:\WINDOWS\system32\xpssvcs.dll
> 1.672: MyMakePerFileExceptionA: MakePerFileException failed; error=0x6ba.
> 1.672: Copied file: C:\WINDOWS\system32\xpsshhdr.dll
> 1.704: MyMakePerFileExceptionA: MakePerFileException failed; error=0x6ba.
> 1.704: Copied file: C:\WINDOWS\system32\prntvpt.dll
> 1.704: MyMakePerFileExceptionA: MakePerFileException failed; error=0x6ba.
> 1.704: Copied file: C:\WINDOWS\Driver Cache\i386\unires.dll
> 1.750: MyMakePerFileExceptionA: MakePerFileException failed; error=0x6ba.
> 1.750: Copied file: C:\WINDOWS\Driver Cache\i386\unidrvui.dll
> 1.766: MyMakePerFileExceptionA: MakePerFileException failed; error=0x6ba.
> 1.766: Copied file: C:\WINDOWS\Driver Cache\i386\unidrv.hlp
> 1.782: MyMakePerFileExceptionA: MakePerFileException failed; error=0x6ba.
> 1.782: Copied file: C:\WINDOWS\Driver Cache\i386\unidrv.dll
> 1.797: MyMakePerFileExceptionA: MakePerFileException failed; error=0x6ba.
> 1.797: Copied file: C:\WINDOWS\Driver Cache\i386\stdschmx.gdl
> 1.797: MyMakePerFileExceptionA: MakePerFileException failed; error=0x6ba.
> 1.797: Copied file: C:\WINDOWS\Driver Cache\i386\stdschem.gdl
> 1.797: MyMakePerFileExceptionA: MakePerFileException failed; error=0x6ba.
> 1.797: Copied file: C:\WINDOWS\Driver Cache\i386\stdnames.gpd
> 1.813: MyMakePerFileExceptionA: MakePerFileException failed; error=0x6ba.
> 1.813: Copied file: C:\WINDOWS\Driver Cache\i386\stddtype.gdl
> 1.813: MyMakePerFileExceptionA: MakePerFileException failed; error=0x6ba.
> 1.813: Copied file: C:\WINDOWS\Driver Cache\i386\mxdwdui.ini
> 1.813: MyMakePerFileExceptionA: MakePerFileException failed; error=0x6ba.
> 1.813: Copied file: C:\WINDOWS\Driver Cache\i386\mxdwdui.gpd
> 1.829: MyMakePerFileExceptionA: MakePerFileException failed; error=0x6ba.
> 1.829: Copied file: C:\WINDOWS\Driver Cache\i386\mxdwdui.dll
> 1.829: MyMakePerFileExceptionA: MakePerFileException failed; error=0x6ba.
> 1.829: Copied file: C:\WINDOWS\Driver Cache\i386\mxdwdrv.dll
> 1.860: MyMakePerFileExceptionA: MakePerFileException failed; error=0x6ba.
> 1.860: Copied file: C:\WINDOWS\Driver Cache\i386\msxpsinc.ppd
> 1.860: MyMakePerFileExceptionA: MakePerFileException failed; error=0x6ba.
> 1.860: Copied file: C:\WINDOWS\Driver Cache\i386\msxpsinc.gpd
> 1.875: MyMakePerFileExceptionA: MakePerFileException failed; error=0x6ba.
> 1.875: Copied file: C:\WINDOWS\Driver Cache\i386\msxpsdrv.inf
> 1.875: MyMakePerFileExceptionA: MakePerFileException failed; error=0x6ba.
> 1.875: Copied file: C:\WINDOWS\Driver Cache\i386\filterpipelineprintproc.dll
> 1.875: MyMakePerFileExceptionA: MakePerFileException failed; error=0x6ba.
> 1.875: Copied file: C:\WINDOWS\system32\DllCache\xpssvcs.dll
> 1.891: MyMakePerFileExceptionA: MakePerFileException failed; error=0x6ba.
> 1.891: Copied file: C:\WINDOWS\system32\DllCache\xpsshhdr.dll
> 1.891: MyMakePerFileExceptionA: MakePerFileException failed; error=0x6ba.
> 1.891: Copied file: C:\WINDOWS\system32\DllCache\printfilterpipelinesvc.exe
> 1.907: MyMakePerFileExceptionA: MakePerFileException failed; error=0x6ba.
> 1.907: Copied file: C:\WINDOWS\system32\DllCache\filterpipelineprintproc.dll
> 1.907: DoInstallation: Installing assemblies with source root path:
> c:\1ce0b44e820c91ab1928a85621\
> 1.907: Num Ticks for Copying files : 1610
> 1.922: Num Ticks for Reg update and deleting 0 size files : 15
> 1.922: Starting process: C:\WINDOWS\system32\spupdsvc.exe /install
> 1.985: Return Code = 0
> 1.985: Starting process:
> c:\1ce0b44e820c91ab1928a85621\update\..\printfilterpipelinesvc.exe /RegServer
> c:\1ce0b44e820c91ab1928a85621\update
> 2.891: Return Code = 0
> 2.891: Starting process: C:\WINDOWS\system32\regsvr32 /s
> C:\WINDOWS\system32\prntvpt.dll
> 2.938: Return Code = 0
> 2.938: Starting process: C:\WINDOWS\system32\regsvr32 /s
> C:\WINDOWS\System32\spool\PRTPROCS\W32X86\FilterPipelinePrintProc.dll
> 2.985: Return Code = 0
> 2.985: Starting process: del /q
> c:\1ce0b44e820c91ab1928a85621\update\..\i386\*
> 2.985: RunInfProcesses: SpawnProcessAndWaitForItToComplete on "del /q
> c:\1ce0b44e820c91ab1928a85621\update\..\i386\*" in [ProcessesToRun] failed:
> 0x2
> 2.985: Return Code = 2
> 2.985: Starting process: del /q
> c:\1ce0b44e820c91ab1928a85621\update\..\amd64\*
> 2.985: RunInfProcesses: SpawnProcessAndWaitForItToComplete on "del /q
> c:\1ce0b44e820c91ab1928a85621\update\..\amd64\*" in [ProcessesToRun] failed:
> 0x2
> 2.985: Return Code = 2
> 2.985: Starting process: rmdir /q
> c:\1ce0b44e820c91ab1928a85621\update\..\i386
> 2.985: RunInfProcesses: SpawnProcessAndWaitForItToComplete on "rmdir /q
> c:\1ce0b44e820c91ab1928a85621\update\..\i386" in [ProcessesToRun] failed: 0x2
> 2.985: Return Code = 2
> 2.985: Starting process: rmdir /q
> c:\1ce0b44e820c91ab1928a85621\update\..\amd64
> 2.985: RunInfProcesses: SpawnProcessAndWaitForItToComplete on "rmdir /q
> c:\1ce0b44e820c91ab1928a85621\update\..\amd64" in [ProcessesToRun] failed:
> 0x2
> 2.985: Return Code = 2
> 2.985: ---- Old Information In The Registry ------
> 2.985: Source:C:\WINDOWS\System32\spool\DRIVERS\W32X86\3\New\jnwdui.dll
> 2.985: Destination:C:\WINDOWS\System32\spool\DRIVERS\W32X86\3\jnwdui.dll
> (0.3.7.0)
> 2.985: Source:C:\pagefile.sys
> 2.985: Destination:
> 2.985: Source:C:\Config.Msi\52bfe.rbf (1.0.3705.6018)
> 2.985: Destination:
> 2.985: ---- New Information In The Registry ------
> 2.985: Source:C:\WINDOWS\System32\spool\DRIVERS\W32X86\3\New\jnwdui.dll
> 2.985: Destination:C:\WINDOWS\System32\spool\DRIVERS\W32X86\3\jnwdui.dll
> (0.3.7.0)
> 2.985: Source:C:\pagefile.sys
> 2.985: Destination:
> 2.985: Source:C:\Config.Msi\52bfe.rbf (1.0.3705.6018)
> 2.985: Destination:
> 2.985: UpdateSpUpdSvcInf: Source [ProcessesToRunAfterReboot] section is
> empty; nothing to do.
> 2.985: Starting process:
> C:\WINDOWS\System32\spool\PRTPROCS\W32X86\printfilterpipelinesvc.exe
> /RegServer c:\1ce0b44e820c91ab1928a85621\update
> 3.344: Return Code = 0
> 3.344: RebootNecessary = 0,WizardInput = 1 , DontReboot = 1, ForceRestart = 0
>
>
>
>

Mark
Wed Nov 19 08:39:00 PST 2008

I am also having this issue. The directory path is different put the files
are the same. I can not manually delete it. I can probably hack the machine
to get rid of it, but I do not know how this got here. Is this related to
the .NET Framework 3.5 SP1? Have you gotten anything from Microsoft to
detail why this is there and how it got there.

Thanks in advanced,

Mark Hall