Upsourcer: Slipstream patches for Office 2007/2010/2013/2016 and rebuild setup source files

You need to login to view this posts content.

 

I take it Upsourcer is designed so it doesn't matter if I integrate those exes or run them manually after vanilla installation, the result is the same, right? I'm asking because I already installed Office 2016 before checking here and want to do the security updates, and this is convenient since I don't have WU (and I'm too lazy to get & run the Office removal tool)

BTW, does Upsourcer do anything about telemetry? I've got some countermeasures set up, so I wonder if I should remove them and reapply after install/update.

Edit: I've read the concept part of the OP again, eek this is more work than I expected. Now I'm wondering if I'll break the system if I just run the stuff from the Office2016-x64.txt file

 

@abbodi1406
SuppressPatches2016.zip need to update

 

Sorry. I just think that whenever there is an update, SuppressPatches2016 should be updated.

 

If I use the patched Office 2010 MSO.DLL on a NT6.x OS, will there be any unexpected errors?
install Office 2010 with patched MSO.DLL on Vista, and it seemed to work fine.

 

It will probably work, but it's patched to work under XP. On Vista+ there is no need for this patching as all functions exists in system.
And yes, maybe some unexpected errors can exist.

 

Personally I've not encountered any errors on any OS (used it for at least 1 year).

Also, thank @George King for the improved patch also available for x64, and @abbodi1406 for integrating it.

 

Del command in the :RemoveBackups label has unquoted %%# variable, so no cleanup if using working directory path with spaces:

Code:

for /r %%# in (*.ism *.svc *.upd *.xex *.lld *.lmx *.bac *.ddf) do (
del /f /q %%#
)

Quote variable or simply use del command only:

Code:

del /s /q /f *.ism *.svc *.upd *.xex *.lld *.lmx *.bac *.ddf 1>nul 2>&1