Installing msu updates. Installing Windows CAB and MSU files manually

& nbsp & nbsp One of the most common ways to disable automatic Windows updates is to disable the Center service. Windows updates”. At first glance, this is the right decision, ensuring the achievement of the ultimate goal in the simplest way, but in fact, this approach can lead to big problems in the future when installing new programs. The fact is that during installation, many software products update the components necessary for their functioning in Windows environment, including components that are Windows updates. If there are no updates required for the program being installed, they are usually installed offline. The offline update installer is used for this. wusa.exe and the Windows Update Service. Specifically, the installer wusa.exe can be executed with the parameter / quiet, which sets the "quiet mode" of the installation of updates without any messages on the screen. In addition, the installer may incorrectly process the results of operations for installing necessary Windows updates. If Windows Update is disabled, at best the error message 0x80070422 will be displayed on the screen:

In the worst case, you may receive a fatal error message while installing the program, or, even worse, there will be no error messages, but the installed software will not work. As a result, the user can spend a lot of time and effort solving the problem that he himself caused by disabling the Windows Update service.

So, the right approach Disabling Automatic Updates assumes that Windows Update is not being disabled. To save system resources, you can set the startup type to "Manual". The update service must be configured for the "Do not check for updates (not recommended)" mode:

Control Panel - Windows Update - Configure Settings

To avoid displaying warnings from the Action Center, you need to disable the corresponding notification:

Control Panel - Support Center - Configure Support Center.

With these settings, the automatic update Windows and the entire functionality of the offline update installer will be preserved wusa.

Sometimes a situation arises when the cause blue screens death is the installation of another update from Micrtosoft. It often happens that there is no time to figure out who is to blame, one of the driver developers (say, antivirus) who did not take into account something, or did something wrong, or the Microsoft developers themselves, we just need to work in the system. There are several ways to remove installed updates.

Method 1. Removing updates through the Add / Remove Programs snap-in

We go into the snap-in of the installation of uninstallation of programs, you can use the interface (Start / Control Panel / Add or Remove Programs) through command line, run appwiz.cpl. Select on the left "View installed updates"

There is a column for the installation date, by which you can sort these updates and remove the desired one.

Method 2. Via the command line

Using wusa command (only works for Windows 7, Server 2008 R2).

You need to run cmd.exe or far.exe with admin rights and execute

wusa / uninstall / kb: update id (where update id is the KB number of the update, for example wusa / uninstall / kb: 2511250)

Method 3. We use wusa and the downloaded update

Download the required update from Microsoft Download Center and save it to some directory, for example c: emp. Run cmd.exe or far.exe with administrator rights and execute the following command:

wusa / uninstall (full hotfix path)

For instance:

wusa / uninstall C: TempWindows6.1-KB980302-x86.msu

Then the uninstall dialog box will appear.

Method 4. Using PKGMGR

1. You need to download the update that you want to remove from Microsoft Download Center and save to some directory like c: emp.

2. Run cmd.exe or far.exe with administrator rights. Run at the command line

3.expand -f: * (update name).msu (destination folder)

The command will unpack the msu file and save the original files in the destination folder

4. Create another empty directory, for example c: emp123

5. Run the command

start / w pkgmgr / m: (full hotfix name).cab / up / s: c: emp123

Where full hotfix name is the destination folder from step 3

Removing service packs

A separate topic is the removal of service packs. This requires:

1. Download the service pack you want to remove from Microsoft Download Center and save to some temporary directory like c: emp

2. Run cmd.exe or far.exe with the required administrator rights.

3. Execute the command

(service pack name)/ x: (destination folder)

For instance,

C: TempWindows6.0-KB936330-X86.exe / x: C: Temp2

All service pack files will be extracted to c: emp2 directory

4. You must select a separate empty directory, for example c: emp3

5. It is necessary to execute the command

start / w pkgmgr / m: (full service pack name).cab / up / s: c: emp3

Post Views: 535

