Microsoft Addressing UAC Concerns in Release Candidate

Well, it appears the Windows 7 chiefs are listening and have posted an update to their UAC article from earlier today. In their latest communication, Steven Sinofsky   and Jon DeVaan say:

With this feedback and a lot more we are going to deliver two changes to the Release Candidate that we’ll all see. First, the UAC control panel will run in a high integrity process, which requires elevation. That was already in the works before this discussion and doing this prevents all the mechanics around SendKeys and the like from working. Second, changing the level of the UAC will also prompt for confirmation.

@mdaria510 says:

Sometimes, inconsistency with your own ideals is a good thing. Make an exception, if only to put people’s fears to rest.

That sums up where we are heading. The first change was a bug fix and we actually have a couple of others similar to that—this is a beta still, even if many of us are running it full time. The second change is due directly to the feedback we’re seeing. This ““inconsistency” in the model is exactly the path we’re taking. The way we‘re going to think about this that the UAC setting is something like a password, and to change your password you need to enter your old password.

Microsoft deserves some big kudos for taking all the community feedback to heart and acting accordingly.   More than that, though, Long Zheng and Raphael Rivera should be applauded for sticking to their guns and doing a heck of good job in researching this issue during a critical time in the release cycle.