Failed to Install KB5001716 Error 0x80070643

Anonymous
2023-10-13T09:33:55+00:00

Failed to Install KB5001716 Error 0x80070643

I am unable to install this update. I start with the basic options of restarting and trying but it has now lasted for quite some time.

I have tried clearing the whole cache of windows update as per the guide by Seema-Bharti here how to clear windows update cache - Microsoft Community

However the failed update just reoccurs on reboot when I restart windows update service.

Os I tried to install it manually from the microsoft catalog. However, the exact KB5001716 cannot be found.

The closest match I found was Microsoft Update Catalog

When I download this, I downloaded the very bottom one, windows 10 and later GDR I cannot find an option to install it just expands into more and more files.

What do I do to clear this bad update?

Windows for home | Windows 10 | Windows update

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments
Answer accepted by question author
TekkieBoy 12,556 Reputation points Volunteer Moderator
2023-10-27T00:39:13+00:00

Try this:

Download and install this Update:

https://catalog.s.download.windowsupdate.com/c/upgr/2022/07/windows10.0-kb5015684-x64_523c039b86ca98f2d818c4e6706e2cc94b634c4a.msu 

Restart the PC when prompted.

After restarting, start the update search on the Windows Update settings page and let Windows install any updates found there.

When done restart the pc again.

Greetings

Was this answer helpful?

300+ people found this answer helpful.
0 comments
Answer accepted by question author
Anonymous
2023-10-20T04:45:31+00:00

I can confirm the inplace Upgrade does not work to resolve this.

Had an online Microsoft officer try the inplace upgrade as well and it will not update.

The issue with this update is that it errors when downloading so install is never attempted.

This issue resolved when the latest major upgrade for Windows 10 came thru. It didn't install the update however the update was removed from the updates to install after the major update had completed

Was this answer helpful?

50+ people found this answer helpful.
0 comments

47 additional answers

Sort by: Newest
Most helpful Newest Oldest
  1. Anonymous
    2024-01-12T15:25:55+00:00

    Found this on the web from TechWorm:

    The update brought a BitLocker encryption bypass that allows users to access encrypted data. So basically, Microsoft is installing a new version of the Windows Recovery Environment (WinRE) that fixes the BitLocker vulnerability.

    Microsoft has also shared a solution to fix the aforementioned problem, so feel free to follow it if you’re facing the issue,

    1. Open a Command Prompt window (cmd) as admin.
    2. To check the WinRE status, run reagentc /info. If the WinRE is installed, there should be a “Windows RE location” with a path to the WinRE directory. An example is, “Windows RE location: [file://%3f/GLOBALROOT/device/harddisk0/partition4/Recovery/WindowsRE]\?\GLOBALROOT\device\harddisk0\partition4\Recovery\WindowsRE.” Here, the number after “harddisk” and “partition” is the index of the disk and partition WinRE is on.
    3. To disable the WinRE, run reagentc /disable
    4. Shrink the OS partition and prepare the disk for a new recovery partition.
      1. To shrink the OS, run diskpart
      2. Run list disk
      3. To select the OS disk, run sel disk<OS disk index>  This should be the same disk index as WinRE.
      4. To check the partition under the OS disk and find the OS partition, run list part
      5. To select the OS partition, run sel part*<OS partition index>*
      6. Run shrink desired=250 minimum=250
      7. To select the WinRE partition, run sel part*<WinRE partition index>*
      8. To delete the WinRE partition, run delete partition override
    5. Create a new recovery partition.
      1. First, check if the disk partition style is a GUID Partition Table (GPT) or a Master Boot Record (MBR).  To do that, run list disk. Check if there is an asterisk character (*) in the “Gpt” column.  If there is an asterisk character (*), then the drive is GPT. Otherwise, the drive is MBR.
        1. If your disk is GPT, run create partition primary id=de94bba4-06d1-4d40-a16a-bfd50179d6ac followed by the command gpt attributes =0x8000000000000001
        2. If your disk is MBR, run create partition primary id=27
      2. To format the partition, run format quick fs=ntfs label=”Windows RE tools”
    6. To confirm that the WinRE partition is created, run list vol
    7. To exit from diskpart, run exit
    8. To re-enable WinRE, run reagentc /enable
    9. To confirm where WinRE is installed, run reagentc /info

    If you carefully follow these steps the update will install flawlessly.

    I can confirm that this solution - to resize the Recovery Partition does fix the problem. None of the other suggestions in this thread worked for me. I was initially hesitant but taking it carefully, step be step, it was successful. The faulty update has now installed correctly

    One additional point is that the OS partition index (referenced in step 4 above) seems to be the large Partition 4 as in...

    DISKPART> list part

    Partition ### Type Size Offset

    Partition 1 Recovery 300 MB 1024 KB

    Partition 2 System 100 MB 301 MB

    Partition 3 Reserved 128 MB 401 MB

    Partition 4 Primary 254 GB 529 MB

    Partition 5 Recovery 764 MB 255 GB

    This is documented in

    Select "OS partition index" - Windows 10 - Microsoft Community

    Good luck to anyone who still has this irritating and obscure bug.

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments
  2. Anonymous
    2024-01-11T22:41:05+00:00

    Found this on the web from TechWorm:

    The update brought a BitLocker encryption bypass that allows users to access encrypted data. So basically, Microsoft is installing a new version of the Windows Recovery Environment (WinRE) that fixes the BitLocker vulnerability.

    Microsoft has also shared a solution to fix the aforementioned problem, so feel free to follow it if you’re facing the issue,

    1. Open a Command Prompt window (cmd) as admin.
    2. To check the WinRE status, run reagentc /info. If the WinRE is installed, there should be a “Windows RE location” with a path to the WinRE directory. An example is, “Windows RE location: [file://%3f/GLOBALROOT/device/harddisk0/partition4/Recovery/WindowsRE]\?\GLOBALROOT\device\harddisk0\partition4\Recovery\WindowsRE.” Here, the number after “harddisk” and “partition” is the index of the disk and partition WinRE is on.
    3. To disable the WinRE, run reagentc /disable
    4. Shrink the OS partition and prepare the disk for a new recovery partition.
      1. To shrink the OS, run diskpart
      2. Run list disk
      3. To select the OS disk, run sel disk<OS disk index>  This should be the same disk index as WinRE.
      4. To check the partition under the OS disk and find the OS partition, run list part
      5. To select the OS partition, run sel part*<OS partition index>*
      6. Run shrink desired=250 minimum=250
      7. To select the WinRE partition, run sel part*<WinRE partition index>*
      8. To delete the WinRE partition, run delete partition override
    5. Create a new recovery partition.
      1. First, check if the disk partition style is a GUID Partition Table (GPT) or a Master Boot Record (MBR).  To do that, run list disk. Check if there is an asterisk character (*) in the “Gpt” column.  If there is an asterisk character (*), then the drive is GPT. Otherwise, the drive is MBR.
        1. If your disk is GPT, run create partition primary id=de94bba4-06d1-4d40-a16a-bfd50179d6ac followed by the command gpt attributes =0x8000000000000001
        2. If your disk is MBR, run create partition primary id=27
      2. To format the partition, run format quick fs=ntfs label=”Windows RE tools”
    6. To confirm that the WinRE partition is created, run list vol
    7. To exit from diskpart, run exit
    8. To re-enable WinRE, run reagentc /enable
    9. To confirm where WinRE is installed, run reagentc /info

    If you carefully follow these steps the update will install flawlessly.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  3. Anonymous
    2024-01-09T08:27:04+00:00

    Absolutely useless from the official Microsoft people, as usual!

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments