The true Administrator account just automatically grants you a higher level of ownership that affects synergistic file & folder interaction; I'm not sure if there could be a vulnerability that'd be any worse than what a "normal" Administrator account has to deal with. When it comes to administrator accounts on personal PC's, a breach is a breach. I do hope I don't come off as patronizing, but I doubt that you've allocated different resources to different accounts; it's not something anyone really needs to do with their own personal computers.

Again, you could manually assign ownership & Full Control permissions after installation with a normal Administrator account, but the true Administrator account makes it less of a hassle.

Posting from my phone, so I apologize in advance for any orthographical issues.

The encountered error message was due to a discrepancy between certificates & user accounts. I did not have the foresight to recommend reinstallation as I've always found myself defaulting to the true Admin account on my home computer, so I apologize if you were understandably confused.

Most importantly, if Mumble is now working even on your old account, I need to know if you had to change your User Account Control permissions as iterated in Step 1. Did you have to set the slider to "Never notify?"

In essence, all the true Admin account is doing is assigning itself full control over all folders & files, negating all potential permission issues, which shouldn't wholly be necessary for the overlay to work, but it has saved me from a lot of potential hitches. If you did have to change your User Account Control setting, then all you need to do is log back in to your original account & in the Command Prompt, without quotations, type in "net user administrator /active:no".

Otherwise, there are two ways to tackle this:

a. Right-click on the parent folder of your affected program, click on Properties -- I apologize for any potential discrepancies as I'm not at my computer -- and then I believe you click on the Permissions tab. Under Advanced, directly assign your User Account with ownership & Full Control.

b. Transfer all documents & AppData from your old account to the new true Admin account. You can then open "netplwiz" and automatically log on to the true Admin account

It's entirely possible that reinstalling Mumble on the true Admin account automatically elevated permissions of Mumble's folders & files to a system-wide Full Control, which is a big reason to use the true Admin account.

First, let's check if your user account has insufficient permissions.

Step 1. Ensure that your User Account Control (UAC) is entirely disabled.
Go to Start, Control Panel. On the top right, set "View by:" to Small icons. Click on User Accounts. Click on "Change User Account Control settings" and set the bar to the lowest level, "Never notify". Click OK and restart if it prompts you.

Step 2. Activating the true Administrator account.
Go to Start, and in the search bar below your programs, type in Command Prompt. Right-click on the program and press "Run as administrator".

Type in, without the quotations, "net user administrator /active:yes"

If it displays that "Access is denied", go back into cmd and type in, without quotations, "sfc /scannow". This will fix integrity issues with your Windows installation.

If it worked, then log off your account & log into the new Administrator account. Ensure that the User Account Controls are properly set to "Never notify" again on your new account, open up Mumble first, ensure that the overlay is enabled, ensure that hl2 is in your whitelist, and then open up Team Fortress 2.

If your account has proper permissions, nothing that was suggested before will make a difference. You can upgrade back to the newest driver release & reinstall GeForce Experience.

Thank you so much!

I don't mean to be a bother, but if you have a moment, could you explain how you went about fixing the item & attribute descriptions?

EDIT: I'm seeing %itemname% appear within crafting tiles still:

http://i.imgur.com/wBrFw2T.png

EDIT 2: Another problem is that some of the spectators' weapons display an arbitrary [unknown] below the icon:

http://i.imgur.com/B8qavCN.png

Only some of the issues supposedly mentioned in the changelog seem addressed, so hopefully it's not something on my end.

Hey, big fan of your HUD here.

I was wondering if you could fix the quickplay resource files (lobbypanel.res, quickplaybusydialog.res, and quickplaydialog.res) to work with today's update that adds advanced features to matchmaking. Hopefully you're still interested in maintaining it.

Thanks for all you've done so far.

EDIT: Also looks like items are being displayed with %itemname% and %attriblist%