Page 1 of 1

Windows 7 / Associate With... suggestion

Posted: 2010-10-12, 12:18 UTC
by DarkRuleR
Hi!

I was trying to Associate an extension using TC v7.55a / Windows 7 x64.
This failed every time untill I started TC in elevated mode.

I would be great if you don't have too start TC in elevated mode to do this???

Greetz,

DR...

Posted: 2010-10-12, 21:50 UTC
by karlchen
Hello, DarkRuleR.

Have you tried to execute the same operation in Windows Explorer? Does it not ask for your consent to elevate your privileges?

Kind regards,
Karl

Posted: 2010-10-14, 15:10 UTC
by DarkRuleR
karlchen wrote:Hello, DarkRuleR.

Have you tried to execute the same operation in Windows Explorer? Does it not ask for your consent to elevate your privileges?

Kind regards,
Karl
Hi Karlchen,

I have checked the same operation in Windows Explorer.
(right click on a file -> Open with -> Choose default program...)
And it did not ask too elevate my privilegis.

Update:
I have done some tests and I don't think it is a privilege issue anymore.
Why?, in non elevated mode:

- I can associate a NEW extention
- I can edit the NEW associated extention

When there a multiple associations in Windows for a file then:
(Check with right click on a file in Windows Explorer -> Open with)

- I can't change the association for a extention
- I can edit the multiple associated extention

In TC it looks like the association is set correct but when you double click on a file the "old" association is still active.

I can't reproduce changing the association in TC started in elevated mode.
This fails all the time now.

Greetz,

DR...

Posted: 2010-10-18, 15:25 UTC
by ghisler(Author)
This is unfortunately a misfeature of Windows Vista/7: As soon as you have used "open with" -> choose program for ANY extension, this key is locked by Windows, so no program can change it except for the same "open with" mechanism! You can verify this by using Regedit - Edit - Permissions on the keys under
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExts

Why? Microsoft did this because many installers reassigned associations to themselves, which was very annoying.