Sometimes wusa.exe and others errors system errors EXE issues may be related to issues in the Windows registry. Several programs can share the same wusa.exe file, but when these programs are uninstalled or changed, sometimes orphaned (invalid) EXE registry entries are left behind.

Basically, this means that while the actual path to the file may have changed, its incorrect former location is still recorded in the Windows registry. When Windows tries looking up these incorrect file references (file locations on your PC), wusa.exe errors can occur. In addition, malware infection may have corrupted the registry entries associated with Windows 7 Home Premium. Thus, these invalid EXE registry entries need to be repaired to fix the root of the problem.

Manually editing the Windows registry to remove invalid wusa.exe keys is not recommended unless you are PC service professional. Errors made while editing the registry can cause your PC to malfunction and cause irreparable damage to your operating system. In fact, even a single comma in the wrong place can prevent your computer from booting!

Because of this risk, we highly recommend using a trusted registry cleaner such as %% product %% (Developed by Microsoft Gold Certified Partner) to scan and repair any wusa.exe-related registry problems. Using a registry cleaner automates the process of finding invalid registry entries, missing file references (like the one causing your wusa.exe error), and broken links within the registry. Before each scan, a backup copy that allows you to undo any changes with one click and protects you from possible damage to your computer. The best part is that fixing registry errors can dramatically improve system speed and performance.

Warning: Unless you are an experienced PC user, we do NOT recommend manually editing the Windows registry. Incorrect use of Registry Editor can lead to serious problems and require reinstall Windows... We do not guarantee that problems resulting from improper use of Registry Editor can be corrected. Your use of the Registry Editor is at your own risk.

Before manually restoring windows registry. You need to create a backup by exporting a portion of the registry related to wusa.exe (eg.Windows 7 Home Premium):

Click on the button To begin.
Enter " command" v search bar ... DO NOT PRESS YET ENTER!
Holding the keys CTRL-Shift on the keyboard, press ENTER.
A dialog box for access will be displayed.
Click on Yes.
The black box opens with a blinking cursor.
Enter " regedit" and press ENTER.
In the Registry Editor, select the wusa.exe-related key (eg.Windows 7 Home Premium) you want to back up.
On the menu File choose Export.
In the list Save to select the folder where you want to save the backup Windows key 7 Home Premium.
In field File name type a name for your backup file, such as "Windows 7 Home Premium Backup".
Make sure in the box Export range value selected Selected branch.
Click on Save.
The file will be saved with the extension .reg.
You now have a backup of your wusa.exe-related registry entry.

The next steps for manually editing the registry will not be described in this article, as they can most likely damage your system. If you would like more information on manually editing the registry, please see the links below.

Recently, in the news about fresh cumulative updates, we began to give links where you can download the .cab or .msu data files of the assemblies. In this article, we will figure out why they are needed, and how to use them.

What are CAB and MSU files

Windows 10 has several file formats that are used to update certain system components. This:

ESD files... They are encrypted and highly compressed ISO images. Used to install major updates (assemblies that change not only the index, but also the major number). With their help you can, for example,.
CAB or MSU files... They are, one might say, archives. Used to install small updates - cumulative, security updates, Adobe updates Flash Player etc.

All mechanisms for working with these files are built into the system. These are the ones that Update Center uses - it just downloads desired file, and then automatically does what is described in this manual. The disadvantages of this approach are the inability to install any updates offline, which some users need from time to time.

I note right away that in Windows 10, the CAB or MSU file of some cumulative update also contains all the previous cumulative updates! There is no need to first, for example, install build 14393.187, then - .189, then - .222. You just need to install the latest package right away.

Where to download the Windows 10 MSU update file

How to install CAB and MSU

Download the CAB or MSU file.
Move it to a folder with some short path. That is, it is better that the file path is, for example, C: \ CAB \ update.cab, but not C: \ Users \ Public \ Downloads \ Folder \ CAB Files \ CabFile1 \ update.cab.

Installing CAB files

Installing MSU files

