WIndows Update stalled on erroneous update

This is what I get when I run Windows update:

The problem is, I do not have Office XP installed on my system (Win10/64 current version) and never have had it installed. My concern is this problem will prevent me from getting any future updates.

I can find no traces of Office XP on my system - which is not surprising since I never had it installed. Is there some way to tell Update to skip this install?

- - - Updated - - -

I thought I might have found a fix for this - but after following the instructions below the same problem recurred.

1. Stop the Automatic Updates service, clear the contents of the DataStore
and Download folders, and restart the Automatic Updates service.
Stop the Automatic Updates Service.
Click Start, Choose Run, In the Run box, type services.msc.
Click OK.
Right-click the Automatic Updates service.
Select Properties.
Under Service status, click Stop.
Click OK.

2. Delete the Contents of the DataStore and Download folders.
Click Start, Choose Run, In the Run box, type %windir%\SoftwareDistribution
Click OK.
Delete the contents of both the DataStore and Download folders (but NOT the folders themselves)

3. Start the Automatic Updates Service
Click Start, Choose Run, In the Run box, type services.msc.
Click OK.
Right-click the Automatic Updates service.
Select Properties.
Under Service status, click Start.
Click OK.

#1 - Yes, I tried the Hide or Show troubleshooter - twice - and although it said it fixed the problem, it did not.

#2 - I have Office 2016 Pro installed. Has that been stabilized and so will not receive any futher updates? I'll see if turning that option off stops the XP update.

Edit: well that seemed to work. So I'll leave it on for now. I do have 3D Builder installed which I do use from time to time. But I reckon I can re-enable the option to check for updates to that, and then disable it again.

Thanks for the suggestion.

Yup - I've seen quite a few of those postings. Many of them go back 2 - 3 years and have upwards of 90 or so counts of people with the same basic problem. So I'm guessing there is some obscure bug somewhere that for whatever reason MS has opted not to address.

My sense is it would be unproductive of me to try to determine what the bug is and what to do about it since so many other folks have failed with that intent. I'll just try to remember to enable the "other MS software" option from time to time to see what it might pick up.