A possible leftover folder after a Windows Update

[The_Hat]

I’m running Windows XP w/SP2.
After a Windows Update installed KB951847 Microsoft .NET Framework 3.5
Service Pack 1 and .NET Framework 3.5 Family Update (KB951847) x86 on my
machine, I found the folder below on another storage drive in my machine and
not the on the primary hard drive and root directory. The main folder has two
subfolders and files as listed:

Folder: ed798b66cbeb3a7b9bde9e55a9e2
Folder: amd64
Files: filterpipelineprintproc.dll
msxpsdrv.cat
msxpsdrv.inf
msxpsinc.gpd
msxpsinc.ppd
mxdwdrv.dll
xpssvcs.dll
Folder: i386
Files: filterpipelineprintproc.dll
msxpsdrv.cat
msxpsdrv.inf
msxpsinc.gpd
msxpsinc.ppd
mxdwdrv.dll
xpssvcs.dll

Since this is only a storage drive, can the folders and files be deleted or
is there a specific procedure for their removal?

[Ottmar Freudenberger]

"The_Hat" <The...@discussions.microsoft.com> schrieb:

> Since this is only a storage drive, can the folders and files be deleted

Yes.

> or is there a specific procedure for their removal?

No.

Bye,
Freudi

[TaurArian]

ed798b66cbeb3a7b9bde9e55a9e2 is a temporary folder which was placed on the HD
with the largest available space.

What I think happens is, the update is downloaded and then extracted into
this temporary folder for installation.

I updated with the full file and I found a similar file and just deleted it
without even thinking about it.

For some reason, it (the update) didn't clean up after itself. Maybe when
the computer rebooted it didn't have access to the storage file for clean up.
Who knows.

--
Disclaimer: The information has been posted "as is" with no warranties or
guarantees and doesn''t give any rights.

[The_Hat]

Thanks to botheTaurArian & Freudi. I deleted the folder and have had no
problems so far.

Taurian, your solution makes a lot of sense because the drive where the
folder was placed does have the most available free space.

Thanks again to the both of you.

[Daryl]

I have the same issue, but it won't let me delete the folder.
"cannot delete filterpipelineprintproc.dll: Access is denied"

[Davide]

Same problem for me.
Simply change permission and delete.
Yes I'm bored about Windows Update but we have choice? We can hope in less
version and better release for the future.

D.

[Dale]

Why is the associated .dll still being held ? This folder cannot be removed
due to the following errror message?

"Cannot delete filterpipelineprintproc.dll: Access is denied"

Also if I attempt to unregister the .dll then I get this message:

---------------------------
RegSvr32
---------------------------
LoadLibrary("filterpipelineprintproc.dll") failed - The specified module
could not be found."

Can you please find a solution for this? I am seeing this at multiple
client's sites and on many workstations.

[Alex]

looks like Microsoft has found the issue as well, it's now documented here:

http://support.microsoft.com/kb/951847/en-us

Today i have worked on a script to automatically detect and remove this
folder after .net installation. I will post the script within the next days
(after completing testing on some machines) on www.verboon.info

[Drake]

I know this seems like a pain, but can anyone offer step by step instructions
to delete these files since I keep getting an error about permission when I
try to manually delete the files.

Thanks!

[Dale]

No one has offered any solution. The folders are building up all over the
word on every server and workstation. All the while scaring the hell out of
a lot of people who would look at such a random string of letters and numbers
for a file name and think - I've been attacked and compromised. Way to go
Microsoft. How many months have we been at it asking for your attention?
Love the customer care and security focus - not!

[Harry Johnston [MVP]]

Dale wrote:

> No one has offered any solution. The folders are building up all over the
> word on every server and workstation. All the while scaring the hell out of
> a lot of people who would look at such a random string of letters and numbers
> for a file name and think - I've been attacked and compromised. Way to go
> Microsoft. How many months have we been at it asking for your attention?
> Love the customer care and security focus - not!

