how to delete protected file under WinXP SP3

5,507

Try this as an administrative user:

  1. Go to Tools > Folder Options > View tab and make sure Use simple file sharing is turned off. If you use Windows XP Home Edition, you cannot do this, and will need to reboot into safe mode to complete the rest of the steps.
  2. Go to My Computer and then to drive C:.
  3. Right-click on the offending folder and click Properties.
  4. Switch to the Security tab, select Advanced, and switch to the Owner tab.
  5. Select your user account from the list.
  6. Check the Replace owner on subcontainers and objects box.
  7. Click OK. It may take a moment to apply the permission changes.
  8. Back in the main properties dialog, make sure your user account has Full Control permissions.
  9. Click OK.

You should now be able to fully browse, modify, and delete that folder and its contents.

Share:
5,507

Related videos on Youtube

Nate Koppenhaver
Author by

Nate Koppenhaver

Gamer, programmer (C/C++/C#; VB.NET), and general computer geek; most of my experience is with Windows (from 9x to 8). Right now I'm running Windows 8 as my main desktop OS. I am currently head engineer on an aquatic robotics team, running and modding SeaPerch ROVs for water quality assessment using the Arduino platform. When I'm not working on technology, I'm an EMT practicing in North Dakota and Minnesota, and a musician gigging around the local jazz/rock and classical scenes.

Updated on September 17, 2022

Comments

  • Nate Koppenhaver
    Nate Koppenhaver over 1 year

    there is a dir called C:\dcfa827bc56b26f4dc922bb28e on my hard disk that is protected or something and I can't view any files in the subdirs Program Files and Setup. I think this may be a rootkit, because I am admin, and still can't do anything. is there any way to delete or change the permissions on the file so I can see what's in it? Thanks

  • Nate Koppenhaver
    Nate Koppenhaver about 13 years
    that worked, it let me in. Turns out it wasn't a rootkit, it was something to do with Visual Studio 10. I have no idea why it needed to be protected, though.