A possible leftover folder after a Windows Update

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.

 

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




"The_Hat" wrote:
<!--coloro:blue--><span style="color:blue <!--/coloro-->
> 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?
> <!--colorc--><!--/colorc-->

 

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

""Johnny" wrote:" wrote:
<!--coloro:blue--><span style="color:blue <!--/coloro-->
> 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!
>
> "Dale" wrote:
> <!--coloro:green--><span style="color:green <!--/coloro-->
> > 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.
> >
> > "TaurArian" wrote:
> > <!--coloro:darkred--><span style="color:darkred <!--/coloro-->
> > > 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" wrote:
> > >
> > > > 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?
> > > > <!--colorc--><!--/colorc--><!--colorc--><!--/colorc--><!--colorc--><!--/colorc-->

 

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.

"Drake" wrote:
<!--coloro:blue--><span style="color:blue <!--/coloro-->
> 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!
>
> "Alex" wrote:
> <!--coloro:green--><span style="color:green <!--/coloro-->
> > looks like Microsoft has found the issue as well, it's now documented here:
> >
> >
> >
> > 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
> >
> >
> > "Davide" wrote:
> > <!--coloro:darkred--><span style="color:darkred <!--/coloro-->
> > > 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"
> > > > <!--colorc--><!--/colorc--><!--colorc--><!--/colorc--><!--colorc--><!--/colorc-->

 

Gary wrote:
<!--coloro:blue--><span style="color:blue <!--/coloro-->
> You then right click on the folder and change ownership
> of the entire folder as outlined in the support page. <!--colorc--><!--/colorc-->

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.

Gary wrote:
<!--coloro:blue--><span style="color:blue <!--/coloro-->
> To Kris and others who have been unable to delete this type of file:
> <!--coloro:green--><span style="color:green <!--/coloro-->
>> Kris wrote:
>><!--coloro:darkred--><span style="color:darkred <!--/coloro-->
>>> 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.<!--colorc--><!--/colorc-->
>> <http://support.microsoft.com/kb/320081><!--colorc--><!--/colorc-->
>
>
> 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.<!--colorc--><!--/colorc-->

 

I stumbled across a solution!

You will need to 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!

"The_Hat" wrote:
<!--coloro:blue--><span style="color:blue <!--/coloro-->
> 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?
> <!--colorc--><!--/colorc-->

 

Hey, Dale and others,

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

From Brian Egan on
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


"Dale" wrote:
<!--coloro:blue--><span style="color:blue <!--/coloro-->
> 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!<!--colorc--><!--/colorc-->

 

""Johnny" wrote:" wrote:
<!--coloro:blue--><span style="color:blue <!--/coloro-->
> 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!
>
> "Dale" wrote:
> <!--coloro:green--><span style="color:green <!--/coloro-->
> > 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.
> >
> > "TaurArian" wrote:
> > <!--coloro:darkred--><span style="color:darkred <!--/coloro-->
> > > 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" wrote:
> > >
> > > > 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?
> > > > <!--colorc--><!--/colorc--><!--colorc--><!--/colorc--><!--colorc--><!--/colorc-->

 

Leftover files after .NET Framework 3.5 Service Pack 1 installation


Also see Known Issue #1 in
(Last Review: July 17, 2009)
--
~PA Bear, MS MVP

 

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.

 

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/

"Mark" wrote:
<!--coloro:blue--><span style="color:blue <!--/coloro-->
> 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.<!--colorc--><!--/colorc-->

 

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.


"Juan" wrote:
<!--coloro:blue--><span style="color:blue <!--/coloro-->
> It wont let me do anything to the files that are in the same folder as
> filterpipelineprintproc.dll.
> Any suggestions?
>
> ""Johnny" wrote:" wrote:
> <!--coloro:green--><span style="color:green <!--/coloro-->
> > 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!
> >
> > "Dale" wrote:
> > <!--coloro:darkred--><span style="color:darkred <!--/coloro-->
> > > 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.
> > >
> > > "TaurArian" wrote:
> > >
> > > > 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" wrote:
> > > >
> > > > > 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?
> > > > > <!--colorc--><!--/colorc--><!--colorc--><!--/colorc--><!--colorc--><!--/colorc-->

 

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.

"Drake" wrote:
<!--coloro:blue--><span style="color:blue <!--/coloro-->
> 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!
>
> "Alex" wrote:
> <!--coloro:green--><span style="color:green <!--/coloro-->
> > looks like Microsoft has found the issue as well, it's now documented here:
> >
> >
> >
> > 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
> >
> >
> > "Davide" wrote:
> > <!--coloro:darkred--><span style="color:darkred <!--/coloro-->
> > > 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"
> > > > <!--colorc--><!--/colorc--><!--colorc--><!--/colorc--><!--colorc--><!--/colorc-->

 

"Marc" wrote:
<!--coloro:blue--><span style="color:blue <!--/coloro-->
> 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.
>
>
> "Juan" wrote:
> <!--coloro:green--><span style="color:green <!--/coloro-->
> > It wont let me do anything to the files that are in the same folder as
> > filterpipelineprintproc.dll.
> > Any suggestions?
> >
> > ""Johnny" wrote:" wrote:
> > <!--coloro:darkred--><span style="color:darkred <!--/coloro-->
> > > 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!
> > >
> > > "Dale" wrote:
> > >
> > > > 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.
> > > >
> > > > "TaurArian" wrote:
> > > >
> > > > > 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" wrote:
> > > > >
> > > > > > 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?
> > > > > > <!--colorc--><!--/colorc--><!--colorc--><!--/colorc--><!--colorc--><!--/colorc-->

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

 

Mark wrote:
<!--coloro:blue--><span style="color:blue <!--/coloro-->
> 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.<!--colorc--><!--/colorc-->

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.

 

[You have rouge folders?]

Marc wrote:<!--coloro:blue--><span style="color:blue <!--/coloro-->
> 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.
>
>
> "Juan" wrote:
><!--coloro:green--><span style="color:green <!--/coloro-->
>> It wont let me do anything to the files that are in the same folder as
>> filterpipelineprintproc.dll.
>> Any suggestions?
>>
>> ""Johnny" wrote:" wrote:
>><!--coloro:darkred--><span style="color:darkred <!--/coloro-->
>>> 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!
>>>
>>> "Dale" wrote:
>>>
>>>> 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.
>>>>
>>>> "TaurArian" wrote:
>>>>
>>>>> 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" wrote:
>>>>>
>>>>>> 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? <!--colorc--><!--/colorc--><!--colorc--><!--/colorc--><!--colorc--><!--/colorc-->

 

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:
<!--coloro:blue--><span style="color:blue <!--/coloro-->
> 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:
> <!--coloro:green--><span style="color:green <!--/coloro-->
> > I have the same issue, but it won't let me delete the folder.
> > "cannot delete filterpipelineprintproc.dll: Access is denied"
> > <!--colorc--><!--/colorc--><!--colorc--><!--/colorc-->

 

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

"Marc" wrote:
<!--coloro:blue--><span style="color:blue <!--/coloro-->
> 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.
>
>
> "Juan" wrote:
> <!--coloro:green--><span style="color:green <!--/coloro-->
> > It wont let me do anything to the files that are in the same folder as
> > filterpipelineprintproc.dll.
> > Any suggestions?
> >
> > ""Johnny" wrote:" wrote:
> > <!--coloro:darkred--><span style="color:darkred <!--/coloro-->
> > > 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!
> > >
> > > "Dale" wrote:
> > >
> > > > 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.
> > > >
> > > > "TaurArian" wrote:
> > > >
> > > > > 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" wrote:
> > > > >
> > > > > > 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?
> > > > > > <!--colorc--><!--/colorc--><!--colorc--><!--/colorc--><!--colorc--><!--/colorc-->

 

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!!!

 

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.