Have you phoned Microsoft Support? Trivial issues (from a technical
perspective) like this one are unlikely to be fixed unless Microsoft get a lot
of phone calls about it.

Harry.

[Dale]

Sorry Harry but you can waste your time and money - I wouldn't be in this
place posting for answers to questions otherwise.

Your attitude about what constitutes important versus trivial is exactly why
the name Microsoft is synonymous with lackadaisical & lackadaisical almost
security and almost reliability. We've posted this months ago but the only
replies from MVP's like yourself come as defensive and not helpful - not
feeling the love nor the synergy of community.

I was incorect in that Alex actually did offer a plausible solution albeit
somewhat obscured in a script on his blog - SubInACL is the tool he used to
gain control. Gotta love that us users have to solve the problems of the
manufacturer because it isn't interested in OS or Patch quality - bah!

[Jon]

> > > > "cannot delete filterpipelineprintproc.dll: Access is denied"- Hide quoted text -
>
> - Show quoted text -

You just need to change the permissions on the folders and files to
Full Control. Instructions to do this are in this Microsoft article:
http://support.microsoft.com/kb/308419#4

[Harry Johnston [MVP]]

Dale wrote:

> Sorry Harry but you can waste your time and money - I wouldn't be in this
> place posting for answers to questions otherwise.

If the update in question is a security update, support from Microsoft is free
of charge.

> Your attitude about what constitutes important versus trivial [...]

Technologically and objectively speaking, this really is a trivial bug. The
left-over folders have no impact whatsoever on the security or performance of
the computer. The problem is strictly cosmetic.

Now, trivial technologically doesn't always mean trivial overall, but it can be
hard to successfully argue a case for this without call volume.

> [...] We've posted this months ago but the only

> replies from MVP's like yourself come as defensive and not helpful - not
> feeling the love nor the synergy of community.

I'm not sure what you expect us to do, exactly. You realise we don't work for
Microsoft, right? We can't fix the bugs, and we don't have a lot of influence
over which bugs get fixed ... that depends mainly on the call volumes.

> I was incorect in that Alex actually did offer a plausible solution albeit
> somewhat obscured in a script on his blog - SubInACL is the tool he used to
> gain control. Gotta love that us users have to solve the problems of the
> manufacturer because it isn't interested in OS or Patch quality - bah!

I think I may have misunderstood your earlier post. Are you wanting
instructions on deleting the folder? A simple search of the knowledge base
would have found this article:

<http://support.microsoft.com/kb/320081>

http://support.microsoft.com/kb/320081

Harry.

[Kris]

Hi, I followed the instructions in the article you linked to and it didn't do
a thing. You can't change the permissions for this particular folder and it's
impossible to remove it.

/Kris

[Harry Johnston [MVP]]

Kris wrote:

> Hi, I followed the instructions in the article you linked to and it didn't do
> a thing. You can't change the permissions for this particular folder and it's
> impossible to remove it.

<http://support.microsoft.com/kb/320081>

http://support.microsoft.com/kb/320081

Note that you may need to reference one or more of the "related topics" shown in
the right-hand margin, particularly on the subject of taking ownership of a
file/folder.

Harry.

[Gary]

To Kris and others who have been unable to delete this type of file:

> Kris wrote:
>
> > Hi, I followed the instructions in the article you linked to and it didn't do
> > a thing. You can't change the permissions for this particular folder and it's
> > impossible to remove it.
>
> <http://support.microsoft.com/kb/320081>

Ever cryptic, Microsoft support pages like this one are almost always very
specific, requiring you to follow every step but rarely CLEARLY OUTLINING
THEM (I'm not yelling here, I'm just highlighting the problem element :)

The FIRST step you must take is to start windows XP in safe mode before
attempting to do anything else with these files.

AFTER you have successfully started XP in safe mode, you must log in as
"Administrator" and then go to the C: directory (or where ever the leftover
folder is located). You then right click on the folder and change ownership
of the entire folder as outlined in the support page. The safe bet is that
the 'administrator' option in the first one in the list that comes up after
right-clicking the folder icon, but make sure to check the 'administrator'
box. This may or may not bring up yet another dialog box requiring you to
check the 'allow' box under 'full control'. Once this is correctly
accomplished, you can delete the folder (which will also delete all of the
files in it and any subfolders).

