I just tried to look it up in the spam comments and couldn’t find anything under your name. If you can please let me know what keywords to look for I can see what I can find.

You may be surprised to hear that a lot of people turn UAC off. This is especially common in the development community because it really hampers what you can do. You’ll also find that it doesn’t work very well with most server type of applications such as databases, web servers, etc.

As well, Microsoft has also realized how many issues there were and between Vista and Windows 7 they really scaled back UAC. In other words, they really toned down on how intrusive and how much checking it does.

And I disagree that turning off UAC will cause bugs. I can assure you they test their system’s without it. I myself have turned off UAC and have never had any issues. Issues can come from all kinds of random things. If you research issues due to UAC, you will actually find the list to be much much much larger. For example, just look at all the issues people have experienced in the comments in this thread alone!!

David,

I shouldn’t have to be an IT professional to use my own computer. Nor should the moms, wives, teenagers, and all others mentioned above and having this problem. Before this happened, I didn’t need to know how “security” worked. Security worked by having a firewall, anti-virus software, and knowing not to download crap to your computer not by preventing my husband from accessing the Quicken data file in his Application Data folder or keeping Norton from updating its files. How many people even know what a device driver is or how to look at it? And what are we supposed to be looking for? People should not need IT help to save a file PERIOD!

Think about it. Microsoft was pushed by the world to do something to prevent PC’s from being inadvertantly running rootkit viruses & other malware. UAC was their big step in helping users to lock down their system.

In Vista & Win 7 they assume that UAC will be there. How much testing do you think they do with this component turned off? I’m guessing ZERO.

Heaps of security & authentication API’s rely on this interface. If it is not there & the layers above do not handle the error correctly you will get all sorts of seemingly random outcomes that are extremely hard to remedy.

I refer back to my earlier post in 07. Learn how security works. & maybe look at your device drivers. it is highly likely this R/O issue with disk is a result of some incompatility with the Disk Driver s/w. (either the vendors or Microsoft)

NB: Interesting fact. In the 1st 8 weeks after shipping Vista, 48% of all Vista bluescreens worldwide were caused by a bug in NVidia’s Graphics driver. (which when they were told they fixed promptly)
So it would be very interesting to see if most people in thie fourm were running disks from a specific vendor.

It is indeed a very long thread! Especially when you consider it’s been around since 2007 and the problem still exists in the new OS!

Hopefully they’ll eventually come to a solution. The best idea would be to just kill UAC. I personally turn it off. It’s just not working as expected and causing too much grief. Great idea but the reality is that it doesn’t work in the real world. It’s too bad.

I am adding my own comment and solution to this problem to this thread – adding a manifest / assembly to the executable.

I have been developing a program and tried to run it on my wife’s computer. Whenever it tried to write to the database, I would get an error.

My solution was to quite easily add a manifest. In Perl, there is a manifest module (http://search.cpan.org/search?query=Win32%3A%3AExe%3A%3AManifest)

If you do not have Perl, go to http://win32.perl.org or http://www.activestate.com

Save the below script into a text file named “gen_manifest.pl” and update the three variables at the top.

* program_filepath – the full path to your exe file

* assembly_name – the program’s name (no spaces allowed)

* execution_level – this is the key variable to set to allow Admin access to your exe. (set to ‘highestAvailable’ first and then to ‘requireAdministrator’ if you need higher access)

Now run the program as follows:

C:\>perl gen_manifest.pl

Here is my script:

### START SCRIPT ###
use strict;
use warnings;

use Win32::Exe;

my $program_filepath = ‘program.exe’;

# no spaces in assembly name
my $assembly_name = ‘ProgramName’;

my $execution_level = ‘highestAvailable’;

my $exe = Win32::Exe->new($program_filepath);
my $manifest = $exe->get_manifest if $exe->has_manifest;

# Get themed controls
$manifest->add_common_controls;

# Change name
$manifest->set_assembly_name($assembly_name);

# Require Admin permissions
$manifest->set_execution_level($execution_level);

# write it out
$exe->set_manifest($manifest);
$exe->write;
### END SCRIPT ###

This updates my exe with a proper manifest. Now the program runs correctly and writes with no problems on Vista.

Hopefully this will work for some of you others who are grappling with this issue.

i play trickster online