Never trust Mr. Softy
Apple pens in its users, domesticates them, and milks them, but at least it treats them nicely and makes them feel good about themselves. Microsoft is like a big, fat ex-boyfriend who shows up at his former girlfriend's apartment drunk and unannounced, insists on having sex, then throws up in her bed after passing out. It's more than just the regret one feels after being forced to deal with Windows, it's the time one has to spend to clean everything up afterwards.
Now, Spacebunny runs Windows 7, and in the course of daily events she made the rookie mistake of allowing Skype to update itself. Naturally, the update immediately caused Skype to stop working on her machine. She tried a few things and then turned the matter over to me because I so enjoy trying to work around Microsoft's idea of making the interface easier. The problem is a fairly common one and is described here by one of the many people who have run into this problem:
"Every time I try to download the newest version of Flash Player, I get an error message stating that I have insufficient user permissions. I am using Windows 7, it's my home computer, I am the administrator (I know because I checked) and no one else uses my computer. I've done everything I can (including creating a new Admin account - still didn't work)."
None of the suggested fixes worked. So, I went through all the various suggestions I could find online, including those on the Microsoft Forum. Most of them were entirely worthless. Seriously, I want to punch the fat, self-satisfied power users who that telling people how to click through the relevant dialogue boxes is a legitimate answer. But the problem obviously isn't people not knowing how to use the operating system, since many of the messages clearly indicate we're dealing with people who know what administrator status is, the problem is that clicking through the obvious dialogue boxes doesn't freaking work!
I did all the obvious things. I even downloaded a special program to unlock the folder, which unlocked the folder but still didn't grant whatever privileges were deemed necessary to simply delete the damned file. Logging in as an administrator didn't work, creating a new administrator didn't work, running the installer as an administrator didn't work, unlocking the folder didn't work, absolutely nothing worked. Even Markku couldn't figure out how to fix the problem within a Microsoft paradigm short of reinstalling Windows. That being said, he did come up with the ultimate answer from the start, which is often apt when one is dealing with a Microsoft product: the first step is to tell Microsoft to fuck off.
Let me explain. The core problem is that the newer Microsoft operating systems do something incredibly stupid. In order to navigate all the complex crap that now surrounds diverse aspects of the increasingly crufty operating system, many installation programs now create a virtual administrator that has control over the various files and directories being used during the installation process. This virtual administrator does not exist, and by virtue of not existing, is not synonymous with any of the actual human administrators who actually use the computer.
Perhaps you already see the intrinsic problem there. If something goes wrong during the installation or update process, the real administrators do not have access to the files that were under the control of this nonexistent administrator. The real admin can see what's there, but he can't do anything about it. He doesn't have access and he can't give himself access. And if that protected file or folder is one that is required by an application installer that has somehow gone haywire, the user is screwed and will not be able to reinstall or use that application without either restoring a previous OS state or completely reinstalling Windows.