Commentary

Dave Methvin
 

Some Hard Data On Vista Users And UAC

Of all the changes in Windows Vista, perhaps the most controversial is the User Account Control functionality that often results in multiple permission prompts that border on annoying. OK, let's be honest: UAC crossed the border, broke down the front door, and is camped-out-on-the-sofa annoying.

Of all the changes in Windows Vista, perhaps the most controversial is the User Account Control functionality that often results in multiple permission prompts that border on annoying. OK, let's be honest: UAC crossed the border, broke down the front door, and is camped-out-on-the-sofa annoying.UAC can be disabled, though, and many Vista users I know have done just that. After you turn off UAC, disable the Vaseline-smeared-transparent-border Aero Glass theme, and tweak the background tasks, Vista starts to behave a lot more like XP. On my own Vista system I have done some of the UI and background task tweaks, but I've stubbornly refused to turn off UAC. I develop Windows applications, and I want to test those apps with the OS running the way most users will have it.

Until recently, all I had was a hunch that most Vista users either wanted UAC, or at least passively left it turned on. In an MSDN blog entry by Chris Jackson, I found some hard data. In that post, Jackson mentions that the Vista installed base that has UAC disabled is "currently hovering around 12%, but on the scale of Windows that's pretty huge."


More Windows Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

Also be aware that there are some functions that break if you have UAC disabled, such as adding a printer. I stumbled across this problem last year, but can't reproduce it now so I suspect it was fixed in Vista SP1.

If you're using Vista, have you disabled UAC on your own computer? If not, why? Now, if you have deployed Vista as part of your job in computer support for your company, have you disabled UAC on those computers? If so, are you crazy?


Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
T-Shirt Giveaway T-Shirt Giveaway: Each week we're selecting one great comment from our readers. The author of the comment will receive an InformaitonWeek Community t-shirt. So get posting!
Subscribe to RSS

Resource Links