1. Welcome Guest! In order to create a new topic or reply to an existing one, you must register first. It is easy and free. Click here to sign up now!.
    Dismiss Notice

A possible leftover folder after a Windows Update

Discussion in 'Windows Update' started by The_Hat, Feb 3, 2009.

  1. The_Hat

    The_Hat Guest

    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?
     
  2. "The_Hat" <The_Hat@discussions.microsoft.com> schrieb:
    <!--coloro:blue--><span style="color:blue <!--/coloro-->
    > Since this is only a storage drive, can the folders and files be deleted<!--colorc--><!--/colorc-->

    Yes.
    <!--coloro:blue--><span style="color:blue <!--/coloro-->
    > or is there a specific procedure for their removal?<!--colorc--><!--/colorc-->

    No.

    Bye,
    Freudi
     
  3. TaurArian

    TaurArian Guest

    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:
    <!--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-->
     
  4. The_Hat

    The_Hat Guest

    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.

    "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-->
     
  5. Daryl

    Daryl Guest

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

    Davide Guest

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

    Dale Guest

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

    Alex Guest

  9. Drake

    Drake Guest

  10. Dale

    Dale Guest

    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!

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

    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.

    <!--coloro:blue--><span style="color:blue <!--/coloro-->
    >
    > "Drake" wrote:
    > <!--coloro:green--><span style="color:green <!--/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:darkred--><span style="color:darkred <!--/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:
    >>>
    >>>> 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-->
     
  12. Dale

    Dale Guest

    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!

    "Harry Johnston [MVP]" wrote:
    <!--coloro:blue--><span style="color:blue <!--/coloro-->
    > Dale wrote:
    > <!--coloro:green--><span style="color:green <!--/coloro-->
    > > 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!<!--colorc--><!--/colorc-->
    >
    > 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.
    >
    > <!--coloro:green--><span style="color:green <!--/coloro-->
    > >
    > > "Drake" wrote:
    > > <!--coloro:darkred--><span style="color:darkred <!--/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:
    > >>
    > >>> 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:
    > >>>
    > >>>> 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-->
     
  13. Jon

    Jon Guest

    On Aug 7, 3:16 am, Drake <Dr...@discussions.microsoft.com> 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:<!--colorc--><!--/colorc-->
    ><!--coloro:green--><span style="color:green <!--/coloro-->
    > ><!--colorc--><!--/colorc-->
    ><!--coloro:green--><span style="color:green <!--/coloro-->
    > > 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) onwww.verboon.info<!--colorc--><!--/colorc-->
    ><!--coloro:green--><span style="color:green <!--/coloro-->
    > > "Davide" wrote:<!--colorc--><!--/colorc-->
    ><!--coloro:green--><span style="color:green <!--/coloro--><!--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.<!--colorc--><!--/colorc--><!--colorc--><!--/colorc-->
    ><!--coloro:green--><span style="color:green <!--/coloro--><!--coloro:darkred--><span style="color:darkred <!--/coloro-->
    > > > D.<!--colorc--><!--/colorc--><!--colorc--><!--/colorc-->
    ><!--coloro:green--><span style="color:green <!--/coloro--><!--coloro:darkred--><span style="color:darkred <!--/coloro-->
    > > > "Daryl" wrote:<!--colorc--><!--/colorc--><!--colorc--><!--/colorc-->
    ><!--coloro:green--><span style="color:green <!--/coloro--><!--coloro:darkred--><span style="color:darkred <!--/coloro-->
    > > > > I have the same issue, but it won't let me delete the folder.
    > > > > "cannot delete filterpipelineprintproc.dll: Access is denied"- Hide quoted text -<!--colorc--><!--/colorc--><!--colorc--><!--/colorc-->
    >
    > - Show quoted text -<!--colorc--><!--/colorc-->

    You just need to change the permissions on the folders and files to
    Full Control. Instructions to do this are in this Microsoft article:
     
  14. 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.<!--colorc--><!--/colorc-->

    If the update in question is a security update, support from Microsoft is free
    of charge.
    <!--coloro:blue--><span style="color:blue <!--/coloro-->
    > Your attitude about what constitutes important versus trivial [...]<!--colorc--><!--/colorc-->

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

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

    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>



    Harry.

    <!--coloro:blue--><span style="color:blue <!--/coloro-->
    >
    > "Harry Johnston [MVP]" wrote:
    > <!--coloro:green--><span style="color:green <!--/coloro-->
    >> Dale wrote:
    >><!--coloro:darkred--><span style="color:darkred <!--/coloro-->
    >>> 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!<!--colorc--><!--/colorc-->
    >> 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.
    >>
    >><!--coloro:darkred--><span style="color:darkred <!--/coloro-->
    >>> "Drake" wrote:
    >>>
    >>>> 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:
    >>>>
    >>>>> 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:
    >>>>>
    >>>>>> 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-->
     
  15. Kris

    Kris Guest

    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

    "Jon" wrote:
    <!--coloro:blue--><span style="color:blue <!--/coloro-->
    > On Aug 7, 3:16 am, Drake <Dr...@discussions.microsoft.com> wrote:<!--coloro:green--><span style="color:green <!--/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:darkred--><span style="color:darkred <!--/coloro-->
    > > > looks like Microsoft has found the issue as well, it's now documented here:<!--colorc--><!--/colorc-->
    > ><!--coloro:darkred--><span style="color:darkred <!--/coloro-->
    > > ><!--colorc--><!--/colorc-->
    > ><!--coloro:darkred--><span style="color:darkred <!--/coloro-->
    > > > 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) onwww.verboon.info<!--colorc--><!--/colorc-->
    > ><!--coloro:darkred--><span style="color:darkred <!--/coloro-->
    > > > "Davide" wrote:<!--colorc--><!--/colorc-->
    > ><!--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.<!--colorc--><!--/colorc-->
    > ><!--coloro:darkred--><span style="color:darkred <!--/coloro-->
    > > > > D.<!--colorc--><!--/colorc-->
    > ><!--coloro:darkred--><span style="color:darkred <!--/coloro-->
    > > > > "Daryl" wrote:<!--colorc--><!--/colorc-->
    > ><!--coloro:darkred--><span style="color:darkred <!--/coloro-->
    > > > > > I have the same issue, but it won't let me delete the folder.
    > > > > > "cannot delete filterpipelineprintproc.dll: Access is denied"- Hide quoted text -<!--colorc--><!--/colorc-->
    > >
    > > - Show quoted text -<!--colorc--><!--/colorc-->
    >
    > You just need to change the permissions on the folders and files to
    > Full Control. Instructions to do this are in this Microsoft article:
    >

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



    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.
    <!--coloro:blue--><span style="color:blue <!--/coloro-->
    >
    > /Kris
    >
    > "Jon" wrote:
    > <!--coloro:green--><span style="color:green <!--/coloro-->
    >> On Aug 7, 3:16 am, Drake <Dr...@discussions.microsoft.com> wrote:<!--coloro:darkred--><span style="color:darkred <!--/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:
    >>>> 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) onwww.verboon.info
    >>>> "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"- Hide quoted text -
    >>> - Show quoted text -<!--colorc--><!--/colorc-->
    >> You just need to change the permissions on the folders and files to
    >> Full Control. Instructions to do this are in this Microsoft article:
    >>

    >><!--colorc--><!--/colorc--><!--colorc--><!--/colorc-->
     
  17. Gary

    Gary Guest

    To Kris and others who have been unable to delete this type of file:
    <!--coloro:blue--><span style="color:blue <!--/coloro-->
    > Kris wrote:
    > <!--coloro:green--><span style="color:green <!--/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 [​IMG]

    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.
     
  18. "Dale" wrote:
    <!--coloro:blue--><span style="color:blue <!--/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:green--><span style="color:green <!--/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:
    > > <!--coloro:darkred--><span style="color:darkred <!--/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--><!--colorc--><!--/colorc--><!--colorc--><!--/colorc-->
     
  19. 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:blue--><span style="color:blue <!--/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:green--><span style="color:green <!--/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:
    > > <!--coloro:darkred--><span style="color:darkred <!--/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--><!--colorc--><!--/colorc--><!--colorc--><!--/colorc-->
     
  20. rambozo

    rambozo Guest

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

Share This Page