You do NOT need "to reference ANY of the "related topics" shown in the

right-hand margin, particularly on the subject of taking ownership of a

file/folder." You simply need to be in safe mode and logged in as an
administrator and then follow the steps as outlined.

I don't don't why so many people have such a hard time just laying out the
instructions so anyone, novice or expert, can follow them, but I hope this
helps.

[wrote:@discussions.microsoft.com "Johnny" wrote:]

["Johnny" wrote:]

Hey my name is Johnny;
I some how stumbled on a way to delete filterpiplineprintproc.dll.
1. Click folder with right mouse send to compressed zipped folder.
2. Delete compressed zipped folder.
3. Then send original filterpipelineprintproc.dll folder to recycling bin.
HOPE IT WORKS FOR EVERYONE AS IT DID FOR ME.
GOD BLESS AND HAVE A GOOD DAY!

[rambozo]

All i did was move the folder to my desktop and then deleted it. Only way i
found to get rid of it.

[KaPiche]

I also was having this problem. Today i solved it.

What you have to do:
- Restart your computer en start in safe mode.
- Login als administrator (some have a password, some not -> youre own
dissission)
- go to the foldername.
- right click with the mouse on the folder en go to properties.
- then go to the second tab (security)
- give yourself the full permissions.
- then go to the folder and you can delete it.

[Alex]

I had mentioned this earlier, here's the complete script we used.

http://www.verboon.info/index.php/2009/08/leftover-files-after-net-framework-35-service-pack-1-installation/

[Juan]

It wont let me do anything to the files that are in the same folder as
filterpipelineprintproc.dll.
Any suggestions?

[Juan]

Go into Safe Mode with Administrator rights. Right click on the folder where
filterpipelineprintproc.dll is located. Click on properties. Then on the
SECURITY TAB. Check the tab that enables "you" to do everything to these
files. Press OK. Then delete the folder. Its as simple as that.

[Harry Johnston [MVP]]

Gary wrote:

> You then right click on the folder and change ownership
> of the entire folder as outlined in the support page.

