Windows 10 Won't Boot After 22H2 Feature Update

Page 1 of 2 12 LastLast

  1. Posts : 75
    Windows 10 21H2, Windows 10 20H2
       #1

    Windows 10 Won't Boot After 22H2 Feature Update


    Hello, I have a setup where I have two different versions of Windows 10 in a dual boot configuration. One is on 20H2 and the primary one is on 21H2. The issue is that when I updated my 21H2 to 22H2, my computer will no longer boot into Windows.

    Before this update, my computer will boot into a dual boot menu where it would let me select which OS I want to run. Now, my computer just goes to a black screen after BIOS loads. I can't boot into any of my windows partitions.

    I think any new feature update messes with the boot menu. Question is, how can I get my windows back? Is there some media disk for WIndows I can use to repair / restore my boot menu?
      My Computer


  2. Posts : 7,917
    Windows 11 Pro 64 bit
       #2

    You could install Macrium Reflect on another PC and create a Reflect recovery drive from then. Then boot to the recovery drive on the PC to fix and select Fix Windows Boot Problems. See Use Macrium Reflect Rescue Media to Fix Windows Boot Issues

    Didn't you have a backup to recover to before the upgrade?
      My Computers


  3. Posts : 5,347
    Windows 11 Pro 64-bit
       #3

    In this video, i will guide you on how to repair Master Boot Record (MBR) in Windows 10 or Windows 11.

      My Computer


  4. Posts : 6,396
    Windows 11 Pro - Windows 7 HP - Lubuntu
       #4

    Is the computer the i9-10850K?
    Did you install as Legacy - MBR or UEFI - GPT?

    You can boot from a Win 10 USB installation drive and fix it, but I need to know if it is a Legacy - MBR or UEFI - GPT.
      My Computers


  5. Posts : 5,347
    Windows 11 Pro 64-bit
       #5

    GPT drives tend to include a “protective MBR.” This type of MBR says that the GPT drive has a single partition that extends across the entire drive. This protective MBR ensures the old tools won’t mistake the GPT drive for an unpartitioned drive and overwrite its GPT data with a new MBR. In other words, the protective MBR protects the GPT data from being overwritten.
      My Computer


  6. Posts : 75
    Windows 10 21H2, Windows 10 20H2
    Thread Starter
       #6

    Megahertz said:
    Is the computer the i9-10850K?
    Did you install as Legacy - MBR or UEFI - GPT?

    You can boot from a Win 10 USB installation drive and fix it, but I need to know if it is a Legacy - MBR or UEFI - GPT.
    My computer is UEFI and disk is GPT. I don't have a Windows 10 22H2 Disk though. It would seem that the computer got confused on what to boot into as it wasn't done updating my 21H2 partition. It restarted to continue updating 21H2 but during the restart got "confused" and booted into a black screen.
      My Computer


  7. Posts : 75
    Windows 10 21H2, Windows 10 20H2
    Thread Starter
       #7

    FreeBooter said:
    GPT drives tend to include a “protective MBR.” This type of MBR says that the GPT drive has a single partition that extends across the entire drive. This protective MBR ensures the old tools won’t mistake the GPT drive for an unpartitioned drive and overwrite its GPT data with a new MBR. In other words, the protective MBR protects the GPT data from being overwritten.
    Are you saying that even though my disk is GPT, it still has MBR on it? Is MBR different from Master Boot Record?
      My Computer


  8. Posts : 5,347
    Windows 11 Pro 64-bit
       #8

    edo101 said:
    Are you saying that even though my disk is GPT, it still has MBR on it? Is MBR different from Master Boot Record?
    Master Boot Record (MBR), still present in GPT disk, it was not we would not have command to repair it.
      My Computer


  9. Posts : 6,396
    Windows 11 Pro - Windows 7 HP - Lubuntu
       #9

    You can rebuild the Windows Boot manager on the EFI partition.
    If you have more than one drive attached to the MB, open the case and detach the SATA or power cable of all them, living on only the windows drive.
    I suggest you build the USB Win 11 22h2 installation drive using MCT

    Boot from a Win 10 USB installation drive and at the Windows Setup screen, press Shift+F10 simultaneously to open a command line prompt and type:
    diskpart
    list disk (it will list all drives. Identify the drive number that has windows.)
    select disk n (replace n by the drive number obtained with list disk)
    list par (identify which partition number is the EFI System partition)
    select part k (replace k by the partition number of the EFI System partition)
    format fs=Fat32 quick
    assign letter=w
    List vol (identify the two windows partition letters)
    exit (to exit diskpart)
    bcdboot X:\Windows /s W: /f UEFI (replace X with the primary windows letter found above with list part)
    bcdboot Y:\Windows /d /addlast (replace Y with the secondary windows letter found above with list part)
    diskpart
    select vol W
    remove letter=W
    exit (to exit diskpart)

    Restart
      My Computers


  10. Posts : 75
    Windows 10 21H2, Windows 10 20H2
    Thread Starter
       #10

    FreeBooter said:
    Master Boot Record (MBR), still present in GPT disk, it was not we would not have command to repair it.
    Steve C said:
    You could install Macrium Reflect on another PC and create a Reflect recovery drive from then. Then boot to the recovery drive on the PC to fix and select Fix Windows Boot Problems. See Use Macrium Reflect Rescue Media to Fix Windows Boot Issues

    Didn't you have a backup to recover to before the upgrade?
    Megahertz said:
    You can rebuild the Windows Boot manager on the EFI partition.
    If you have more than one drive attached to the MB, open the case and detach the SATA or power cable of all them, living on only the windows drive.
    I suggest you build the USB Win 11 22h2 installation drive using MCT

    Boot from a Win 10 USB installation drive and at the Windows Setup screen, press Shift+F10 simultaneously to open a command line prompt and type:
    diskpart
    list disk (it will list all drives. Identify the drive number that has windows.)
    select disk n (replace n by the drive number obtained with list disk)
    list par (identify which partition number is the EFI System partition)
    select part k (replace k by the partition number of the EFI System partition)
    format fs=Fat32 quick
    assign letter=w
    List vol (identify the two windows partition letters)
    exit (to exit diskpart)
    bcdboot X:\Windows /s W: /f UEFI (replace X with the primary windows letter found above with list part)
    bcdboot Y:\Windows /d /addlast (replace Y with the secondary windows letter found above with list part)
    diskpart
    select vol W
    remove letter=W
    exit (to exit diskpart)

    Restart
    Hi, so I was somehow able to tap back into Windows and finish my update. It appears the main mix up with dual boot systems is that if one of the partitions is being updated, you can lose access to boot when the computer is restarting to complete its feature update.

    But there is slight hitch I notice every now and then. Now that my system is back to working, every now and then, my computer boots into a black screen. The only way to get back to my boot menu is being doing a forced shutdown via the power button or switching off my PSU. And then the computer properly boots into the boot menu.

    I haven't been able to identify what could cause this occasional hiccup. What can I do to eliminate it? 90% of the time, the computer restarts properly to my dual boot menu. But 10% of the time, during a restart, it boots into a black screen and my monitors can't pick up any signal.
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 16:57.
Find Us




Windows 10 Forums