H
hogyu
Very informative thread. While I understand the logic for UAC, I have the
sneaking suspicion that it was designed to protect click-happy daredevils
from themselves. If you don't click on any offer in a pop-up window that
comes along, you'll be OK.
But with the emerging under-the-radar installers on the Web, I'm not so sure
anymore.
So the logic is based on writing to protected locations? And if a program
(or a .dll or other app helper?) can't write to those protected places, they
won't run? Period?
Second question: This business about UAC quieting down after a few days just
isn't happening for me.
Jimmy Brush wrote in the other thread:
"Whenever a non-compliant program opens a file in a protected location,
UAC first checks to see if there is a "modified" version of that file
inside of your user profile folder, and if so, opens the modified file
instead of the original, without the program realizing it.
This allows the program to function by making it THINK that it is
writing to a protected location, when in reality it is not."
When I first read this, I thought it meant that after UAC diverts a
program's attempts to write to protected locations, that diversion to a
modified version should happen automatically from then on. I've already told
UAC the program is OK by allowing the first write to my user profile folder,
so why won't the process look seamless the next time?
But it isn't happening with WinRAR, much to my annoyance every time I try to
create or open a zip file. Am I missing something, or is UAC supposed to
sound off every time a program is diverted from the protected to modified
location?
Thanks.
sneaking suspicion that it was designed to protect click-happy daredevils
from themselves. If you don't click on any offer in a pop-up window that
comes along, you'll be OK.
But with the emerging under-the-radar installers on the Web, I'm not so sure
anymore.
So the logic is based on writing to protected locations? And if a program
(or a .dll or other app helper?) can't write to those protected places, they
won't run? Period?
Second question: This business about UAC quieting down after a few days just
isn't happening for me.
Jimmy Brush wrote in the other thread:
"Whenever a non-compliant program opens a file in a protected location,
UAC first checks to see if there is a "modified" version of that file
inside of your user profile folder, and if so, opens the modified file
instead of the original, without the program realizing it.
This allows the program to function by making it THINK that it is
writing to a protected location, when in reality it is not."
When I first read this, I thought it meant that after UAC diverts a
program's attempts to write to protected locations, that diversion to a
modified version should happen automatically from then on. I've already told
UAC the program is OK by allowing the first write to my user profile folder,
so why won't the process look seamless the next time?
But it isn't happening with WinRAR, much to my annoyance every time I try to
create or open a zip file. Am I missing something, or is UAC supposed to
sound off every time a program is diverted from the protected to modified
location?
Thanks.