[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-09-25T19:15:20+00:00

    The thinks I mention below, show not direct cause for the upgrade problems but I will just bring them up in case someone notices something.  I don't really see anything else that seems relevant.

    You could try the command below and see if it can be re-enabled. 

    reagentc /enable

    Other things, ASUS utilities that came with the motherboard can be problematic.

    You have an XPS viewer loading and NetFX3, what ever that is..

    These same four entries repeat over and over again.  I do not know what the plugin being mentioned is.

    Warning    [0x0808fe] MIG    Plugin {d2caca93-9eef-4c24-9790-61cdefd255d4}: RETURN_IF_FAILED(Offline_InstallAssembly(absoluteAssemblyDir, absoluteManifestFilename, pIMalloc, pStore, pIdentity, pAppIdAuthority)) failed with 0x80070bc2

    Info       [0x0808fe] MIG    Plugin {d2caca93-9eef-4c24-9790-61cdefd255d4}: Install assembly succeeded with 0x52b7d470 (ERROR_SUCCESS_REBOOT_REQUIRED). This is informational only (wouldhave been fatal if not performed offline)

    Info       [0x0808fe] MIG    Plugin {d2caca93-9eef-4c24-9790-61cdefd255d4}: Install assembly C:$WINDOWS.~BT\Store\MachineSpecific\File\srcworkingalias\agentmgr\CCSIAgent\005A53BA\ requires a reboot

    Info       [0x0808fe] MIG    Plugin {d2caca93-9eef-4c24-9790-61cdefd255d4}: Found assembly to install: C:$WINDOWS.~BT\Store\MachineSpecific\File\srcworkingalias\agentmgr\CCSIAgent\005A53BA\SxsAsm17

    Info       [0x0808fe] MIG    Plugin {d2caca93-9eef-4c24-9790-61cdefd255d4}: Found assembly manifest to install: C:$WINDOWS.~BT\Store\MachineSpecific\File\srcworkingalias\agentmgr\CCSIAgent\005A53BA\SxsAsm17\amd64_microsoft.vc90.mfcloc_1fc8b3b9a1e18e3b_9.0.21022.8_none_6dee77c650852292.manifest

    Was this answer helpful?

    0 comments
  2. Anonymous
    2019-09-25T16:52:54+00:00

    C:\WINDOWS\system32>reagentc /info

    Windows Recovery Environment (Windows RE) and system reset configuration

    Information:

        Windows RE status:         Disabled

        Windows RE location:

        Boot Configuration Data (BCD) identifier: a1c96e4a-80d7-11e8-bdc8-eaa28adfb254

        Recovery image location:

        Recovery image index:      0

        Custom image location:

        Custom image index:        0

    REAGENTC.EXE: Operation Successful.

    Regarding BattlEye I found it in several locations.

    http://www.mediafire.com/file/4nuti3vlo2302jn/BattlEyePict.JPG/file

    Was this answer helpful?

    0 comments
  3. Anonymous
    2019-09-25T15:58:00+00:00

    A question and a comment.

    If you run reagentc /info in an administrative command prompt, could you show us the listing?  It looks like the install can extract a replacement Winre.wim file and continue but your recovery options may not be available in your normal install.

    There have been comments related to antiCheat software, namely BattlEye.  If you were to have something like that, it might make a difference..  I do not know the current status of this situation.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2019-09-25T12:53:34+00:00

    Sumit,

    Interesting, that path\file doesn't exist in my system.

    http://www.mediafire.com/file/uty0ugt6k7pvel3/Capture.JPG/file

    Was this answer helpful?

    0 comments
  5. Sumit 44,316 Reputation points Volunteer Moderator
    2019-09-25T02:02:41+00:00

    The entire problem lies here, I think.

    2019-09-22 17:14:11, FatalError [0x090001] PANTHR Exception (code 0xC0000005: ACCESS_VIOLATION) occurred at 0x00007FFABE0789D3 in C:$WINDOWS.~BT\Sources\migcore.dll (+00000000001D89D3).  Minidump attached (101391 bytes) to diagerr.xml and C:\Windows\Panther\mnd25EF.diagerr.mdmp.

    2019-09-22 17:14:11, Info                  SP     SETUPPLATFORMCOMM: Progress message received: Phase: First Boot, Operation: Migrate data, Percentage: 60%

    2019-09-22 17:14:11, Warning    [0x08094f] MIG    MigHost: CMigPluginSurrogate::WaitForHostTermination**: Parent process unexpectedly exited. Terminating host.**

    Please share C:\Windows\Panther\mnd25EF.diagerr.mdmp for further help

    Was this answer helpful?

    0 comments