Mailbag: Temporary files can be left behind after running .NET Framework 3.0 or 3.5 setup

re: Mailbag: Temporary files can be left behind after running .NET Framework 3.0 or 3.5 setup

TH — Tue, 30 Nov 2010 08:11:42 GMT

Hi astebner, thank you very much for your assistance... That is the plan then, to run the XPS installer beforehand :)

re: Mailbag: Temporary files can be left behind after running .NET Framework 3.0 or 3.5 setup

Aaron Stebner — Mon, 29 Nov 2010 16:37:51 GMT

Hi TH - If you want to eliminate these temporary files, I think the cleanest option would be for you to run the XPS installer before installing the .NET Framework 3.5 SP1. If that isn't an option, I believe it would be safe to remove those registry keys in addition to removing the temporary files.

re: Mailbag: Temporary files can be left behind after running .NET Framework 3.0 or 3.5 setup

TH — Mon, 29 Nov 2010 11:55:59 GMT

Hi astebner,

So the folder is always randomly named... in one case it is:

D:\09cb04b43b693cd9fa19

then when searching through the reistry this location is referenced in the following keys:

HKLM\Software\Microsoft\Updates\Windows Server 2003\SP4\KB954550-v5\Filelist\0

The key is:Location

The value is: d:\09cb04b43b693cd9fa19\update\..\amd64

HKLM\Software\Microsoft\Updates\Windows Server 2003\SP4\KB954550-v5\Filelist\1

The key is:Location

The value is: d:\09cb04b43b693cd9fa19\update\..\amd64

HKLM\Software\Microsoft\Updates\Windows Server 2003\SP4\KB954550-v5\Filelist\10

The key is:Location

The value is: d:\09cb04b43b693cd9fa19\update\..\i386

HKLM\Software\Microsoft\Updates\Windows Server 2003\SP4\KB954550-v5\Filelist\11

The key is:Location

The value is: d:\09cb04b43b693cd9fa19\update\..\i386

HKLM\Software\Microsoft\Updates\Windows Server 2003\SP4\KB954550-v5\Filelist\12

The key is:Location

The value is: d:\09cb04b43b693cd9fa19\update\..\i386

HKLM\Software\Microsoft\Updates\Windows Server 2003\SP4\KB954550-v5\Filelist\13

The key is:Location

The value is: d:\09cb04b43b693cd9fa19\update\..\i386

HKLM\Software\Microsoft\Updates\Windows Server 2003\SP4\KB954550-v5\Filelist\14

The key is:Location

The value is: d:\09cb04b43b693cd9fa19\update\..\i386

HKLM\Software\Microsoft\Updates\Windows Server 2003\SP4\KB954550-v5\Filelist\2

The key is:Location

The value is: d:\09cb04b43b693cd9fa19\update\..\amd64

HKLM\Software\Microsoft\Updates\Windows Server 2003\SP4\KB954550-v5\Filelist\3

The key is:Location

The value is: d:\09cb04b43b693cd9fa19\update\..\amd64

HKLM\Software\Microsoft\Updates\Windows Server 2003\SP4\KB954550-v5\Filelist\4

The key is:Location

The value is: d:\09cb04b43b693cd9fa19\update\..\amd64

HKLM\Software\Microsoft\Updates\Windows Server 2003\SP4\KB954550-v5\Filelist\5

The key is:Location

The value is: d:\09cb04b43b693cd9fa19\update\..\amd64

HKLM\Software\Microsoft\Updates\Windows Server 2003\SP4\KB954550-v5\Filelist\6

The key is:Location

The value is: d:\09cb04b43b693cd9fa19\update\..\amd64

HKLM\Software\Microsoft\Updates\Windows Server 2003\SP4\KB954550-v5\Filelist\8

The key is:Location

The value is: d:\09cb04b43b693cd9fa19\update\..\amd64

HKLM\Software\Microsoft\Updates\Windows Server 2003\SP4\KB954550-v5\Filelist\9

The key is:Location

The value is: d:\09cb04b43b693cd9fa19\update\..\amd64

For every server its a different random folder names and then its refenced in these registry keys... Let me know if it would help ou if I supplied the value of the FileName Key in each of the locations above.

what I dont want to do is delete this random folder and have all these entries in the registry still there, referencing a location that I have deleted.... doesnt seem like good practice, especially on a Terminal Server.

The other option I guess is too just run the XPS package before installing .Net 3.5 SP1?

re: Mailbag: Temporary files can be left behind after running .NET Framework 3.0 or 3.5 setup

Aaron Stebner — Sun, 28 Nov 2010 17:04:50 GMT

Hi TH - There are a few different cases I know of where temporary files can be left behind like this. What are the exact files that you see listed in your registry, and what locations do they appear at in your registry?

re: Mailbag: Temporary files can be left behind after running .NET Framework 3.0 or 3.5 setup

TH — Fri, 26 Nov 2010 19:42:19 GMT

Hi,

This randomly named folder is also referenced all over the registry... is it safe to delete the folder and leave all registry references to it?

re: Mailbag: Temporary files can be left behind after running .NET Framework 3.0 or 3.5 setup

Aaron Stebner — Mon, 01 Jun 2009 19:24:27 GMT

Hi Blakedue - You would have to write a tool/script to clean up the folders afterwards if you need them to be removed. The folders have randomly generated names, so your tool would need to look for folders at the root of the drive letter with the largest amount of free space, then check inside the folder to see if it is from .NET Framework 3.5 SP1 setup, and if so, delete the files and folder.

If you would like to avoid the folder being created in the first place, you can pre-install the XPS package before running the .NET Framework 3.5 installer. Here are the download locations:

For the x86 XPS package - http://go.microsoft.com/fwlink/?LinkId=123098

For the x64 XPS package - http://go.microsoft.com/fwlink/?LinkId=123099

re: Mailbag: Temporary files can be left behind after running .NET Framework 3.0 or 3.5 setup

Blakedue — Fri, 29 May 2009 18:20:43 GMT

Hi,

How can I delete those temp folders automaticly?

I have around 600 servers in me environment so I won't do it manually on each server.

Or,

Is is possible do find a way to install .Net Framework 3.5 SP1 and not getting those temp folders.

Thanks