[Case Closed; No Solution] Windows 10 keeps failing update to 1903

Anonymous
2019-09-20T12:49:46+00:00

Hello,

I'm currently running 1803 and every single time I am trying to upgrade to 1903 I got a BSOD with a PFN List Corrupt.

  1. I have tried several method: let Windows Update download and install; Creating a Win10 installation Media in USB
  2. I have more than 43GB of free space.
  3. I've run File System checker, CheckDisk, and any other tool / utility

The other day I change MSConfig and select selective startup to disable other services/programs to load and after rebooting my PC couldn't even find Windows booting to a Boot Manager where only Windows 7 was an option (??????) (My original OS was Win7 but I upgrade to Win10 through Microsoft Upgrade Program) but no trail of Win7 neither. I used a third-party boot utility that fix the boot and I'm again in Win10 that keeps reminding me that I have an old version, that I would not get more updates and I have to upgrade... but the damn update keeps failing after download, reboot, install and after the 2 or 3 reboot in the installation process I got the ERROR.

I need like 2 restarts to see see the message saying is putting all back to previous state and then boot again and still ion ver 1803.

Please advice. I have tried all those canned solutions people post on forums with no difference.

Thanks.

Windows for home | Windows 10 | Install and upgrade

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

107 answers

Sort by: Newest
Most helpful Newest Oldest
  1. Anonymous
    2019-11-02T17:22:12+00:00

    The Winre.wim is on parition 3 or the 500 MB Recovery partition.

    The tools are working now... ;)  I really hope that lets your upgrade complete.  If not, maybe we can find another reason..

    Was this answer helpful?

    0 comments
  2. Anonymous
    2019-11-02T17:14:20+00:00

    Saltgrass,

    1. WinRE

    2.

    1. I can't find any Winre.wim on my system.... ???

    Thanks

    Was this answer helpful?

    0 comments
  3. Anonymous
    2019-11-02T16:28:50+00:00

    It shows the system does have access to the BCD store but your Recovery Tools are not set up.  Getting that done may help..

    You can try using Reagentc /disable and then Reagentc /enable to see if it comes back and shows similar (not exact) to the one below..

    To fix it, I will need a Disk Management picture with expanded so we can read the partition descriptions and use the snipping tool to take a picture.  We need to find where the Winre.wim file is which is normally in a Recovery\WindowsRE folder..

    C:\WINDOWS\system32>reagentc /info

    Windows Recovery Environment (Windows RE) and system reset configuration

    Information:

        Windows RE status:         Enabled

        Windows RE location:       \?\GLOBALROOT\device\harddisk1\partition1\Recovery\WindowsRE

        Boot Configuration Data (BCD) identifier: f92186b6-7c00-11e9-827c-409f38b82098

        Recovery image location:

        Recovery image index:      0

        Custom image location:

        Custom image index:        0

    REAGENTC.EXE: Operation Successful.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2019-11-02T15:21:23+00:00

    Hello Saltgrass,

    1. Window RE

    1. BCDEdit (I don't know what I am looking for. Idk how this command works)

    1. BEService in several places.

    1. ASUS. I have ASUS router, ASUS Monitor, ASUS MoBo, and ASUS Radeon card. The only ASUS entry I found in programs is this but I think is from previous installation as it doesn't have an entry of where is currently installed

    Thanks

    Was this answer helpful?

    0 comments
  5. Anonymous
    2019-11-02T14:24:10+00:00

    I am still seeing problems with your Recovery Tools image file.  Did you ever get the reagentc /info command to show it was enabled?  Can you run a bcdedit command and see if it gives you a listing?

    These are the error messages I am concerned about.  The log shows it recreated the Reagent.xml file but it may not stick during reboots.

    Error                        [SetupHost.Exe] BcdOpenObject(WinRE) failed: 0xc0000034

    Info                         [SetupHost.Exe] winreGetWinReGuid returning 0X2

    Info                         [SetupHost.Exe] ReAgentConfig::ReadBcdAndUpdateEnhancedConfigInfo WinRE disabled, WinRE Guid could not be determined  (0x2)

    The is one more error which was not there before.  The file may be an IIS migration utility..  I don't think this is stopping the upgrade, but again, I can't be sure.

    If Battleye could be involved, and I don't know it is,

    (BEService)- Service Path: C:\Program Files (x86)\Common Files\BattlEye\BEService.exe

    You are still running the ASUS utilities..  If you want to keep them, at least make sure they are up to date.

    Was this answer helpful?

    0 comments