With them, everything is a little easier. They can be installed even by simply double-clicking on them. But there is a way to do it through the console as well.

Hello dear readers.
Today, as I promised you, I will tell you about the most popular tools that create software installers.
Many of them are very simple, so they can be used not only by programmers and software manufacturers, but also by those who want to assemble an installer with their own hands.
However, the assembly of installation packages is not the topic of this article, the topic of my article: what basic keys are supported by certain installers, how to use them, and how to determine which installer is used for a particular program.

InstallShield

Perhaps I'll start with the most voluminous software, the most beloved by large commercial software developers. InstallShield is a powerful professional tool for creating reliable installation packages.

With the help of Project Assistant, the developer goes through all the stages of creating an installer step by step. No training is required, all the basic features of InstallShield X Express can be learned in less than one day. Full integration with the Visual Studio .NET development environment, support for .NET, Linux, Web services and applications for mobile devices.

You can meet him very often in paid products, for example:

As a rule, such installers do not cause any difficulties, it is enough to run them with the “S” key, and the program will be installed in quiet mode.
Note: If the “wait” parameter does not work, try using the “SMS” key
Example:

Start / wait setup.exe / s / sms

How to determine if the Install Shield was used to package the installer

Open the file properties, on the "Details" tab in the "Description" and "Original file name" items, as a rule, the value "setup.exe" will be indicated, and in the "Product name": "InstallShield".
In addition, by running such an installer for a typical installation, as a rule, you will come across the following words:
InstallShield Wizard
Welcome to the InstallShield Wizard for xxxxxxx
The InstallShield (R) Wizard will install, etc.

Naturally, all this can be written in English as well.

Windows Installer Service (* .msi)

Well, what can I say about this ... Technology Windows Installer Service (MSI) is the de facto standard in the world system administrators engaged in the distribution and support of software for desktop and server Windows versions... The MSI format is supported by all major configuration management systems (Microsoft SCCM, CA Unicenter, and many others), and for some software distribution systems it is even the only supported format.

All installers packed with using Windows Installer have the extension “* .msi”.
Examples of programs:

This type of installers supports the following keys for quiet installation:
"Qb" and "QN".
When using the "QB" key, the installation progress will be displayed, but no questions will be asked to the user, and the "Cancel" button will not be displayed.
Example:

Start setup.msi / qb

Next key: “qn”
When using this key, the installation process will be completely hidden. The installation progress will also not be displayed.
Example:

Start setup.msi / qn

It should be noted that some programs require a computer restart after installation. To avoid this, use the properties (REBOOT = ReallySuppress) enclosing it in quotes along with the key.
Example:

Start setup.msi "/ qb REBOOT = ReallySuppress"

Using the InstallShield * .msi extension

Starting with version 7, InstallShield can create files with the "* .msi" extension. they in turn can be separate files and in conjunction with setup.exe,
For example as OBI
The latter, in turn, are of two types:
InstallScript MSI and Basic MSI. InstallScript MSI uses traditional InstallShield keys. Basic MSI is another interesting story.
To automatically install an application using Basic MSI, you need to specify the "/ s / v" ... "" switches. The ellipsis must be replaced with keys that must be passed directly to the Windows Installer (msiexec). In other words, if you want to install the application completely invisibly and avoid rebooting, then use this command

Start setup.exe / s / v "/ qn REBOOT = ReallySuppress"

Windows * .msu offline update installer

Due to this information often required, edited the article :-), adding the keys for * .msu to it as well.
msu is offline installers Windows updates. Once you download the updates, you can install them even without the presence of the Internet and you don't have to download them again.
All of these installers have a * .msu extension and support the following command line switches.

/ quiet - quiet mode with no user interaction. All windows will be hidden. If a reboot is required after the update, it will be performed.

/ norestart - Use this switch with quiet to avoid restarting.

/ warnrestart - When used with quiet, warns that a restart will take place.

/ promptrestart - When used with quiet, a prompt will appear asking to restart the computer.

