amd64, i386?

[Smirnoff]

XP Pro, SP3, MSE

Probably a naive question but haven't really thought about it before.

When I am in Win Explorer, under Local Disk (C), there are 2 folders listed
with about 24 alpha/numeric characters. In each of these are 2 other
folders, amd64 and i386.

None of these four sub-folders contain any data (0 Bytes).

1. What are they for?

2. Is it normal to have 2 versions of these? (the reason I ask this is that
I recently did a clean install and wonder if one relates to my old
settings).

 

[DL]

They are udate files from winupdate that were'nt removed after a reboot,
just delete them (send to recycle)
If you did a clean install nothing from the origonal installation will have
been retained, thats why its called a clean install

 

[Smirnoff]

There were other folders in WE that had alpha/numeric characters, however,
none of them contained sub-folders. I looked at these and saw that each
contained a couple of old update files, I successfully deleted the folders
and files.

When I try to delete the ones containing the above sub-folders, I am told
that access is denied (either write protected or in use). If I go into
properties and uncheck the Read Only attribute and Apply, the system will
still not let me delete them.

 

[Guest]

They are from .NET Framwork 3.5 SP1 installation. It's a known issue in XP
leaving those files behind. In Windows Server they can be deleted but in XP
Pro you can take the ownership...

 

[Jose]

There were other folders in WE that had alpha/numeric characters, however,
none of them contained sub-folders. I looked at these and saw that each
contained a couple of old update files, I successfully deleted the folders
and files.

When I try to delete the ones containing the above sub-folders, I am told
that access is denied (either write protected or in use). If I go into
properties and uncheck the Read Only attribute and Apply, the system will
still not let me delete them.

When Windows installs some things, it creates a randomly named/
numbered temporary folder (20-25 characters I think) in the root drive
of the volume that contains the most free space. This is why the
often show up on the D drive.

In a perfect world, they would be removed when the installation is
complete, sometimes they are not.

If normal removal attempts fail, you can often remove them by booting
temporarily in Safe Mode.

Really stubborn ones can also be removed with third party tools like
Unlocker:

http://ccollomb.free.fr/unlocker/

Remove Unlocker when you are done if you don't need it.

If you want to go the take ownership approach here are instructions:

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

 

[Smirnoff]

I see, thanks.

Should there be 2 folders with sub-folders though?

Also, is it worth taking ownership (I'll have to check how to do that) and
deleting them or do most people leave them?

 

[Smirnoff]

When Windows installs some things, it creates a randomly named/
numbered temporary folder (20-25 characters I think) in the root drive
of the volume that contains the most free space. This is why the
often show up on the D drive.

In a perfect world, they would be removed when the installation is
complete, sometimes they are not.

If normal removal attempts fail, you can often remove them by booting
temporarily in Safe Mode.

Really stubborn ones can also be removed with third party tools like
Unlocker:

http://ccollomb.free.fr/unlocker/

Remove Unlocker when you are done if you don't need it.

If you want to go the take ownership approach here are instructions:

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

I used the Take Ownership route and deleted both folders, thanks

 

[Smirnoff]

As you can see from my other post, I was concerned that there were two
folders, however, as they should have been deleted after install anyway, I
took ownership of them and deleted both.

Thanks for your help.

 

[Jose]

As you can see from my other post, I was concerned that there were two
folders, however, as they should have been deleted after install anyway, I
took ownership of them and deleted both.

Thanks for your help.

Whack 'em.

Taking ownership is one method but I try to do things as efficiently
as possible without just changing Windows system settings that not
everybody has seen before.

Nobody explains how the folders got there in the first place, what do
they mean, why are they on D when my install is on C, etc., etc.

The suggestion to "take ownership" is seen often but then there
usually no instructions or posts to a link to tell you how to actually
do it. Just "take ownership". Well, not everybody knows what that
means, so I post a link so you can decide for yourself what to do.

Next questions are usually - I don't see the Security tab, why not,
what do I do now, more message cycles, try booting in Safe Mode then
take ownership, that didn't work, clicking, adding, view, options,
uncheck Simple File Sharing and there is no advice n whether or not
you need to check it back when done (well, do you?) Try, try, try...
I would rather do.

 

[Guest]

Joe,

If you take ownership of them & delete them. What is the problem?

--
SPAMCOP User

As you can see from my other post, I was concerned that there were two
folders, however, as they should have been deleted after install anyway, I
took ownership of them and deleted both.

Thanks for your help.

Whack 'em.

Taking ownership is one method but I try to do things as efficiently
as possible without just changing Windows system settings that not
everybody has seen before.

Nobody explains how the folders got there in the first place, what do
they mean, why are they on D when my install is on C, etc., etc.

The suggestion to "take ownership" is seen often but then there
usually no instructions or posts to a link to tell you how to actually
do it. Just "take ownership". Well, not everybody knows what that
means, so I post a link so you can decide for yourself what to do.

Next questions are usually - I don't see the Security tab, why not,
what do I do now, more message cycles, try booting in Safe Mode then
take ownership, that didn't work, clicking, adding, view, options,
uncheck Simple File Sharing and there is no advice n whether or not
you need to check it back when done (well, do you?) Try, try, try...
I would rather do.

 

[Guest]

Jose,

Unlocler just tries to free up the file handles but wouldn't work if you
don't have permission...

--
SPAMCOP User

There were other folders in WE that had alpha/numeric characters, however,
none of them contained sub-folders. I looked at these and saw that each
contained a couple of old update files, I successfully deleted the folders
and files.

When I try to delete the ones containing the above sub-folders, I am told
that access is denied (either write protected or in use). If I go into
properties and uncheck the Read Only attribute and Apply, the system will
still not let me delete them.

When Windows installs some things, it creates a randomly named/
numbered temporary folder (20-25 characters I think) in the root drive
of the volume that contains the most free space. This is why the
often show up on the D drive.

In a perfect world, they would be removed when the installation is
complete, sometimes they are not.

If normal removal attempts fail, you can often remove them by booting
temporarily in Safe Mode.

Really stubborn ones can also be removed with third party tools like
Unlocker:

http://ccollomb.free.fr/unlocker/

Remove Unlocker when you are done if you don't need it.

If you want to go the take ownership approach here are instructions:

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

 

[Guest]

Glad to have helped you Smirnoff