A possible leftover folder after a Windows Update

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?

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

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

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

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


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

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:
>
> 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
>
>
> "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"
> > >

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:

> 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:
> >
> > 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
> >
> >
> > "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"
> > > >

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.


>
> "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:
>>>
>>> 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
>>>
>>>
>>> "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"
>>>>>

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:

> 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.
>
>
> >
> > "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:
> >>>
> >>> 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
> >>>
> >>>
> >>> "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"
> >>>>>
>

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.


>
> "Harry Johnston [MVP]" wrote:
>
>> 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.
>>
>>
>>> "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:
>>>>>
>>>>> 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
>>>>>
>>>>>
>>>>> "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"
>>>>>>>