Yeah, that happened to me on a W10 Enterprise laptop earlier today, too! I've never seen that error before! When I was offsite on a non-corporate wireless connection the subsequent update check was successful. I wonder if this was something transient in nature(?).
My initial reaction was that it was possibly caused by Microsoft being in the middle of prepping the update servers and services. Tomorrow is "Patch Tuesday" after all but I don't think the Microsoft phone stuff follows the same schedule. As a side note I find it amazing that Apple, who has 10 times as many smartphones to support, can push the button for 100% of their devices to all receive updates at once and can handle it with no issue. Microsoft's market share is laughable at best and still can't handle updating all of their devices at once? It's a good thing their market share isn't going up because it would take 2 years to push out an update at this rate.
-Mc