Are we looking at the same support page? The one I referenced provides no
instructions on how to take ownership of a file or folder, which is why I
suggested following the associated topic link - although I've just realized that
the link in question is dead. :-(

For the record, you take ownership of a file (or folder) by right-clicking on
the file (or folder) and selecting Properties. Then you go to the Security tab,
click on Advanced, select the Owner tab, and select your account in the list
under "Change owner to". If it's a folder, you probably want to turn on
"Replace owner on subcontainers and objects". Then press OK.

At that point you should be able to change the permissions, unless there's a
more serious problem such as file system corruption.

HOWEVER ... to complicate matters, the Security tab won't appear in the default
Windows configuration - I'd forgotten about this. The simplest way to work
around this is probably to boot to Safe Mode.

You don't actually need to log in as "Administrator" - any administrative
account will do. If in doubt, however, as to which accounts are administrative,
"Administrator" is probably your best bet.

Harry.

[Chris]

I stumbled across a solution!

You will need to [url=http://support.microsoft.com/kb/308421]take
ownership[/url] of the folder and subfolders/files. You will then be able to
delete the folder as normal. If it tells you that you need special
permissions, push the "yes" button. For some reason if you give yourself
delete permissions through any other means, the computer will "forget" that
you have permission.

This worked on my DELL OEM version of Windows XP SP2. I logged in as the
specaial account called "Administrator"

Hope that helped!

[Barker]

Hey, Dale and others,

Just found this fix on another site. Fast, easy and it actually worked. No BS:

From Brian Egan on www.question-defense.com
August 9th, 2009 at 1:13 pm

(1) Right mouse click on the folder containing filterpipelineprintproc.dll
(e.g. Folder: ed798b66cbeb3a7b9bde9e55a9e2) and choose Properties
(2) Go to the Security tab
(3) Select the"Full Control" button under Allow
(4) Delete the folder

Cheers,
~JKB

[Lee]

[PA Bear [MS-MVP]]

Leftover files after .NET Framework 3.5 Service Pack 1 installation
http://www.verboon.info:80/index.php/2009/08/leftover-files-after-net-framework-35-service-pack-1-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

[Mark]

Here is the solution. Right click on that main folder with the long name
.... click sharing and security ... check share this folder on the network
box ..... give it a name .... apply. Now you can delete the folder and
everything in it.

[mptigert]

You are the man, simplicity never hurt anybody. This totally worked.
everything else was just a bunch of comp jargon that i didn't understand.
It's sad it took this many posts just to get the right one ha. But pat
yourself on the back you made the most sense.

Thanks again
\tony/

[Marc]

I am running Windows XP/SP2 and was able to delete the rouge folder this way:

1. Disable simple file sharing
a. In the Control Panel, Select Folder Options, then select the View Tab
b. Scroll down to the end and uncheck the box next to "Use simple file
sharing (Recommended)"
c. Click Apply, OK, and exit Control Panel.

2. Change permissions of rouge folder
a. Navigate to the ed798b66cbeb3a7b9bde9e55a9e2 folder left behind from
the .NET framework update
b. Right click the folder, select Permissions, then select the Security tab
c. Under the "Allow" column, click the first box for "Full Control". All
the boxes (or at least most of them) will automatically get checked.
d. Click Apply then OK.

3. Drag rouge folder to the Recycle Bin. This should delete without a
problem. I told this solution to a friend and he had to go into the rouge
folder and perform step #2 for both the folders present for some reason, but
the end result was the same. The offending folder got deleted.

Hope this works for you.

[Marc]

I am running Windows XP/SP2 and was able to delete the rouge folder this way:

1. Disable simple file sharing
a. In the Control Panel, Select Folder Options, then select the View Tab
b. Scroll down to the end and uncheck the box next to "Use simple file
sharing (Recommended)"
c. Click Apply, OK, and exit Control Panel.

2. Change permissions of rouge folder
a. Navigate to the ed798b66cbeb3a7b9bde9e55a9e2 folder left behind from
the .NET framework update
b. Right click the folder, select Permissions, then select the Security tab
c. Under the "Allow" column, click the first box for "Full Control". All
the boxes (or at least most of them) will automatically get checked.
d. Click Apply then OK.

3. Drag rouge folder to the Recycle Bin. This should delete without a
problem. I told this solution to a friend and he had to go into the rouge
folder and perform step #2 for both the folders present for some reason, but
the end result was the same. The offending folder got deleted.

Hope this works for you.

[Mihajlo]

"Marc" wrote:

Thank you so much Mark for explainin step by step how to do it.

[Harry Johnston [MVP]]

Mark wrote:

The catch to this, I think, is that you have to turn on network sharing first in
order to do it, thereby lowering your overall security ... particularly if you
don't know how to set it up properly.

Harry.

[PA Bear [MS MVP]]

[You have rouge folders?]

[David]

I also had the same problem and was able to delete the folder by editing the
permissions, giving my admin account full access and removing all other roles.

"Davide" wrote:

> Same problem for me.
> Simply change permission and delete.
> Yes I'm bored about Windows Update but we have choice? We can hope in less
> version and better release for the future.
>
> D.
>
>
>
> "Daryl" wrote:
>
> > I have the same issue, but it won't let me delete the folder.

> > "cannot delete filterpipelineprintproc.dll: Access is denied"
> >

[sa_philip]

Jonny, your solution didn't work.
Marc, Your solution worked perfectly! Thanks.
Sheila

[Micha]

Johnny, when I zip a folder, it creates the zipped folder in addition to the
original. So the original remains unzipped and unable to be deleted.

Marc, I don't have an option for "Use simple file
sharing (Recommended)" and I am using XP SP2 as well...

So I still have no idea how to remove this stubborn folder!!!

[janwm]

There is another way which I found on the net and which is, I guess,
quite simple. Just drop and drag these files (or whole subfolders)
from the Explorer into SDSpybot's Secure Shredder (Advanced Mode -
Tools) and remove them. After that you can delete the leftover folder.

[Donald]

Yes, this solution works well. Thanks Marc.

[mrspar]

SDSpybot's Secure Shredder worked like a charm--thank you.

[stulpa]

You can install cygwin, which is a linux shell emulator for windows... I
deleted the folder and files by changing the permissions from a cygwin shell.

[Xue@discussions.microsoft.com James Xue]

I just do it as Marc's suggest,I work.thx.

[okirishchik]

"Mark" wrote:

Finally something that worked! I tried everything here with nothing. This
stupid file was dumped on my external hard drive and it bugged me to see it
there. Harmless or not, I DONT WANT IT! And thankfully this simple method
worked for me. Thank you

[Tina]

Thank you for the help Marc! It worked perfectly!

"Marc" wrote:

> I am running Windows XP/SP2 and was able to delete the rouge folder this...

[superniku]

It really works, thx very much
--
n

[Steve]

Even simpler way to delete it is to create a new folder and drag the
offending 'ed798b66cbeb3a7b9bde9e55a9e2' folder into it. Thus any permissions
that it is inheriting will be now be parented by the folder you created (so
you will have read/write permissions on it)

then just delete the new folder.

[wega51]

"Mark" wrote:

Brilliant! Works also on XP home edition.

Thanks, wega51.

[Lyngengr]

There is an easy way to delete this directory. You must be logged in as an
administrator to do this. Select the folder with a right-mouse click, and
then select the properties menu item (last one in the list). Click on the
Security tab (third one), select the Administrators group/user name, and then
in the permissions box click on "Full Control". Select the Apply button and
exit. Then you can delete the entire "ed798b66cbeb3a7b9bde9e55a9e2"
directory and subfolders/files.

[phoinix]

thank you this works perfectly... i just had to remove the 2 subfolders
first... and then the main...

[Todd-1]

The easiest way to delete anything that Windows won't let you delete is to
boot a different OS (e.g. GNU/Linux) from a live CD or flash drive and then
delete the file from there.

"Dale" wrote:

[brussel]

I have the same problem as Micha. Please tell me how I can delete this folder.

"Micha" wrote:
>Marc, I don't have an option for "Use simple file
>sharing (Recommended)" and I am using XP SP2 as well...

>So I still have no idea how to remove this stubborn folder!!!

[darrincates]

Thanks Marc! - This worked for me too!

[aman]

Thanks Marc!!! Your solution worked perfectly, thankssss!!!

[HLL]

Just follow rambozo's (in page 2 of this thread) two steps which is the
easiest way but has been overlooked. I had the same problem as yours
that I cannot see the security tab therefore I cannot disable the
"simple file sharing" in my XP home edition. Most of the people in this
thread does not address this. But anyway rambozo's method works! i.e.
Just drag the folder to the desktop and delete it from there.

--
HLL
Posted via http://www.vistaheads.com

[Dezo]

Thanks worked great so simple feel newbish for not thinking of it lol...tried
all the others first with no luck!!!

[Martin@discussions.microsoft.com Nick Martin]

I found the most simplest of solutions, as none of the above worked.

My computer has been crashing and failing to load for a few weeks now and
starting to become a real pain..

I just went into the sharing properties of the folder, and allowed it to be
viewed and altered by third parties (other users) and then deleted it. Job
done!

Hope this works.

[Patrick]

' This is a sort of generic solution.
' Search all fixed disk drives (WHERE DriveType=3) for folders that
' have the i386\mxdwdrv.dll and amd64\mxdwdrv.dll, and delete them

Dim objFSO : Set objFSO = CreateObject("Scripting.FileSystemObject")
Dim objWMI : Set objWMI = GetObject("winmgmts:\\.\root\cimv2")
Dim colDrives : Set colDrives = objWMI.ExecQuery("SELECT * from
Win32_LogicalDisk WHERE DriveType='3'")
Dim objRoot, objFolder

For Each Drive in colDrives
Set objRoot = objFSO.GetFolder(Drive.Name & "\")

For Each objFolder in objRoot.Subfolders
If objFSO.FileExists(objFolder.Path & "\i386\mxdwdrv.dll") And
objFSO.FileExists(objFolder.Path & "\amd64\mxdwdrv.dll") Then
WScript.Echo "Purging folder: " & objFolder.Path
objFolder.Delete
End If
Next
Next

[McMenamin@discussions.microsoft.com Greg McMenamin]

Beautiful solution! Jackpot!

[deanv]

Perfect Nick!
Thank you

[Colin]

Hi All,

Just right click on the folder and make sure the "read only" box is
completely unchecked and apply it to all subfolders and files. Then you can
simply delete the folder as usual.

Cheers,
Colin

[John]

thanks, Nick. works for me.

[Kobi]

Thanks Nick, you're solution worked for me.

I think the reason that people don't see the option about 'simple file
sharing' is because that option doesn't exist in Windows XP home, only in XP
Pro.

[sns]

I found a very simple way too!!!!

I created a new folder in the folder where the ed798b66cbeb3a7b9bde9e55a9e2
folder was.

I put in this folder (i named it caca but any name must work) the
ed798b66cbeb3a7b9bde9e55a9e2 folder.

then selected the caca folder properties and unticked the "read only" box

...and i cancelled normally the caca folder with all the annoying files init!

[Stefaan]

Nick's solution is the only one that works !

Thanks Nick !

[Neal]

[Neal]

Great, Nick, worked for me too!

[Leonhard]

Thanks Marc, After a couple of weeks trying to delete the folder I was
worried about it, but your solution did the job perfectly.

Thanks again!

"Marc" wrote:

> I am running Windows XP/SP2 and was able to delete the rouge folder this way:
>
> 1. Disable simple file sharing
> a. In the Control Panel, Select Folder Options, then select the View Tab

> b. Scroll down to the end and uncheck the box next to "Use simple file
> sharing (Recommended)"

[BwC]

you guys are great...thanks for this...that folder has been annoying
the heck out of me for months :-)

[MrSolo]

[cajun]

Thank you for this solution. It worked for me when nothing else did! I had
two such files, on in my C:\Programs Files folder, and one on my second
internal hard drive. They were installed on two different dates. I deleted
the one under the C:\Program Files in Safe Mode, but it wouldn't let me
delete the one on my second internal drive. I was going to try the Spybot
trick posted here of dragging the folder to the Secure Shredder, but I don't
have a Secure Shredder under Tools in Advanced Mode. I'm running XP Home and
also don't have an option to "remove simple file sharing."

[Castor]

I tried all suggestions and it's yours which help me to solve this problem.
At least !
Nick, you're the best, congratulations !!!

Castor

[TonyaMae]

"Steve" wrote:

> Even simpler way to delete it is to create a new folder and drag the
> offending 'ed798b66cbeb3a7b9bde9e55a9e2' folder into it. Thus any permissions
> that it is inheriting will be now be parented by the folder you created (so
> you will have read/write permissions on it)
>
> then just delete the new folder.

Steve, You Rock!!!
I run the XP Home and it took me having to make folders inside the offending
folder, then making another folder OUTside the offending folder, unchecking
the read boxes the whole way, and only THEN after moving it to the new folder
did it let me delete it! man! talk about being a pain in the neck!
actually that folder needed to PAY! as it ate one of my folders that held 2
months worth of work I did on a website. (accidently dropped it in the folder
when moving it to another location)

[TMon]

Thank you for the great solution Nick Martin.

Btw. i can't believe microsoft is such a lame, leaving unused garbage,
what's more, protected on one's HDD.
Weird. Not even a patch released to clean up the mess.

Dear Microsoft,

Don't do that again.

[Chris]

OK I've got one for you. I deleted the file but not it is stuck in my
recycle bin and not visible. NOTE: I have norton utilities installed and
managing my Recycle bin as well.

I've tried going into safe mode, but no luck. Still can't see the file.
Any ideas????

[knightofmathematics]

Well, your solution almost worked. I had to visit the folder and delete its
two subfolders one by one. I still had problems deleting the original folder
and here's how I managed that:

1. I opened the Windows Task Manager and a command line window.
2. In the Task Manager, I killed all processes with the image name
"explorer.exe". This causes the taskbar and desktop icons to disappear, but
this isn't a problem (see step 5).
3. I then went to the command line window and gave the command:

rmdir/s <name_of_folder>

4. The folder was deleted!
5. I then gave the command explorer in the command line window to get the
desktop and icons back.

"Marc" wrote:

> I am running Windows XP/SP2 and was able to delete the rouge folder this way:
>
> 1. Disable simple file sharing
> a. In the Control Panel, Select Folder Options, then select the View Tab

> b. Scroll down to the end and uncheck the box next to "Use simple file
> sharing (Recommended)"

[Chris]

. . . but now it is stuck . . .

[coco]

After reading a lot of info on this problem, scripts required, etc. etc.,
Nick's solution worked perfectly. Thanks for thinking out of the box Nick!

[Graeme]

Yes Nick!
That's the one!
5th "method" I've tried and it went off without a hitch.
Thanks Nick!

[maelbe]

Thank you!
That folder has been driving me crazy. I did not know what it was, how I had
gotten it or how to have it removed. Nothing worked - until your excellent
advice. Sometimes the simplest solutions are the best. Just creat a new
folder, drop the .dll files and its folder in it and delete! =)

[Greginwv]

[Greginwv]

Your advice worked the best. Thanks for the help! :-)

