Installing Windows Updates that are not able to be automatically packaged

What
Use this workflow when FileWave reports a Windows update as missing, but the update is not one FileWave can automatically package as a Software Updates Fileset. This is the manual MSU deployment path for admins searching for Windows Update Catalog installs, offline Windows update installation, or updates that show as missing but cannot be auto-packaged.
When/Why
FileWave can report missing Windows updates even when it cannot build a Fileset for a specific update automatically. This is common for standalone 
.msu packages from the Microsoft Update Catalog.
How
Windows updates can come as 
.msu files for the Windows Update Standalone Installer. Install those packages with 
%windir%\System32\wusa.exe.
For example, if the Windows6.0-KB934307-x86.msu file is in the D:\934307 folder, type the following command at a command prompt to install the update package:
wusa.exe /quiet /norestart d:\934307\Windows6.0-KB934307-x86.msu
In FileWave, start by downloading the update from the Microsoft Update Catalog. Then add the MSU file to an empty Fileset.
Next, create a Fileset by making an Empty Fileset and then add the update as seen here:
To install the MSU you will need to add an Activation Script to it.
Here is the text of install.bat. 
The screenshots and script use a shortened MSU filename to keep the example readable. If you keep the original download filename, copy the full filename into the script. Keep the quotation marks around the path if the filename or folder path contains spaces.
Install.bat
REM For all script types, returning an exit code of 0 (success) means the
REM script execution completed successfully.
REM Add the contents of your script below:
 
%windir%\System32\wusa.exe /quiet /norestart "c:\programdata\FileWave\Installers\windows10.0-kb5012599.msu"
 
exit 0
The example uses 
/norestart. If the update requires a restart, configure the Fileset properties so FileWave controls the reboot prompt and timing.
wusa.exe exits cleanly when the update is already installed or does not apply to the device. If you want FileWave to skip the Fileset before activation, add a Requirements script that checks whether the KB is already installed and exits accordingly.
After installation, inventory must update before the Software Updates section shows the patch as installed. Wait for the normal verification cycle (every 24 hours or after restart), or send an explicit Verify command. Repeat this process for any MSU file that you need to deploy with FileWave.
Related Content
Windows Software Update Reporting
Fileset Creation and Deployment
Digging Deeper
More information on wusa.exe is here: 
https://support.microsoft.com/en-us/topic/description-of-the-windows-update-standalone-installer-in-windows-799ba3df-ec7e-b05e-ee13-1cdae8f23b19
When you are testing it may be difficult to repeat your testing once an update installs, but wusa has an /uninstall switch as well that can save you time. Below is an example that would remove a patch. Another alternative is to use a Virtual Machine for testing and use snapshots to be able to install and then roll back to before the update was installed. 
wusa /uninstall /kb: KB5000802 /quiet /promptrestart
For troubleshooting to view the Windows Update Standalone Installer event log on a client device, follow these steps:
Click Start, type event viewer in the Start Search box, and then click Event Viewer in the Programs list. 
In Event Viewer, expand Windows Logs, and then click Setup.
Setup events appear in the middle pane.
In the Actions pane, click Filter Current Log.
In the Event sources list, click to select the WUSA check box, and then click OK.