Problem with updating to 23H2

Anonymous
2025-04-12T00:03:58+00:00

Hello! I have a problem that I'm trying to fix for a year and its regarding Windows 11, version 23H2 update. When I download and install it from the WIndows Update everything is fine but when it starts insalling this is where the problem begins. It goes to black screen and the text saying "Update is underway. Don't turn your pc off. Your pc may restart a few times". This is a normal screen appearing everytime you download, but when it gets to the first restart it changes to another windows with different looking text and it stays for a few seconds then it says "Undoing the changes made to your pc". Then when I go into the Window Update I see an "Install error - 0x80248007" . This has appeared everytime I try to update it. I have tried everything that I could find on the internet, chatgpt, the robot chat responder at microsoft, but nothing works and I need somebody to help me with this problem.

Windows for home | Windows 11 | Windows update

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments
Answer accepted by question author
Anonymous
2025-04-14T18:54:45+00:00

No need for that i finally did it. I serached on internet for this error message and came upon another forum that talked about the error and all i had to do was type this command in command pront as Admin:

rundll32.exe pnpclean.dll,RunDLL_PnpClean /DRIVERS /MAXCLEAN

Then I had to turn off my wifi and bluetooth before rerunning the setup. I didn't thought it would work but as soon as my laptop restarted the update was stuck on 0% but it actually started at 12% and I was in shock and it did install and now my laptop is up to date. Thank you for all the work that you put to help me! I'm really greatfull and here is the link to the the forum page that I got the solution from, its the first comment under the post: https://answers.microsoft.com/en-us/windows/forum/all/the-installation-failed-in-the-safeos-phase-with/7f910879-39b1-4459-b3e0-abe84208e4d6

Was this answer helpful?

0 comments No comments

127 additional answers

Sort by: Most helpful
  1. Anonymous
    2025-04-12T09:16:41+00:00

    I just did the WDV and i didn't get a bsod after following the instruction in link that you gave me.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2025-04-12T09:03:22+00:00

    I created a restore point. Should I proceed with the other steps or should I first try to locate the Tuneup.log File?

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2025-04-12T08:50:19+00:00

    I did the Tuneup and it said that a file Tuneup.log was created on my desktop but it isn't on there.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2025-04-12T08:45:05+00:00

    Looks good.

    Please run Tuneup plus > create a new restore point

    Post new log files.

    Start WDV.

    The first run are the 3 customized tests in the TF tutorial.

    These are the next runs:

    Group 2

    [ ] 0x00000002 Force IRQL checking. 
    
    [ ] 0x00000008 Pool tracking. 
    
    [ ] 0x00000200 Force pending I/O requests. 
    
    [ ] 0x00000010 I/O verification. 
    
    [ ] 0x00002000 Invariant MDL checking for stack. 
    
    [ ] 0x00004000 Invariant MDL checking for driver. 
    
    [ ] 0x00000800 Miscellaneous checks.
    

    Group 3

    [ ] 0x00008000 Power framework delay fuzzing. 
    
    [ ] 0x00010000 Port/miniport interface checking. 
    
    [ ] 0x00040000 Systematic low resources simulation.  
    
    [ ] 0x00200000 NDIS/WIFI verification. 
    
    [ ] 0x00800000 Kernel synchronization delay fuzzing. 
    
    [ ] 0x01000000 VM switch verification. 
    
    [ ] 0x00000100 Security checks.
    

    Group 4

    [ ] 0x02000000 Code integrity checks.
    
    [ ] 0x00000020 Deadlock detection. 
    
    [ ] 0x00000080 DMA checking.  
    
    [ ] 0x00080000 DDI compliance checking (additional).
    
    [ ] 0x00020000 DDI compliance checking.
    

    For each group if there is no immediate BSOD then open administrative command prompt and copy and paste:

    verifier /querysettings

    Post a share link.

    For any BSOD post a new V2 share link into the newest post.

    Was this answer helpful?

    0 comments No comments