DEV Community

Vincent Tommi
Vincent Tommi

Posted on

How to Fix Windows 11 Installation Problems on Lenovo ThinkPad E490: A Complete Clean Installation Guide

#rufus #learning #beginners #lenovo

How to Fix Windows 11 Installation Problems on Lenovo ThinkPad E490: A Complete Clean Installation Guide

Introduction

Have you ever tried installing Windows 11 on your laptop, only to discover that after installation and restarting, the computer still loads the old Windows installation?

I recently encountered this issue while troubleshooting a Windows 11 installation on a Lenovo ThinkPad E490.

The installation process appeared to work normally. Windows Setup loaded, installation files were processed, and multiple Windows 11 boot options appeared. However, selecting either option continued loading the old Windows installation.

Initially, I suspected that Windows was retaining cached installation files or failing to recognize the new installation properly.

After investigating the boot configuration and internal storage, I discovered that the computer had multiple Windows boot entries and two internal drives.

In this tutorial, I'll walk through the troubleshooting process and explain how to perform a clean Windows 11 installation using a bootable USB.

1. Understanding the Problem

The issue presented itself in the following way:

  • Created a bootable Windows 11 USB using Rufus.
  • Connected the USB to the Lenovo ThinkPad E490.
  • Started the computer and selected the USB from the F12 boot menu.
  • Windows installation files loaded.
  • Two Windows 11 boot options appeared:
    • Windows 11 on Volume 2.
    • Windows 11 on Volume 5.
  • Selecting either option continued loading the old Windows installation.

This suggested that the computer might have multiple boot entries pointing to existing Windows installations.

However, duplicate boot entries do not necessarily mean that multiple complete Windows installations exist.

The next step was to investigate the Windows Boot Manager configuration.

2. Inspecting Windows Boot Configuration Using BCDEdit

Windows provides a built-in command-line utility called BCDEdit.

It allows administrators to inspect and manage the Windows Boot Configuration Data (BCD).

To inspect the current boot configuration:

  1. Boot into Windows.
  2. Open Command Prompt as Administrator.
  3. Execute: 
bcdedit /enum
Enter fullscreen mode Exit fullscreen mode

This displays the Windows Boot Manager and registered Windows Boot Loader entries.

Important properties to examine include:

Property Description
identifier Identifies a boot entry
device Identifies the partition containing boot files
osdevice Identifies the Windows operating system partition
path Specifies the Windows boot loader
description Displays the boot menu name
default Identifies the default boot entry

For example:

Windows Boot Loader

identifier      {default}
device          partition=\Device\HarddiskVolume2
path            \Windows\system32\winload.efi
description     Windows 11
osdevice        partition=\Device\HarddiskVolume2
systemroot      \Windows
Enter fullscreen mode Exit fullscreen mode

The investigation revealed that the default Windows boot entry referenced HarddiskVolume2, while the currently running Windows installation was identified as C:.

This was an important clue, but it was not sufficient to establish whether these were separate installations.

3. Mapping Windows Volumes Using FLTMC

The next step was identifying the volumes referenced by Windows Boot Manager.

Windows provides another useful command:

fltmc volumes
Enter fullscreen mode Exit fullscreen mode

This displays mounted volumes and their device names.

Example output:

Volume Name

\Device\HarddiskVolume5
\Device\HarddiskVolume6
\Device\HarddiskVolume3
\Device\HarddiskVolume2
Enter fullscreen mode Exit fullscreen mode

In the investigation, the following device names were particularly important:

  • HarddiskVolume2: Referenced by the default Windows boot entry.
  • HarddiskVolume3: Referenced by Windows Boot Manager and identified as the EFI partition.
  • HarddiskVolume5 and HarddiskVolume6: Additional NTFS volumes.

One important lesson: HarddiskVolume numbers are not the same thing as Disk 0, Disk 1, or Windows drive letters.

You should map them to actual partitions before making changes.

4. Inspecting Physical Drives Using DiskPart

The next investigation involved DiskPart, a Windows command-line utility for managing disks and partitions.

Open Command Prompt as Administrator and execute:

diskpart
Enter fullscreen mode Exit fullscreen mode

List the physical disks:

list disk
Enter fullscreen mode Exit fullscreen mode

The Lenovo E490 showed two internal drives:

Disk ###  Status    Size
Disk 0    Online    119 GB
Disk 1    Online    298 GB
Enter fullscreen mode Exit fullscreen mode

Both disks had an asterisk under the GPT column.

This indicated that both drives were using the GUID Partition Table (GPT) partitioning scheme.

Next, inspect the available volumes:

list volume
Enter fullscreen mode Exit fullscreen mode

The results showed:

Volume ###  Ltr  Fs      Size
Volume 0    C    NTFS    117 GB
Volume 1         FAT32   100 MB
Volume 2         NTFS    1285 MB
Volume 3         NTFS    297 GB
Enter fullscreen mode Exit fullscreen mode

Based on the sizes, the likely configuration was:

Volume Size File system Possible purpose
Volume 0 (C:) 117 GB NTFS Existing Windows partition
Volume 1 100 MB FAT32 EFI System Partition
Volume 2 1,285 MB NTFS Recovery partition
Volume 3 297 GB NTFS Secondary storage partition

Important: The volume listing alone does not conclusively establish which physical disk contains each partition. Use detail disk to verify the mapping.

For example:

select disk 0
detail disk
list partition
Enter fullscreen mode Exit fullscreen mode

Then inspect the second drive:

select disk 1
detail disk
list partition
Enter fullscreen mode Exit fullscreen mode

This helps identify which partitions belong to each physical disk.

To leave DiskPart:

exit
Enter fullscreen mode Exit fullscreen mode

5. Understanding UEFI and GPT

Modern Windows 11 installations generally use UEFI firmware and GPT partitioning.

Understanding these technologies is important when creating a bootable installation USB.

UEFI

Unified Extensible Firmware Interface (UEFI) is the modern replacement for traditional BIOS booting.

It supports features such as Secure Boot and uses an EFI System Partition to store boot files.

GPT

GUID Partition Table (GPT) is a modern disk partitioning format designed to work with UEFI systems.

For a standard Windows 11 installation, the recommended Rufus configuration is:

Rufus setting Recommended option
Boot selection Windows 11 ISO
Partition scheme GPT
Target system UEFI (non-CSM)
File system Use Rufus default

Always verify that your laptop is configured to boot using UEFI.

6. Creating a Bootable Windows 11 USB Using Rufus

To prepare the installation media:

  1. Download the official Windows 11 ISO from Microsoft.
  2. Download and launch Rufus.
  3. Insert a USB flash drive with sufficient capacity (8 GB minimum).
  4. Select your USB device.
  5. Select the downloaded Windows 11 ISO.
  6. Choose GPT as the partition scheme.
  7. Select UEFI (non-CSM) as the target system.
  8. Start the process.

Rufus will prepare the bootable USB.

Official resources:

Remember that creating bootable installation media will erase the USB flash drive.

7. Booting the Lenovo ThinkPad E490 From USB

After preparing the USB:

  1. Shut down the laptop.
  2. Connect the bootable USB.
  3. Power on the Lenovo ThinkPad E490.
  4. Press F12 repeatedly when the Lenovo logo appears.
  5. Open the boot device selection menu.
  6. Select the USB device under the UEFI boot options.

Windows Setup should now load directly from the USB.

If the computer continues loading the existing Windows installation, verify that you selected the USB device rather than Windows Boot Manager.

8. Performing a Clean Windows 11 Installation

Once Windows Setup loads:

  1. Select your preferred language.
  2. Choose your keyboard layout.
  3. Click Install Windows 11.
  4. Accept the licence terms.
  5. Select the custom installation option when presented.
  6. Continue to the disk and partition selection screen.

You should see the available drives and partitions.

Identifying the correct installation drive

In this troubleshooting case, the laptop had:

  • Disk 0: 119 GB.
  • Disk 1: 298 GB.