[Allan Warner]

There was only one other step (apart from allowing full access to
administrators group) I had to do and that was to find the process that had
hold of the filterpipelineprintproc.dll.

I use processexplorer (from sysinternals (now part of MS)), its by Mark
Russionvich. Its free and really good, it is an advanced replacement for task
manager. But it does a load more and it can also find handles for files.
http://technet.microsoft.com/en-us/sysinternals/bb896653.aspx

The Printer Spooler was the process that had hold of the
filterpipelineprintproc.dll file, once I had stopped this and assigned the
full control permissions to the root folder and children I could delete the
folders.

"Lyngengr" wrote:

> There is an easy way to delete this directory. You must be logged in as an
> administrator to do this. Select the folder with a right-mouse click, and
> then select the properties menu item (last one in the list). Click on the
> Security tab (third one), select the Administrators group/user name, and then
> in the permissions box click on "Full Control". Select the Apply button and
> exit. Then you can delete the entire "ed798b66cbeb3a7b9bde9e55a9e2"
> directory and subfolders/files.

[Navlim]

Thank you Nick,

none of the above given solutions worked for me, but yours did.

thanks a bunch.

[drestar]

If you have XP Home...This WORKS!!!!!

Thanks sns!!!!!!!!!!!

[AndrewMcD999]

