User talk:85.210.106.248

Office notes

So-called Dogfood_DevMain branch was discovered around 2018. It appears to get daily builds of Office (or several a day, for example, 16.0.15822.20000 uploaded around 2022-10-24 17:30 GMT, 16.0.15824.20000 uploaded ~3 hours later).

Latest Dogfood_DevMain builds have no symbols available, and currently (1582x) do identify as v2211.

All old builds remain on CDN (those who understand C2R know why, you can install whichever older/current version you want), earliest known build so far confirmed to exist: 16.0.6101.1000 (uploaded 2016-12-14, but compiled on 2015-08-02, corresponds roughly to Office 2016 post-RTM).

A GitHub repo ( https://github.com/CNMan/C2R ) does document builds on all branches starting from 2018-05-04. Earlier build numbers are documented on http://ms-vnext.net/OfficeVersionTracker/ (but Dogfood_DevMain pre-2018 tends to only have .1000, then .2000 deltas, which in many cases are not documented to exist on OfficeVersionTracker).

Given that a single build is ~40-70GB for all languages, and this is 7+ years of daily builds, an estimate of disk space for all builds would be at least 70-127TB (assuming 260 builds compiled per year, over 7 years)...

85.210.106.248 10:25, 25 October 2022 (UTC)

Tried to install 6101.1000, it requires the use of a period-accurate Office Deployment Tool; and with all instances of the current channel GUID in UTF-16LE strings patched to the Dogfood_DevMain one (or everything already downloaded and in the right place); then install works fine. 85.210.106.248 16:31, 29 October 2022 (UTC)

Office notes, part 2

Early builds available in dogfood_devmain:

16.0.3309.1000 (2014-09-11)
16.0.3511.1000 (2014-11-12)
16.0.3518.1000 (2014-11-19)
16.0.3525.1000 (2014-11-26)
16.0.3602.1000 (2014-12-02)
16.0.3609.1000 (2014-12-10)
16.0.4300.1000 (2015-10-14?!)
16.0.6018.1000 (2015-07-09)
16.0.6020.1000
16.0.6021.1000
16.0.6023.1000
16.0.6024.1000
16.0.6025.1000
16.0.6027.1000
16.0.6028.1000
16.0.6029.1000
16.0.6030.1000
16.0.6101.1000 (2015-08-02)

Installing 3309.1000 (x64) was awkward for me:

• get my patched Office Deployment Tool (16.0.2731.1008), this build is the only one I know of that can handle the version cab layout
• obtain i640.cab for the build.
• right click i640.cab->properties->digital signatures->details->view certificate->certification path->Microsoft Testing Root Certificate Authority 2010->view certificate->install certificate->local machine->place all certificates in the following store->Trusted Root Certification Authorities (and finish the wizard, clicking yes as needed). we need to add test cert to trusted roots otherwise sigchecks for installing this testsigned office build will fail
• run setup_3327 /configure config.xml - it will error
• extract i640.cab to C:\Program Files\Microsoft Office 16\ClientX64 and also to C:\Program Files\Common Files\microsoft shared\ClickToRun (create directory trees as needed)
• run setup_3327 /configure config.xml again - this time the build should install

3309 has Office 2013 branding still.

85.210.106.248 13:28, 26 December 2022 (UTC)

Office 15/2013 4xxx

FFN 9981A3FE-BBC6-41C7-86F4-89DC69E477E2 appears to be O15 dogfood_devmain, it has daily builds from 4302 (2012-07-03) onwards.

85.210.106.248 19:08, 26 December 2022 (UTC)

O15 deployment tool (reshacked with correct FFN) can be used to install 4302, as long as the testsign root is trusted AND date is set back. 85.210.106.248 19:37, 26 December 2022 (UTC)

No need to trust testsign root or set date back for O15, it actually works with HKLM\SOFTWARE\Microsoft\ClickToRun\OverRide!DontVerify (REG_DWORD) set to 1 85.210.106.248 13:33, 27 December 2022 (UTC)

I say that, yet 4302 has a timebomb. 85.210.106.248 13:43, 27 December 2022 (UTC)