also, Windows Defender shows a black screen. seems the security center is disabled.
How to fix install error - 0x80248007 for 2023-04 Update for Windows 11 Version 22H2 for x64-based Systems (KB4023057) ?
Hello team,
I am unable to update my windows 11 please assist me further. Previously I was using dev channel and now I am switched to stable win 11 and now the error is appearing.
10 answers
Sort by: Most helpful
-
-
Bart Plasmeijer 1 Reputation point
2024-06-02T21:18:34.04+00:00 I having the issue on Microsoft Surface Laptop 2...
The C:\Windows\SoftwareDistribution move to backup not working.
dism /Online /Cleanup-image /Restorehealth not working
sfc /scannow not working
-
Evil Arcane 0 Reputation points
2024-07-20T01:35:02.6833333+00:00 <rant on>
It's just bizarre that, after all these years, we're forced to google an arcane hexadecimal failure code for Windows updates.
I've been using both Windows and Linux since they were created. I have never had a stock Linux distro just fail to upgrade in that time, but I've run into this recurring problem with windows at least once on half a dozen systems.
I have two VMs, both Win 11, which I use for testing. They have no software installed. I simply update them to the latest updates, and if I do install any 3rd party software I revert the snapshot later. One of them updated fine today, and one of them is now throwing this stupid error. Resetting all the directories, checking the system, etc. has done nothing to improve the situation.
Why Microsoft hasn't made an updater that actually fixes the problems itself is beyond me. Please tell me why it can't at least tell us what it was doing when the failure occurred.
<rant off>
Well, I'm off to re-build the VM from scratch... because I've already wasted 2 hours trying to fix something Microsoft could have at least written to give a more descriptive error.
-
Loren Nashh 0 Reputation points
2024-07-20T09:34:47.3966667+00:00 Good luck And Thank you
-
Leo Salas 1 Reputation point
2024-10-25T18:47:36.17+00:00 This solution worked, but it's frustrating that one has to do then when the internal troubleshooter of the OS should have caught this and fix it automatically, not to mention the audit trail questions and loss of good man hours hunting this down and applying a fix manually like this.