How to fix blue screen error during upgrade on Windows 10

When upgrading to a new version of Windows 10, you may see blue screen errors, which can happen for many reasons. It could be a result of a compatibility problem with an old program or security software. Or it could be because of corrupted files in the current installation or damaged installation media — to name a few.

Usually, when an error occurs, the setup will revert the changes to the previous installation without reason.

In the case that you are dealing with errors during the installation of Windows 10, uninstalling non-essential apps, clearing out corrupt downloads, disconnecting non-essential peripherals, or even performing a clean install of the OS may resolve the issue.

Uninstall incompatible app

To uninstall an app that may be conflicting with the installation of windows 10, use these steps:

  1. Open Settings.
  2. Click on Apps.
  3. Click on Apps & features.
  4. Select the app that may be causing issues and click the Uninstall button.

    1. Click the Uninstall button again.

      Quick note: If you're removing a legacy desktop application, you may need to continue with the on-screen directions.

  5. Once you complete the steps, you may need to repeat the steps to uninstall additional apps, and then you can try the upgrade one more time. After the update, you can reinstall the apps again.

    Redownload installation files

    Sometimes, if you're using Windows Update to upgrade the system, you may see a Blue Screen of Death when one or multiple installation files have been damaged during the download process. In this case, you can use the Settings app to clear the previous files allowing Windows Update to redownload the files.

    To allow Windows Update to redownload the upgrade files, use these steps:

    1. Open Settings.
    2. Click on System.
    3. Click on Storage.
    4. Under the local disk section, click the Temporary files item.

    5. Clear the preselected options.
    6. Check the Temporary Windows installation files option.

    7. Click the Remove files button.

After you complete the steps, open the Windows Update settings and try to upgrade one more time.

If you continue with the same problem, you should consider using the Update Assistant utility to perform an in-place upgrade. Or if the utility didn't work, you can also try using the Media Creation Tool to create an installation media to install the new version.

Analyze upgrade problem

Alternatively, you can also use the SetupDiag tool to troubleshoot blue screen errors. SetupDiag is a tool that Microsoft provides as an optional download to diagnose and determine why an update or upgrade failed to apply, which is valuable information that can help you resolve the bug check problem.

To use SetupDiag after the upgrade of Windows 10 failed with a blue screen, use these steps:

  1. Open SetupDiag download page.
  2. Click the Download SetupDiag button.

  3. Select a destination folder to save the file.

  4. Click the Save button.

  5. Open File Explorer.

  6. Navigate to the folder where you downloaded the file.

  7. Right-click the "SetupDiag.exe" and select the Run as administrator option.

  8. Right-click the SetupDiagResults.log file and select the Open option.

    Once you complete the steps, the default text editor will open the log file with the diagnostic results based on the known rules specified by Microsoft.

    If an error was detected, the logs will detail the information to determine why the device blue screened during the update, and if it's a known issue, you'll also get the steps to resolve it.

    Sometimes you won't get any recommendations. If this happens, follow the link (if applicable) available in the log file, or use the error code or any meaningful information to research the problem online. (Use this guide for more detailed instructions.)

     

    Should the above instructions did not resolve the issue, please don't hesitate to contact us so we can further assist you. You can always reach us out through our support channels below:

     

No Comments
Back to top