
Now, you have to run UpdateInstaller.exe (at this point it failed, I couldn't get it running fine). cab files stored in the client/wsus/ folder. With the first one you can scan your current office installation and check for the missing updates: WINEPREFIX=~/.wine/Office2013 WINEARCH=win32 wine ~/wsusoffline/UpdateGenerator.exe I've tested wsusoffline it has two executables: UpdateGenerator.exe and UpdateInstaller.exe (in "client" folder).

Second option (use an automated software) Pros: you will have a full updated office using files directly from Microsoft. msp file in the /update folder and will apply them. You can clone a current office 2013 updates database following the directions here: /how-to-download-microsoft-office-2013-updates-the-easy-way/ and place the files in the /updates folder, so then, you install office using: WINEPREFIX=~/.wine/Office2013 WINEARCH=win32 wine ~/office/setup.exeĪnd setup.exe will detect any. msp file stored in /update folder under the installation path. The Office installer has an option to install any. To clone a current office update database): Use an automated software to identify which updates are required in the current Wine instalation and deploy it under Linuxįor these two options the outcome is the same: you will have to re-install office 2013 in order to get it full patched, the only difference is the source of these update files.įor the first case (1. To clone a current office 2013 update scheme in Windows OS and transfer it to the Wine instalationĢ. There could be some strategies to keep Office 2013 update:ġ.
.png)
The ISO image of the installer was mounted with


