How do I: Move HEX:9e184e9b442c76102d613e97963bde Directories?

[tjdarth]

The above stated directory: 9e184e9b442c76102d613e97963bde is on a partition
that I now want to format and use for other purposes. If I try to move it to
copy/move this directory to another location, I get the famous 'Access
Denied' message. I'm not sure why the OS is choosing ramdon drives as in this
cas of a product update but I want to accomplish two things if possible:

1) Move this directory to another location and be able to use that
location if this directory is ever called upon for future updates.

2) change whatever registry value that might exist to help
establish a dedicated location for future updates and upgrades.

It would be great if someone can help me solve this problem

 

[David H. Lipman]

From: "tjdarth" <[email protected]>

| The above stated directory: 9e184e9b442c76102d613e97963bde is on a partition
| that I now want to format and use for other purposes. If I try to move it to
| copy/move this directory to another location, I get the famous 'Access
| Denied' message. I'm not sure why the OS is choosing ramdon drives as in this
| cas of a product update but I want to accomplish two things if possible:

| 1) Move this directory to another location and be able to use that
| location if this directory is ever called upon for future updates.

| 2) change whatever registry value that might exist to help
| establish a dedicated location for future updates and upgrades.

| It would be great if someone can help me solve this problem

Remanent of an update.

Take ownership and delete.

 

[Jose]

The above stated directory: 9e184e9b442c76102d613e97963bde is on a partition
that I now want to format and use for other purposes. If I try to move itto
copy/move this directory to another location, I get the famous 'Access
Denied' message. I'm not sure why the OS is choosing ramdon drives as in this
cas of a product update but I want to accomplish two things if possible:

     1)    Move this directory to another location and be able to use that
location if this    directory is ever called upon for future updates.

     2)     change whatever registry value that might exist to help
establish a dedicated location for future updates and upgrades.

It would be great if someone can help me solve this problem

Here is how it all works.

I say "delete" a lot, but you can replace delete with rename or move
or whatever is appropriate for you (I would delete the annoying
olders).

When some programs (including Windows programs) installs things, it
may create a temporary folder consisting of 20-30 random letters and
numbers in the root drive of the volume with the most free space.
This explains why sometimes the folders are on your C drive or on some
other drive - which one has the most free space?

For example you may see a folder similar to or called:

D:\9470bb12e8a4f3447657236478e41c5

There may be other folders and files under that main temporary
folder.

These should normally be removed when the installation is complete,
but sometimes they are not - especially if the installation fails.
They are harmless but annoying. You may think something is wrong when
there is not or be afraid the files are really needed. To avoid
confusion you can delete the temporary folders.

If your installation failed or the installation does not delete the
randomly named folder when it completes running the installation again
will make another randomly named folder.

You may be able to identify the installation (for curiosity) by
looking at some of the folder contents and decide if that installation
was okay, just delete the files/folders. If the installation did not
work properly for some reason, running the installation again will
just create a new randomly named temporary folder so the old
temporary
folder is really of no use.

Sometimes the folders are stubborn to delete. Even if you are an
Administrator on the system you may get a "sharing violation", "access
denied", "being used" or similar type message when trying to remove
the temporary folders. Installations sometimes use different
permissions than a regular user with Administrator group might have.

There are many methods to try to remove the folders and some involve
third party programs to install or changing certain Windows settings
that may compromise your system security if you don't change them back
when you are done.

Booting your system in Safe Mode (pressing the F8 key repeatedly right
before XP tries to load) is a good method to try and remove the
folders since it doesn't involve making any changes to your system
configuration or downloading any third party programs.

If Safe Mode does not work you can change the security of the folder
to give your user Full Control over the folder by browsing to it in
Explorer, click Tools, Folder Options, View and in the Advanced
settings window, uncheck (at the bottom) Use simple file sharing
(recommended), and click OK. This turns off the recommended simple
file sharing on your computer so you will want to turn it back on when
you are done.

Right click the stubborn folder, Properties and click the now visible
Security tab. Select your user name and check the box to allow Full
Control, click OK to apply the changes.

Now try to manipulate/delete the folder.

It is a good idea to go back into Explorer and turn back on (Enable)
Simple file sharing (recommended) when you have finished.

If none of the above work, try a popular third party tool called
Unlocker.

Unlocker can be download from here:

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

Unlocker can be uninstalled when you are finished using it.

Reboot when you are finished to be sure the annoying folders are
really gone.

 

[tjdarth]

Thanks David for your quick response. You and Jose have both given me useful
information of which I will look into both

 

[tjdarth]

Thanks Jose for your quick response, also. I will look at both you and
David's response
and let you all know which one works the best for me..

Thanks again . . .
TomJ

 

[tjdarth]

Jose, just a note to bring you guys up to date and let you know that your
suggestion had the right details for me to overcome this problem. Although I
ended up having to change the security settings for the entire partition, it
alowed me to go forward and completeled move the entire directory w/o
destroying the contents of it. Once I began to snoop around the contents of
the directory I discovered it was actually used to update my SQL Express 2008
application edition.

 

[Jose]

Jose, just a note to bring you guys up to date and let you know that your
suggestion had the right details for me to overcome this problem. Although I
ended up having to change the security settings for the entire partition,it
alowed me to go forward and completeled move the entire directory  w/o
destroying the contents of it. Once I began to snoop around the contents of
the directory I discovered it was actually used to update my SQL Express 2008
application edition.

That's good.

I understand the reluctance to just delete the offending folders
completely - I wondered about what they were for a long time and was
hesitant to follow the usual advice:

They are temporary folders - just delete them.

That advice is almost as bad as "just ignore the message".

I want to know what they are, and how they got there in the first
place, then I will decide if they need deleting or not.

I want to know how they get there and who to blame for not removing
the temporary folders.

Now I understand what they are, why they used to always be on my C
drive, then they started showing up on my D drive and now they show up
on my H drive. There is a method to this madness and now I know what
it is.

When the install creates a temp folder and the install fails, it will
leave the temp folder and then create a new temp folder with a
different random name the next time you try to install, so you may
have some junk.

Some installers just seem to be sloppy, but generally, they seem to
work okay unless there is a problem, then you have your problem,

MS SQL is one I believe would leave crap laying around. So is VB.
They sure do leave a bunch of junk in the registry when they are
uninstalled (I use snake oil to clean it up).