Windows 10 Update KB4013868: Is Microsoft’s WSUS broken?

Some strange thing happens since yesterday. A blog reader pointed it out to me in a private message. His Windows Services Update Server (WSUS) received 'an update KB4013868' for Windows 10, but it wasn't available for WU. Here are a few details.

It's a strange thing, what just happens with WSUS. Blog reader Michael R. has reported it to me within a private message. He wrote:

I just got Update KB4013868 for Windows 10 in WSUS, but Google didn't know anything about that Update. Also Windows 10 Windows Update didn't show this package, and I can't find it in Microsoft Update Catalog.

I posted it within my German blog and received another comment from a blog reader, confirming this strange behavior. This reader pointed out, that his WSUS is receiving since yesterday many updates like:

LanguageFeatureOnDemand – Windows 10 Build 15042 for x86-based Systems – (KB4013868) [ms-MY]
You may need to restart your computer. See the associated Microsoft Knowledge Base article for more info about this update.

LanguageFeatureOnDemand – Windows 10 Build 15042 for x86-based Systems – (KB4013868) [ne-NP]
You may need to restart your computer. See the associated Microsoft Knowledge Base article for more info about this update.

FeatureOnDemandTaiwaneseCalendar – Windows 10 Build 15042 for AMD64-based Systems – (KB4013868) [zh-TW]
You may need to restart your computer. See the associated Microsoft Knowledge Base article for more info about this update.

GDRDU: Cumulative Update for Windows 10 Build 15042 (KB4013868)
Install this update to resolve issues in Windows. For a complete listing of the issues that are included in this update, see the associated Microsoft Knowledge Base article for more information. After you install this item, you may have to restart your computer.

All Updates has KB4013868 in common, but there is no Knowledge Base article mentioned within update description, (this isn't really new to Microsoft), and this time also Microsoft Update Catalog doesn't have this package.

Blog reader Michael R. told me later, that he received 200+ updates (mostly features demand updates) with this KB number via WSUS. It seems that something is terribly broken with WSUS. Any idea what's going on?

Update: I've contacted Woody Leonhard, and we have another post here. Somebody supposed, it could have something to do, that Microsoft is switching Windows 10 Update to Universal Update Platform (UUP).