Jump to content

Slipstreaming all MSO 2010 updates


Recommended Posts

On 9/6/2020 at 10:16 PM, Dave-H said:

As far as Office 2010 is concerned, I think it would be better to wait until a couple of months' time when support has ended and there will be no more updates.
Then the package will not get out of date.
:)

 

On 10/2/2020 at 4:54 PM, Dave-H said:

Unfortunately I kept very few of the updates as there was no reason to as they just happened automatically through Microsoft Update (RIP) and I never had to install them manually.
:no::(

Between 9/6 & 10/2 ? 

Link to post
Share on other sites

On 10/4/2020 at 8:04 AM, Dylan Cruz said:

Hmm... looks like I've got mostly CABs on my end. I have everything through August. Waiting till 10/13 to get the rest.

AFAIK, the new updates are still EXEs.  I think those extract to CABs, which can then be slipstreamed into the ISO for install.

I'll take both / whatever can be had in a collection :D 

Link to post
Share on other sites
3 minutes ago, crashnburn4u said:

 

Between 9/6 & 10/2 ? 

There might be more updates on the October 13th "Patch Tuesday", but they will be the very last I would have thought.
:)

Link to post
Share on other sites

@crashnburn4u @Dave-H

I only have through August. However, everything I have can be downloaded from here:

https://docs.microsoft.com/en-us/officeupdates/office-updates-msi

e.g. https://support.microsoft.com/en-us/help/4484800/january-2019-updates-for-microsoft-office is January 2019

Not really sure if I want to upload them anywhere because I think it probably violates the TOS of this site.

You'll end up with maybe 10 files, which you need to extract.

I'll do it all again next Tuesday... can't wait to have a shiny final copy of Office! Only wish ESU updates applied to that as well as Windows :(

Link to post
Share on other sites

@Dave-H @crashnburn4u @win32

Well, well, today's the big day! It's been ten awesome years of Office twenty-ten, and EOS is today, but not the EOL! Office 2010 is on its way to a new immortality! :D

Time to get all those updates, soon! Will be doing that shortly, hopefully, but not today - bit backlogged with other things at the moment...

  • Like 1
Link to post
Share on other sites
8 minutes ago, Dylan Cruz said:

Office 2010 is on its way to a new immortality! :D

Imagine. Someone extends Office 2010 in the future so it can properly render all documents made with Office 365.2064! :lol:

And wrote plugins that incorporated all of that new version's features...

Why didn't anyone do that with 2000/2003? OK there's the compatibility pack (wish it worked on Windows 95) but I've seen PPTXs that don't even work properly with 2007.

I bought Office 2000 because I thought it would be the gateway to reading Office Open XML documents on Windows 95. :thumbdown

Link to post
Share on other sites
22 hours ago, win32 said:

Imagine. Someone extends Office 2010 in the future so it can properly render all documents made with Office 365.2064! :lol:

 

Isn't it already fully compatible?

I haven't encountered any issues

 

22 hours ago, win32 said:

And wrote plugins that incorporated all of that new version's features...

Why didn't anyone do that with 2000/2003? OK there's the compatibility pack (wish it worked on Windows 95) but I've seen PPTXs that don't even work properly with 2007.

 

Yup, and Excel sheets, too.

 

22 hours ago, win32 said:

I bought Office 2000 because I thought it would be the gateway to reading Office Open XML documents on Windows 95. :thumbdown

 

Link to post
Share on other sites
26 minutes ago, Dylan Cruz said:

 

Isn't it already fully compatible?

I haven't encountered any issues

Sorry, I thought the versioning for 365 had a year component to it. Turns out it's actually similar to Windows 10 versioning (currently they're on version 2009).

Link to post
Share on other sites
On 10/14/2020 at 1:41 PM, win32 said:

Sorry, I thought the versioning for 365 had a year component to it. Turns out it's actually similar to Windows 10 versioning (currently they're on version 2009).

But what's the compatability issue? I've not noticed any. 

Microsoft's motto lately though seems to be "if it ain't broke, break it". Hope they don't do that here! :realmad:

Link to post
Share on other sites
44 minutes ago, Dylan Cruz said:

But what's the compatability issue? I've not noticed any. 

The 365.2064 was referring to whatever Office release would come out in 2064. While Office 2010 hasn't yielded any compatibility issues for me yet, it is a "when" and not an "if" based on previous experience.

In fact, I printed a Word 2007 document with Office 365 in 2019 and there were several inexplicable spaces inserted into the document.

Link to post
Share on other sites
3 minutes ago, win32 said:

The 365.2064 was referring to whatever Office release would come out in 2064. While Office 2010 hasn't yielded any compatibility issues for me yet, it is a "when" and not an "if" based on previous experience.

In fact, I printed a Word 2007 document with Office 365 in 2019 and there were several inexplicable spaces inserted into the document.

Well, we already know 2007 has some major compatibility issues :D

Anyways, here's the final three months of dependency supersedences:

And yeah, I used replaces and supersedes interchangeably when I was taking notes, just downloaded these now. I'll need to merge these with the 2020-07 base I have leftover, extract everything, slipstream, reinstall, and see where we end up. Crossing my fingers this gets me to the finish line... which is *14.0.7261.5000 * the FINAL VERSION of Office 2010 ever. Once you get here, you're golden! :D

A bit said it's EOS, and there's no ESU, but honestly there's something kind of nice knowing you've got the final version and it won't get any newer. OK, sorry, I'm trying to find a silver lining ;)

October supersedes (and none are superseded, obviously)
4486707 replaces 4486665
4486700 replaces 4484532
4486701 replaces 4486660
4486663 replaces 4484373
4486703 replaces 4484492

September supersedes and is not superseded by October (??? not superseded, but supersede updates also superseded by Oct... ???):
4484530 replaces 4484373
4484533 replaces 4484492
All other Sept. updates superseded by Oct.

August supersedes and is not superseded by Sept/Oct:
4484385 supersedes 4464527
4484461 supersedes 4484415
4484454 - non-superseding update
4484379 replaces 4484238
4484375 supersedes 4484266
4484497 supersedes 4484382
4092435 - non-superseding update
4484494 supersedes 4484458
All other Aug updates (only 1!) superseded by Sept/Oct

Link to post
Share on other sites

OK, a few corrections, now that I went ahead and merged them:

October supersedes (and none are superseded, obviously)
4486707 replaces 4486665
4486700 replaces 4484532
4486701 replaces 4484533
4486663 replaces 4484497
4486703 replaces 4486660

September supersedes and is not superseded by October
4484530 replaces 4484373
All other Sept. updates superseded by Oct.

August supersedes and is not superseded by Sept/Oct:
4484385 supersedes 4464527
4484454 - non-superseding update *I feel like this is superseded, based on file size/name, but I can't find a succession for it

 OK - sanity check update-  I manually installed the update I thought supersedes this (...4530) and trying to install 4454 after says "update is already installed" - so although the Microsoft website is screwed up, this update IS superseded...

Best sanity check is sort alphabetically and look for very similar file sizes. That's a strong hint that one of those updates supersedes the other one.

back to August cont:


4484379 replaces 4484238
4092435 - non-superseding update
All other Aug updates superseded by Sept/Oct

These updates are at least as old as July, possibly much older, and were never superseded. I didn't track superseding last time I did updates from 2020/03 through 2020/07, so I don't have notes on these but they are there. Really wish Microsoft made this easier than having to track supercession of every update! A real PITA! They should do it for us... sure it's in their database, there's got to be a more elegant way to do it... anyways... that's it for now... going to extract and reinstall soon...

Edited by Dylan Cruz
Link to post
Share on other sites

Just curious... people always post about "security mitigations" for old Windows... what about for old Office?

Disable macros... which I never use anyways... but is there anything else?

Link to post
Share on other sites

@win32 @Dave-H @crashnburn4u

OK, I gave in... I can't figure out exactly how much of my February folder is redundant and it some updates failed in XP, so *maybe* I need a clean start.

Should have done this from the beginning, but since MSFT isn't providing one, I guess I'll make one

would a supersedence chart with full details be useful to anyone?

started making it:

 

Untitled.png

  • Like 1
Link to post
Share on other sites

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 account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...