[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 No comments

107 answers

Sort by: Oldest
  1. 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 No comments
  2. 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 No comments
  3. Anonymous
    2019-09-25T22:28:39+00:00

    C:\WINDOWS\system32>reagentc /enable

    REAGENTC.EXE: Unable to update Boot Configuration Data.

    C:\WINDOWS\system32>

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2019-09-26T18:55:03+00:00

    Well, trying to reconfigure the process can be done but it isn't easy.  I have been looking at your log and it tries to get the normal recovery configuration from the recovery folder and cannot.  It then goes to the Windows folder to get one and cannot.  It even tries to use a PBR image to get what it needs but that also seems to fail.

    Since you still have mentions of Skydrive on your system, I will assume you have been using that install for quite a while.  Maybe first, if you have a copy of your current build install media you could do an in-place upgrade which only refreshes your install and does not wipe out other things unless you tell it to.  Skydrive may be responsible for the DefaultAPPPOOL situation.

    Barring an in-place upgrade it may be time to reinstall.  Since the new build should be out in the not too distant future, you could use the time to get ready.

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2019-09-26T23:37:33+00:00

    Hi Saltgrass,

    I don't know if I understood your last post. Let me tell you about this system. It was a Win7 installed in a HDD. I installed a 128Gb SSD and cloned the OS to this new drive and used the HDD for data/program files/games. I was running out of space on this SDD so I installed a new 256Gb SSD and cloned the OS to this one and use the 128Gb for data/program files. I wonder if with all those transfer during all this years any info was lost. I was able to upgrade after some attends from previous ver to 1803, but can't to 1903. I have another 500Gb SSD. Thinking to do a clean install on this one but running out of SATA power connections.

    I didn't catch you what you meant by "Maybe first, if you have a copy of your current build install media you could do an in-place upgrade which only refreshes your install and does not wipe out other things unless you tell it to." that would be the Win7 disk, right? as I "free" upgraded to Win10 from the desktop when the notification to upgrade popped-up.

    Please advise.

    Thanks.

    Was this answer helpful?

    0 comments No comments