The plan was to install Windows 11 on the 119 GB SSD.

Before deleting anything, verify the disk sizes and partition layout carefully.

Removing existing Windows partitions

If you want a completely fresh installation and are certain that all data on the target drive can be erased:

  1. Identify the correct target disk.
  2. Select each partition belonging to that disk.
  3. Click Delete.
  4. Continue until the target disk shows Unallocated Space.
  5. Select the unallocated space.
  6. Click Next.

Windows Setup will automatically create the required partitions, including:

  • EFI System Partition.
  • Microsoft Reserved Partition (MSR).
  • Windows partition.
  • Recovery partition.

Warning: Deleting partitions permanently destroys the data stored on them. Make sure you have identified the correct physical disk.

If your computer has multiple internal drives, disconnecting the secondary drive during installation, where practical and safe, can help prevent Windows Setup from placing boot files on the wrong drive.

9. Handling the First Restart

One common mistake during Windows installation is repeatedly booting from the USB after Windows has started copying installation files.

Windows Setup normally restarts the computer several times.

After the first restart:

  1. Allow the laptop to restart.
  2. Remove the USB when the computer begins restarting.
  3. Allow the computer to boot from Windows Boot Manager on the internal SSD.
  4. Continue the Windows initial setup.
  5. Configure your country, keyboard, network and user account.

Do not start the installation process again unless necessary.

10. Verifying the New Windows Installation

After completing the installation, verify that Windows is running from the intended drive.

Open Command Prompt as Administrator and execute:

echo %windir%
Enter fullscreen mode Exit fullscreen mode

Then:

bcdedit /enum
Enter fullscreen mode Exit fullscreen mode

Check that the Windows Boot Manager and Windows Boot Loader reference the intended installation.

You can also inspect the disk layout:

diskpart
list disk
list volume
exit
Enter fullscreen mode Exit fullscreen mode

The objective is to have one working Windows installation with a correctly configured UEFI boot process.

11. Common Mistakes to Avoid

Here are some lessons from this troubleshooting experience:

1. Confusing boot entries with physical Windows installations

Two Windows boot menu entries do not necessarily mean that two complete Windows installations exist.

2. Assuming Windows has cached the old installation

The problem may be caused by incorrect boot configuration, selecting the wrong boot device, or an incomplete installation.

3. Formatting the wrong drive

Always verify physical disk sizes and partition layouts before deleting anything.

4. Ignoring the EFI System Partition

Windows needs an EFI System Partition to boot correctly in UEFI mode.

5. Restarting into the USB installation repeatedly

After the first installation restart, allow the laptop to continue from its internal drive.

6. Deleting boot entries without investigating them

Use BCDEdit to understand the configuration before modifying it.

12. Useful Windows Troubleshooting Commands

Here is a quick reference to the commands used throughout this tutorial.

Command Purpose
bcdedit /enum Display boot configuration
bcdedit /enum {current} Display current boot entry
bcdedit /enum {default} Display default boot entry
fltmc volumes List mounted volume device names
diskpart Open disk management utility
list disk Display physical disks
list volume Display available volumes
select disk 0 Select Disk 0
detail disk Display selected disk details
list partition Display partitions on selected disk
echo %windir% Display current Windows directory

Conclusion

Troubleshooting Windows installation problems requires more than simply reinstalling the operating system.

In this Lenovo ThinkPad E490 investigation, the important discoveries were:

  • Multiple Windows boot entries were registered.
  • The default and current Windows boot entries referenced different volume identifiers.
  • The computer had two internal GPT drives.
  • The Windows installation and EFI boot configuration needed further verification before making destructive changes.

The safest approach is to inspect the boot configuration, identify the physical disks, verify the installation target, and then perform a clean Windows installation.

Whether you are troubleshooting a Lenovo ThinkPad, Dell Latitude, HP EliteBook, or another Windows laptop, these diagnostic techniques can help you understand what is happening before modifying your partitions.

Remember: Always identify your target disk before deleting partitions. A few minutes of diagnosis can save hours of recovery work.

Top comments (0)