Microsoft Office 2016 Version 1802 -build 16.0.9029.2167 C2r- Re Download %5bhot%5d

The string explicitly mentions C2R. This is crucial because Office 2016 existed in two parallel worlds:

| Feature | C2R Version | Traditional MSI Version | | :--- | :--- | :--- | | Installation | Streaming, virtualized app environment | Standard Windows Installer | | Updates | Automatic, incremental, seamless | Requires patch files (.MSP) | | Versioning | Unique build numbers (e.g., 9029.2167) | Standard version numbers (e.g., 16.0.xxxx) | | Redownload | Uses Office Deployment Tool | Uses original ISO/media |

Why are users re-downloading build 9029.2167 specifically?
Because subsequent C2R updates (1803, 1804, etc.) introduced changes that some users disliked, including: The string explicitly mentions C2R

Thus, build 16.0.9029.2167 became a “golden build” for users who want the February 2018 feature set without later intrusions.

Once you have the setup.exe and the CAB/ODT files: Thus, build 16

Microsoft’s official tool can fetch specific builds if you know the GUID. Once you have the setup

<Configuration>
  <Add OfficeClientEdition="64" Channel="MonthlyTargeted">
    <Product ID="ProPlus2019Volume" PIDKEY="XXXXX-XXXXX-XXXXX-XXXXX-XXXXX">
      <Language ID="en-us" />
    </Product>
  </Add>
</Configuration>

Note: For build 9029.2167, you need to specify Version="16.0.9029.2167" and Channel="PerpetualVL2016". 3. Run: setup.exe /download configuration.xml 4. The build will re-download to your local source folder.

While Office 2016 was perpetual, by version 1802, Microsoft had already launched Office 2019. This specific build was the final cumulative update for the original 2016 Click-to-Run channel before Microsoft split servicing into "Semi-Annual Enterprise" and "Monthly."

Users on forums note that this build loads legacy VBA macros faster than any subsequent security patch.