Easy fixes for common install problems in Vista
If you’ve made the switch to Vista like I have, chances are you’ve run into issues. Installs that fail with strange errors (error 2739 and others) or you get something saying you don’t have permission to change a directory, abort or retry.
Both are tre annoying and don’t offer much help for a solution. In fact I had a ton of trouble installing my Blackberry software a while back. I did get it to work but this morning I had the same problem installing the newest version of Skype. A quick look in the forums reminded me of the solution.
Launch the command prompt as Administrator (right-click the shortcut to see this option) and run these commands at the prompt:
regsvr32 c:\windows\system32\vbscript.dll
regsvr32 c:\windows\system32\jscript.dll
That will often do the trick, but that wasn’t enough to get the Skype install to work. I was still getting error messages. The final trick is to run the installer as Administrator. Same as the command prompt, right-click it and select “Run as Administrator” and you’ll have to approve the action too.
After doing all this I could finally get Skype 3.2 installed.
The question is, why can’t software makers get this right? What is it about Vista that is making it so hard for them to make installers that work? I see this on a regular enough basis, and given that RIM and Skype are no slouches in the dev department, I am left the conclusion that Vista is causing headaches for everyone, users, developers, and support people alike.
I just hope a fix is coming soon.
Tags: Vista tips, Vista tweaks, Vista troubleshooting, Vista installer problems
Related Stories
POSTED IN: Vista, Software tips
3 opinions for Easy fixes for common install problems in Vista
MattB
May 25, 2020 at 1:08 pm
Hello,
Tried your instructions and got a bit further with installing skype 3.2 but after I have agreed to terms and clicked next the installer will “start” but just hangs ad infinitum. Task manager needed to cancel the install too. Any ideas?
MattB
May 25, 2020 at 3:23 pm
It worked after a re-start. Should have thought of that earlier! Thanks Tris.
Tris Hussey
May 27, 2020 at 10:38 am
Matt you’re very welcome. It’s a handy trick to know. I come back to these posts often to remember the file names of the DLLs … I could print them out, but that would be cheating!
Have an opinion? Leave a comment: