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

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

  1. abbodi1406

    abbodi1406 MDL KB0000001

    Feb 19, 2011
    17,188
    90,645
    340
    Can you check Event Log if it list the errors?
     
  2. abbodi1406

    abbodi1406 MDL KB0000001

    Feb 19, 2011
    17,188
    90,645
    340
    After some search, this problem seems common with Office 2007
    it might be caused by the short/long name confliction, or it's caused by update KB2767916 (niceclass)

    if you would like to test:
    - try OUS2007_u.7z
    or
    - try OUS2007_v3.7z but exclude niceclass-x-none.msp from updates

    if none worked, add these registry values after installing Office 2007
    Code:
    reg add HKCU\Software\Microsoft\Office\12.0\Access\Options /f /v NoReReg /t REG_DWORD /d 1
    reg add HKCU\Software\Microsoft\Office\12.0\Excel\Options /f /v NoReReg /t REG_DWORD /d 1
    reg add HKCU\Software\Microsoft\Office\12.0\Outlook\Options /f /v NoReReg /t REG_DWORD /d 1
    reg add HKCU\Software\Microsoft\Office\12.0\Powerpoint\Options /f /v NoReReg /t REG_DWORD /d 1
    reg add HKCU\Software\Microsoft\Office\12.0\Word\Options /f /v NoReReg /t REG_DWORD /d 1
     
  3. asdddsa101

    asdddsa101 MDL Member

    Feb 11, 2021
    121
    41
    10
    Thanks, solved. :)
     
  4. asdddsa101

    asdddsa101 MDL Member

    Feb 11, 2021
    121
    41
    10
    I click "uninstall" button in the control panel. Found that Office 2010 could not be uninstalled. I checked the event viewer and there are no warnings or errors.
    In Office 2007, I click "Change" button in the Control Panel, an error occurs. But "uninstall" button works fine. Office 2007 can be uninstalled normally.
     
  5. abbodi1406

    abbodi1406 MDL KB0000001

    Feb 19, 2011
    17,188
    90,645
    340
    That happen if original setup files are not replaced with modified files (or original files restored)
    or if C:\Windows\Installer\fffff.msp file is deleted

    check SetupExe*.log files in %temp%
     
  6. asdddsa101

    asdddsa101 MDL Member

    Feb 11, 2021
    121
    41
    10
    Code:
    08/01/2023 21:42:22 Uninstalling chained package: Office64WW
    Resource File Manager : Converted CultureTag [zh-cn] to LocaleId [2052].
    Catalyst Package Uninstall...
        Package: Office64WW
        Package Code: {90140000-002A-0000-1000-0000000FF1CE}
        Command Line: REBOOT=ReallySuppress LAUNCHEDBYSETUPEXE=1 MSIRESTARTMANAGERCONTROL="Disable" SETUPEXEINSTALLUILANGUAGE=2052 SETUPINTLDLLDIRECTORY="C:\Users\John\AppData\Local\Temp\Setup00000144\" UNINSTALL_ACIDS="9DA2A678-FB6B-4E67-AB84-60DD6A9C819A;"
    MSI(INITIALIZE): '<NULL>'
    MSI(COMMONDATA): '1: 0 2: 0 3: 936 '
    MSI(INFO): 'The install source for this product is not available. Please verify that the source exists and is accessible.
    C:\Windows\Installer\1374ed.msi'
    MSI(COMMONDATA): '1: 2 2: 0 '
    MSI(COMMONDATA): '1: 2 2: 1 '
    MSI(TERMINATE): '<NULL>'
    Error: Failed to configure: {90140000-002A-0000-1000-0000000FF1CE} ErrorCode: 1612(0x64c).
    
    Log level changed from: Standard to: Verbose
    Rolling back chain
    08/01/2023 21:42:23 Rolling back package: Office64WW
    There appears to be no rollback work to do for package: Office64WW path: C:\MSOCache\All Users\{90140000-0012-0000-0000-0000000FF1CE}-C\Office64WW.MSI
    SystemRestore : Attempting to cancelling System-Restore-Point for Product [Microsoft Office Standard 2010] (with RestorePointType [1, Removed]).
    SystemRestore : Successfully cancelled System-Restore-Point for Product [Microsoft Office Standard 2010] (with RestorePointType [1, Removed]).
    Showing completion dialog.
    Reboot requested if needed.
    No reboot is needed.
    Catalyst execution finished: 08/01/2023 21:42:23.  Return code: 1612.
    PERF: TickCount=76156 Name=RunSetup Description=End function
     
  7. asdddsa101

    asdddsa101 MDL Member

    Feb 11, 2021
    121
    41
    10
    It may be caused by failed to verify the digital signatures of setup.exe and osetup.dll.
    However, the relevant files of Office 2007 also lost their signatures, but Office 2007 can still be uninstalled normally.
    Code:
    PERF: TickCount=670765 Name=OBootStrapper::Run Description=Begin function
    Operating System version: 6.0.6003 Service Pack 2. Platform ID: 2
    Running 32-bit setup on a 64-bit operating system.
    Command line: "C:\MSOCache\All Users\{90140000-0012-0000-0000-0000000FF1CE}-C\setup.exe"
    No command line arguments given
    Searching for best setup controller dll to load...
    Checking for setup controller dll at [C:\MSOCache\All Users\{90140000-0012-0000-0000-0000000FF1CE}-C\Updates].
    Checking for setup controller dll at [C:\MSOCache\All Users\{90140000-0012-0000-0000-0000000FF1CE}-C].
      Found setup controller dll at [C:\MSOCache\All Users\{90140000-0012-0000-0000-0000000FF1CE}-C\OSETUP.DLL].
      Version [14.0.7211.5000].
    Verify file signature in "C:\MSOCache\All Users\{90140000-0012-0000-0000-0000000FF1CE}-C\setup.exe"
    C:\MSOCache\All Users\{90140000-0012-0000-0000-0000000FF1CE}-C\setup.exe is trusted.
    Verify file signature in "C:\MSOCache\All Users\{90140000-0012-0000-0000-0000000FF1CE}-C\OSETUP.DLL"
    Error: C:\MSOCache\All Users\{90140000-0012-0000-0000-0000000FF1CE}-C\OSETUP.DLL is not trusted.
    Log level changed from: Standard to: Verbose
    Failed to verify file signature from the selected setup controller dll in location "C:\MSOCache\All Users\{90140000-0012-0000-0000-0000000FF1CE}-C\OSETUP.DLL"
    C:\MSOCache\All Users\{90140000-0012-0000-0000-0000000FF1CE}-C\OSETUP.DLL digital signature does not validate or is not present.
    
     
  8. abbodi1406

    abbodi1406 MDL KB0000001

    Feb 19, 2011
    17,188
    90,645
    340
    Did you verify if C:\Windows\Installer\fffff.msp file exist?

    modified setup.exe ignore digital signature
    you either have old cached files, or the setup files are not replaced correctly during Upsourcer process
     
  9. fch1993

    fch1993 MDL Senior Member

    Mar 14, 2020
    381
    273
    10
  10. abbodi1406

    abbodi1406 MDL KB0000001

    Feb 19, 2011
    17,188
    90,645
    340
    Yes
    it's the same PatchAAA.msp file inside _bin folder

    the inserted PatchAdd vbscript is supposed to create that file during Office installation
    but that may not succeed if "Windows Script Host" is disabled, or Antivirus prevented vbscript

    that's why last point of Important Remarks:

     
  11. asdddsa101

    asdddsa101 MDL Member

    Feb 11, 2021
    121
    41
    10
    After installing Office, I executed RegisterOfficePatches.cmd. After that, "C:\Windows\installer\fffff.msp" exists.
    But I try to uninstall Office 2010, and it displays "failed to complete the uninstallation". At this point fffff.msp has been removed.
     
  12. asdddsa101

    asdddsa101 MDL Member

    Feb 11, 2021
    121
    41
    10
    #96 asdddsa101, Aug 2, 2023
    Last edited: Aug 2, 2023
  13. fch1993

    fch1993 MDL Senior Member

    Mar 14, 2020
    381
    273
    10
    @abbodi1406

    About the third point.

    I have checked the files I tested it's the SP1 images, I just put the wrong links.

    So this error happened to all cabs of "Proofing Tools 2013 With SP1".

    Images links updated.

    PS: The RTM files I used to test with "Office 2013 Retail" Editions.