Other way of doing this that worked for me -just drag the folder to 'Shared
Documents' folder and delete it in there. This worked when Spybot shredder
and permissions changes didn't,

A

"Mark" wrote:

> Here is the solution. Right click on that main folder with the long name
> .... click sharing and security ... check share this folder on the network
> box ..... give it a name .... apply. Now you can delete the folder and
> everything in it.

[ryandrews]

Thanks Marc, this worked for me!
That file's beein pi**ing me off for ages!

Ryan

"Marc" wrote:

> I am running Windows XP/SP2 and was able to delete the rouge folder this way:
>
> 1. Disable simple file sharing
> a. In the Control Panel, Select Folder Options, then select the View Tab

> b. Scroll down to the end and uncheck the box next to "Use simple file
> sharing (Recommended)"

[Thomas]

Hi Nick,

Worked like a charm for me, well done!

Thomas

[BM]

Thank you Marc for the details. It worked for me.

"Marc" wrote:

> "Juan" wrote:
>
> > It wont let me do anything to the files that are in the same folder as
> > filterpipelineprintproc.dll.
> > Any suggestions?
> >

[ericp3371]

This is leftover from .net sp1 update. It can be deleted. You may need to
modify permissions to give yourself full control of the dirs/files before you
can delete them. In some cases, it still won't let you as it'll tell you
that you're not the original owner, and/or the original owner is unknown. It
that's the case, and you can't delete no matter what you do, forget trying
all the difficult and tedious suggestions in here, just boot into knoppix
(google "knoppix", it's a linux os that runs off of a cd... you can download
and burn it onto a cd and then boot off that cd). Once you're booted into
knoppix, just delete the dirs/files from there (navigation and interface is
pretty similar to Windows, so you should be able to figure out your way
around no problem). Once those files/dirs are deleted, reboot back into
Windows.

