The documents mention that the issue was resolved after upgrading to software version 17.6.4, indicating that this is the principal software version being discussed.
The software version 17.6.4 is the one that resolved the issue, whereas the initial software version was 16.12.1s which had the problem.