Is Office Update broken?

Another investigative note from ch100:

While doing research using the Windows Update MiniTool, I found few interesting results.

This tool is free and does not require an installer, being fully portable.

It appears to be a wrapper on top of Microsoft and/or Windows Update, uses the same databases, while providing more information than the Microsoft’s native tool.
It can even scan the WSUS database, if selected.

First run against Microsoft Update, out of the box settings, never completing (few hours, after which I stopped it).

The WindowsUpdate.log shows

2016-06-12          07:45:18:698       140        1710       Agent    Bundle contains no deployed children and thus is invalid.
2016-06-12          07:45:18:698       140        1710       Agent    Update {16C5A20C-D16E-4DAA-8F80-3BDEBF21C790}.201 is not a valid bundle. Not returning it.
2016-06-12          07:45:18:698       140        1710       Agent    Bundle contains no deployed children and thus is invalid.
2016-06-12          07:45:18:698       140        1710       Agent    Update {AC00B614-10F0-442C-9EFD-D4470795869A}.201 is not a valid bundle. Not returning it.
2016-06-12          07:45:18:714       140        1710       Agent    Bundle contains no deployed children and thus is invalid.
2016-06-12          07:45:18:714       140        1710       Agent    Update {7FF19D18-BB37-4ABD-812D-71B5342C93C2}.201 is not a valid bundle. Not returning it.
2016-06-12          07:45:18:714       140        1710       Agent    Bundle contains no deployed children and thus is invalid.
2016-06-12          07:45:18:714       140        1710       Agent    Update {04C1E818-87D9-4619-B550-B09A6CE9A242}.200 is not a valid bundle. Not returning it.
2016-06-12          07:45:18:714       140        1710       Agent    Bundle contains no deployed children and thus is invalid.
2016-06-12          07:45:18:714       140        1710       Agent    Update {7E94A429-9D5B-4859-8261-05D2448B2E27}.201 is not a valid bundle. Not returning it.
2016-06-12          07:45:18:714       140        1710       Agent    Bundle contains no deployed children and thus is invalid.
2016-06-12          07:45:18:714       140        1710       Agent    Update {ED40C741-DBD4-4110-94B9-BC143CCF1097}.200 is not a valid bundle. Not returning it.
2016-06-12          07:45:18:714       140        1710       Agent    Bundle contains no deployed children and thus is invalid.
2016-06-12          07:45:18:714       140        1710       Agent    Update {BA1F3C4F-4488-412A-8444-A40F89B86095}.201 is not a valid bundle. Not returning it.
2016-06-12          07:45:18:714       140        1710       Agent    Bundle contains no deployed children and thus is invalid.
2016-06-12          07:45:18:714       140        1710       Agent    Update {D5623D50-08F4-48B5-AB80-56D703052083}.200 is not a valid bundle. Not returning it.
2016-06-12          07:45:18:714       140        1710       Agent    Bundle contains no deployed children and thus is invalid.
2016-06-12          07:45:18:714       140        1710       Agent    Update {2341B05A-52A4-4CCC-8492-A2F69D5F152E}.201 is not a valid bundle. Not returning it.
2016-06-12          07:45:18:714       140        1710       Agent    Bundle contains no deployed children and thus is invalid.
2016-06-12          07:45:18:714       140        1710       Agent    Update {53CEFC99-5393-462C-99F3-DAC697654926}.201 is not a valid bundle. Not returning it.
2016-06-12          07:45:18:714       140        1710       Agent    Bundle contains no deployed children and thus is invalid.
2016-06-12          07:45:18:714       140        1710       Agent    Update {9783A6B9-AC8B-4857-9FC1-6FCE24F7CB2F}.201 is not a valid bundle. Not returning it.
2016-06-12          07:45:18:714       140        1710       Agent    Bundle contains no deployed children and thus is invalid.
2016-06-12          07:45:18:714       140        1710       Agent    Update {333B09CF-719C-41C6-BA84-1436D9F093F2}.200 is not a valid bundle. Not returning it.
2016-06-12          07:45:18:714       140        1710       Agent    Bundle contains no deployed children and thus is invalid.
2016-06-12          07:45:18:714       140        1710       Agent    Update {381952E2-CC60-4C88-ACC2-3E062B4DD5A7}.200 is not a valid bundle. Not returning it.
2016-06-12          07:45:18:714       140        1710       Agent    Bundle contains no deployed children and thus is invalid.
2016-06-12          07:45:18:714       140        1710       Agent    Update {093D54FD-35CD-4271-A51B-5AB0EB47BA96}.202 is not a valid bundle. Not returning it.

After that, I managed to complete the scan repeatedly by checking the box “Include superseded”.

However, the same entries remained in the log.
I did a lookup of those Updates in Microsoft Catalog and all of the problematic GUIDs point to Office 2013 Updates which my WSUS shows as “installed” but they are not found under Programs and Features.

Something is broken with Office 2013 Update.

The problem Office Updates as they have been identified in Microsoft Catalog are:

KB3114947
KB3039779
KB3101506
KB3114505
KB3114489
KB3114820
KB3115016
KB3055006
KB3114351
KB2975808
KB3114829
KB3114358
KB3114506
KB3114944

Maybe I should say that this installation of Windows 7 Ultimate 64-bit with Office 2013 is relatively new (few weeks old only), fully patched except for few Windows 10 Upgrade patches and I ran Disk Cleanup on it.

Is Disk Cleanup to blame for this situation or it can be easily reproduced on other installations?