Yea it's related to the port bindings for SQL Server. There is a way to manually fix it but installing the update is the easiest way. Though correcting the bindings may prove useful in future if Microsoft messes it up again.
It's actually a standard update now. AC is probably referencing the Preview July rollup update which also corrected the issue. But the update was finalized a few days ago in the August release. When you run Windows update, look for 2018-08 Security Monthly Quality Rollup for Windows.
Also strongly recommended to get that update installed before upgrading to V10 if you haven't already. If you do have orphaned bindings in the SQL settings, your V10 upgrade will fail.
.png "ACUF Donor I")
