Is it harmful to change ownership of a file?

Hello,

I have a question regarding taking ownership of an executable that is in the WindowsApps folder in Program Files. I want to take ownership of it so I can make it launch at startup every time I boot up Windows. That's because for some reason, putting a shortcut of the executable in the Startup folder of Windows doesn't launch it at boot.

The current ownership of that executable is TrustedInstaller but I want to change that to myself. I am wondering however if this would lead to any problems or errors regarding automatic processes that Windows uses for that executable. Or if it would lead to problems if I want to uninstall or reinstall the app.

lehnerus2000 said:

I'd suggest that you don't change any files owned by "TrustedInstaller".

Have you tried using the "Task Scheduler" to start the App?

The tutorials shown below might help.

Tutorials:
Create Elevated Shortcut without UAC prompt in Windows 10
Create Startup Apps shortcut in Windows 10

I'd agree. Try anything but taking ownership, the consequences are unpredictable.

If you can find no other way, then as a last resort take ownership just long enough to add your user account to the permissions. Then give ownership back to TrustedInstaller straight away. The name you'll need to type in the 'Change owner' dialog is: NT SERVICE\TrustedInstaller

lehnerus2000 said:

When I was testing the W7 Betas, I removed "TrustedInstaller" and then I couldn't restore it...
These days I wouldn't think of removing "TrustedInstaller", without creating a backup image of my OS.

Well, I did say it was only to be tried as a last resort (if at all) :)

Restoring ownership to TrustedInstaller is only possible if you use its full name. The 'NT SERVICE' bit is essential, else 'check names' says it can't be found.

lehnerus2000 said:

...(IMO) it would still be prudent to create a backup image (just in case).

IMO too. In fact it's a prudent safeguard even if you're not planning on hacking your system. It's part of my monthly routine, make an image before each cumulative update, and keep the previous images for as long as I have space to do so (I think I still have one for 10240, I certainly have the one for the OEM Win7 this system started with).

Thanks for the replies guys. I'm amazed taking ownership just to make it launch at startup can have bad consequences like that.

Bree said:

I'd agree. Try anything but taking ownership, the consequences are unpredictable.

If you can find no other way, then as a last resort take ownership just long enough to add your user account to the permissions. Then give ownership back to TrustedInstaller straight away. The name you'll need to type in the 'Change owner' dialog is: NT SERVICE\TrustedInstaller

If I give it back to TrustedInstaller again, do I still have permission to launch the app at startup?