The problem details explicitly mention that the issue occurred in version '16.12.x' before upgrading to 17.6.4. From the provided software version list, the closest valid match is '16.12.4', which is part of the 16.12.x series.
The issue was observed in the 16.12.x release series, and 16.12.4 is a valid member of that series listed in the options.