Over the weekend, after getting an OS update to my Windows XP, a folder
called f3e2792ea014a7a9c95fd55e has appeared on my C: with two subfolders:
amd64 and i386. In particular, there is a file in both the subfolders called
filterpipelineprintproc.dll that Windows won't let me delete. I know this
folder was just left over from the update and should be able to be deleted,
but so far my efforts to delete this folder have been fruitless. Can anyone
help? Thanks, ~Adam

"psyadam" <(E-Mail Removed)> wrote in message
news:731B19CD-69E8-4E24-9F50-(E-Mail Removed)
> Over the weekend, after getting an OS update to my Windows XP, a
> folder called f3e2792ea014a7a9c95fd55e has appeared on my C: with two
> subfolders: amd64 and i386. In particular, there is a file in both
> the subfolders called filterpipelineprintproc.dll that Windows won't
> let me delete. I know this folder was just left over from the update
> and should be able to be deleted, but so far my efforts to delete
> this folder have been fruitless. Can anyone help? Thanks, ~Adam

A few of those folders are still "in use" and thus cannot be deleted.
Have you tried deleting from a Cold Start and then Safe Mode? If you
still can't delete it, I'd leave it alone. It's not hurting anything &
not worth the effort to do much to get rid of it..

Twayne`

http://www.microsoft.com/communities...b-c6b75ae0a984

"psyadam" <(E-Mail Removed)> wrote in message
news:731B19CD-69E8-4E24-9F50-(E-Mail Removed)...
: Over the weekend, after getting an OS update to my Windows XP, a folder
: called f3e2792ea014a7a9c95fd55e has appeared on my C: with two subfolders:
: amd64 and i386. In particular, there is a file in both the subfolders
called
: filterpipelineprintproc.dll that Windows won't let me delete. I know this
: folder was just left over from the update and should be able to be
deleted,
: but so far my efforts to delete this folder have been fruitless. Can
anyone
: help? Thanks, ~Adam

On Mon, 17 Aug 2009 06:55:01 -0700, psyadam
<(E-Mail Removed)> wrote:

>Over the weekend, after getting an OS update to my Windows XP, a folder
>called f3e2792ea014a7a9c95fd55e has appeared on my C: with two subfolders:
>amd64 and i386. In particular, there is a file in both the subfolders called
>filterpipelineprintproc.dll that Windows won't let me delete. I know this
>folder was just left over from the update and should be able to be deleted,
>but so far my efforts to delete this folder have been fruitless. Can anyone
>help? Thanks, ~Adam

Try deleting in safe mode .

-------- Original-Nachricht --------

> Over the weekend, after getting an OS update to my Windows XP, a folder
> called f3e2792ea014a7a9c95fd55e has appeared on my C: with two subfolders:
> amd64 and i386. In particular, there is a file in both the subfolders called
> filterpipelineprintproc.dll that Windows won't let me delete. I know this
> folder was just left over from the update and should be able to be deleted,
> but so far my efforts to delete this folder have been fruitless. Can anyone
> help? Thanks, ~Adam

1st try: reboot, then delete
2nd try: reboot in safe mode with admin rights
3rd try: download http://ccollomb.free.fr/unlocker/ and delete

Bernd

On Aug 17, 9:55*am, psyadam <psya...@discussions.microsoft.com> wrote:
> Over the weekend, after getting an OS update to my Windows XP, a folder
> called f3e2792ea014a7a9c95fd55e has appeared on my C: with two subfolders:
> amd64 and i386. *In particular, there is a file in both the subfolders called
> filterpipelineprintproc.dll that Windows won't let me delete. *I know this
> folder was just left over from the update and should be able to be deleted,
> but so far my efforts to delete this folder have been fruitless. *Can anyone
> help? *Thanks, ~Adam

They are leftovers.

Boot in Safe Mode and try to remove the files (sometimes works)

Or try Unlocker:

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

You can uninstall Unlocker when you are done.

For "invalid" folders/filenames where Unlocker does not work:

http://www.purgeie.com/delinv/

Leftover files after .NET Framework 3.5 Service Pack 1 installation
http://www.verboon.info:80/index.php...-installation/

Also see Known Issue #1 in http://support.microsoft.com/kb/951847/en-us
(Last Review: July 17, 2009)
--
~PA Bear, MS MVP
www.banthecheck.com

psyadam wrote:
> Over the weekend, after getting an OS update to my Windows XP, a folder
> called f3e2792ea014a7a9c95fd55e has appeared on my C: with two subfolders:
> amd64 and i386. In particular, there is a file in both the subfolders
> called filterpipelineprintproc.dll that Windows won't let me delete. I
> know this folder was just left over from the update and should be able to
> be deleted, but so far my efforts to delete this folder have been
> fruitless. Can anyone help? Thanks, ~Adam

Thankyou to Tom Willett and Jim for the suggestion of using the Unlocker
program. The Unlocker program was able to delete the folder for me. I did
try to log in as Administrator in Safe Mode first, however even that did not
allow me to delete the folder when I tried that. Anyways, Unlocker worked.
Thanks, guys.

On Aug 17, 8:49*pm, psyadam <psya...@discussions.microsoft.com> wrote:
> Thankyou to Tom Willett and Jim for the suggestion of using the Unlocker
> program. *The Unlocker program was able to delete the folder for me. *I did
> try to log in as Administrator in Safe Mode first, however even that did not
> allow me to delete the folder when I tried that. *Anyways, Unlocker worked. *
> Thanks, guys.

Like I said - Safe Mode sometimes works.

Don't worry Jose I don't think Adam was trying to hurt your ego, I think he
was just giving thanks to the guys that fixed his problem.
After all, he never did say you said safe mode would fix it everytime


"Jose" wrote:

> On Aug 17, 8:49 pm, psyadam <psya...@discussions.microsoft.com> wrote:
> > Thankyou to Tom Willett and Jim for the suggestion of using the Unlocker
> > program. The Unlocker program was able to delete the folder for me. I did
> > try to log in as Administrator in Safe Mode first, however even that did not
> > allow me to delete the folder when I tried that. Anyways, Unlocker worked.
> > Thanks, guys.
>
> Like I said - Safe Mode sometimes works.
>
>