Forum Discussion
Jauhar
Apr 14, 2021Iron Contributor
Cumulative update KB5001330 fails to install
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...
whiteboyjohn
Apr 15, 2021Copper Contributor
To everyone having this problem with KB5001330, I spoke with a Microsoft support agent last night after a day of trying various different file checking solutions. I have been getting this error (0x8007000d) which basically means that there are corrupted files within the update. The agent said, in response to me listing a number of the solutions i've tried, that I should reset windows on my computer. Basically I think it just uninstalls a bunch of updates so you can add them back in their original state (I am not great with computers, bear with me) I notice we all seem to have different error codes, but I am going to attempt the reset in about an hour I will report back if it works. You can keep all your personal data they just recommend you make a recovery drive to back up a couple system files so I'm going to get a USB. I will keep yall posted.
Ken94110
Apr 15, 2021Copper Contributor
John
I reset my PC to factory OEM reset on 4/10 and still get the errors. Microsoft and their support staff and even volunteers on their community sites are very dismissive and always assume it's us and not them! The updates have turned into an endless cat & mouse chase. There are numerous articles in major media venues about these issues and Microsoft is still not acknowledging that it's them, simply because the updates have worked for a few but not the rest of us.
I reset my PC to factory OEM reset on 4/10 and still get the errors. Microsoft and their support staff and even volunteers on their community sites are very dismissive and always assume it's us and not them! The updates have turned into an endless cat & mouse chase. There are numerous articles in major media venues about these issues and Microsoft is still not acknowledging that it's them, simply because the updates have worked for a few but not the rest of us.