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

Discussion in 'Microsoft Office' started by abbodi1406, Jun 24, 2023.

Page 10 of 10
  1. abbodi1406

    abbodi1406 MDL KB0000001

    Feb 19, 2011
    16,454
    86,511
    340
    #181 abbodi1406, Mar 3, 2024 (OP)
  2. abbodi1406

    abbodi1406 MDL KB0000001

    Feb 19, 2011
    16,454
    86,511
    340
    #182 abbodi1406, Mar 18, 2024 (OP)
  3. abbodi1406

    abbodi1406 MDL KB0000001

    Feb 19, 2011
    16,454
    86,511
    340
    #183 abbodi1406, Mar 18, 2024 (OP)
    # Office 2013 MSI Upsourcer

    - Updated msp applicability for VisProWW.msi and VisStdWW.msi
    - Updated "suppress updates" vbscripts for SharePointDesigner

    thanks to @adguard
     
  4. asdddsa101

    asdddsa101 MDL Member

    Feb 11, 2021
    110
    39
    10
    #184 asdddsa101, Apr 11, 2024
  5. Nykto

    Nykto MDL Junior Member

    Oct 3, 2015
    55
    25
    0
    #185 Nykto, Apr 19, 2024
    Last edited: Apr 19, 2024
    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
     
Page 10 of 10