Cheers!

[Harry Johnston [MVP]]

On 2010-01-21 3:04 p.m., ericp3371 wrote:

> [If]

> that's the case, and you can't delete no matter what you do, forget trying
> all the difficult and tedious suggestions in here, just boot into knoppix
> (google "knoppix", it's a linux os that runs off of a cd... you can download
> and burn it onto a cd and then boot off that cd). Once you're booted into
> knoppix, just delete the dirs/files from there (navigation and interface is
> pretty similar to Windows, so you should be able to figure out your way
> around no problem). Once those files/dirs are deleted, reboot back into
> Windows.

I wouldn't recommend this procedure. From the Knoppix FAQ:

Q: How can I write data on NTFS partitions?

A: Knoppix 5 supports write access for NTFS partitions using libntfs and fuse.
While preliminary results show generally good stability and a low likelihood of
data corruption on the NTFS partition, these libraries are still beta and there
is risk of data loss and disk corruption (back up your data first). Knoppix (and
the Linux kernel) can read NTFS partitions just fine, the danger is only present
when attempting to write to it.

Harry.

--
"I wish that, just once, some terrorist would try something that you can only
foil by upgrading the passengers to first class and giving them free drinks."
- Bruce Schneier
http://www.schneier.com/blog/archives/2009/12/separating_expl.html

[Holmesy ilson uk]

And five months down the line your solution is the only one that worked for
me, Cheers me dears!
--
Thanks for your time and help, Holmesy.

[Carl]

I've stumbled across the perhaps easiest way of resolving this. I read all of
your post, and came to the conclusion that this was indeed a Windows file
permission issue, that then (of course) would indeed also be fixed by the
disable easy file sharing process that are mentioned several times in this
post. However. I like the good things about Easy file sharing, and although I
could (presumably) quite easily disable and re-enable after getting rid of
the folder, I found a better solution.

TLDR:
Just do like this:

Start menu / Run / cmd.exe

cacls.exe C:\stuckfoldername /T /G yourwinaccountname:F

Go ahead.

This will give your account the F(ull) permissions over the folder
(something obviously got messed up with these permissions doing that
particular update) and you will then be able to delete the folder.

[apophis]

[apophis]

"Carl" wrote:

absolutely kicking...got me out of trouble...thanks very much

[Crouch@discussions.microsoft.com Eric Crouch]

Thanks Nick - this is the way to go with XP Home

[Sunny]

Thank you so much!! We tried all the other ways of doing it posted here and
elsewhere and yours worked straight away. Easy, brilliant. You are a star!

[Muaddib]

that works perfectly, thanks.

"Nick Martin" wrote:

> I found the most simplest of solutions, as none of the above worked.
>
> My computer has been crashing and failing to load for a few weeks now and
> starting to become a real pain..
>
> I just went into the sharing properties of the folder, and allowed it to be
> viewed and altered by third parties (other users) and then deleted it. Job
> done!
>
> Hope this works.
>
>

[Mj]

This worked for me, anyone else having this problem and none of the above
works, use Nick's suggestion.