I have a Dell XPS 8930 SE desktop computer, running Windows 11 Pro. I have Bitdefender Total Security and Malwarebytes Premium as my security software.
I have never encountered any issue updating Windows with this computer until now.
This is a link to my topic at Bleeping Computer:
Windows 11 July Cumulative Update KB5015814 Fails - Error 0x8007054f - Windows 11
I will be updating that topic to state that I am requesting help here, providing the link to this topic, and will ask a Moderator to close my BC topic.
I have attached an SFC scan that I ran today. I have run several in the last two days since the problem arose and there are never any errors.
I ran SFCFix.exe as an Administrator. As you can see it hung after the successful DISM and I left it for 30 minutes, but there was no activity in the Task Manager. I tried again with the same result, after adding SFCFix.exe as an exception to my Bitdefender.
I tried all of the fixes enumerated in the BC topic, plus today tried installing the update from a Clean Boot. Always the same: Windows downloads the update, installs the update, and requests a restart. It does its 30% updating before restarting. Then it restarts normally and gets to 92 to 94 percent complete. At that point, it initiates a restart, and tries again starting from around 35%, and again failing at the same point or bit more, before restarting yet again, and then the infamous message: "Something didn't go as planned. Don't worry ...". The computer then restarts three or four times before the update is finally rolled back.
All in all, it takes about 45 minutes each from initiating the update download to getting my computer back with the update rolled back.
I don't have Speccy on my computer, but here is
the link to a complete AIDA64 Extreme report done after this all started two days ago.
I have not noted any software or hardware issues with the computer. It has been working flawlessly.
If there is any other information that you require, don't hesitate to ask. Thank you, in advance, for your interest in my issue.
Regards,
Phil
