If you choose "Install missing packages on-the-fly: Ask me first", MiKTeX will ask you each time whether a package should be installed for all users or only for you. That way you can install all packages into the main MiKTeX admin folder.
Yes, it is default behaviour of MiKTeX to install missing packages “on-the-fly”, but this can be changed in the Options dialogue. All in this way installed packages go into %APPDATA%\MiKTeX\<version>\
(<version>
is 2.9 at time of writing), the MiKTeX variable is UserInstall
. Since Windows Vista %APPDATA%
resolves to C:\Users\<username>\AppData\Roaming
, therefore your observation.
But this needs an active connection and a responding download mirror. At least one of these two things did not work in your case. If it was the mirror you can take a look on the CTAN mirror monitor Status of CTAN Mirrors, and if necessary in MiKTeX settings change the active mirror (MiKTeX Options, in tab “Packages” the first line shows the active MiKTeX repository and on the right you can change it).
I prefer to install all packages with the Package Manager, but this needs to be done on a regular basis, about once a week, and of course one needs enough disk space. In the rare cases, when I was asked for installation, I stopped this and ran the installation with the package manager. (Note, that this is different from, what is usually meant with “manual installation”! You already linked to the according question.)
All with the package manager installed packages go into the main MiKTeX tree (see Root 3
in your question), if you made the update in admin mode or in single user installation with writing rights in this folder. If you did a user mode installation packages will always be installed in UserInstall
.
One would expect, that installation in admin mode goes into CommonInstall
, what is the same folder in your case. But on my system this is not used, the folder, to whome CommonInstall
points, does not exist!
Other related questions, at least partially:
Best Answer
The original command is
mthelp
, as noted by Torbjørn, to be used on command prompt. Latertexdoc
was introduced as alias formthelp
, so Harish’s hint is valid, as well. Executemthelp -?
(or withtexdoc
) for command line options (Note, that MiKTeX’stexdoc
does not understand all command line options from TeX Live’stexdoc
and vice versa.)To quote Ulrike Fischer from her answer to the related question How to force MikTeX' texdoc to open package manuals with a PDF reader rather than the DVI viewer? (read also the other answers!):
In addition:
By simply writing
mthelp ⟨supposed-package-name⟩
it can happen that a local HTML page is produced and opened with your default browser showing the found results. This local HTML file is on my machine saved inC:\Users\Steffen\AppData\Local\MiKTeX\2.9\miktex\mthelp\
(in general the “UserData” root of MiKTeX, cf. the “Additional Note” in Create a local texmf tree in MiKTeX). It does not matter here, whether I invoked the search withmthelp
ortexdoc
.A good example would be
mthelp dickimaw
. This will produce a HTML file with 3 results, if the Dickimaw tutorials are installed:But typing
mthelp --view dickimaw
will open the first result of them, i.e.dickimaw-minexample.pdf
.Note, that there is a certain amount of packages, where the name of main documentation is different from the package name. TikZ is a good example where you will be without success:
You have to know that TikZ is part of of the pgf bundle and described in
pgfmanual.pdf
, somthelp pgfmanual
will open this file in you default PDF viewer.I am meanwhile used to look directly in the
doc
subtree of MiKTeX. But when you use the feature of installing packages “on-the-fly”, these are found in your user profile, according to MiKTeX denomination in “UserConfig” (cf. again “Additional Note” in Create a local texmf tree in MiKTeX).