Installing CAB and MSU files for Windows updates manually. Uninstalling updates from Microsoft Wusa command line options

Sometimes wusa.exe and other EXE system errors can be related to problems in the Windows registry. Several programs can use the wusa.exe file, but when those programs are uninstalled or modified, sometimes "orphaned" (incorrect) EXE registry entries are left behind.

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

Manually editing the Windows registry to remove invalid wusa.exe keys is not recommended unless you are PC service professional. Mistakes made when editing the registry can render your PC inoperable and cause irreparable damage to your operating system. In fact, even one comma placed 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, you can automate the process of finding corrupted registry entries, missing file references (like the one causing the wusa.exe error), and broken links within the registry. Before each scan, a backup copy is automatically created, allowing you to undo any changes with one click and protecting you from possible damage to your computer. The best part is that eliminating 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. Using Registry Editor incorrectly may cause serious problems that may require you to reinstall Windows. We do not guarantee that problems resulting from incorrect use of Registry Editor can be corrected. You use Registry Editor at your own risk.

Before you manually repair your Windows registry, you need to create a backup by exporting a portion of the registry associated with wusa.exe (eg. Windows 7 Home Premium):

Click on the button Begin.
Enter " command" V search bar... DON'T CLICK YET ENTER!
While holding down the keys CTRL-Shift on your keyboard, press ENTER.
A dialog box for access will be displayed.
Click 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 select Export.
On the list Save to Select the folder where you want to save the Windows 7 Home Premium key backup.
In the field File name Enter a name for the backup file, for example "Windows 7 Home Premium backup".
Make sure the field Export range value selected Selected branch.
Click Save.
The file will be saved with extension .reg.
You now have a backup of your wusa.exe-related registry entry.

The following steps for manually editing the registry will not be described in this article, as they are likely to damage your system. If you would like more information about editing the registry manually, please check out the links below.

Setting up UltraVNC Connecting to the server Installing and configuring the UltraVNC SC repeater (Single Click) - remote assistance without first installing the UltraVNC server
UltraVNC is an excellent solution for providing remote assistance. The connection is made directly to the Windows console session, i.e. you always see on the screen what the user of the remote computer sees. Using the repeater utility, you can configure access to servers on a local network located behind a NAT router, while only one port needs to be forwarded on the router. Can also be used for presentations. The program is free. Installing UltraVNC. First you need to download the distribution kit, drivers and repeater (if needed).
UltraVNC official website: http://www.uvnc.com/
Download section: http://www.uvnc.com/download/
At the time of writing, the latest version is 1.0.8.2. You can only download the client. Versions available for both win32 and x64.
Latest drivers from...

Setting up redirection in IIS in pictures Download the URL Rewrite module and install it. Go to IIS. Select the desired site. On the right select the item " URL Rewriting"In the window that opens, press RMB and select the item: " "In the window that opens, press RMB and select" Add override scheme". Enter a name for the scheme (any). The override scheme window will open. Next RMB =>" Add mapping entry" and enter the source and destination addresses. Note: source address must be relative and destinations must be absolute Let's go back to the window" View override schemes". press RMB and select the item " Add rules"Choose a template" Rule with override scheme"We install Select rule action: Redirect. Select override scheme: the newly created scheme. Click OK. Everything is ready.

You must first install Lamp-server. Starting from Ubuntu 7.04, LAMP can be installed using Tasksel. To do this you need to run the command: sudo tasksel install lamp-server During installation, you will be asked for a password for the MySQL database administrator. Don't forget to install the php5-ldap php5-imap modules. sudo apt-get install php5-ldap php5-imapLdap module will start working immediately after Apache restart ( sudo/etc/init.d/apache2 restart), but the imap module is disabled by default. Therefore, it must be enabled with the command php5enmod imap. I recommend also installing phpMyAdmin Installation from repositorysudo apt-get install glpiDuring installation, the database will be configured ( will ask for the MySQL administrator password and ask you to set a password for the glpi user). After this, a window will appear asking you to log in through a browser at http://host_name/glpi. After clicking on this link, the glpi web interface will open. For the first login, use: Login: glpiPassword: glpi Manual installation(not tested on new versions) For n…