/ forcerestart - When used with quiet, a so-called forced restart will be performed, i.e., all applications will be forcibly closed and the computer will restart.

/ log - Sets the logging and path to the log file.

Start c: \ updates \ kb3456246.msu / quiet / norestart /log:update.log

Inno setup

An excellent, free tool for creating installers that supports scripts in the PASCAL language, it is quite easy to learn and convenient to use.
Inno setup can register libraries and ActiveX components, Create encrypted installers, modify the registry, and also run external applications, but this is only a small part of what Inno Setup can do, even too little ....
It should be noted that the help system is reasonably well written and backed up by numerous examples.

Inno Setup is not inferior to many systems for creating installers, and leaves some of them far behind in terms of convenience and capabilities, although it is free to tell the truth, I like it more than all those listed in this article, which helped me out many times.

Recently, Inno Setup has been increasingly used to create installation packages, not only by developers free software but also commercial products, for example:

Hmm, that I signed it, I will be about the main thing.

Inno Setup supports two main keys for silent installation, they are "SILENT" and "VERYSILENT".
Example:

Start setup.exe / verysilent
Start setup.exe / silent

Sometimes a small problem arises: a window pops up asking if you want to continue with the installation. To hide this window, use the key “SP-“.
Example:

Start setup.exe / VERYSILENT / SP-

How do I know if Inno Setup is being used to package a program?

Run the installer, in the window that opens, open the system menu (ALT + SPACE "Space")
Select "ABOUT Setup" or "About",
A window will open with something like this:
About Setup
Inno Setup version 5.4.0 (a) Copyright (C) 1997-2010 Jordan RussellPortions Copyright (C) 2000-2010 Martijn LaanAll rights reserved. Inno Setup home page: http: //www.innosetup.com/RemObjects Pascal Script home page : http: //www.remobjects.com/psInno Setup Preprocessor home page: http: //ispp.sourceforge.net/
OK

Nullsoft Scriptable Install System (NSIS)

Nullsoft Scriptable Install System (NSIS) - the program is designed to easily and quickly create professional installation packages. The program allows software developers to create a compressed win32 exe-file, with the ability to check its integrity. Has no limitation on the number of files included in the distribution kit. Uninstall function is supported. Built in own virtual machine turns this product into a complete professional tool.
Examples:

Installers created with the free NSIS run with the “S” key.
Example:

Start setup.exe / S

Be careful, the key must be in uppercase, otherwise it may simply not work.
You can use the “D” key to specify the installation directory.
Example:

Start setup.exe / S / D = c: \ myprogram

How to determine the use of NSIS

All installers created with NSIS have a very similar interface, study carefully the installation process of Winamp, and you can easily determine if NSIS is being used.

WISE Installer

After digging around on the Internet, here's a nice description I found for it:
Wise for Windows Installer enables professional developers to quickly create robust packages. MicrosoftI using the latest technologies Windows Installer from Microsoft. The unique features of Wise for Windows Installer help small and large development teams create installation packages for all types of platforms, including workstations and handheld computers, application and web servers, and mobile devices Windows Mobile, Windows CE, Pocket PC, Microsoft .NET Compact Framework, Palm OS and smartphones.

Wise Installation Studio allows you to effortlessly create installation packages of applications for operating system Windows Vista, 64-bit versions of Windows and the mobile platform Windows Mobile 5. This package supports the Windows Installer (MicrosoftI) format, and also has its own format - WiseScript (.EXE).

Users will also be able to take advantage of the innovative Altiris Software Virtualization Solution technology embedded in Wise Installation Studio, which creates virtual application archives (.VSA) and ensures that there is no conflict between the products being installed.

Moreover, a new version Wise Installation Studio integrates with Nalpeiron's PRO-Tector Standard package. This solution allows developers to create trial versions software products and provides reliable protection of intellectual property from illegal use.

Only this is bad luck, it looks like the project has died ...
well, okay, let's not talk about sad things ...

Installers created with WISE Installer accept the standard "S" key.
Example: