[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-11T21:34:46+00:00

    OK, can I assume running the SFC, after your finished the DISM, finished without errors?

    There should only be a couple of things that could cause corruption with a clean install.  The install media, which was mentioned in the other thread, or a drive/controller situation.  Having a new drive should rule out the drive possibility but the controller could still be a suspect.

    If you were using a USB drive, it might be deficient or the setup for it caused problems.  There have be certain models of flash drives that are not good for doing upgrades.

    If you system is acting up, you can check the Event Viewer or put this in a run box, perfmon /rel and see what info the graph it produces, shows.

    One thing you might do for testing, is to turn off the Fast Startup to eliminate the possibly a bad driver is being reloaded.

    Was this answer helpful?

    0 comments
  2. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

    Comments have been turned off. Learn more

  3. Anonymous
    2019-11-11T19:47:18+00:00

    Device Manager is not showing any problem with any device and I can access all of them. But you can check this other thread on what I have been seeing and happening after doing a fresh install twice.

    https://answers.microsoft.com/en-us/windows/forum/all/fresh-installation-in-another-ssd-worst-that-old/8d31801a-6ddf-4e54-afd4-33e2996dd2f0

    Thanks.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2019-11-11T19:15:30+00:00

    After you do a clean install, many things will happen which take processing power.  Keep Task Manager open and watch the performance tab..

    No hurry of the file, you may learn what you need from the clean install.  Perhaps you might see in the Device Manager, some devices that you can't get to work

    Was this answer helpful?

    0 comments
  5. Anonymous
    2019-11-11T18:44:23+00:00

    I will check for that log. FYI I disconnected my OS drive and installed a new one and installed Win10 1903 as fresh copy and I am seeing weird unstable issues. (e.g Firefox takes 2 minutes to open while the whole system freezes while I see high disk activity led flashing) after it opens then the system is fine again.

    I will reconnect the previous drive with 1803 and look for that log.

    Thanks.

    Was this answer helpful?

    0 comments