Updates for the Windows operating system are released in packages with the extension M.S.U. or CAB. In the event that the standard functionality of the Windows Update service does not work (specially disabled), the cumulative updates or security updates required for the system can be downloaded and installed manually in offline mode. In this article we will show you how to download and install updates in MSU and CAB file format on Windows 10.

Where to download Windows update MSU file

Microsoft initially releases its updates and patches in the format CAB file. This is how your computer receives updates from Microsoft update servers or a local server. For more convenient manual distribution of individual updates by clients through the Microsoft update catalog, these CAB files are packaged in a special format M.S.U.(Microsoft Update Standalone Package).

How to extract CAB file from MSU update package

In some cases, when the Windows Update service, which is used by the wusa utility, does not work correctly (try running it first), it is not possible to install the update in MSU format. In this case, you can manually unzip the MSU package, extract the update CAB file from it, and manually install it on the system.

To unpack the MSU package into the C:\Temp\kb4056887 directory (the directory must first be created), run the following command:

expand _f:* “C:\Temp\windows10.0-kb4056887-x64.msu” C:\Temp\kb4056887

Microsoft (R) File Expansion Utility Version 10.0.10011.16384
Copyright (c) Microsoft Corporation. All rights reserved.
Can't open input file: _f:*.
Adding C:\Temp\kb4056887\WSUSSCAN.cab to Extraction Queue
Adding C:\Temp\kb4056887\Windows10.0-KB4056887-x64.cab to Extraction Queue
Adding C:\Temp\kb4056887\Windows10.0-KB4056887-x64-pkgProperties.txt to Extraction Queue
Adding C:\Temp\kb4056887\Windows10.0-KB4056887-x64.xml to Extraction Queue
Expanding Files….
Expanding Files Complete...
4 files total.

As you can see, 4 types of files have appeared in the directory:

.xml file (Windows10.0-KB4056887-x64.xml) - contains msu package metadata and is used by Wusa.exe
.cab file (Windows10.0-KB4056887-x64.cab - one or more) – directly the archive with the Windows update
*pkgProperties.txt file (Windows10.0-KB4056887-x64-pkgProperties.txt) – contains package properties (release date, architecture, package type, KB link, etc.)

Installing a CAB file for updates in Windows 10

There are two ways to install a CAB update file obtained from an MSU package.

The most universal way to install an update from a CAB file is a utility DISM.exe. The installation command could be like this:

DISM.exe /Online /Add-Package /PackagePath:c:\Temp\kb4056887\Windows10.0-KB4056887-x64.cab

Deployment Image Servicing and Management tool
Version: 10.0.10240.16384
Image Version: 10.0.10240.16384
Processing 1 of 1 — Adding package Package_for_KB4056887~31bf3856ad364e35~amd64~~10.0.1.0
[==========================100.0%==========================]
The operation completed successfully.

Note. Please note how quickly the package is installed via DISM compared to the speed of installing an update from an MSU file.

If you need to install the CAB package in silent mode and suppress the request to restart the computer after installing the update, the DISM command will be like this:

start /wait DISM.exe /Online /Add-Package /PackagePath: c:\Temp\kb4056887\Windows10.0-KB4056887-x64.cab /Quiet /NoRestart

In Windows 8 and Windows 7, you can install the update through the package manager Pkgmgr. Team:
start /w Pkgmgr /ip /m:c:"c:\Temp\kb4056887\Windows10.0-KB4056887-x64.cab"

Note. In Windows 10/Windows Server 2016, the package manager PkgMgr.exe is no longer supported. When you run it, a warning appears about the need to use DISM.exe to manage packages.

Note: The PkgMgr.exe has been deprecated. Please update your scripts to use dism.exe to extract, install, uninstall, configure and update features and packages for Windows.

Note. Please note that Windows language packs (MUIs) are also distributed in CAB format. However, you will not be able to use the DISM command to install them. Instead, you need to use a separate utility to install new languages on the system lpksetup.exe.

These instructions for manually installing cumulative updates (if you don’t remember what this is, read the article about systems) and any other Windows updates apply to all supported OS versions: Windows 10 / 8.1 / 7 and Windows Server 2016 / 2012 / R2 / 2008 / R2 .

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

What are CAB and MSU files

In Windows 10, there are several file formats used to update certain system components. This:

ESD files. They are an encrypted and highly compressed ISO image. They are used to install major updates (assemblies in which not only the index, but also the main number changes). With their help you can, for example, .
CAB or MSU files. They are, one might say, archives. Used to install small updates - cumulative updates, security updates, Adobe Flash Player updates, and so on.

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

Let me immediately note that in Windows 10, a CAB or MSU file of some cumulative update also contains all previous cumulative updates! There is no need to first, for example, install assembly 14393.187, then .189, then .222. It is enough to immediately install the latest package.

Where to download Windows 10 update MSU file

How to install CAB and MSU

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

Installing CAB files

Installing MSU files

Everything is a little easier with them. They can be installed even by simply double-clicking on them. But there is a way to do this through the console.

Hello dear readers.
Today, as I promised you, I will tell you about the most popular tools that create program installers.
Many of them are very simple, so they can be used not only by programmers and software producers, but also by those who want to build an installer with their own hands.
However, assembling installation packages is not the topic of this article, the topic of my article is: 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

I'll start with perhaps the most voluminous software, the most beloved by major commercial 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 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 find it very often in paid products, for example:

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

Start /wait setup.exe /s /sms

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

Open the file properties, on the “Details” tab in the “Description” and “Initial file name” items, as a rule, the value “setup.exe” will be indicated, and in the “Product name”: “InstallShield”.
In addition, when you run such an installer for a normal installation, as a rule, you will encounter the following words:
InstallShield Wizard
Welcome to InstallShield Wizard for xxxxxxx
The InstallShield(R) Wizard will install, etc.

Naturally, all this can be written in English.

Windows Installer Service (*.msi)

Well, what can we say about this... Windows Installer Service (MSI) technology is the de facto standard in the world of system administrators involved in the distribution and support of software for desktop and server versions of Windows. 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 packaged using Windows Installer have the “*.msi” extension.
Example programs:

This type of installer supports the following keys for silent installation:
"qb" and "QN".
When using the "QB" key, the installation progress will be displayed, but the user will not be asked any questions, nor will the "Cancel" button 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) by enclosing it in quotes along with the key.
Example:

Start setup.msi "/qb REBOOT=ReallySuppress"

Using the InstallShield *.msi extension

Since version 7, InstallShield can create files with the extension "*.msi". 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 a separate interesting story.
To automatically install an application that uses Basic MSI, you need to specify the keys "/s /v"...". 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 quietly and avoid rebooting, then use this command

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

Standalone Windows Update Installer *.msu

Due to the fact that this information is often required, I edited the article :-), adding also keys for *.msu.
msu are standalone Windows update installers. Once you download the updates, you can install them even without the Internet and you won’t have to download them again.
All of these installers have a *.msu extension and support the following command line switches.

/quiet - silent mode without user interaction. All windows will be hidden. If a reboot is needed after the update, it will be performed.

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

/warnrestart - When used with quiet, will warn that a reboot will occur.

/promptrestart - when used with quiet, a question will appear asking you 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 reboot.

/log — Sets logging and the 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, is quite easy to learn and convenient to use.
Inno setup can register libraries and ActiveX components, create encrypted installers, change the registry, and also launch external applications, but this is only a small part of what Inno Setup can do, even too small...
It should be noted that the help system is quite well written and supported by numerous examples.

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

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

Hmm, what did I sign, I’ll talk about the main thing.

Inno Setup supports two main keys for silent installation, these 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 the installation. To hide this window, use the “SP-“ key.
Example:

Start setup.exe /VERYSILENT /SP-

How can I tell 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 approximately the following text:
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) is a program 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. There is no limit on the number of files included in the distribution. Uninstall function supported. The built-in native virtual machine turns this product into a full-fledged professional tool.
Examples:

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

Start setup.exe /S

Be careful, the key must be in upper case, 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 NSIS Use

All installers created using NSIS have a very similar interface; study the Winamp installation process carefully and you can easily determine whether NSIS is used.

WISE Installer

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

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

Users will also benefit from the innovative Altiris Software Virtualization Solution technology included in Wise Installation Studio, which allows the creation of virtual application archives (.VSA) and ensures that there are no conflicts between products being installed.

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

It’s just bad luck, it looks like the project is dead...
oh well, let's not talk about sad things...

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