InterLinked Posted October 18, 2020 Author Share Posted October 18, 2020 OK, here's what I've got so far: You can download it in Excel format from here: https://w2k.phreaknet.org/ All the updates going back through beginning of 2018 now. I can do more if needed, but this seems like it should cover most of them. 1 Link to comment Share on other sites More sharing options...
InterLinked Posted October 18, 2020 Author Share Posted October 18, 2020 (edited) @win32 OK, in a bit of a rough spot, maybe you have an idea? All I had to do was replace MSO.DLL on XP in that Office14 folder and THIS time, it worked! No need to replace the system32 My Office version was Oct2018, but I think that's because of the old MSO.DLL. Other programs were more recent. So, I did the same thing in Vista. This time, I only extracted and slipstreamed updates that were in my 2020-10 folder, not the 2020-02 folder. That means I only slipstreamed the following (had to /extract: each of these, then slipstream): Mode LastWriteTime Length Name ---- ------------- ------ ---- -a---- 10/17/2020 4:34 PM 15798848 access2010-kb4484385-fullfile-x86-glb.exe -a---- 10/17/2020 4:37 PM 4493984 ace2010-kb4484379-fullfile-x86-glb.exe -a---- 10/17/2020 4:26 PM 37930176 excel2010-kb4486707-fullfile-x86-glb.exe -a---- 8/7/2020 12:58 PM 64 Extract Syntax.txt -a---- 10/17/2020 4:27 PM 3095752 graph2010-kb4486700-fullfile-x86-glb.exe -a---- 10/17/2020 4:28 PM 9944784 kb24286772010-kb4486701-fullfile-x86-glb.exe -a---- 10/17/2020 4:30 PM 9691128 mso2010-kb4484530-fullfile-x86-glb.exe -a---- 10/17/2020 4:29 PM 88360832 outlookloc2010-kb4486663-fullfile-x86-glb.exe -a---- 8/7/2020 12:42 PM 18306024 powerpoint2010-kb4484235-fullfile-x86-glb.exe -a---- 10/17/2020 4:39 PM 47024608 powerpointloc2010-kb4092435-fullfile-x86-glb.exe -a---- 8/7/2020 12:51 PM 8388528 project2010-kb4484463-fullfile-x86-glb.exe -a---- 8/7/2020 12:41 PM 7824976 publisher2010-kb4032216-fullfile-x86-glb.exe -a---- 8/7/2020 12:49 PM 2786192 vbe72010-kb4484377-fullfile-x86-glb.exe -a---- 8/7/2020 12:41 PM 22120752 visio2010-kb4462225-fullfile-x86-glb.exe -a---- 10/17/2020 4:29 PM 28030128 word2010-kb4486703-fullfile-x86-glb.exe I didn't slipstream the extractions of the following: Mode LastWriteTime Length Name ---- ------------- ------ ---- -a---- 2/22/2020 1:44 PM 7682502 access-x-none_8b5269f69d8184a3d57452c15344a77c4029e3e0.cab -a---- 2/22/2020 2:22 PM 65528 accessolkaddin-x-none_4571200d0c9db16b528f6102c7efcc394775f61f.cab -a---- 2/22/2020 6:03 PM 618864 convintl-en-us_38dc63af44da4516f4e34c703bddd4895991ff7e.cab -a---- 2/22/2020 2:25 PM 3904392 csi-x-none_d8eb94e0c20a0a6e007dbcf657ace19a293e5171.cab -a---- 2/22/2020 5:54 PM 873260 excelintl-en-us_643f56790952224f651b92cbcfd18938de8f3720.cab -a---- 2/22/2020 2:26 PM 92512 exppdf-x-none_78e193d7fa3be46fa6c07f73d3efebeed167a549.cab -a---- 2/22/2020 1:48 PM 4564452 filterpack-x-none_0badc2b5c4c30be34378d267f4284034573a1496.cab -a---- 2/21/2020 9:47 PM 554548 fm20-x-none_28210a36f7d5d948e8b95cc9d4b9a9141eedc557.cab -a---- 2/22/2020 5:44 PM 562396 fm20-x-none_9649a309eee15b5d32c65c1d1b522c4d8eeee716.cab -a---- 2/22/2020 5:53 PM 371854 gfonts-x-none_23715aec547df5d7824747f46ff04e82f36a2d33.cab -a---- 2/22/2020 2:02 PM 748770 gfx-x-none_3b7db2e32c6c15db9aa5f868e28b2966e833e84d.cab -a---- 2/22/2020 2:24 PM 2697424 gkall-x-none_b77a1de492d2701b6e8ecb2c627d4e8ec2e76fb3.cab -a---- 2/22/2020 2:38 PM 18090128 groove-x-none_c9e8eb19a37187686489aa3562e51a54d41a9bab.cab -a---- 2/21/2020 9:49 PM 218820 ieawsdc-x-none_48528979c421e062fd198908d5de4828b99ff32e.cab -a---- 2/21/2020 9:45 PM 3066620 infopath-x-none_71e941bd9c288cac97405c0b44dd140d171bebde.cab -a---- 2/22/2020 1:53 PM 2432544 ipeditor-x-none_286d99c11bb8da6afadfd38842eb965a3869a40a.cab -a---- 2/22/2020 2:14 PM 108956 msaddndr-x-none_fe7e444293cb613cbd3883bac96bf50eb76ba8a1.cab -a---- 2/22/2020 6:43 AM 519110 mscomctlocx-x-none_037c2e34dfa1b048ad37c896d4a6826125fc0b8d.cab -a---- 2/22/2020 6:40 AM 1134182 mshelp-x-none_4c3af1336cc8599e0b6f1cebcc7a22d2fd44d524.cab -a---- 2/22/2020 2:03 PM 47116 msocf-x-none_b6de60914c3e537e2c9fa1053f90faebc4b61e92.cab -a---- 2/21/2020 9:51 PM 653292 msohevi-x-none_a01a35c87b1b61d7cab0f6782c01e98dbbc2f72c.cab -a---- 2/22/2020 6:01 PM 897790 msointl-en-us_cbb2e8d950e9de471c4b7770b6699032dde0ef98.cab -a---- 2/22/2020 2:20 PM 10656590 msores-x-none_c7a4834f7b28175fd385cb8c83b4420b73384a09.cab -a---- 2/22/2020 6:46 AM 417890 msptls-x-none_e2cdd9de533758b57ac6c6cc3520ddd55da0ba85.cab -a---- 2/22/2020 1:57 PM 1695784 mstore-x-none_c408d603eb2a9c0c0573a888818c1e8533e44fa7.cab -a---- 2/22/2020 2:29 PM 33570 mtextra-x-none_d02b158e7c2dc7219dde12e91568dcde7a3c13ca.cab -a---- 2/22/2020 5:45 PM 7420174 oart-x-none_0ea4efd1d02042004a2378c3dfbb69a8e2849860.cab -a---- 2/22/2020 6:49 AM 7630110 oart-x-none_5b6a337944a2f282db4c626bf56243a5a9e8fa4c.cab -a---- 2/22/2020 2:33 PM 3607794 oartconv-x-none_daef313f48ba188dec24ae1779a9cc7b9486f802.cab -a---- 2/22/2020 6:50 AM 3611138 oartconv-x-none_db1971e40e0069c84e31a87cc0231de5694925d5.cab -a---- 2/22/2020 1:58 PM 175480 ocfxca-x-none_ea01b56460836086e46ac9135fa5ff094dd4b818.cab -a---- 2/22/2020 2:40 PM 2745950 offowc-x-none_2874cb2b3ef22a8ea1f839c8adb8aae66547c56c.cab -a---- 2/22/2020 2:31 PM 1563358 oleo-x-none_6295985a2c496a5ed4be2b454247afc14f3d7c48.cab -a---- 2/22/2020 6:00 PM 571128 onenoteintl-en-us_52ec80bd9d14edd1dfdb312ee0ef0f45f4879a1c.cab -a---- 2/22/2020 2:36 PM 1096390 osc-x-none_31d563081f0a879ba0c775ae9b25578279591abd.cab -a---- 2/22/2020 1:40 PM 147398 ose-x-none_3078d43e678365e4c9e8743915f13a74d8bc089c.cab -a---- 2/22/2020 1:40 PM 1936384 osetup-x-none_1d9ab800d30916ec8a16a7d5f792ec58a16f25f1.cab -a---- 2/22/2020 5:52 PM 225858 ospp-x-none_5d0c591708ab6fdb76553c0a2ca137dc3a8b7282.cab -a---- 2/22/2020 6:43 AM 239058 otkruntimertl-x-none_ed039e26757d92e91629f0ef966dedd3aeace2a7.cab -a---- 2/22/2020 2:35 PM 363872 outexum-x-none_2dc9cb78765fe55550051b768eb883ba94247e88.cab -a---- 2/22/2020 6:06 PM 3288294 outlfltr-x-none_0a5c2c66c1d8cf822d0b4b2b8f6940d66ced1faf.cab -a---- 2/22/2020 2:46 PM 3288998 outlfltr-x-none_d315e4d39aea9d809dd0112dcd6ab8b1ffdbbb14.cab -a---- 2/22/2020 5:49 PM 741956 powerpointintl-en-us_c3fdea1cc362f2472dd94ba8d001fc36e8955d29.cab -a---- 2/22/2020 6:02 PM 9312482 proof-en-us_a3a11b51b90c7f31fd661d7b401bcc7abbe260be.cab -a---- 2/22/2020 5:59 PM 4318298 publisher-x-none_2fdbf1786c5e550b7076d2aac9bf8f732b9ef89d.cab -a---- 2/22/2020 5:43 PM 765248 riched20-x-none_e31f07b596a5e1c0989d04d214a55225955c68cc.cab -a---- 2/22/2020 5:43 PM 1138968 stslist-x-none_af83eec5aba68f724978bde564bbdefb27ae950f.cab -a---- 2/22/2020 2:23 PM 19034 targetdir-x-none_4df7780127a2023254259c63c856feaed955abb5.cab -a---- 2/22/2020 1:56 PM 9416 targetdir-x-none_9cc0dbf4acd3806cd7efb742772affe9e9384c4d.cab -a---- 2/22/2020 6:04 PM 295404 usp10-x-none_4bf400783d89e5dd97c93cc8c65d394ac43721a0.cab -a---- 2/22/2020 2:28 PM 1473420 vbe7-x-none_2b1e4e0617ccd54821ed36fa61cc8dd04da5804f.cab -a---- 2/22/2020 6:47 AM 1476636 vbe7-x-none_da7ecd740b30d8f2699acc30f5beda805138241e.cab -a---- 2/22/2020 1:42 PM 20724250 visio-x-none_3208a2d87b4c506255d9f123c747278f8d79b349.cab -a---- 2/22/2020 2:39 PM 20796824 visio-x-none_5969b6a7114f7dceaf1150c5e1b26594ba286553.cab -a---- 2/22/2020 1:43 PM 4570324 vviewer-x-none_d78f3d1bc020ff923b6126dd297480c3c0b06050.cab -a---- 2/22/2020 6:50 AM 419528 wce-x-none_85cc31f351a3cd3c448ed06bcf311babdbbbfd22.cab -a---- 2/22/2020 2:00 PM 367364 wec-x-none_9524dc91a4f6d1b09c4f5ff2ae22d6a9779d9a65.cab -a---- 2/22/2020 5:58 PM 371216 wordintl-en-us_8c28c699d2c958183efaa43e34d3e109e0b0582e.cab I guess I was dumb and discarded the MSUs these are from so I don't know how many of these February 2020 files have been superseded! In a real pickle now, unless I want to start over. don't remember how i got here. i can't search by cab, can I? only thing I can do is I put together a powershell script to return the signing time of all files e.g. outlfltr-x-none_d315e4d39aea9d809dd0112dcd6ab8b1ffdbbb14.cab SigningTime : 10/16/2013 5:04:14 AM powerpointintl-en-us_c3fdea1cc362f2472dd94ba8d001fc36e8955d29.cab SigningTime : 6/26/2018 2:55:23 PM so MAYBE the KB# could be deduced if it's something specific like powerpointintl-, but not if it's generic like office-... I ask b/c there are a bunch of files from the February folder not in my new folder, like stuff that modifies riched20, etc. Currently, I get to 7258 Office and 7257 PPT and 7261 Word, the latest of those each, on Vista, but I'm worried I'm still missing something. Doesn't seem like there's a clean way to tell. What I was doing before was copying the february folder into updates, then copying the new one, and clicking "Copy and replace" on conflicts. But I didn't use the feb folder at all this time and it would seem I am still updated. Just don't want to delete the feb folder if it has needed updates. Is there any realistically practical way of tracing these cab files to KB#s via just name of the cab and signingtime? Some of these are 5-7 years old, and I find it hard to believe they contain the latest updates. Some are from 2019 though so they may not be superseded. I think this is what @crashnburn4u was talking about when he said all the MSUs are now EXEs! I must've been downloading MSUs which extracted to CABs back before February, and now it's all EXEs so hard for me to figure out what's what and what I really need. I personally prefer the EXE way, as it has the KB #s in the filename and I can extract those directly into the updates. MSU has to be extracted to CABs, then CABs have to be extracted to updates, so I have three tiers of files taking up space and confusing me! For instance, I just tried "tracing" visio-x-none_5969b6a7114f7dceaf1150c5e1b26594ba286553 That's KB 4488446. How do I know? Because the signature is Jan 2019, and according to my Excel sheet, there was only one update for Visio in Jan 2019. So I looked up the KB# and downloaded the EXE, extracted it. I also copied the CAB file and extracted that using 7ZIP. Guess what? Same 20,936 KB MSP file inside each and 6 KB XML. The EXE version also has a EULA but that's irrelevant. So this CAB file belongs with that update. Ultimately, I may have to trace all those February updates to KB #s in this manner, but no way to do it accurately w/o actually downloading and extracting all these KB #s one by one. And that kind of sucks, b/c there's 58 CAB files to trace. But, in the end, if I can get all EXEs, life is better... Oh, and just to iterate my point, 4488446 is NOT a superseded update, it IS Needed. Hence, why some of the updates in the February folder are still needed. Edited October 18, 2020 by Dylan Cruz Link to comment Share on other sites More sharing options...
InterLinked Posted October 18, 2020 Author Share Posted October 18, 2020 Here's the full signature list in the feb update folder (meaning feb 2020 or before): PS> .\DigitalSignatureCheck.ps1 access-x-none_8b5269f69d8184a3d57452c15344a77c4029e3e0.cab SigningTime : 2/15/2019 6:38:33 PM accessolkaddin-x-none_4571200d0c9db16b528f6102c7efcc394775f61f.cab SigningTime : 10/14/2015 11:50:17 AM convintl-en-us_38dc63af44da4516f4e34c703bddd4895991ff7e.cab SigningTime : 8/25/2017 8:11:33 PM csi-x-none_d8eb94e0c20a0a6e007dbcf657ace19a293e5171.cab SigningTime : 9/5/2015 1:36:14 AM excelintl-en-us_643f56790952224f651b92cbcfd18938de8f3720.cab SigningTime : 3/23/2015 1:47:50 AM exppdf-x-none_78e193d7fa3be46fa6c07f73d3efebeed167a549.cab SigningTime : 8/13/2015 8:20:05 AM filterpack-x-none_0badc2b5c4c30be34378d267f4284034573a1496.cab SigningTime : 6/18/2019 4:55:07 PM fm20-x-none_28210a36f7d5d948e8b95cc9d4b9a9141eedc557.cab SigningTime : 11/20/2014 12:12:59 PM fm20-x-none_9649a309eee15b5d32c65c1d1b522c4d8eeee716.cab SigningTime : 6/24/2015 3:22:34 AM gfonts-x-none_23715aec547df5d7824747f46ff04e82f36a2d33.cab SigningTime : 10/3/2014 7:04:45 PM gfx-x-none_3b7db2e32c6c15db9aa5f868e28b2966e833e84d.cab SigningTime : 7/24/2013 10:24:55 AM gkall-x-none_b77a1de492d2701b6e8ecb2c627d4e8ec2e76fb3.cab SigningTime : 5/17/2016 8:01:29 PM groove-x-none_c9e8eb19a37187686489aa3562e51a54d41a9bab.cab SigningTime : 12/18/2013 8:11:06 PM ieawsdc-x-none_48528979c421e062fd198908d5de4828b99ff32e.cab SigningTime : 7/16/2015 10:24:02 AM infopath-x-none_71e941bd9c288cac97405c0b44dd140d171bebde.cab SigningTime : 2/10/2016 12:47:59 AM ipeditor-x-none_286d99c11bb8da6afadfd38842eb965a3869a40a.cab SigningTime : 12/18/2013 8:10:34 PM msaddndr-x-none_fe7e444293cb613cbd3883bac96bf50eb76ba8a1.cab SigningTime : 4/17/2014 6:12:41 PM mscomctlocx-x-none_037c2e34dfa1b048ad37c896d4a6826125fc0b8d.cab SigningTime : 12/11/2015 5:09:19 PM mshelp-x-none_4c3af1336cc8599e0b6f1cebcc7a22d2fd44d524.cab SigningTime : 10/25/2013 7:47:32 PM msocf-x-none_b6de60914c3e537e2c9fa1053f90faebc4b61e92.cab SigningTime : 8/14/2013 4:40:23 AM msohevi-x-none_a01a35c87b1b61d7cab0f6782c01e98dbbc2f72c.cab SigningTime : 12/18/2018 12:28:58 PM msointl-en-us_cbb2e8d950e9de471c4b7770b6699032dde0ef98.cab SigningTime : 2/17/2015 8:16:04 PM msores-x-none_c7a4834f7b28175fd385cb8c83b4420b73384a09.cab SigningTime : 9/7/2013 1:11:01 AM msptls-x-none_e2cdd9de533758b57ac6c6cc3520ddd55da0ba85.cab SigningTime : 10/20/2018 4:22:37 PM mstore-x-none_c408d603eb2a9c0c0573a888818c1e8533e44fa7.cab SigningTime : 11/12/2014 2:05:51 AM mtextra-x-none_d02b158e7c2dc7219dde12e91568dcde7a3c13ca.cab SigningTime : 8/28/2018 5:11:46 PM oart-x-none_0ea4efd1d02042004a2378c3dfbb69a8e2849860.cab SigningTime : 1/22/2019 6:44:30 PM oart-x-none_5b6a337944a2f282db4c626bf56243a5a9e8fa4c.cab SigningTime : 5/17/2018 2:43:51 PM oartconv-x-none_daef313f48ba188dec24ae1779a9cc7b9486f802.cab SigningTime : 1/22/2019 6:44:02 PM oartconv-x-none_db1971e40e0069c84e31a87cc0231de5694925d5.cab SigningTime : 5/17/2018 2:43:31 PM ocfxca-x-none_ea01b56460836086e46ac9135fa5ff094dd4b818.cab SigningTime : 6/17/2015 5:26:57 PM offowc-x-none_2874cb2b3ef22a8ea1f839c8adb8aae66547c56c.cab SigningTime : 2/15/2019 6:40:22 PM oleo-x-none_6295985a2c496a5ed4be2b454247afc14f3d7c48.cab SigningTime : 11/30/2018 3:50:03 PM onenoteintl-en-us_52ec80bd9d14edd1dfdb312ee0ef0f45f4879a1c.cab SigningTime : 7/12/2016 11:56:08 PM osc-x-none_31d563081f0a879ba0c775ae9b25578279591abd.cab SigningTime : 5/14/2015 6:12:33 PM ose-x-none_3078d43e678365e4c9e8743915f13a74d8bc089c.cab SigningTime : 6/27/2018 10:15:24 AM osetup-x-none_1d9ab800d30916ec8a16a7d5f792ec58a16f25f1.cab SigningTime : 6/26/2018 2:18:58 PM ospp-x-none_5d0c591708ab6fdb76553c0a2ca137dc3a8b7282.cab SigningTime : 11/12/2014 2:05:53 AM otkruntimertl-x-none_ed039e26757d92e91629f0ef966dedd3aeace2a7.cab SigningTime : 2/10/2016 12:48:40 AM outexum-x-none_2dc9cb78765fe55550051b768eb883ba94247e88.cab SigningTime : 3/14/2019 1:52:12 PM outlfltr-x-none_0a5c2c66c1d8cf822d0b4b2b8f6940d66ced1faf.cab SigningTime : 7/12/2016 11:28:26 PM outlfltr-x-none_d315e4d39aea9d809dd0112dcd6ab8b1ffdbbb14.cab SigningTime : 10/16/2013 5:04:14 AM powerpointintl-en-us_c3fdea1cc362f2472dd94ba8d001fc36e8955d29.cab SigningTime : 6/26/2018 2:55:23 PM proof-en-us_a3a11b51b90c7f31fd661d7b401bcc7abbe260be.cab SigningTime : 6/5/2017 5:33:40 PM publisher-x-none_2fdbf1786c5e550b7076d2aac9bf8f732b9ef89d.cab SigningTime : 5/17/2018 2:44:16 PM riched20-x-none_e31f07b596a5e1c0989d04d214a55225955c68cc.cab SigningTime : 7/16/2015 10:25:29 AM stslist-x-none_af83eec5aba68f724978bde564bbdefb27ae950f.cab SigningTime : 2/15/2019 6:41:52 PM targetdir-x-none_4df7780127a2023254259c63c856feaed955abb5.cab SigningTime : 8/14/2013 4:46:08 AM targetdir-x-none_9cc0dbf4acd3806cd7efb742772affe9e9384c4d.cab SigningTime : 7/21/2011 3:12:30 PM usp10-x-none_4bf400783d89e5dd97c93cc8c65d394ac43721a0.cab SigningTime : 8/27/2017 1:28:39 PM vbe7-x-none_2b1e4e0617ccd54821ed36fa61cc8dd04da5804f.cab SigningTime : 4/12/2017 2:28:42 PM vbe7-x-none_da7ecd740b30d8f2699acc30f5beda805138241e.cab SigningTime : 10/20/2016 3:18:56 PM visio-x-none_3208a2d87b4c506255d9f123c747278f8d79b349.cab SigningTime : 5/17/2016 8:03:01 PM visio-x-none_5969b6a7114f7dceaf1150c5e1b26594ba286553.cab SigningTime : 1/22/2019 6:45:24 PM vviewer-x-none_d78f3d1bc020ff923b6126dd297480c3c0b06050.cab SigningTime : 5/17/2016 8:00:40 PM wce-x-none_85cc31f351a3cd3c448ed06bcf311babdbbbfd22.cab SigningTime : 6/5/2017 5:03:52 PM wec-x-none_9524dc91a4f6d1b09c4f5ff2ae22d6a9779d9a65.cab SigningTime : 9/5/2015 1:37:31 AM wordintl-en-us_8c28c699d2c958183efaa43e34d3e109e0b0582e.cab SigningTime : 12/28/2018 11:43:19 PM Link to comment Share on other sites More sharing options...
Dave-H Posted October 18, 2020 Share Posted October 18, 2020 FWIW, would one way of determining exactly what updates are current be to install a clean pre-service pack Office 2010 onto a supported operating system like Windows 10, and then see what updates are offered for it by the Windows Update system? Any which aren't offered can surely be presumed to have been superseded? Link to comment Share on other sites More sharing options...
InterLinked Posted October 18, 2020 Author Share Posted October 18, 2020 50 minutes ago, Dave-H said: FWIW, would one way of determining exactly what updates are current be to install a clean pre-service pack Office 2010 onto a supported operating system like Windows 10, and then see what updates are offered for it by the Windows Update system? Any which aren't offered can surely be presumed to have been superseded? Hmm... it could certainly corroborate other methods... but Windows Update has been so whack I don't I would rely on it. Is it something you're able to do? WSUS apparently has some way of showing supersedence for updates, but I'm not running a WSUS operation here! I'm currently extending my Excel sheet back so I can use it for crosschecking updates. In the middle of 2016 so far, will probably have to take it back to 2013 or 2012 or so. I was able to successfully check a few CABs, 2 were not superseded and 1 was. Still need to do the other ~50 eventually! I'll continue making my findings available as I learn more. Wouldn't it be nice if Microsoft just released SP3? Link to comment Share on other sites More sharing options...
Dave-H Posted October 18, 2020 Share Posted October 18, 2020 Well I'm thinking of installing Office 2010 on my netbook, which is Windows 10 32 bit. I already have it on the Windows 10 side of my multi-boot main desktop, which has the 64 bit version on it, and Windows Update has always worked fine to update that. If I go ahead with the new 32 bit installation, I'll let you know what updates get offered! Link to comment Share on other sites More sharing options...
InterLinked Posted October 18, 2020 Author Share Posted October 18, 2020 1 minute ago, Dave-H said: Well I'm thinking of installing Office 2010 on my netbook, which is Windows 10 32 bit. I already have it on the Windows 10 side of my multi-boot main desktop, which has the 64 bit version on it, and Windows Update has always worked fine to update that. If I go ahead with the new 32 bit installation, I'll let you know what updates get offered! Awesome, thanks! It'll be interesting to see where that lines up. One problem I've noticed is Microsoft is, well, sloppy about supersedence. For one thing, a lot of their Outlook updates (the really large ones) show up as not superseded, except I know, in practice, they have been, becuase there'll be a newer version with a similar filename that's only a few KB larger or smaller. I'm still finding non-superseded (possibly legitmate) updates though as far back as 2016. Talk about a real PITA. NOWHERE on the official update webpages does it say, oh yeah, go back and download all these updates since 2013. It just links to the latest KB as if that were all you need! What a joke! Link to comment Share on other sites More sharing options...
InterLinked Posted October 18, 2020 Author Share Posted October 18, 2020 OK @Dave-H The Excel file is complete. Downloadable from w2k.phreaknet.org - it's right at the top It contains *EVERY* single Office 2010 update ever released, to my knowledge. I scoured all the Microsoft KB articles. Probably took around ~5 hours total. Supersedence for every update is also listed where provided, and formulas and colors keep track of which updates have been made unnecessary by future updates. There's still some questions I have, but this helps, so it's a start. Anyways, could be a great asset in crosschecking updates now. I'd be interested to see what updates you're offered and how they line up on this sheet. Maybe you can note the KBs but not install? 1 Link to comment Share on other sites More sharing options...
Dave-H Posted October 18, 2020 Share Posted October 18, 2020 I don't think that not installing the updates is an option, Windows Update will just do it automatically. They will remain listed in Windows Update though so it will be easy to see which ones were installed. I don't know when I will get to doing this, don't expect it too quickly! My plan is to probably uninstall Office 2010 from the Windows 10 side of my main machine, and replace it with Office 2019, which I suspect will be the last standalone non-subscription version of Office. Then I will use the Office 2010 licence key from that old desktop installation to install it on the Windows 10 side of my netbook. Link to comment Share on other sites More sharing options...
InterLinked Posted October 18, 2020 Author Share Posted October 18, 2020 OK, @Dave-H and @crashnburn4u I figured out part of what's going on, in the process of tracing my mysterious CABs Now that I have the Excel sheet, it's fairly easy. Properties displays the version number of every MSU in the files extracted in the CAB, so I just go in each folder. What I'm finding is that what happened is that catalog.update.microsoft.com offers update in CAB format. However, the newer KBs, from at least the past few years, link to EXEs on download.microsoft.com. I think what happened is up through February, I was copying KB #s into the Catalog portal, and downloading CAB files, but after that, I just clicked the links in the KB articles and downloaded the EXEs, and never looked back. Interesting! Personally, I prefer the EXEs, because they contain the KB number in them which makes referencing really easy. The CAB file names are only listed in update.catalog - I would need to make some kind of script to trawl through the site and iterate over all KB numbers and make a list of which CAB file names go with which KBs - and not sure how to approach to be honest... esp. since some KBs have multiple files for download. Also explains why I only downloaded the en-us CAB for some of those updates, whereas the EXEs have all the languages. Didn't want to manually download every language update! Many older KBs do not have EXE updates, though, so I have to keep the CABs around in the event they are necessary. Once I know exactly what CABs are which KBs, and I know if they were definitely superseded or not, I can then manually try installing them on my patched Vista testbench and see what happens. Then, we'll know a little bit more, and maybe some of those CABs really are redundant. At that point, I'll be feeling much more confident about all this! 1 Link to comment Share on other sites More sharing options...
InterLinked Posted October 18, 2020 Author Share Posted October 18, 2020 2 hours ago, Dave-H said: I don't think that not installing the updates is an option, Windows Update will just do it automatically. Can't you set it to "Download but let me choose to install" or whatever it's called? 2 hours ago, Dave-H said: They will remain listed in Windows Update though so it will be easy to see which ones were installed. I don't know when I will get to doing this, don't expect it too quickly! My plan is to probably uninstall Office 2010 from the Windows 10 side of my main machine, and replace it with Office 2019, which I suspect will be the last standalone non-subscription version of Office. Nope, they've already confirmed there will be a non-subscription "Office 2022" next year. Course, I won't be buying it. I honestly wouldn't care much now if they discontinued the perpetual, because Office is so awful now (like Windows) that I would never use a modern version. 2 hours ago, Dave-H said: Then I will use the Office 2010 licence key from that old desktop installation to install it on the Windows 10 side of my netbook. OK, now we're talking! Here's where I've gotten. Surprisingly, my spreadsheet helped me considerably in tracing many of these CABs. I probably could trace about 60% already. I need a bit more help with the other ones. Most of the newer ones I was able to trace, but some of the older ones are more difficult because there aren't EXEs available and CAB tracing is a mess. If only there were a way in the catalog to feed it a CAB name and get a KB back. But nope. Tried it, and now I get a server error every time I use that. Have to check the catalog in a different browser now. Anyways, here's what I've gotten at so far - traced/confirmed KB #s listed below the appropriate update - the way I traced was not actually using the signing time as much but mostly just the version numbers, then going there in the sheet, finding the appropriate category, and checking each of a handful of updates until I found a file name match like "access-x-none" for instance: access-x-none_8b5269f69d8184a3d57452c15344a77c4029e3e0.cab SigningTime : 2/15/2019 6:38:33 PM 4018363 accessolkaddin-x-none_4571200d0c9db16b528f6102c7efcc394775f61f.cab SigningTime : 10/14/2015 11:50:17 AM convintl-en-us_38dc63af44da4516f4e34c703bddd4895991ff7e.cab SigningTime : 8/25/2017 8:11:33 PM 3213626 csi-x-none_d8eb94e0c20a0a6e007dbcf657ace19a293e5171.cab SigningTime : 9/5/2015 1:36:14 AM 3054886, no EXE (CAB only) https://www.catalog.update.microsoft.com/Search.aspx?q=3054886 excelintl-en-us_643f56790952224f651b92cbcfd18938de8f3720.cab SigningTime : 3/23/2015 1:47:50 AM 2589348, no EXE exppdf-x-none_78e193d7fa3be46fa6c07f73d3efebeed167a549.cab SigningTime : 8/13/2015 8:20:05 AM 3055047, no EXE filterpack-x-none_0badc2b5c4c30be34378d267f4284034573a1496.cab SigningTime : 6/18/2019 4:55:07 PM 4509295 fm20-x-none_28210a36f7d5d948e8b95cc9d4b9a9141eedc557.cab SigningTime : 11/20/2014 12:12:59 PM 3054873, no EXE (CAB ONLY) fm20-x-none_9649a309eee15b5d32c65c1d1b522c4d8eeee716.cab SigningTime : 6/24/2015 3:22:34 AM 2553154, no EXE gfonts-x-none_23715aec547df5d7824747f46ff04e82f36a2d33.cab SigningTime : 10/3/2014 7:04:45 PM 2589386, no EXE gfx-x-none_3b7db2e32c6c15db9aa5f868e28b2966e833e84d.cab SigningTime : 7/24/2013 10:24:55 AM --- Patch;gfx;14.0.7106.5000 - somewhere around Apr 2014? gkall-x-none_b77a1de492d2701b6e8ecb2c627d4e8ec2e76fb3.cab SigningTime : 5/17/2016 8:01:29 PM groove-x-none_c9e8eb19a37187686489aa3562e51a54d41a9bab.cab SigningTime : 12/18/2013 8:11:06 PM slightly older than https://support.microsoft.com/en-us/help/2825817/description-of-the-sharepoint-workspace-2010-hotfix-package-groove-x-n ieawsdc-x-none_48528979c421e062fd198908d5de4828b99ff32e.cab SigningTime : 7/16/2015 10:24:02 AM infopath-x-none_71e941bd9c288cac97405c0b44dd140d171bebde.cab SigningTime : 2/10/2016 12:47:59 AM 3114414 ipeditor-x-none_286d99c11bb8da6afadfd38842eb965a3869a40a.cab SigningTime : 12/18/2013 8:10:34 PM msaddndr-x-none_fe7e444293cb613cbd3883bac96bf50eb76ba8a1.cab SigningTime : 4/17/2014 6:12:41 PM 2880971, no EXE (CAB only) mscomctlocx-x-none_037c2e34dfa1b048ad37c896d4a6826125fc0b8d.cab SigningTime : 12/11/2015 5:09:19 PM 2881029 mshelp-x-none_4c3af1336cc8599e0b6f1cebcc7a22d2fd44d524.cab SigningTime : 10/25/2013 7:47:32 PM msocf-x-none_b6de60914c3e537e2c9fa1053f90faebc4b61e92.cab SigningTime : 8/14/2013 4:40:23 AM msohevi-x-none_a01a35c87b1b61d7cab0f6782c01e98dbbc2f72c.cab SigningTime : 12/18/2018 12:28:58 PM 2553332 msointl-en-us_cbb2e8d950e9de471c4b7770b6699032dde0ef98.cab SigningTime : 2/17/2015 8:16:04 PM msores-x-none_c7a4834f7b28175fd385cb8c83b4420b73384a09.cab SigningTime : 9/7/2013 1:11:01 AM msptls-x-none_e2cdd9de533758b57ac6c6cc3520ddd55da0ba85.cab SigningTime : 10/20/2018 4:22:37 PM 3114565 mstore-x-none_c408d603eb2a9c0c0573a888818c1e8533e44fa7.cab SigningTime : 11/12/2014 2:05:51 AM 2553140, no EXE mtextra-x-none_d02b158e7c2dc7219dde12e91568dcde7a3c13ca.cab SigningTime : 8/28/2018 5:11:46 PM 4092436 oart-x-none_0ea4efd1d02042004a2378c3dfbb69a8e2849860.cab SigningTime : 1/22/2019 6:44:30 PM 4462172 oart-x-none_5b6a337944a2f282db4c626bf56243a5a9e8fa4c.cab SigningTime : 5/17/2018 2:43:51 PM 3115197 oartconv-x-none_daef313f48ba188dec24ae1779a9cc7b9486f802.cab SigningTime : 1/22/2019 6:44:02 PM 4462187 oartconv-x-none_db1971e40e0069c84e31a87cc0231de5694925d5.cab SigningTime : 5/17/2018 2:43:31 PM 3115248 ocfxca-x-none_ea01b56460836086e46ac9135fa5ff094dd4b818.cab SigningTime : 6/17/2015 5:26:57 PM 2553347 (no EXE, CAB only) offowc-x-none_2874cb2b3ef22a8ea1f839c8adb8aae66547c56c.cab SigningTime : 2/15/2019 6:40:22 PM 4461626 oleo-x-none_6295985a2c496a5ed4be2b454247afc14f3d7c48.cab SigningTime : 11/30/2018 3:50:03 PM onenoteintl-en-us_52ec80bd9d14edd1dfdb312ee0ef0f45f4879a1c.cab SigningTime : 7/12/2016 11:56:08 PM osc-x-none_31d563081f0a879ba0c775ae9b25578279591abd.cab SigningTime : 5/14/2015 6:12:33 PM ose-x-none_3078d43e678365e4c9e8743915f13a74d8bc089c.cab SigningTime : 6/27/2018 10:15:24 AM 4022206 osetup-x-none_1d9ab800d30916ec8a16a7d5f792ec58a16f25f1.cab SigningTime : 6/26/2018 2:18:58 PM 4022208 ospp-x-none_5d0c591708ab6fdb76553c0a2ca137dc3a8b7282.cab SigningTime : 11/12/2014 2:05:53 AM otkruntimertl-x-none_ed039e26757d92e91629f0ef966dedd3aeace2a7.cab SigningTime : 2/10/2016 12:48:40 AM outexum-x-none_2dc9cb78765fe55550051b768eb883ba94247e88.cab SigningTime : 3/14/2019 1:52:12 PM 3114559 outlfltr-x-none_0a5c2c66c1d8cf822d0b4b2b8f6940d66ced1faf.cab SigningTime : 7/12/2016 11:28:26 PM outlfltr-x-none_d315e4d39aea9d809dd0112dcd6ab8b1ffdbbb14.cab SigningTime : 10/16/2013 5:04:14 AM powerpointintl-en-us_c3fdea1cc362f2472dd94ba8d001fc36e8955d29.cab SigningTime : 6/26/2018 2:55:23 PM 4022136 proof-en-us_a3a11b51b90c7f31fd661d7b401bcc7abbe260be.cab SigningTime : 6/5/2017 5:33:40 PM publisher-x-none_2fdbf1786c5e550b7076d2aac9bf8f732b9ef89d.cab SigningTime : 5/17/2018 2:44:16 PM 4011186 (SUPERSEDED) riched20-x-none_e31f07b596a5e1c0989d04d214a55225955c68cc.cab SigningTime : 7/16/2015 10:25:29 AM 2589318, no EXE stslist-x-none_af83eec5aba68f724978bde564bbdefb27ae950f.cab SigningTime : 2/15/2019 6:41:52 PM 2589339 targetdir-x-none_4df7780127a2023254259c63c856feaed955abb5.cab SigningTime : 8/14/2013 4:46:08 AM targetdir-x-none_9cc0dbf4acd3806cd7efb742772affe9e9384c4d.cab SigningTime : 7/21/2011 3:12:30 PM usp10-x-none_4bf400783d89e5dd97c93cc8c65d394ac43721a0.cab SigningTime : 8/27/2017 1:28:39 PM 3213631 vbe7-x-none_2b1e4e0617ccd54821ed36fa61cc8dd04da5804f.cab SigningTime : 4/12/2017 2:28:42 PM 3128031 vbe7-x-none_da7ecd740b30d8f2699acc30f5beda805138241e.cab SigningTime : 10/20/2016 3:18:56 PM 3115120 visio-x-none_3208a2d87b4c506255d9f123c747278f8d79b349.cab SigningTime : 5/17/2016 8:03:01 PM 3114872 visio-x-none_5969b6a7114f7dceaf1150c5e1b26594ba286553.cab SigningTime : 1/22/2019 6:45:24 PM 3115314 vviewer-x-none_d78f3d1bc020ff923b6126dd297480c3c0b06050.cab SigningTime : 5/17/2016 8:00:40 PM 2999465 wce-x-none_85cc31f351a3cd3c448ed06bcf311babdbbbfd22.cab SigningTime : 6/5/2017 5:03:52 PM 3191908 wec-x-none_9524dc91a4f6d1b09c4f5ff2ae22d6a9779d9a65.cab SigningTime : 9/5/2015 1:37:31 AM wordintl-en-us_8c28c699d2c958183efaa43e34d3e109e0b0582e.cab SigningTime : 12/28/2018 11:43:19 PM Link to comment Share on other sites More sharing options...
InterLinked Posted October 18, 2020 Author Share Posted October 18, 2020 OK, here's something weird... @Dave-H So I went through and tried installing all the EXE updates I'd determined from CABs (and previously deleted the corresponding CABs, since I don't need them regardless). Most of them actually installed, so a lot of these older updates still are required to get up to date and aren't superseded. These all said "already installed" so these are in practice superseded or irrelevant - and now noted in my Excel sheet (not yet updated online): access2010-kb4018363-fullfile-x86-glb.exe oart2010-kb3115197-fullfile-x86-glb.exe - probably would've been valid but there's a newer update in the set oartconv2010-kb3115248-fullfile-x86-glb.exe - ditto vbe72010-kb3115120-fullfile-x86-glb.exe vbe72010-kb3128031-fullfile-x86-glb.exe visio2010-kb3114872-fullfile-x86-glb.exe visio2010-kb3115314-fullfile-x86-glb.exe So, I deleted all of these. This is part of why I wanted to back-trace the CABs to KB #s. I knew that some of them had to be irrelevant. I suspect some of the CABs I've not been able to trace to KB #s are also irrelevant, but not sure how I can test that or get KB #s easily from those still. Only thing left is powerpointloc2010-kb4022136-fullfile-x86-glb.exe When trying to install it says: There are no products affected by this package installed on the system and I can't figure out why. My sheet doesn't show it's been superseded and it's a "relatively" new update. It says PowerPoint 2010 equation editor, and I don't see how that wouldn't affect me. There is also talk about "localized versions of PowerPoint", but I don't really get what the deal is here. Why is it refusing to install? Link to comment Share on other sites More sharing options...
Dave-H Posted October 18, 2020 Share Posted October 18, 2020 Quote Can't you set it to "Download but let me choose to install" or whatever it's called? On Windows 10 Home updates are installed whether you like it or not AFAIK. On Windows 10 Pro, which is what I have, you can defer them for a period, but that's all. Not quite the same thing! Doesn't worry me as I'll want to install the updates anyway. Quote Nope, they've already confirmed there will be a non-subscription "Office 2022" next year. Course, I won't be buying it. That's good to know! I was fairly convinced that MS had now gone down the rental route with Office, like another major software vendor *cough* Adobe *cough*. I wish you could still buy copies of things like Photoshop and Premiere outright instead of having to permanently rent them for a monthly fee, but I guess that's never going to happen again now. I was fairly convinced that MS were doing the same, and it's good if they are still going to be producing standalone versions of Office that you can just buy and keep. I still reckon I'll update before Office 2022 comes out though! Link to comment Share on other sites More sharing options...
InterLinked Posted October 19, 2020 Author Share Posted October 19, 2020 2 hours ago, Dave-H said: On Windows 10 Home updates are installed whether you like it or not AFAIK. On Windows 10 Pro, which is what I have, you can defer them for a period, but that's all. Not quite the same thing! Doesn't worry me as I'll want to install the updates anyway. Whoops, I was thinking of Windows 7! 2 hours ago, Dave-H said: That's good to know! I was fairly convinced that MS had now gone down the rental route with Office, like another major software vendor *cough* Adobe *cough*. Oh, yeah, that's just disgusting. But Adobe has the same problem anyways. Their Reader DC programs are absolute dog stuff. I prefer XI and the older programs anyways, so good riddance. I can stop paying two pipers at once: Microsoft AND Adobe... thanks, guys! 2 hours ago, Dave-H said: I wish you could still buy copies of things like Photoshop and Premiere outright instead of having to permanently rent them for a monthly fee, but I guess that's never going to happen again now. Well... you could use the old ones... they're better anyways, IMO partly for that reason. 2 hours ago, Dave-H said: I was fairly convinced that MS were doing the same, and it's good if they are still going to be producing standalone versions of Office that you can just buy and keep. I still reckon I'll update before Office 2022 comes out though! Link to comment Share on other sites More sharing options...
Dave-H Posted October 28, 2020 Share Posted October 28, 2020 (edited) OK, I just installed Office 2010 new onto my Windows 10 Netbook, 32 bit version, from an ISO file. I was then offered 11 updates, in this order of installation - KB2553092 Office KB2553065 Office File Validation KB2553347 Office KB2553406 Outlook Social Connector KB2825640 Office KB982726 Definition Update KB3115475 Definition Update KB2553310 Office KB2566445 Sharepoint Workspace KB3001652 Visual Studio 2010 Tools for Office KB2687455 Service Pack 2 After restarting and scanning again, I was offered another 63 updates! - KB2589375 Office KB2589298 Office KB2850016 Office KB2817369 InfoPath KB2880971 Office KB2589386 Office KB2883019 Office KB2553140 Office KB2553154 Office KB2956076 Office KB3054873 Office KB2589318 Office KB2553313 Office KB3055047 Office KB2553388 Office KB3054886 Office KB2791057 Office KB2881029 Office KB2956063 Office KB2881030 Office KB2999465 Visio Viewer KB3191908 Office KB3213626 Office KB3213631 Office KB2553308 Outlook Social Conector KB3114414 InfoPath KB4011610 Office KB3115248 Office KB4022206 Office KB4022208 Office KB4092436 Office KB3213636 Office KB3114565 Office KB4461579 Office KB2553332 Office KB4462187 Office KB4461626 Office KB2589339 Office KB3115197 Office KB3114559 Outlook KB2920812 PowerPoint KB3114879 Filter Pack 2.0 KB4032216 Publisher KB2597087 Office KB3203462 Office KB4484377 Office KB3114885 OneNote KB4462172 Office KB4484385 Access KB4484379 Office KB4484530 Office KB2760601 SharePoint Workspace KB4486700 Office KB4092435 PowerPoint KB4486663 Outlook KB3203468 Office KB4484235 PowerPoint KB4486703 Word KB2956084 Excel KB4461625 Word KB4486707 Excel KB2881025 Visio KB4462225 Visio I assume the second lot were actually the updates to Service Pack 2 after it was installed. I hope this helps. This was on Windows 10, but I assume the same updates would be applied if the procedure was done on XP or any other version of Windows. Cheers, Dave. Edited October 28, 2020 by Dave-H Amendment Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now