Windows 7 - Leftover folders after Update

Asked By mme000 \(add on 24-Sep-08 06:37 AM
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 Bear [MS MVP] replied on 24-Sep-08 09:47 AM
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 \(add replied on 25-Sep-08 04:53 AM
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 [MVP] replied on 25-Sep-08 12:51 PM
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
===============
koawmfo replied on 24-Oct-08 06:54 PM
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?
koawmfo replied on 28-Oct-08 11:22 AM
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 Aldwinckle replied on 02-Nov-08 05:00 PM
No.  Where?



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

E:\>set /a c =0x6ba
1722
E:\>net helpmsg %c%

The RPC server is unavailable.

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
---
Mark Hal replied on 19-Nov-08 11:39 AM
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
Ale replied on 03-Dec-08 09:43 AM
same for me, also having those files left over....... appreciate some input
from MS on this.
MarkHal replied on 03-Dec-08 12:32 PM
I have validated that this hotfix is part of .NET Framework 3.5 SP1.  It
might be part of .NET 3.0, but that is installed with the 3.5 installation.

I noticed this issue when creating a base image for our client machine, so I
had the option to start over with a clean OS.  How I got rid of this was to
install Windows XP SP2, install the XPS Essentials Pack and then install 3.5
SP1.  It still left the folders around, but this time I could delete them.

Maybe the hotfix installation team should look at the installation because
based on the log, they are copying the file to the %windir% (somewhere I
forget), but then registering it as a print provider in the hotfix temporary
installation folder. Arghhh.

Mark
Ander replied on 03-Dec-08 04:37 PM
"Mark Hall" wrote:
Ander replied on 03-Dec-08 05:12 PM
I too have found these rogue files that I can't delete. Had about 20 Windows
Security Updates listed on the same day. Do I just leave the files alone
hoping they'll disappear on their own (not likely)?
Ale replied on 06-Dec-08 05:30 AM
Hi,

you can't delete the folders because some strange permissions are applied to
it, so you must first change the permissions. A colleague of me found out
that if you install the XPS essentials pack prior the .net 3.5sp1 package, no
folders are left over. I think this .net 35 SP1 has a serious bug MS should
fix.
koawmfo replied on 07-Jan-09 09:23 AM
Right here:




the update is being installed during T-12 of windows setup.  maybe the RPC
server isn't fully accessible at that moment?  this update is included as
part of .NET Framework 3.5 SP1.  I believe it actually sets the folder for
deletion using the PendingFileRenameOperations reg key, but the permissions
on it are strange, or rather different than the permissions on the other
folders and maybe it cannot remove it after the first reboot?  i can try
re-setting the permissions with a script before the first reboot and see if
that helps.  I know what folders are supposed to be there, so it should be
easy to figure out what shouldn't and need explicit perms set.

this is from the .net framework log:

[01/06/09,15:07:57] XPSEPSC Installer: GenericComponent Action:
CreateProcess launched with cmd line :
D:\$oem$\fw\3.5\dotnetfx30\XPSEPSC-x86-en-US.exe /quiet /norestart
/log:"%TEMP%\dd_XPS.txt"
[01/06/09,15:07:57] BWaitForMSI(): Verifying we're the only installation
currently in progress.
[01/06/09,15:07:57] BWaitForMSI(): Ready to proceed with installation.
Continuing...
[01/06/09,15:08:09] XPSEPSC Installer:
D:\$oem$\fw\3.5\dotnetfx30\XPSEPSC-x86-en-US.exe exited with return value 0
[01/06/09,15:08:09] InstallReturnValue: GFN_MID XPSEPSC x86 Installer, 0x0
[01/06/09,15:08:09] XPSEPSC Installer: Error code 0 for this component means
[01/06/09,15:08:09] XPSEPSC Installer: Setup Succeeded on component XPSEPSC
Installer
[01/06/09,15:08:09] XPSEPSC Installer: CBaseComponent::LaunchWatson() -
Obtained CSetupWatson instance
[01/06/09,15:08:09] XPSEPSC Installer:
ISetupManager::GetGlobalCustomProperty() failed to find global prop in
CBaseComponent::GetGlobalCustomProperty()
[01/06/09,15:08:09] XPSEPSC Installer:
ISetupManager::GetGlobalCustomProperty() failed to find global prop in
CBaseComponent::GetGlobalCustomProperty()
[01/06/09,15:08:09] Setup.exe: GetGlobalCustomProperty - Property:
{2B7DE335-914B-476F-AF77-E9EF03938188} - PropertyName: Component Number -
Value: 3
[01/06/09,15:08:09] Setup.exe: GetGlobalCustomProperty - Property:
{2B7DE335-914B-476F-AF77-E9EF03938188} - PropertyName: Component Number -
Value: 3
[01/06/09,15:08:09] XPSEPSC Installer:  Pending Reboot Table state : Logging
start
[01/06/09,15:08:09] XPSEPSC Installer:
_________________________________________
[01/06/09,15:08:09] PFR:  GFN_MID XPSEPSC x86 Installer, RENAME, , ,
C:\WINDOWS\System32\spool\DRIVERS\W32X86\3\New\jnwdui.dll,   (  ----  ),
(--:--:--), C:\WINDOWS\System32\spool\DRIVERS\W32X86\3\jnwdui.dll,   (
1.7.2600.5512 ) ,   ( Mon Apr 14 04:41:58 2008 )
[01/06/09,15:08:09] PFR: GFN_MID XPSEPSC x86 Installer, DELETE, , ,
C:\pagefile.sys,   (  ----  ),   ( Tue Jan 06 09:53:31 2009 )
[01/06/09,15:08:09] PFR: GFN_MID XPSEPSC x86 Installer, DELETE, mscoree.dll,
MSCOREE.DLL, C:\Config.Msi\9df0e.rbf,   ( 1.0.3705.6018 ) ,   ( Wed Jun 27
18:25:12 2007 )
[01/06/09,15:08:09] PFR: GFN_MID XPSEPSC x86 Installer, DELETE, , ,
c:\444efc15cfcbbb5142c3e0e5bb,   (  ----  ),   ( Tue Jan 06 15:08:09 2009 )
[01/06/09,15:08:09] XPSEPSC Installer:  Pending Reboot Table state : Logging
end
[01/06/09,15:08:09] XPSEPSC Installer:
_________________________________________
ax_cap replied on 10-Feb-09 11:55 AM
this folder is created by the microsoft XPS printer. it's safe to
deleted.

do delete the folder:

windows XP proffesional:

1: open c:\
2:click "tools --> folder options" on the toolbar
3: select "view"
4: drop down the toolbar an deselect "use simple file sharing". click
ok
5:right click on the folder and select "properties".
6:on the security tab, select "administrators" group(anything that say
administrator)
7:click or select "full control" on the "permission" box.
8:click ok.

now you have the rights to delete the folder.


--
ax_cap
Posted via http://www.vistaheads.com
maged alyami replied to ax_cap on 16-Dec-09 02:42 AM
replay
maged alyami replied to ax_cap on 16-Dec-09 02:43 AM
i have file i can not delete it .
Jackie replied to ax_cap on 14-Jul-10 04:34 PM
Was wondering if anyone can "dumb down" the removal procedure for me? :)

I've had the folder for ages in my latest harddisc, where i have no programs concerning Microsoft installed, it's only for storage so it irks me to have a rogue, out of place folder there (or rather, suffering from a OCD and can't stand it!!!!)



Can i remove it by simply left-click on it and unclick the whatever it's called in English that won't let it be deleted or will that mess things up?

i've read through this thread already but most of it makes no sense to me, sorry....



Thanks for any help!!!!
paul heffer replied to Jackie on 16-Jul-10 06:39 PM
You can follow the procedure to Take Ownership of files/folders/resources OR...



Get Unlocker Assistant.



If you have permission to install programs (e.g. ur personal pc) you can use it to kill most anything.  If it's really tricky it may delete on reboot.  There are a number of similar tools but for the last year or three this has served me well.



do links work in this forum?  google it otherwise.  Here's the link:

http://ccollomb.free.fr/unlocker/



Dunno why Microsoft Explorer still has trouble deleting folders with pictures because of the Thumbs.db file.  Real pain the backside.. at least Unlocker releases the locking handles and let's you delete the file without having to close every program to figure out what is hanging on to it.. even Explorer itself.



Hope this helps.  :)



the leftover from updates like described above are generally safe to delete and like u i suffer a bit from an OCD thing... u know, it really bugs me when u do a defrag and there's one little square that doesn't want to behave .....  ;)
paul heffer replied to Jackie on 16-Jul-10 06:40 PM
You can follow the procedure to Take Ownership of files/folders/resources OR...



Get Unlocker Assistant.



If you have permission to install programs (e.g. ur personal pc) you can use it to kill most anything.  If it's really tricky it may delete on reboot.  There are a number of similar tools but for the last year or three this has served me well.



do links work in this forum?  google it otherwise.  Here's the link:

http://ccollomb.free.fr/unlocker/



Dunno why Microsoft Explorer still has trouble deleting folders with pictures because of the Thumbs.db file.  Real pain the backside.. at least Unlocker releases the locking handles and let's you delete the file without having to close every program to figure out what is hanging on to it.. even Explorer itself.



Hope this helps.  :)



the leftover from updates like described above are generally safe to delete and like u i suffer a bit from an OCD thing... u know, it really bugs me when u do a defrag and there's one little square that doesn't want to behave .....  ;)
Richard Moore replied to Jackie on 17-Jul-10 08:13 PM
For users with XP home edition you will need to change the permissions using a different method.



The following worked for me:



Right click on the problem directory and select "Sharing and security"



Check the boxes that say:

Share this folder on the network

Allow network users to change my files



You should be able to delete the folder now.  (You will get a warning about the files being shared.  Just select OK.)