Re: Vista and file associations



Strange: according to http://windowsconnected.com/blogs/jerry/archive/2005/12/21/97.aspx
I have to add manifest with level="highestAvailable" specification.
But on my Vista RC1 build 5728 it does not work when I'm truing to write to HKET_LOCAL_MACHINE (doing the same thing as Brian, i.e. making file assocociation; instead, when I rename my program to something, which contains "setup" in it's name (for example "DataLoader - setup.exe", orig. name was "DataLoader.exe"), Vista is warning me that the program tries to get access to my comp and if I say "OK" it runs my program and then allows it to change file association. So, indeed, the behaviour is defined by program's name, not by manifest (at least in Vista RC1 build 5728). Strange...

klunk wrote:
And yes, I'm running the app as administrator..



In Vista, when User Account Control (UAC) is in effect, any
user with "administrator" rights operates under
what MS is calling a split token -- which means effective rights
are as a limited user except when rights are elevated to perform
tasks that require admin rights. The executable requiring admin
rights must request them via a manifest setting. Apps that attempt
to write to protected areas without proper elevation will either fail,
or have their writes go to either a file or registry "Virtual Store."

You shouldn't elevate your main exe, since it shouldn't require
admin rights to do its normal functions. What you need is a
separate exe to run your admin related routines that can request
admin rights elevation via a manifest.

The fact that an admin user is not always an admin is going to
be one of the most confusing and difficult things for users to
understand and get used to, in my opinion.

Here are some links to documents that explain all this in more
detail:

UAC:
http://blogs.msdn.com/uac/
http://blogs.msdn.com/uac/archive/2006/06/28/650262.aspx

VirtStore:
http://windowsconnected.com/blogs/jerry/archive/2005/12/19/86.aspx

Manifests:
http://windowsconnected.com/blogs/jerry/archive/2005/12/21/97.aspx



.



Relevant Pages

  • Re: I turned off UAC
    ... Five Misunderstood Features in Windows Vista ... The User Access Control (UAC) can detect rootkits before they ... full-rights admin like on XP. ... The admin-user is only a user with Standard user rights, ...
    (microsoft.public.windows.vista.general)
  • Re: Problem with manifest file under vista basic home
    ... I'm getting my feet wet with Vista. ... manifest file to give our app Administrator privilages at run time. ... This is what it's supposed to do - even if you right-click and select 'Run as admin' instead of using a manifest file and even if the user is logged on to Windows as a user with admin rights. ...
    (microsoft.public.vb.general.discussion)
  • Re: How to receive ICMP TTL Expired packets on Vista?
    ... Elevation involves specifying requireAdministartor in your manifest. ... The user running the executable must already be a local admin. ... admin functions just like any other regular user under Vista can't. ... but I don't get the ICMP error messages. ...
    (microsoft.public.win32.programmer.networks)
  • Re: UnauthorizedAccessException
    ... I did set my VS to run as Admin and still have the same issue. ... my ignorance but what is different in Vista security wise ... even an account with Admin rights on Vista is locked down to Standard user rights and rights of the Admin must its privileges escalated when doing things or running programs on Vista. ... You have to start the VS 2005 or whatever you're using with Run As Administrator, which can be set on and exe or a short-cut pointing to the exe. ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: Use of credentials with UAC in vista
    ... until such time it needs to use the Admin Full rights Secuirty ... Vista, with UAC enabled. ... in Vista if you run under a limited user account you can't run ...
    (microsoft.public.windows.vista.general)