Quantcast Vista Users - UAC and You - WoWInterface
Thread Tools Display Modes
01-21-08, 11:27 AM   #1
Premium Member
WoWInterface Super Mod
AddOn Author - Click to view addons
Join Date: Mar 2007
Posts: 818
Vista Users - UAC and You

If you don't want to know all the background information on WHY this is necessary, and just want to get WoW to work, then scroll down "Making It Work" below.

Are you having trouble installing addons? Are you changing files or deleting your WTF folder, but somehow magically WoW ignores the changes? If you're on Windows Vista, a new security feature called "User Account Control" is likely to blame.

About User Account Control (UAC)
Microsoft's Windows Vista is the latest generation of their Windows operating system. Along with new eye-catching features, Vista also takes a new, hard stance on security. This new stance, however, caught some programmers off-guard. As a result, these new features have caused some programs to operate slightly differently than expected, and unfortunately, World of Warcraft is one of them.

The new feature in question is called "User Account Control" or "UAC." UAC is a great feature that provides users with the security that they are not running as administrators all the time. *nix users will be familiar with this system, as the overwhelming majority of them will agree that you should not be running as root, and only give permissions to programs as necessary.

One of the restrictions imposed by this is that the Program Files folder cannot be modified without "escalated" (administrative-level) permissions. WoW (by default) does not run escalated, so it does not have access to the Program Files folder. You may, however, be aware that WoW needs to write files there! It stores all of your configurations (in the WTF folder), it stores the cache data (in the Cache folder), and it even puts some default addon keys there.

So why doesn't WoW just crash when it can't write there? Well, Microsoft was intelligent. They foresaw that older programs consistently used this folder to store configuration information, even though it has been strongly discouraged by Microsoft for years in favor of the %APPDATA% folder. So they invented this idea of "virtualization." If a program does not indicate to Vista that it is "UAC Aware" (via a "manifest"), Vista assumes that the program is not aware of the permissions restrictions. So, instead of denying access, it "fakes" write access. Anything the program tries to write or create in the Program Files folder then gets actually written to the "Virtual Store" which is located at C:\Users\[username]\AppData\Local\VirtualStore. If you go there and don't properly have WoW set up, you may even see that there is a Program Files\World of Warcraft folder there with various files that have been virtualized away.

Making It Work
So, how do we stop this? There are actually several solutions, though some are preferred over others due to simplicity.
  • Option 1: Install in an Unprotected Location

    This option is best for people whom haven't yet installed or aren't worried about installing again and losing their settings. The idea behind it is quite simple: If you don't install in the Program Files folder, WoW won't be restricted by Vista. Many people recommend creating a C:\Games folder or something similar. Thus, your program would be installed in

    C:\Games\World of Warcraft

    So long as you don't use the "Windows" or "Program Files" folders, you should be OK.

    You can also use another drive for World of Warcraft. If you do so, it is perfectly acceptable to create a "Program Files" folder on that drive and install it there, like the screenshot below. In such a case, Vista realizes that this is not the "real" Program Files directory, so it is not protected by UAC.

    (Note that the folder is called "Program Files (x86)" because this is a 64-bit copy of Vista and a 32-bit program.)

  • Option 2: Provide Administrative Permissions

    This isn't always the easiest option because it requires a bit of moving, especially if you've already played WoW for a while and your settings are currently virtualized away. It does, however, avoid the need for a new installation. Giving WoW administrative permissions provides a means for WoW to write directly to the Program Files folder, so it doesn't get virtualized anymore.

    If you right click on "WoW.exe" in your Program Files directory, you will find an option "Properties." Clicking on this will bring up the Program Properties window. Click on the "Compatibility" tab. You will see the following pane:

    Check the box next to "Run this program as an administrator."

    Next, do the same for "Launcher.exe" in the same folder. Open the "Compatibility" tab and check "Run this program as an administrator."

    If this is done correctly, the next time you run WoW, you will get a UAC escalation popup, which looks like this:

    This popup asks for escalated permissions for the program shown. If it does not say "Blizzard Entertainment" and "Blizzard Launcher" or "WoW.exe," double-check that it's the right program before giving permissions.

    However you have another problem -- all your old settings! Now that WoW has administrative permissions, it will no longer consult the Virtual Store for settings, meaning all your settings have been lost! Fortunately, we can move them back to where they need to be.

    Go to "C:\Users\[Username]\AppData\Local\VirtualStore\Program Files\World of Warcraft" and you will find all of your WTF folders, etc. Copy your WTF folder into "C:\Program Files\World of Warcraft" and your settings will be restored. If prompted, the files in your VirtualStore should overwrite the ones that may already exist in your Program Files directory. Keep in mind that if you are using a 64-bit Vista, "Program Files" will be named "Program Files (x86)."

  • Option 3: Disable UAC
    This is a last-resort option and probably should not be used, but I place it here for informational purposes anyway. UAC is a beneficial feature which protects you from malicious code being executed at an administrative level where it can do serious harm. If not given escalated permissions, most malicious code may cause a little harm, but nothing too severe (perhaps an annoyance more than anything).

    However, it is possible to turn it off if you really want to, and that will stop all of these Virtual Store and permissions problems. You will, however, be turning off one of the most crucial security features that Vista has to offer, so be absolutely sure you want to do this before you do it.

    Click on the "Start" button and then choose "Control Panel" on the right side. Find the "User Accounts" icon and double click it. This will open up the "User Accounts" control panel. At the bottom, you will see an option "Turn User Account Control On or Off." Click on this option. You will see a UAC box pop up; validate that it is from Microsoft and then accept it. (Naturally you must give administrative permissions to disable this!). Uncheck the checkbox in the window that appears, and then select OK. UAC is now disabled. You may wish to follow the instructions in option 2 above, now, to copy over your WTF folder to your WoW folder, as these settings will no longer be virtualized away.

