What Is TrustedInstaller & Why Does it Keep Me From Renaming Files?

Ads by Google

trustedinstaller rename fileTrustedInstaller is a built-in user account in Windows 8, Windows 7, and Windows Vista. This user account “owns” a variety of system files, including some files in your Program Files folder, your Windows folder, and even the Windows.old folder that is created after you upgrade from one version of Windows to another. To rename or delete these files, you’ll have to take ownership of them away from the TrustedInstaller user account.

If you’ve just upgraded to a new version of Windows and are trying to get rid of the Windows.old folder, there’s an easier way to do it – you don’t have to delete the folder by hand.

Who Is TrustedInstaller?

The TrustedInstaller user account is used by the Windows Modules Installer service included with Windows. This service is responsible for installing, modifying, and removing Windows updates and other optional Windows components, so it has the exclusive ability to modify them.

trustedinstaller rename file

Deleting The Windows.old Folder

If you’re trying to delete the C:\Windows.old folder after upgrading to a new version of Windows and you’re seeing a message saying you need permission from TrustedInstaller, you don’t need to take ownership of the files at all. You just need to use the Disk Cleanup wizard.

To open the Disk Cleanup wizard, press the Windows key and type Disk Cleanup. On Windows 7, click the Disk Cleanup shortcut that appears in the Start menu. On Windows 8, click the Settings category and select the “Free up disk space by deleting unnecessary files” shortcut.

Ads by Google

permission trustedinstaller rename

Click the Clean up system files button in the Disk Cleanup window.

permission trustedinstaller rename

If you have a Windows.old folder on your hard drive, you’ll see a “Previous Windows installations” checkbox in the list of system files you can delete. Enable the option and click OK. Windows will delete the Windows.old folder for you – ensure you’ve copied any important files out of it before running Disk Cleanup on it.

Taking Ownership of Files

Warning – the TrustedInstaller user account owns your system files. If TrustedInstaller is preventing you from renaming or deleting a folder, it’s often for a good reason. For example, if you rename the C:\Windows\System32 folder, your operating system will stop functioning and will need to be repaired or reinstalled.

permission trustedinstaller rename

You should only take ownership of system files and rename, delete, or move them if you know what you’re doing. If you do know what you’re doing, follow the instructions below to take ownership of the files.

Locate the folder or file you want to take ownership of, right-click it, and select Properties.

trustedinstaller rename file

Click the Security tab in the properties window and click the Advanced button near the bottom.


Click the Change link next to TrustedInstaller to change the owner.

trustedinstaller rename file

Type Administrators into the box and click the Check Names button. Windows will automatically complete the rest of the name. This gives ownership to all administrators on the system. Click the OK button to save this change.


Enable the “Replace owner on subcontainers and objects” setting if you want to apply these changes to all subfolders and files in them. Click the OK button at the bottom of the Advanced Security Settings window.


Click the Edit button in the properties window.


Select the Administrators user and enable the Full Control checkbox to give administrator accounts full permissions to the files.

trustedinstaller rename file

Click the OK button twice to save your changes. You now have the ability to rename, delete, or move the files as you please.

If you find yourself regularly taking ownership of files, you may want to download a .reg file that will add a “Take Ownership” option to your right-click menu. You’ll be able to take ownership of files and folders with a few quick clicks.

For more answers to tech questions, check out MakeUseOf Answers.

Why did you need to take ownership of a folder away from TrustedInstaller? Leave a comment and share any other tricks you have!

Ads by Google
Check out more about:

16 Comments - Write a Comment



There goes MS, complicating things again. Instead of leaving Administrator as the owner of all the System files, they have to introduce another userid. Obfuscate, don’t innovate seems to be their motto. Brilliant, just f’ing brilliant!

Mihovil Pletikos

this way users won’t mess around with things they shouldn’t. and most of them won’t need to do it ever. those who need to do it, know how do deal with it…. it is just safer


“it is just safer”
In what way is it safer? Sounds like security by obscurity. Make things more “secure” by creating additional Administrator-level accounts. If Windows O/S was designed properly from the start, one Administrator account would be sufficient and secure. Is Microsoft going to create a separate “secure” userid for each system task?

All other O/Ss have only one Administrator or root account and they are much more secure than Windows. In other O/Ss each user is isolated in his own sandbox. By default and design they cannot “mess around with things they shouldn’t”. In Linux, for instance, a user installs an application into a folder in his own partition. If that application blows up it only affects that user’s partition. In Windows the application is installed in a system folder and when it fails, it can take the entire system down. That is why viruses and other malware is so successful on Windows PCs. It runs as a system process.

Chris Hoffman

Theoretically it makes it harder to mess with system files — and for applications to mess with them. Since so much stuff on Windows runs with Administrator permissions, well..


“Theoretically it makes it harder to mess with system files”
The key word being “theoretically”. When it comes to practice, that is a horse of a different color.



i thought this was why Trustedinstaller existed. is it by chance possible to log in as Trustedinstaller? it would be risky, but is it possible?

Chris Hoffman

Well, there’s no password by default, so you’d have to assign a password. It probably wouldn’t let you without a lot of silly stuff like assigning a password and allowing logons and such. It might not even do it then, as it’s a system account without a folder under Users.

So, definitely don’t even try!


Jorge Andrade

Faced this problem just the other day! Great help from this post



For people who need to do it It’s better to know how do it safe. Great



I would like to have ownership so I can delete thousands of unwanted pictures with symbols etc. from windows photo gallery and hundreds of unwanted Videos that I don’t want. No idea where they came from and I need “trustedInstaller” permission to delete them..Some of the pictures and Videos don’t show a SECURITY tab when I click PROPERTIES so I am stumped..Please help!!!!



Tried this. But every time I try to replace the owner I get denied.


Sean Kurth

Personally, I think the steps they use for taking ownership are too complicated. I recognize that some users aren’t comfortable with using the command line, but the TAKEOWN command really is easier.

Just open cmd.exe at an administrator level (Run>cmd>Right click>Run as administrator), and that’s pretty much it.

Type TAKEOWN /F C:\example folder\example subfolder\*

Why go through all those complicated menus and administrative control panels when all you have to do is basically type the path of the file/folder/drive you want to take and hit enter?



This is great – I can finally delete a wallpaper image that was pre-installed and really not a quality photo or an attractive image. Thanks – the process should be so much easier to manage the images on teh screensavers and wallpapers.



Thank you!



It keeps popping the message: “you are not running an official version of Windows”. But I bought my laptop 4 years ago with Windows 7 included and have never had this message until this last week. What’s up?



“failed to enumerate objects in the container. Access is denied.”


Your comment