For RTM ISO, there are errors processing the proof.msi in both proof.en and proof.zh-cn folders. As you can see, in the CMD window, there's no proof.cab items in '-Create new CAB Files' Step. Maybe the issues is caused by the proof*.msp (For SP1 .msp, it's named proofsp*.msp, but for post-SP1 Updated, it's named proof.msp). Spoiler: Pic For already SP1 ISO, Code test passes successfully. Spoiler: Codes Code: - Move Office WOW files to a single folder Press any key to continue... - Modify Setup and Package xml files Press any key to continue... - Restore administrative installation table Press any key to continue... - Slipstream Updates zh-cn\proof.en\proof.msi zh-cn\proof.zh-cn\proof.msi zh-cn\accessmui.msi zh-cn\dcfmui.msi zh-cn\excelmui.msi zh-cn\groovemui.msi zh-cn\infopathmui.msi zh-cn\lyncmui.msi zh-cn\officemui.msi zh-cn\office32mui.msi zh-cn\onenotemui.msi zh-cn\osmmui.msi zh-cn\osmuxmui.msi zh-cn\outlookmui.msi zh-cn\powerpointmui.msi zh-cn\proofing.msi zh-cn\publishermui.msi zh-cn\wordmui.msi office32ww.msi proplusww.msi Press any key to continue... - Replace original osetup.dll, setup.dll and setup.exe Press any key to continue... - Insert PatchAdd vbscript into MSIs Press any key to continue... - Create MakeCAB DDF directives zh-cn\proof.en\proof.msi zh-cn\proof.zh-cn\proof.msi zh-cn\accessmui.msi zh-cn\dcfmui.msi zh-cn\excelmui.msi zh-cn\groovemui.msi zh-cn\infopathmui.msi zh-cn\lyncmui.msi zh-cn\officemui.msi zh-cn\office32mui.msi zh-cn\onenotemui.msi zh-cn\osmmui.msi zh-cn\osmuxmui.msi zh-cn\outlookmui.msi zh-cn\powerpointmui.msi zh-cn\publishermui.msi zh-cn\wordmui.msi office32ww.msi proplusww.msi Press any key to continue... - Create new CAB files zh-cn\proof.en\Proof.cab zh-cn\proof.zh-cn\Proof.cab zh-cn\AccLR.cab zh-cn\DCFMUI.cab zh-cn\ExcelLR.cab zh-cn\GrooveLR.cab zh-cn\InfLR.cab zh-cn\LyncMUI.cab zh-cn\OfficeLR.cab zh-cn\OWOW32LR.cab zh-cn\OnoteLR.cab zh-cn\OSMMUI.cab zh-cn\OSMUXMUI.cab zh-cn\OutlkLR.cab zh-cn\PptLR.cab zh-cn\PubLR.cab zh-cn\WordLR.cab OWOW32WW.cab ProPsWW.cab ProPsWW2.cab Press any key to continue... - Remove administrative installation directories Press any key to continue... - Restore Office WOW files to the original folder(s) Press any key to continue... - Remove original files backups ============================================================ Finished. Press any key to exit. But, when it comes to the real installation on VM, the setup asks me to browse for Office.zh-cn\OfficeMUI.msi and Office.zh-cn\OfficeMUI.xml continuously. And the setup cannot continue. Spoiler: Pic
# Office 2013 MSI Upsourcer v5 - Use SHORTFILENAMES property workaround to avoid issues with Unicode files names or long paths - Updated WiMakCabs.vbs thanks to @kkhww for reporting and testing
Yes, to remove stslist but it's not needed if you don't use kb5002244 i will wait until month to see if the updates continue
The github links for the MSP file listings appear to have vanished. Is there a mirror or reupload of these anywhere? Specifically I need the ones for Office 2010 x86.
First of all, I would like to thank @abbodi1406 for the hard work he put into creating and maintaining this tool. First time using Upsourcer (Office2016) and I managed to follow the instructions successfully. Now I have this very stupid question : The msp files are not needed anymore, right? I don't need to include the "Updates" folder into my final Office2016 ISO file, If I'm understanding correctly?
Hi, @abbodi1406. I´m rebuilding my Office 2013 installer and I read this: From what I understand, it's no longer necessary to use the script contained in SuppressPatches2013.zip because using Insert_PatchAdd_VBScript would make all the slipstreamed patches appear as already installed, right? Or am I misunderstanding? The problem is that, although the installer's slipstreaming process completes without errors, when I install Office 2013, KB2880463 still appears in Windows Update. You explained the relationship between KB2880463 and KB4011677 to me some time ago, but looking at the Patches2013.vbs file, I see that you already worked with them in that script. Am I doing something wrong in the process, or am I misunderstanding the Insert_PatchAdd_VBScript option? I thought this option was meant to avoid the need to manually run RegisterOfficePatches.cmd later, because Office 2013 reached its end-of-life (EOL) a long time ago. Thank you for your work and your help.
@abbodi1406. I downloaded the new script you provided me and rebuild the installer, but Windows Update still offers KB2880463. I am open to try/test whatever you need to. Update: I ran further tests on another computer and it worked fine this time, and Windows Update no longer offers KB2880463. I'll run more tests on other computers and let you know the results.