TechnologyTechnician wrote:So would it be acceptable to run WSUSoffline several times in a row until it says nothing to do and then reboot?
No, most likley not. WSUS Offline runs until a system reboot is needed, the number of updates per stage are reached, or it has nothing to do. In the latter case, it's obviously OK to skip the reboot. Only in the second case it would be theoretically possible to run it again without a reboot, but there's a good reason for the number of updates per stage (system memory limit, usage by Windows Update service).
Why is there a discrepancy between wsusoffline and windows update?
There are several. The Update History is pretty useless when installing updates via WSUS Offline, which has been mentioned quite often in the forum. Use the list of Installed Updates instead. Failed updates are not seen as installed (obviously). Furthermore, WSUS Offline only downloads and installs security updates, nothing more. Anything beyond that, like optional updates, are only available via Windows Update.
If updates fail to install, you should try to fix that. If you want us to help you with that, you should post the KB numbers, the contents of C:\Windows\wsusofflineupdate.log, and perhaps C:\Windows\WindowsUpdate.log (Win7/8.1) or the output of Get-WindowsUpdateLog PowerShell command (Win10).
Regards
Dalai