Forum Discussion
Cumulative update KB5001330 fails to install
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.
Open command>
diskpart
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
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:
\EFI\Boot
\EFI\Microsoft\Boot
\EFI\Microsoft\Recovery
... 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.
- zenshadeMay 01, 2021Copper Contributor
kr0tki had most of the answer I needed. In my case, shortly after buying my current laptop about a year ago with Windows 10 Home pre-installed, I played around with dual booting a few different flavors of Linux before finally settling on using vmWare to run Linux Mint as a virtual guest OS. Pop_OS! for some reason left behind a 72MB EFI folder, which left NO free space on my system/EFI partition. I removed the Pop_OS! folder, following most of @kr0tki's instructions, and after that the update finished without any issues. Hope that helps someone else get past this time consuming irritation quickly.
Edit: My error code was 0x800f0922, which I think primarily indicates a problem with the EFI partition not being big enough (or lacking free space) for the update.
- kr0tkiMay 03, 2021Copper ContributorGlad that you managed to resolve the issue.
Just worth pointing out: Apparently 0x800f0922 indicates a general problem with the EFI partition, not limited to lack of space. In my case there was enough free space, but the update failed to install because of missing files in \EFI\Microsoft\Boot.