Good question. Yes, we only need one as all products are always included in every image. Only the setup.exe differs. I don't know the reason / strategy behind this. So your question should be passed to and answered by Microsoft.
Which version of office is the most feature rich or has closest parity to Office 365? office 2016 mondo vs office 2019 vs office 2021 preview?
@ratzlefatz, @abbodi1406 Well, I am stumped. I followed all of the directions you guys supplied in here - PLUS, I went into the registry with elevated privileges and deleted every single key or reference to Office I could find. Run Office Scrubber and it tells me it can find no installations (OK, that seems encouraging...) Still, activation fails, with BOTH OfficeRTool AND KMS_VL_ALL. I'm starting to think that even if I do a full re-format and re-install of Windows, I'm STILL going to not be able to activate on this machine.
@Bladeslap there are no actual en-gb language for Office C2R, or proofing tools i'm not sure how MatchOS works i this case, but i will test and see - you can run YAOCTRU second time and choose Proofing Tools (with same channel and bittness)
@Bladeslap Could you make a test install with ODT along with Language ID="MatchOS" Fallback="en-us"? and share *.log files from Code: %temp% C:\Windows\Temp
An Update, on the off chance that there is some useful information to be gleaned (probs not, but...): After several attempts with OfficeRTool - install, convert, attempt to activate (fail) and then a wipe with OfficeScrubber (including running O16_MSI.vbs and C2R.vbs manually), and then also attempting authorization through KMS_VL_ALL - which were all unsuccessful, I changed up two things and got it to authorize. 1) After another complete scrub (including of every reference to MS Office I could find anywhere on the hard drive and in the Registry) I went with the C2R install with OfficeRTool instead of the OTC (or whatever the acronym is for the dedicated local install), which STILL failed local KMS authorization with OfficeRTool, but then; 2) That installation, of the C2R version, DID finally authorize with KMS_VL_ALL. I don't know if/why the C2R version would make a difference and I'm certainly not enough of a coder to know why the KMS_VL_ALL local KMS emulation would work while the OfficeRTool local KMS emulation apparently doesn't, but there it is. 3) Also, interestingly, @Bill_Boquet instructions on how to delete the difficult registry key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\Common\Smart Tag\Actions\{B7EFF951-E52F-45CC-9EF7-57124F2177CC} Seemed only to work once. I was able to run an elevated cmd prompt and open Regedit and navigate to that registry key, and go to "Permissions" -> "Advanced" and click on 1st entry and effectively "take ownership"/give myself authorization to delete the key, ONCE. All subsequent attempts to delete it from the elevated cmd/Regedit resulted in a "You Do Not Have authorization to Delete this Key" error. Can giving myself authority over that key once change something about it? Anyway, there's some additional info for you, if it is at all useful. Again, thanks to everyone on this forum for all the great work and especially the individualized assistance. You guys rule!