Why won't my EXE run under Vista with UAC Enabled?

  • Thread starter Thread starter Joseph Geretz
  • Start date Start date
In message <[email protected]> "Joseph Geretz"
Yes, as I suggested:


But that's too tricky?
Click to expand...

How would you suggest doing that?

The problem is that the security token needs to be assigned at runtime,
an app cannot be elevated while running. This is required, otherwise a
non-elevated app could hook into an app which it suspects might become
elevated in the future, and once the elevation happens, the non-elevated
app would have full elevated privileges.

Worse, consider what would happen to a regular user (non-administrator)
who happened to be running a program that needed to be elevated part way
through. The program would not only received an administrator token,
but also an entirely different security context -- The new context might
not even have the ability to read it's own EXE, or the files it was
reading previous to the elevation.
 
How would you suggest doing that?

By scanning the executable at load time.

- Joseph Geretz -
 
Joseph

Those guidelines are general. If you don't see your specific issue addressed
in those documents, go to the developer forums, and ask your specific
question there. This is where all of the Microsoft developers, who wrote
most of the code for Vista, post answers to messages. I'm sure you can find
the soulution you are looking for on those forums. Start with the Where Is
the Forum For...?

MSDN Forums:
http://forums.microsoft.com/MSDN/default.aspx?SiteID=1
 
That's not really possible. Windows can't tell what a program does be
examing the exe. While some things could of course be gleaned, like declared
API calls, the program may jump to the API address or use the ordinal rather
than use symbolic names.

MS solution is .NET programming language with it managed code model.

Why don't you drop the manifest into the exe.
 
In message <[email protected]> "Joseph Geretz"
By scanning the executable at load time.
Click to expand...

To what end? How do you determine if an EXE will desire to write to
Program Files pragmatically? Or whether it will want to write to a
portion of the registry which is off-limits without elevated privileges?

I suspect you'd find that any similar solution would be even more buggy,
and there would be just as many complaints of "Why can't Vista figure
out that setup.exe is an installer and needs elevated privileges"
 
AAAAAAaaaarrrrggggggghhhhh!!!!!!

It's the NAME of the executable, AutoUpdate, which makes Vista THINK
(assuming
that this brain-dead OS is capable of such a thing) that the process
needs to run elevated.

kpg, this explains your issue as well; In your case it's that third
app in the chain which has the magical term 'update' in it, for me
it's the second. Who the !#$%@$# slapped this so-called OS together,
J.K. Rowling?
Click to expand...

wow...just got back to this thread.

Unbelievable!

Reminds me of the time a when I had a component named bridge.dll -
Windows defender thought it was spyware based solely on it's name - because
there was some malware that used a bridge.dll file - how about checking
signatures?

whatever...

kpg
 
Hi,

What has the vendor, EA Sports, said about this issue with their software?

At a guess, from your very brief description, I'd say there is a conflict
with it and some security software you are running (firewall, antivirus,
antispyware, etc.).

--
Best of Luck,

Rick Rogers, aka "Nutcase" - Microsoft MVP

Windows help - www.rickrogers.org
My thoughts http://rick-mvp.blogspot.com
 
Was UAC enabled when you installed the program?
Some have reported problems when a program is installed in one state
and then used in another.

Check with EA and see if there are any patches.
 
Back
Top