If the latter I need to take it out back and beat it with a stick, maybe...

Ever since AVG screwed up what is now a data drive, I've been playing World of Warcraft by using a shortcut to access the game that is still on that drive. I simply put the shortcut on my current main drive (I'll call it Drive C for uniformity) and it draws data from what I'll call Drive E for uniformity. This has worked perfectly since the problem.

But today the game was patched and players are blocked from entering the game without the LATEST version. So I launch the game and it starts to download the patch, but the patch won't install because the game is on Drive E and the patch apparently assumes it's on Drive C. The patch downloads via the game launcher, and then just stops.

So I put the game setup CD in my CD drive (this is Drive F), figuring I have to finally install the game properly on Drive C. A popup instantly appears saying, "Windows cannot access the specified device, path, or file. You do not have appropriate permissions."

WTH? When I first set up this computer, with what is now Drive E, being my main hard drive, the game installed just FINE.

I go into My Computer, access Drive F and right click on Setup to Run As Administrator. That produces a popup saying, "Sorry the installer was unable to start up. You may be out of disk space."

Drive C has over 350 GB free space on it. Maybe Drive F doesn't, but it's not SUPPOSED to, it's a DVD drive, not a hard drive!

I cannot go to Drive E and try to either update or uninstall the game there because that drive is screwed up, absolutely ANY action whatsoever I try to do on the computer and it stops responding. It just hangs for years and years and eons and eons (and every ice age in between) and hitting any key whatsoever on the keyboard and the window will produce a "Not Responding" message.

I run my computer, it does not run ME. My computer had better find an agreeable solution quick while I go shopping for a nice stout club. If it hasn't gotten that solution by the time I return, then it's time for a little "talk" out back...

EDIT: I tested a theory by entering BIOS setup and instructing my computer to boot to Drive D, my second hard drive (I have three hard drives). Drive D allows the game installer to run without any problems, and it is running the same version of Windows Vista as Drives C and E. This makes me believe that Windows UAC is not the culprit here. I will try disabling my Comodo Firewall and then if necessary, my Avast anti-virus. I will provide another update once this is done.

EDIT 2: Bingo. I disabled Comodo Firewall Pro and the game is busy installing itself on its new home on Drive C. I would simply delete this post altogether but apparently we cannot delete our own posts on these forums. Therefore the moderators are called on to either delete the post or mark it Solved. I don't blame my computer for coming here and asking for help though.... I WAS in the process of finding a nice stout club in order to show it that I run my computer, not the other way around... >;) hehehehe

That's interesting, most people love Comodo Firewall.

Personally I think the built-in Windows firewall works perfectly well.

i don't like anything slowing down my computer and comodo was the worst. not including antivirus programs. when i give a review they are for everyday average users, not power users. no normal user would find comodo one bit useful. it fights and prompts everything, even normal windows functions. no one wants to see over 60 comodo prompts in less than five minutes. then uninstalling it is even worse, it fights right up to the end. no one needs a firewall like this. i've never heard a good argument for it, just a bunch of annoying comments from people who think lockergnome is a place for an intelligent conversation. comodo doesn't even remember the settings you tell it. everyone says you have to set it up, normal people are lucky if they can do a hard shut down with this thing running. eset's firewall set on interactive with my router is all i need. just my opinion from what i've experienced, not what i've heard...