Fresh Install Win 10 Po 22h2 But With Conflicting 0x80070643

I have done a lot of reading on this error but also KB5001716 has been updated twice. The first was KB5001716 installed on Feb 24th 2024 the second time it was installed Mar 8 2024. Now on KB5033441 I'm getting the error code (0x80070643) on a daily basis. My question how can I have to KB5001716 installed on two different dates and no I can't uninstall either one. I so confused about this issue or issue's can anybody shed some light on this for me. Thank you.

The problem with KB5001716 has been solved by MS.
To solve the KB5033441 problem you have to increase the size of the Recovery partition.
Post a screenshot of "Diskmanagement" to give you the right advice.

Pentagon said:

The problem with KB5001716 has been solved by MS.
To solve the KB5033441 problem you have to increase the size of the Recovery partition

Thanks for your reply but my Recovery partition is well over the size that Windows is requesting. It is showing 522MB in Recovery partition which is more than enough as far as Microsoft is concerned. Thanks again for your reply.

duster340 said:

Thanks for your reply but my Recovery partition is well over the size that Windows is requesting. It is showing 522MB in Recovery partition which is more than enough as far as Microsoft is concerned. Thanks again for your reply.

522 MB is not enough!

Pentagon said:

522 MB is not enough!

If 522MB isn't enough at least you could of told me what it should be set at? Thanks again for your reply.

780mb

Pentagon said:

Post a screenshot of "Diskmanagement" to give you the right advice.

duster340 said:

Thanks for your reply but my Recovery partition is well over the size that Windows is requesting. It is showing 522MB in Recovery partition which is more than enough as far as Microsoft is concerned.

If someone ignores the request of a "Diskmanagement" screenshot and believes that 522 MB is more than enough, you can't help

Hi duster340,

To address your question about KB5001716, there are two updates with the same KB number, but they have different dates. If you look closely you will see the one on top of your list (below) is dated March 2024 and the other at the bottom of the list is dated October 2023.




Kind regards,

tecknot

Well you can tell me all you want what it should be but the bottom line is that reference KB from Microsoft is their screw up and your wasting time since it will be in time coded correctly. I found a program from Microsoft called Troubleshooting Pack Cabinet (.diagcab)
which allows me or anyone to ignore this and hide this mistake until its rectified. I for one am not going waste my time on this topic so I will be Unsubscribing from this Thread.