vs Missing Help Viewer (Helpviewer) how to handle

Refer to a tutorial on the Web, do a record here!

1. Locate the Packages\help path in the iOS image installation file.

2. Open the console command, CD to this path

3. Install by typing the following command in the console

msiexec/i Help3_vs_net.msi Vs_setup=1

Sometimes there will be a click Help manager, the manager has been stuck in the start page situation, even if multiple unloading load help viewer also can not solve, this situation seems to have no other way, click on the Control Panel, uninstall the program, to vs then repair can, and sometimes even fix the problem is still not resolved, You can try to remove the Help Viewer (helper Manager) and reload it again in the way above, but I can't.

About the usage of msiexec:

The Windows Installer technology uses Msiexec.exe for installing MSI and MSP packages. This tool gives your full control over the installation process, allowing your to set:

Windows installation technology uses Msiexec.exe to install MSI and MSP packages, which gives you complete control of the installation process, allowing you to set: Install options (install, uninstall, Administrative install, advertise a product) installation options (install, uninstall, Administrator install ...) display options (full, Basic or no UI during the Insta llation) Performance options (complete, Basic, or no UI at installation) Restart options (if the machine would be a restarted after the installation) restart option (after installation to reboot) Logging options Log option Update options (apply or Remove Updates) option (applying or removing update) repair options (only for the installed P ackage) repair option (only for a package that is already installed) public properties which is used by the installation when the software is installed (such as the current user and all users)

The usual form of the MSIEXEC command line was this:

The msiexec command uses the following:

Msiexec.exe <install_option> <path_to_package> [package_parameters]

Install OptionsInstallation options

When a installation package is launching, you can set the install type through these options:

To install a package Yes, you can select the following options:

msiexec.exe [/i][/a][/j{u|m|/g|/t}][/x] <path_to_package>

/I-Normal Installation General installation /A-Administrative Install Administrator form /j-Advertise the product u-advertise to the current user installs only m-advertise to all users/g-the language ident Ifier used by the advertised package/t-Apply transform to advertise package / x-Uninstall the package removal

Sample command line:

Example

msiexec.exe/i "C:\Example.msi"

Display Options

The user interface level of the installation can is configured according to the target environment. For example, a package distributed to clients should has a full UI, while a package deployed through Group Policy should There are no user interface. Msiexec.exe sets the UI level of the installation through these options:

 /I <path_to_package> [/quiet][/passive][/q{n|b|r|f}]

/quiet-Quiet mode (there is no user interaction) /passive-Unattended mode (the installation shows only a progress bar) / Q-Set the UI level:n-No UI b-basic UI r-reduced UI F-full UI

Sample command line:

msiexec.exe/i "C:\Example.msi"/qn

Restart Options

Sometimes an installation overwrites files which is in use or needs to reboot the machine in order to finish it. The reboot policy used by the installation can set through these options:

 /I <path_to_package> [/norestart][/promptrestart][/forcerestart]

/norestart-The machine won't be restarted after the installation are complete /promptrestart-the user would be prompted if a reboot is required /forcerestart-The machine would be restarted after the installation are complete

Sample command line:

msiexec.exe/i "C:\Example.msi"/norestart

Logging Options

When debugging the installation package you can use the multiple logging parameters in order to create a log. This log would contain different information for each parameter your use:

msiexec.exe [/i][/x] <path_to_package> [/l{i|w|e|a|r|u|c|m|o|p|v|x+|!| *}][/log] 
<path_to_log>

/ L-Enable logging I-include status messages w-include non-fatal warnings e-include all error messages a-mention whe N An action is started R-include Action-specific Records u-include user requests c-include the initial UI parameters M-include out-of-memory or fatal exit information O-include out-of-disk-space messages P-include terminal Propertie s v-verbose output x-include extra debugging information +-Append to an existing log file! -Flush each line to the log *-log all information, except for V and x options /log-the equivalent of /l*

Sample command line:

msiexec.exe/i "C:\Example.msi"/l*v "C:\package.log"

Update Options

The Windows Installer command line can apply or remove updates (patches for example) through these options:

msiexec.exe [/p][/update][/uninstall[/package<product_code_of_package>]] 
<path_to_package>

/ P-Install a MSP patch. When installing a patch silently, you need to set reinstallmode the property to "Ecmus" and REINSTALL to "all". Otherwise the patch would simply update the MSI cached on the target machine. /update-Apply updates (if there is multiple updates, you can separate them through the " ;"character). /uninstall-Remove an update for a product (if there is multiple updates, you can separate them through the " ;"Character"/package-specifies the package for which, the update is removed.

Sample Command lines:

msiexec.exe/p "C:\MyPatch.msp"
msiexec.exe/p "C:\MyPatch.msp"/qb reinstallmode= "Ecmus" reinstall= "All"
Msiexec.exe/update "C:\MyPatch.msp"
msiexec.exe/uninstall {1bcbf52c-cd1b-454d-aef7-852f73967318} 
  / Package {AAD3D77A-7476-469F-ADF4-04424124E91D}

The above command line, the first GUID is the Patch identifier GUID and the second one are the Product Code of the MSI fo R which the patch was applied. Repair Options

If you have a installed package, you can use the Windows Installer command line for repairing it:

msiexec.exe [/f{p|o|e|d|c|a|u|m|s|v}] <product_code>

/ F-Repair a package P-repair only if a file is missing O-repair if a file was missing or an older version is installed E -Repair if file is missing or an equal or older version is installed D-repair if a file is missing or a different vers Ion is installed C-repair if a file was missing or the checksum does not match the calculated value a-forces all files To is reinstalled U-repair all the required user-specific registry entries M-repair all the required computer-specific Registry entries S-repair all existing shortcuts V-run from source and recache the local package

Sample command line:

MSIEXEC.EXE/FA {AAD3D77A-7476-469F-ADF4-04424124E91D}

The above command line, the GUID is the Product Code of the MSI which would be repaired. Set Public Properties

The name of a public property is contains only uppercase letters (for example property). This type of properties can is set through the command line like this: property= "value".

Sample command line:

msiexec.exe/i "C:\Example.msi" my_prop= "MyValue"