Cumulative update KB4598242-OS Build mismatches-W10 20H2

Foxfan · 21 Jan 2021

ASUS Vivobook running Win 10 20H2 Home - OS Build 19042.685 (per winver)

WU offers, downloads and then installs KB4598242, and then fails with a "files missing or similar (my recall)-will try again" plus error code 0x8007000D.

I tried letting WU rerun it, same problem, and also cleared SoftwareDistribution and catroot2 folders, then rerunning. Same problems, same error.

The KB4598242 is listed on MS as being for W10 20H2, and for OS builds 19041.746 and 19042.746 - which aren't my build of 19042.685. I guess this may be why it doesn't install!

Any suggestions as to how I deal with this, including blocking this from WU?

Edit
I have removed SoftwareDistribution folder etc. which has of course removed the failed update from Update History. However, looking at Updates via Control Panel, I see an update KB4599841 Security Update, same date as first failed install of the other KB..242 (18/1), but this Security Update doesn't appear in Update History, though the MSRT on same date does, under Other Update.

Try3 · 21 Jan 2021

That CU updates you to 19042.746 so that is not the reason for the problem. A CU always increases the build number so starting from your current .685 is perfectly normal.

Whilst it might not be necessary, I suggest you use Windows Update - Reset - TenForumsTutorials
- It is the most comprehensive resetting procedure I have ever found and it resolved my problem ages ago when all other online guides to resetting WU had failed to fix it.

There is a TenForums News page for every CU including this one. Go to
KB4598242 CU - TenForums
and, at the bottom of the page, you will see direct download links for the CU. Download it and then run it after checking the SSU.

SSUs
- Many, but not all, CUs require an "SSU" to be run first.
- Read the CU page before doing anything and note the SSU referred to.
- Check for that SSU number [Control panel, Progs & features, View installed updates] and install it before the CU if it has not already been done. When WU attempts to install a CU, it automatically checks for any required SSU and runs it automatically. You'd normally not even notice it.
- If you are ever unsure about whether or not an SSU has already been done then you can download it and try to run it yourself. If it has already been done then it will just tell you so and no harm will have been done.

Denis

Foxfan · 22 Jan 2021

Denis,

Thanks for that.

I have run the batch file, and realise I should have piped the output somewhere, but didn't. However, it ran OK, with these points:-
- BITS and appidsvc weren't running anyway, and this was the case when I tried manual resetting before. I think I need to check the settings of those services anyway, although they haven't been changed on that machine from Day One.
-the key deletions in Windows Update policy reset section failed, because the keys apparently weren't there.

My plan now is to:-
1) check the SSU and instal if needed (which I think it is)
2) recheck for update via WU and see what happens.

As regards 2), I have the standalone CU update package for KB4598242 ready to use, but I am in two minds whether to run this after 1) above rather than going via WU as 2). Any recommendations?

sdowney717 · 22 Jan 2021

I like running stand alone msu installers, why not use that. ?
I had some update issue before and running the installer installed it when WU could not.

Try3 · 22 Jan 2021

Foxfan said:

I have run the batch file, and realise I should have piped the output somewhere, but didn't. However, it ran OK, with these points:-
- BITS and appidsvc weren't running anyway, and this was the case when I tried manual resetting before. I think I need to check the settings of those services anyway, although they haven't been changed on that machine from Day One.
-the key deletions in Windows Update policy reset section failed, because the keys apparently weren't there.

That is not a surprise & is not a problem. The batch file deletes things that might be there. They will not all be there in all cases.

Foxfan said:

My plan now is to:- 1) check the SSU and instal if needed (which I think it is)

I agree. Do it.

Foxfan said:

My plan now is to:- 2) recheck for update via WU and see what happens.
As regards 2), I have the standalone CU update package for KB4598242 ready to use, but I am in two minds whether to run this after 1) above rather than going via WU as 2). Any recommendations?

There is no benefit to using WU for this. You've got the CU now so just go ahead and run it.

All the best,
Denis

Foxfan · 22 Jan 2021

Denis,

Thank you for the information.

I've checked the SSU, which is listed as KB4598481, and it is shown as installed on 18/1, which is the same day as the main failing CU first tried to install via WU. Subsequent fails of that are obviously with an up-to-date SSU already in place.

I'll go for a direct update using the CU .msu file, and see what happens.

- - - Updated - - -

KB4598242 looked promising, but failed again with the 00x8007000D error, when run from the CU msu file.

I'm not sure where to go next, but I guess it may be to step through the reset batchfile and try it all over again.

No problems revealed with sfc, by the way.

Not particularly happy, as my HP desktop can't yet update to 2004/20H2 because of the unresolved and apparently unaddressed Conexant drivers issue, and now my ASUS laptop can't update thus CU for no apparent reason. So much for a reliable, stable Windows 10!

Try3 · 22 Jan 2021

Perhaps one of these threads might help
windows update error 00x8007000D site:tenforums.com
a non-TenForums search gives you a longer list but at least some of its results point to websites that might be useless
windows update error 00x8007000D

Personally, if the TenForums threads do not help, I suggest using the ISO/InstallUSB for the current Version to run a Repair install
- I would make a new system image first so I could be confident of getting back to square one. But installed applications should not be affected by a Repair install.
- I would check that all my file backups were up to date but there is on reason to expect your own files to be affected by a Repair install.
- My test of the Repair install effects would be to re-run the current SSU & CU. These need to be repeated after a Repair install because that procedure sets the computer back to the build number of the ISO when it was published.

Download Windows 10 ISO File -TenForumsTutorials
Repair Install - TenForumsTutorials

Denis

Try3 · 22 Jan 2021

Foxfan said:

… my HP desktop can't yet update to 2004/20H2 …

Hold on a minute. KB4598242 is a Version 2004-20H2 update not a Version 1909 update. I thought you had said you were on 20H2 but your last comment indicates otherwise [or were you merely dropping in a comment about your other computer?].

If you are on Version 1909 then you should not be using KB4598242 so you might not actually have any problem at all.

The latest Version 1909 CU is KB4598298 - KB4598298 - MSSupport There does not seem to be a TenForums page about it. This is unusual.
- The very latest one, KB4598298, is a so-called 'Preview' version issued on the third Tuesday of the month.
- The latest Version 1909 CU for which there is a TenForums News page is KB4598229 and I would go for that one because it is the latest 'Patch Tuesday' one.

Denis

Foxfan · 22 Jan 2021

Apologies for causing confusion.

The miscreant is an Asus laptop running W10 Home 20H2. This is the machine where the msu-run KB4598242 has again fallen over with the 0x8007000D error.

My other desktop machine (which I use for most things including writing in forums, as it has a decent keyboard and screen) is at present stuck on 1909 through the Conexant driver problems, but is not concerned in the problem at hand.

Try3 · 22 Jan 2021

OK.

So have you decided yet?
- Investigate using the links I posted?
- Just run a Repair install in the hope that it replaces whichever is the missing/misbehaving file?

Looking back at that post of mine, I regret giving the impression that investigation is better than a Repair install.
- I spent months investigating one Windows XP-7-10 problem without reaching any firm conclusions let alone any remedy.
- A Repair install is an established & reliable procedure that might allow you to resume normal operations without banging your head against the wall at all.

Denis