EDIT: March 21, 2007 - I figure I'll get this out of the way and add the linkage to my other just created thread that is highly relevant and related to this particular post on many levels. If you're interested in knowing or learning more about why this method below is so useful, after reading this post go read Vista, Admin rights, UAC, and You. Thanks...
Ok, I've been considering this for some time now, and I know we've got a "tips and tweaks" thread stickied at the top but, somehow I think if I post it there it'll just get lost in the muss soooo... without further ado.
Vista is out, and upon us all it seems, and some people - that's some people - are having issues with some software installations, and even just getting the damned things to run properly after they're installed.
The tip I'm about to offer seems pretty simple on the surface, and it is really, but since no one else has come out and flatly stated it with a posting like this one, well, use the tip and report on your experiences if you want; I already know the results from over 950 Vista installs and several thousand pieces of software tested so far in my own experience.
What this tip is meant to do is alleviate some of the most predictable and common issues people are having with Vista: installing software, and once the software is actually installed, running it without issues or loss of data (i.e., you have to keep redoing application configuration/settings every time you run it), or you get errors about permissions, etc.
NOTE: If you're seriously [H]ardCore and you've disabled UAC, or you've enabled the ability to elevate tasks to Administrator level by using either a Registry edit or possibly something from the Group Policy Editor, most of what follows won't apply to you. This tip is designed for Joe Average, consumer that happens to own a computer running Windows Vista - any edition - and is sick of having issues installing and running his software.
Having said that, here's the first part of the tip:
When you get ready to install a piece of software, regardless of what that software is, use the option to right-click on the installer file, typically an .exe of some kind (like setup.exe) or possibly one of those newfangled .msi installer files that are supposed to be better. Regardless of which method is chosen, start by right-clicking on the .exe or the .msi or whatever and choose Run as Administrator on the popup menu that appears.
The only time this might not appear to be an option is if you're installing direct from a CD or a DVD and you just inserted the CD or DVD and AutoPlay started up the installer for you - if that's the case, close the installer application and open Explorer so you can browse the CD or DVD and find the actual stub installer, meaning the setup.exe, the setup.msi or whatever actual installer applicaton exists.
For some people, this is going to be a chore, I know that. They simply want to put in the CD or DVD and install the software and be done with it, and with Vista, and with a lot of older software and even some brand new stuff, that's just not going to work out right. Permission issues, software that won't run, software that doesn't seem to save your settings and you end up redoing them each time you run the software - that is, if you can get the software to run at all <hint, hint> - and other various issues can all be addressed by using this tip to its fullest.
If you are using some AutoPlay function and just letting the installer run off an inserted CD or DVD, well, it's time to learn how Windows installs software in that manner. There's a tiny file called autoplay.inf most of the time on a CD or DVD that Windows looks for when the CD or DVD is inserted. If Windows finds that autoplay.inf, it will read it (it's just a tiny text file with instructions on what to do automatically) and act upon the instructions found within.
Typically that means it'll "run" a specific piece of software, like a setup.exe file, or perhaps a setup.msi or something similar. The point is, the autoplay.inf file contains the name of the executable installer file you're looking for - the one you need to locate so you can right-click directly on the filename and choose Run as Administrator.
You can open the autoplay.inf file by right-clicking on it and choosing Open on the popup menu that appears (NOTE: Choosing Open on the popup menu does not open/run the file itself, it just "opens" the .inf in Notepad so you can read the contents). Inside you'll see something similar to this:
[AutoRun]
OPEN=setup.exe
That's about it, really. It's a very simple file with very basic instructions, sometimes more complex, but the gist is: it'll tell you the specific file it runs to start the application software installer. It might say setup.msi, or <software name>.msi, <software name>.exe, etc - I think you can figure it out from here. It might even list it like this:
[AutoRun]
OPEN=\installer\setup.exe
meaning the installer file is inside the "installer" directory on the CD or DVD and not directly in the root (\) directory.
Moving on...
Once you've located the installer file, be it the *.exe, the *.msi, etc. now's the time to right-click on it and choose Run as Administrator from the popup. If you haven't disabled UAC as mentioned in the NOTE above, you'll get the obligatory popup asking for permission to Continue, which you obviously will click, right? Right.
Install the software, then when the software installation is done - and this is the most crucial part of all so pay attention:
Do not run the application or software or whatever it is you've just installed at the end of the installation. Do not let the application or software installer automatically run the application or software you just installed after it's done; i.e. don't let Acrobat automatically start up after you install it, don't let Microsoft Word start up after you installed Office, etc.
Read that again if you must because it's absolutely critical for this entire tip to have any value at all. The problem with a lot of people installing software is that a lot of application software installers give you the option to "Run <xxx> when the installation is done." option as either a step during the installation or as the last step in the installation itself.
I hope that makes sense there, if not, I'll try to explain it better if people want. I can't say this is "Sticky" material but, I can promise that if people follow it, with each application or software package they wish to install, it'll go a long damned way towards cutting down on the problems that most people are having with Vista.
So, where to from here? Glad you asked, here's the second part of the tip:
Now that the application or software package is installed, and you've done the necessary reboot if you're forced to do it because the application or software is using some type of driver (an all too common thing nowadays), or it just likes being pushy (most software does not require a reboot after the installation; software that does typically needs an update or just needs to be written better), it doesn't matter. The point is the software is now installed and now it's ready to be run for the first time, and this is the second crucial point of the tip.
The first time you run the application or the software package, do the exact same thing meaning right-click on the application or software package launcher and choose Run as Administrator - only this time there's a helpful catch:
You don't necessarily need to locate the *.exe that is the actual application or software package launcher - you can do this from any shortcut the installer created. You can go digging into the Program Files directory (on Vista 32 bit and 64 bit editions), or even the Program Files (x86) directory (the default installation location for 32 bit applications and software on Vista 64 bit editions) and locate the actual .exe file that launches the application or the software package, but doing it from a Start Menu or Desktop or even a QuickLaunch shortcut icon is perfectly acceptable.
So, find a shortcut icon someplace to the software you just installed, or go digging for the actual *.exe file that launches it, right-click on that file, choose Run as Administrator, and as before, on the popup dialogue box that appears asking for you to give permission to continue, click Continue and voila...
That's it.
Following this tip - and I know it seems complicated but, I prefer to give more info than people probably want so they don't come back trying to chew me a new one because I left something out - will typically see you using nearly any application or software package you want under Vista (obviously they need to be Windows apps) without any of the issues, hassles, backlash, problems, situations, etc. that are plaguing people nowadays.
Installing software using Run as Administrator sets the proper Registry key permissions on any keys that are created by the installation program - this is the first crucial way this tip "fixes" a lot of crap people are going through.
Running software the first time using Run as Administrator does basically the same thing but... it also has the added benefit of setting permissions on the user data and application folders required by the software to work properly and ties it to that user account so you don't have these problems with saving data, loss of configuration information (i.e. having to redo the settings each time you run the software, etc).
If you've noticed some software seems to make you redo the window layouts, the fonts, the save folders, options, etc. each and every time you run it, that's why. Just installing with Admin priviledges is only half the battle - you then need to run the software the first time using the same right-click Run as Administrator "trick" and that will force the permissions to spread across any directories or folders the software creates the first time its actually run and ties those permissions to the user account name - and not specifically to anyone that's an Admin, although that's a permission issue you can resolve easily (I just won't cover that with this tip).
Sooooo... if you've read this far, congrats. You should now understand that there's two parts to installing applications and software packages under Vista that can practically guarantee a trouble-free operating system that doesn't nag you anywhere nearly as often as the idiotic "Mac vs PC" ads would have you believe.
I don't recommend disabling UAC, ever. I don't recommend changing elevation priviledges, ever. This stuff can be done on a case-by-case basis and it typically only affects the user one time and never again on an application or software package basis - it's not everyday you're constantly reinstalling a single application or software package and need to keep doing this over and over again, right?
And that's the whole point of this tip:
Do it right the first time.
Hope this helps, and have fun, always...
Ok, I've been considering this for some time now, and I know we've got a "tips and tweaks" thread stickied at the top but, somehow I think if I post it there it'll just get lost in the muss soooo... without further ado.
Vista is out, and upon us all it seems, and some people - that's some people - are having issues with some software installations, and even just getting the damned things to run properly after they're installed.
The tip I'm about to offer seems pretty simple on the surface, and it is really, but since no one else has come out and flatly stated it with a posting like this one, well, use the tip and report on your experiences if you want; I already know the results from over 950 Vista installs and several thousand pieces of software tested so far in my own experience.
What this tip is meant to do is alleviate some of the most predictable and common issues people are having with Vista: installing software, and once the software is actually installed, running it without issues or loss of data (i.e., you have to keep redoing application configuration/settings every time you run it), or you get errors about permissions, etc.
NOTE: If you're seriously [H]ardCore and you've disabled UAC, or you've enabled the ability to elevate tasks to Administrator level by using either a Registry edit or possibly something from the Group Policy Editor, most of what follows won't apply to you. This tip is designed for Joe Average, consumer that happens to own a computer running Windows Vista - any edition - and is sick of having issues installing and running his software.
Having said that, here's the first part of the tip:
When you get ready to install a piece of software, regardless of what that software is, use the option to right-click on the installer file, typically an .exe of some kind (like setup.exe) or possibly one of those newfangled .msi installer files that are supposed to be better. Regardless of which method is chosen, start by right-clicking on the .exe or the .msi or whatever and choose Run as Administrator on the popup menu that appears.
The only time this might not appear to be an option is if you're installing direct from a CD or a DVD and you just inserted the CD or DVD and AutoPlay started up the installer for you - if that's the case, close the installer application and open Explorer so you can browse the CD or DVD and find the actual stub installer, meaning the setup.exe, the setup.msi or whatever actual installer applicaton exists.
For some people, this is going to be a chore, I know that. They simply want to put in the CD or DVD and install the software and be done with it, and with Vista, and with a lot of older software and even some brand new stuff, that's just not going to work out right. Permission issues, software that won't run, software that doesn't seem to save your settings and you end up redoing them each time you run the software - that is, if you can get the software to run at all <hint, hint> - and other various issues can all be addressed by using this tip to its fullest.
If you are using some AutoPlay function and just letting the installer run off an inserted CD or DVD, well, it's time to learn how Windows installs software in that manner. There's a tiny file called autoplay.inf most of the time on a CD or DVD that Windows looks for when the CD or DVD is inserted. If Windows finds that autoplay.inf, it will read it (it's just a tiny text file with instructions on what to do automatically) and act upon the instructions found within.
Typically that means it'll "run" a specific piece of software, like a setup.exe file, or perhaps a setup.msi or something similar. The point is, the autoplay.inf file contains the name of the executable installer file you're looking for - the one you need to locate so you can right-click directly on the filename and choose Run as Administrator.
You can open the autoplay.inf file by right-clicking on it and choosing Open on the popup menu that appears (NOTE: Choosing Open on the popup menu does not open/run the file itself, it just "opens" the .inf in Notepad so you can read the contents). Inside you'll see something similar to this:
[AutoRun]
OPEN=setup.exe
That's about it, really. It's a very simple file with very basic instructions, sometimes more complex, but the gist is: it'll tell you the specific file it runs to start the application software installer. It might say setup.msi, or <software name>.msi, <software name>.exe, etc - I think you can figure it out from here. It might even list it like this:
[AutoRun]
OPEN=\installer\setup.exe
meaning the installer file is inside the "installer" directory on the CD or DVD and not directly in the root (\) directory.
Moving on...
Once you've located the installer file, be it the *.exe, the *.msi, etc. now's the time to right-click on it and choose Run as Administrator from the popup. If you haven't disabled UAC as mentioned in the NOTE above, you'll get the obligatory popup asking for permission to Continue, which you obviously will click, right? Right.
Install the software, then when the software installation is done - and this is the most crucial part of all so pay attention:
Do not run the application or software or whatever it is you've just installed at the end of the installation. Do not let the application or software installer automatically run the application or software you just installed after it's done; i.e. don't let Acrobat automatically start up after you install it, don't let Microsoft Word start up after you installed Office, etc.
Read that again if you must because it's absolutely critical for this entire tip to have any value at all. The problem with a lot of people installing software is that a lot of application software installers give you the option to "Run <xxx> when the installation is done." option as either a step during the installation or as the last step in the installation itself.
I hope that makes sense there, if not, I'll try to explain it better if people want. I can't say this is "Sticky" material but, I can promise that if people follow it, with each application or software package they wish to install, it'll go a long damned way towards cutting down on the problems that most people are having with Vista.
So, where to from here? Glad you asked, here's the second part of the tip:
Now that the application or software package is installed, and you've done the necessary reboot if you're forced to do it because the application or software is using some type of driver (an all too common thing nowadays), or it just likes being pushy (most software does not require a reboot after the installation; software that does typically needs an update or just needs to be written better), it doesn't matter. The point is the software is now installed and now it's ready to be run for the first time, and this is the second crucial point of the tip.
The first time you run the application or the software package, do the exact same thing meaning right-click on the application or software package launcher and choose Run as Administrator - only this time there's a helpful catch:
You don't necessarily need to locate the *.exe that is the actual application or software package launcher - you can do this from any shortcut the installer created. You can go digging into the Program Files directory (on Vista 32 bit and 64 bit editions), or even the Program Files (x86) directory (the default installation location for 32 bit applications and software on Vista 64 bit editions) and locate the actual .exe file that launches the application or the software package, but doing it from a Start Menu or Desktop or even a QuickLaunch shortcut icon is perfectly acceptable.
So, find a shortcut icon someplace to the software you just installed, or go digging for the actual *.exe file that launches it, right-click on that file, choose Run as Administrator, and as before, on the popup dialogue box that appears asking for you to give permission to continue, click Continue and voila...
That's it.
Following this tip - and I know it seems complicated but, I prefer to give more info than people probably want so they don't come back trying to chew me a new one because I left something out - will typically see you using nearly any application or software package you want under Vista (obviously they need to be Windows apps) without any of the issues, hassles, backlash, problems, situations, etc. that are plaguing people nowadays.
Installing software using Run as Administrator sets the proper Registry key permissions on any keys that are created by the installation program - this is the first crucial way this tip "fixes" a lot of crap people are going through.
Running software the first time using Run as Administrator does basically the same thing but... it also has the added benefit of setting permissions on the user data and application folders required by the software to work properly and ties it to that user account so you don't have these problems with saving data, loss of configuration information (i.e. having to redo the settings each time you run the software, etc).
If you've noticed some software seems to make you redo the window layouts, the fonts, the save folders, options, etc. each and every time you run it, that's why. Just installing with Admin priviledges is only half the battle - you then need to run the software the first time using the same right-click Run as Administrator "trick" and that will force the permissions to spread across any directories or folders the software creates the first time its actually run and ties those permissions to the user account name - and not specifically to anyone that's an Admin, although that's a permission issue you can resolve easily (I just won't cover that with this tip).
Sooooo... if you've read this far, congrats. You should now understand that there's two parts to installing applications and software packages under Vista that can practically guarantee a trouble-free operating system that doesn't nag you anywhere nearly as often as the idiotic "Mac vs PC" ads would have you believe.
I don't recommend disabling UAC, ever. I don't recommend changing elevation priviledges, ever. This stuff can be done on a case-by-case basis and it typically only affects the user one time and never again on an application or software package basis - it's not everyday you're constantly reinstalling a single application or software package and need to keep doing this over and over again, right?
And that's the whole point of this tip:
Do it right the first time.
Hope this helps, and have fun, always...