UAC is a useful feature provided by Microsoft that enforces policies that have been encouraged a long time ago. Unfortunately, programs are still not up with the times, and thus these changes sometimes cause a few glitches along the way. UAC still can provide the security you desire and your programs can get along with it just fine, it just may take a little extra attention. With this attention you can be sure to have a secure user account while enjoying the world we all love.
It's my turn next.

Shakespeare liked regexes too!

Last edited by Shirik : 01-24-08 at 10:35 AM.
  Reply With Quote
03-07-08, 05:42 PM   #2
A Cyclonian
Thrae's Avatar
AddOn Author - Click to view addons
Join Date: Jun 2005
Posts: 42
Two other solutions to add:
* You can simply move the "World of Warcraft" folder from outside of the default install location, "C:\Program Files" or "C:\Program Files (x86)" to somewhere else. Once you run the program again via the Launcher, it will automatically detect where it is and change the needed registry settings itself. You do not need to reinstall.

* Second option involves manually adding the security information. Note that these procedures assume you installed World of Warcraft into its default location.

- Click on START.
- Double-click on your system drive ( C: ).
- Vista 32-bit only: Double-click on the folder labeled "Program Files"
- Vista 64-bit only: Double-click on the folder labeled "Program Files (x86)"
- Right-click on the "World of Warcraft" folder and select "Properties".
- Click on the "Security" tab.
- Click on the "Edit" button. If UAC is enabled, it will prompt you to continue. Do so.
- Click on the "Add" button.
- Type in the name of your user account into this field. Usually it will be "Senior Admin", and be at the top of your Start Menu. If you are unsure, after typing in the name, click on "Check Names". If it gives "Name Not Found", that means it was incorrect. If you are still unsure of your user account name, go into the User Accounts in the Control Panel and it should be listed there.
- Click OK.
- Back in the "Permissions for World of Warcraft" window, select your user account name (again, probably "Senior Admin").
- In the Permissions box, click on the little checkbox for "Full Control".
- Click OK.
- Click OK.

You should now have no problems with anything that requires access to your World of Warcraft folders, such as Addons.
Yes, I was a Tauren. Yes, it was bigger.
  Reply With Quote
03-08-08, 11:22 AM   #3
A Deviate Faerie Dragon
AddOn Author - Click to view addons
Join Date: Mar 2007
Posts: 18
Couldn't you just put the addons in the local store copy?
  Reply With Quote
03-09-08, 09:51 AM   #4
A Cyclonian
Thrae's Avatar
AddOn Author - Click to view addons
Join Date: Jun 2005
Posts: 42
Originally Posted by Falcon213 View Post
Couldn't you just put the addons in the local store copy?
WoW isn't smart enough with Vista to do that. And with patching, there's a lot of stuff that needs to be changed session per session.
Yes, I was a Tauren. Yes, it was bigger.
  Reply With Quote
03-24-08, 03:13 AM   #5
A Fallenroot Satyr
AddOn Author - Click to view addons
Join Date: Nov 2007
Posts: 26
I usually disable UAC the 1st time I boot into my newly installed Window Vista.
  Reply With Quote
05-16-08, 07:01 PM   #6
Auctioneer Lead Developer
MentalPower's Avatar
Premium Member
Join Date: Jul 2005
Posts: 121
Originally Posted by digmouse View Post
I usually disable UAC the 1st time I boot into my newly installed Window Vista.
That is fine if you're computer savvy and know the risks involved. However it is not something you should recommend to mom and pop that do not know the risks that disabling UAC brings.

Also note that disabling UAC usually means that Vista will nag you about it via its security center every time you boot.
MentalPower, Lead Developer for the Auctioneer AddOns package

"If life hands you lemons ask for tequila and salt"
  Reply With Quote
07-12-08, 07:24 AM   #7
Softrix's Avatar
AddOn Author - Click to view addons
Join Date: Jun 2008
Posts: 16
Thumbs down Uac

Bad idea to disable UAC, its there for your protection. Although it can be annoying at times I agree, you need to remember its there to help prevent malicious software on your computer being installed without your consent such as key loggers, back doors etc thats there to steal your wow login details or credit card details.

UAC shouldnt be disabled at all!
Michael Boyle
Softrix Studios
  Reply With Quote
07-30-08, 08:43 AM   #8
Premium Member
Premium Member
AddOn Author - Click to view addons
Join Date: Mar 2006
Posts: 59
Originally Posted by Shirik View Post
UAC is a useful feature provided by Microsoft that enforces policies that have been encouraged a long time ago.
I actually remember reading a DEV-Blog not too long ago where a MS Windows Development Leader / Designer / Whatever basically said that UAC was BAD, and that's what the MEANT IT TO BE.

They Designed UAC to annoy the user in an effort to force programmers to write programs that didn't cause UAC Violations (Popups) by doing so programmers would write better programs that were more "secure" in the first place.

Hence why they have an option to turn it off.
  Reply With Quote
09-14-08, 05:58 PM   #9
A Chromatic Dragonspawn
AddOn Author - Click to view addons
Join Date: Jul 2008
Posts: 156
Well, it is not "UAC bad", it is "Virtualization bad".
It just hides the fact that problem (Program writing data in installation folder) exists.
But we're here not for discussing Windows design troubles.

Let me add Option 4? Pure theorycrafting, I hate Crapsta enough to never touch it even with 100-feet stick.
But it is what I'm doing if I have such problem with applications under W2k/WinXP.
Note before you dive into reading: It require some additional tools to complete process, so read it to the end BEFORE you start following these instructions. If you have slightest feel that you're not understand intentions, process, and expected results, DON'T! Just don't do it.

Step 1:
Start WoW as administrator once and let it create all the needed "WTF/**" folders for your account. You do not need to log in every character you have. One is enough. Ok, you did it. Log your char out, close WoW client.

Step 2:
Go to your %APPDATA% folder. Basically, open any Explorer window (Win+E anyone?) and type
in the address bar. (The "<CR>" thingy stands for "Enter" key. Hope you know it, but if not - you are now.)

Step 3:
Create the "Blizzard/World of Warcraft" folder there in %APPDATA%. 2 steps, I hope you can do it yourself. Refer to "Windows for dummies" for more precise instructions.

Step 4:
Go to "%ProgramFiles%/World of Warcraft/WTF" folder. Open it in separate window. You must see your account name as folder in there.
Copy "%ProgramFiles%/World of Warcraft/WTF/<YourAccount>" to "%APPDATA%/Blizzard/World of Warcraft/<YourAccount>".
Critical: I emphase the word "Copy" because you must do exactly that. Copy it, otherwise you may have applied rights moved along with folder and effect would not be what we want to be done.
Hold "Ctrl" key while dragging your stuff, or use whatever you feel applicable for that task. I know at least 4 ways to have it done through Explorer itself.

Step 5:
Delete "%ProgramFiles%/World of Warcraft/WTF/<YourAccount>". (Shall I notice you to make a backup?)

Step 6:
Create symlink to "%APPDATA%/Blizzard/World of Warcraft/<YourAccount>" at "%ProgramFiles%/World of Warcraft/WTF/<YourAccount>".
Cannot be done through Explorer. Find your way and tool. You should be able to do so.

Step 7:
That's all. Log in your another char and see if you have it's settings created in the "%APPDATA%/Blizzard/World of Warcraft/<YourAccount>/<YourAnotherChar>".

I *really* hope it would work. Otherwise, I'd say M$ really stupid... >.>

Advantages? Ok, you asking, I tell you.
You'll be able to have different system accounts to have their own WoW profiles stored inside system profiles. Easy to backup, transfer, etc.
And for patchdays, it's Real Simple. Unlink WTF/** folders.
Update. See if all works ok in first place. Cleanup WTF folder and link your profiles back. See if all works as expected. Make adjustments, shuffle backups etc. As you need.
  Reply With Quote
07-21-09, 12:07 PM   #10
A Kobold Labourer
Join Date: Jul 2009
Posts: 1
I found this helpfull but alittle confusing.The easyiest way I found to get addons working was just right clicking on desktop wow icon and using open file location.This opened up public files games.That's where I found all my wow files and just added my addon to the interface and it worked.Maybe this will help someother peoples out. Quarko
  Reply With Quote
05-22-12, 06:12 PM   #11
A Kobold Labourer
Join Date: May 2012
Posts: 1
Is it still necessary to do all this or is the wow client already patched to support user account control ?

  Reply With Quote

WoWInterface » AddOns, Compilations, Macros » AddOn Help/Support » Vista Users - UAC and You

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off