Apr 14 2021 09:11 AM
Apr 14 2021 09:11 AM
Hello Everyone ! I am getting an error for installing update KB5001330 Windows 10 version 20H2. I have no idea how to fix the issue. I have troubleshooted windows update but it wasn't helpful. I have made 4 back to back attempts to install KB5001330 but failed every time. I am looking for your kind help. The latest update has the same issue we had been facing with KB5000842 in the last two weeks
Apr 14 2021 12:52 PM
Apr 15 2021 02:02 AM
Apr 15 2021 02:51 AM
Apr 15 2021 04:00 AM
@Jauhar same issue here on 19042.844 (20H2).
Updates KB5001330 & KB5000842 fail to install.
Moreover my windows indsider program keeps telling me that it has to "fix a problem" and is unable to do so.
So no more updates installing and no more build incoming... nice move.
Apr 15 2021 06:35 AM
Apr 15 2021 06:36 AM
Apr 15 2021 10:49 AM - edited Apr 15 2021 02:11 PM
@Jauhar I was suffer with exact same situation.
It happens if you're using UEFI and your OS disk doesn't have EFI and MSR partition.
You have to recreate both of partition.
before you create it, you have to secure at lease 500MB from OS disk.
select disk 0(your OS installed disk)
create partition efi size=300
format quick fs=fat32 label="system"
create partition msr size=128
hope it will help
Apr 15 2021 12:07 PM
Apr 15 2021 12:22 PM
Apr 15 2021 12:28 PM
Apr 15 2021 12:34 PM
Apr 15 2021 02:06 PM - edited Apr 15 2021 02:09 PM
It's MB. Here is my Disk Status.
DISKPART> select disk 0
Disk 0 is now the selected disk.
DISKPART> list partition
Partition ### Type Size Offset
------------- ---------------- -------- --------
Partition 1 Primary 953 GB 32 KB
Partition 2 System 300 MB 953 GB --> EFI Partition
Partition 3 Reserved 128 MB 953 GB --> MSR Partition
it works your partition style should be GPT.
you can find out your partition style from input 'Get-Disk | ft -auto' in Windows PowerShell.
Apr 16 2021 04:25 AM
Apr 16 2021 04:59 AM - edited Apr 16 2021 05:03 AM
@Johnny_KimYour answer pointed me in the right direction to fix the error by myself.
In my case, the KB5001330 was installing successfully, then the computer restarted, then at 96% the update failed and rolled itself back, and after another restart i went to Windows Update to see the error number 0x800f0922. In my case, the reason for the failure was that my EFI partition was missing some files.
So, TL;DR: I fixed the error by replacing the \EFI\Microsoft\Boot directory on the EFI partition with the contents of C:\Windows\Boot\EFI.
The long story:
DISCLAIMER: this is technical, I do not take any responsibility, etc.
The EFI partition should contains the following directories:
... and if you dual-boot it may contain other directories, but that's irrelevant.
In my case the problem was, my EFI partition has got corrupted a month ago, and Windows, in its attempt to fix it, has broken it even more, the result being:
- some files and directories in \EFI\Microsoft\Boot went missing,
- in the root directory of the partition, several hundred files with randomly-numbered names have appeared.
This was preventing the KB5001330 update from installing.
So, first I assigned the drive letter to the EFI partition - it is normaly not assigned. I opened the cmd shell in administrator mode and entered "mountvol p: /s" (see here for details). The EFI partition became visible as the P: drive.
Then I removed all the randomly-named files from the root directory of P:\
Then I removed all the contents of the P:\EFI\Microsoft\Boot directory. Some of the files there were protected from deletion (in particular,BCD and BCD.log), so I just left them intact.
Then I copied the contents of the C:\Windows\Boot\EFI directory to P:\EFI\Microsoft\Boot. This way I restored the correct contents of the EFI partition.
Then I rebooted, to verify that the system still runs properly. (By the way, you do not need to unassign that drive letter P: - it disappearsafter reboot.)
Then I went to Windows update and proceeded to install KB5001330 again. This time it went smooth.
Note that the size of my EFI partition is 100MB; the standard size as created when installing Windows 10 from scratch. The size was not an issue in my case - I have 73 MB free on the EFI partition and it was enough to install KB5001330.
To reach my success, I used some information about restoring the EFI partition from this article. In my case it was not necessary to restore the whole partition from scratch, but if my solution does not help some of you, you might want to do the full restoration as described in that article.
Apr 16 2021 08:20 AM
Windows 10 Pro, 20H2, 19042.906, Windows Feature Experience Pack 120.2212.551.0, 32-bit O/S:
I restarted the update service, ran the troubleshooter and rebooted. Update KB5001330 continues to fail with error code 0x800f0984. Internet searching suggests the error code indicates component folders exist but component installer files are missing.
This issue kinds of seems like it is going to be: hold our breath and hope for an eventual fix. If components are missing, there isn't much we can do about that. I am going to pause updates for a few weeks so that my computer doesn't waste bandwidth trying the install repeatedly.
Apr 16 2021 08:31 AM
Apr 16 2021 08:55 AM
I have 3 laptops with Windows 10 Pro, all Dells:
- Latitude E7450 - no problem with update.
- Precision 7510 - no problem with update.
- Precision 5510 (my main workstation) - I tried all possible options and nothing worked for me.
I don't have any suspicious applications nor games installed, all my computers are very clean. I use Norton360, and all computers are virus and malware free.
Below is what I tried:
1) I downloaded from MS site the windows10.0-kb5001330-x64_48f2955cc5688bf56b32be1cca4cd1f02f1d36e2.msu file. It didn't work, the same result as when I used the standard "Windows Updates". I'm found in OS logs message: "Installation Failure: Windows failed to install the following update with error 0x8007000D: 2021-04 Cumulative Update for Windows 10 Version 20H2 for x64-based Systems (KB5001330)."
2) I downloaded from MS windows the
10.0-kb5001330-x64_d026afc35d0bd37f9580bd0865841d1d8607ac8d.cab update file, and proceeded using "dism /online /add-package /packagepath:.\10.0-kb5001330-x64_d026afc35d0bd37f9580bd0865841d1d8607ac8d.cab" from terminal window as administrator.
The same result as in #1.
3) Checked images using DISM and SFC
a) SFC /scannow
b) DISM /Online /Cleanup-Image /CheckHealth
This step reporter that the image can be repaired.
Note: After cleaning and (step 3c and 3d) and next update retry I'm getting "the image can be repaired."
c) DISM /Online /Cleanup-Image /ScanHealth
d) DISM /Online /Cleanup-Image /RestoreHealth
e) DISM /Online /Cleanup-Image /CheckHealth
Everything looks clean.
4) Repeated steps 1 - 3 twice...
On Monday and Thursday I spend more than 4 hours of my time, it's ridiculous that vendor of commercial grade operating system doesn't have solution...
I'm not planning to spend more time on it, but if somebody would find an "silver bullet", please let me know.