I initially thought that too, KayleighLimacher...but the following seems to quash that posibility:
(taken from https://technet.microsoft.com/en-us/windows/release-info.aspx?f=255&MSPPError=-2147217396)
"Microsoft has updated its servicing model. The Semi-Annual Channel is a twice-per-year feature update release targeting around March and September, with 18-month servicing timelines for each release. The Semi-Annual Channel replaces the Current Branch (CB) and Current Branch for Business (CBB) concepts starting with Windows 10, version 1703, which released for broad deployment on July 27, 2017. Windows Update for Business deferral policies based on broad deployment readiness should be calculated from that date.
With each Semi-Annual Channel release, we recommend beginning deployment right away to targeted devices and ramp up to full deployment at your discretion. This will enable you to gain access to new features, experiences, and integrated security as soon as possible."
According to the accompanying chart in the above article, 1709 is in the Semi-Annual Channel, ready & available.
And James Johnson hits it on the head. And no amount of resetting of Win components, cycling of services, clearing/renaming the SoftwareDistribution folder, adjusting registry entries for reading/pulling the 1709 update, etc.....seems to correct it. I've tried all of it, ad nauseum.
But the issue is most certainly between the Enterprise variant of 1709 & Windows Update. The Pro variant downloads & installs via Windows Update without issue.