VC_Red folder, files within

Oh ok, then yeah it's something left over from the install of somehting on the machine (May have been done "at the factory").


Unfortuately the file may have been placed there by the installer and has permissions set for hte installer only. You can try to "Take Ownership" of the file and delete it that way. You can do it by hand from the properties dialog from right clicking the file if you know how or you can DL and install the "Take Ownership" shortcut (Search this forum for "take ownership".

Definately do not use that command willy nilly though

right click menu only has "copy" and "extract"

have used ubuntu in the past, but really don't want to install just to get rid of some files that this system, for some reason(?) doesn't want me to get rid. of would rather like to understand the "whys" and "whatfors" first.

thanxz anyway
river

understand, and thanxz, might end up doing that, but want to find out about these files first.

Did you try "taking ownership"?

just took ownership, and cut and pasted to temp folder, ready for reboot, keeping fingers crossed, and ready for one to shoot up in the air if it screws something up !

i'm back, no smoke, no grinding noises, no explosions, so all is right with the world(?)

question: the take ownership that i just did is for the "vc_red" cab only, correct? and is there any reason to go back in to permissions and change that back?

thanxz for pointing me in that direction. guess i'll leave them in temp for a few days and then delete them.

river

Yeah basically you changed the permisions for that one file to give you full control. And no you shouldn't have to put the permissions back. 99% sure that it was just a temp file left over by some installer.

It is something you can do "manually" by navigating through the security menus under the properties for the file, but it's WAY quicker to just use the Take Ownership short cut. :)

More than likely the file "belonged" to the windows installer process so as-is you were not able to delete it.
It should never really be needed by 99% of all users but then there are issues like this where an installer crashed during install or someone turned of the machine and the installer left it's "personal" temp files lying around and you have to whip out a little admin tool to take control of the situation :)