[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-22T22:38:35+00:00

    I tried running the Setup in the USB from the Desktop. Installation searched for updates and then started to install. After 100% then it reboot and doing the updating configuration. Again got stuck for a long time at 27% (I see a lot of people get stuck in the same %) finally after 30% or 40% rebooted again. Went up to 60% but then I see went to 57%. It rebooted again to do a "Undoing Changes" without getting a BSOD with the PFN List Corrupt. After putting the system back and restarted I logged in and the Win 10 Setup window.

    We Couldn't install Windows 10

    0xC1900101 - 0x3000D

    The installation failed in the FIRST_BOOT phase with an error during MIGRATE_DATA operation.

    I am uploading a zip file again with the logs

    http://www.mediafire.com/file/5vxm5jkth2qx7t5/Win10Logs.rar/file

    Thank you.

    s://www.mediafire.com/file/5vxm5jkth2qx7t5/Win10Logs.rar/filehttps://www.mediafire.com/file/5vxm5jkth2qx7t5/Win10Logs.rar/file

    Was this answer helpful?

    0 comments
  2. Anonymous
    2019-09-22T17:58:58+00:00

    Haven't upgrade yet. Before I do. It is safe to delete the whole C:$WINDOWS.~BT folder? I think I going to try upgrade from USB (created with Media Tool). I tried to install booting from USB with no success. I am going to try fire the setup from the desktop. I gives me the option to keep files and apps. Let's see if I get somewhere using this path. What do you think?

    Was this answer helpful?

    0 comments
  3. Anonymous
    2019-09-22T15:43:55+00:00

    @Sumit, if you are going to recommend a reset or clean install, hopefully your observation regarding the problem is at least, accurate.  Since I have not seen the Setupact.log, I can not confirm aspnet_regiis is involved.

    Hopefully, the upgrade is already complete.

    Was this answer helpful?

    0 comments
  4. SD - IA 179.3K Reputation points Independent Advisor
    2019-09-22T15:21:14+00:00

    I think we might be approaching a dead end. Is it possible for you to do a clean install?

    Was this answer helpful?

    0 comments
  5. Anonymous
    2019-09-21T22:25:09+00:00

    I just set my system up and only checked the request filtering box in IIS.  It installed a bunch of files and folders in the Windows\System32\inetsrv folder.  I then unchecked the same box and it restarted and uninstalled all of those files.

    I did not try to set a configuration on the install so there may have been no requirement that might have stopped me from doing a normal uninstall.

    It is noteworthy that most of the IIS situations revolve around the isssetup.exe file which won't run normally.  If your next upgrade attempt fails, all I could think is a .Net situation.  But maybe when one problem is repaired, another one will show up..

    Was this answer helpful?

    0 comments