Windows 11 26H2 Setup fails to detect hardware on Dell Latitude 5300 2-in-1

Adeel Alam 0 Reputation points
2026-11-19T18:07:56.4033333+00:00

I'm experiencing an installation issue with Windows 11 26H2 on my Dell Latitude 5300 2-in-1.

I previously used Windows 11 26H2 successfully on this exact laptop for approximately one to two months after its release. However, when attempting a fresh installation using a recently downloaded 26H2 ISO, Windows Setup displays the "Install drivers to show hardware" screen and cannot proceed normally.

I tested the installation media using both Ventoy and a USB drive written directly from the ISO. Both methods produced the same result. I also tested the BIOS storage configurations (RAID and AHCI), but neither resolved the issue.

During inspection of the ISO, I discovered a potentially significant build-version mismatch:

Boot image (boot.wim): Build 26100.9457

Installation image (install.wim): Build 26300.9457

The boot environment and the actual Windows installation image therefore appear to come from different build versions.

Since Windows 11 26H2 previously worked on this same hardware, I suspect a possible issue with the installation ISO, mismatched Setup components, or a regression in Windows Setup rather than a fundamental hardware compatibility problem.

Could Microsoft investigate whether this ISO contains incorrectly matched installation components or whether there is a known issue affecting hardware and storage-device detection during Windows Setup?

Device: Dell Latitude 5300 2-in-1
Affected release: Windows 11 26H2
Boot image build: 26100.9457
Installation image build: 26300.9457

Windows for business | Windows Client for IT Pros | Devices and deployment | Set up, install, or upgrade
0 comments No comments

2 answers

Sort by: Most helpful
  1. Chance Maurice Niyonzima 825 Reputation points Independent Advisor
    2026-11-19T19:16:56.76+00:00

    Hello Adeel,

    Thank you for posting your question on the Microsoft Windows Forum!

    I’m sorry you’re going through this, especially since the laptop ran 26H2 fine before. The build numbers are interesting, but they may be normal for this media, and I couldn’t find a Microsoft-confirmed issue. Other users report that newer install media ships with fewer built-in drivers, which would explain why Setup can’t see your storage controller.

    Here’s the plan

    1. Load the Dell storage driver in Setup. On another PC, download the Intel Rapid Storage Technology (RST/VMD) driver for the Latitude 5300 2-in-1 from Dell Support, extract it to a second USB drive, then use Browse on the "Install drivers to show hardware" screen.
    2. Update the BIOS to the latest version from Dell, then retry.
    3. Rebuild the USB with the Media Creation Tool or Rufus instead of Ventoy and check the ISO's SHA-256 hash against Microsoft's page.
    4. If it still fails, install 25H2 with the Dell drivers first, then upgrade in place to 26H2. That skips the Setup driver problem entirely.

    If you can, please send a report through Feedback Hub (Windows + F) with the build numbers, so Microsoft can check the ISO.

    Could you tell us whether the drive is NVMe or SATA, and whether the Dell RST driver shows up when you browse to it in Setup?

    Microsoft References

    I hope this answer has brought you useful information. If so, please click on "Accept Answer" and consider upvoting it. Doing so helps other community members identify useful solutions to similar issues.

    Was this answer helpful?

    0 comments No comments

  2. AI answer

    2026-11-19T18:10:03.25+00:00

    The 26100.9457/26300.9457 difference is not sufficient to prove a defective ISO, so first replace it with a newly downloaded Microsoft ISO and then use WinPE disk detection and Setup logs to distinguish a storage-driver problem from malformed media or a Setup regression.

    Windows 11 26H2 uses build family 26300, and 26300.9457 is its GA baseline; build 26100 belongs to 24H2. However, Microsoft’s documentation does not confirm that a 26100.9457 boot.wim paired with a 26300.9457 installation image is the expected composition of 26H2 retail media.^1^ No matching installation/storage-detection issue is currently listed on the 26H2 release-health page.^2^

    1. Eliminate the ISO as the variable

    Since Ventoy, direct USB writing, RAID, and AHCI have already produced the same result, do not repeat those tests.

    1. Download another ISO directly from Microsoft’s Download Windows 11 page, preferably from a different working PC. Microsoft identifies that page as the supported source for automated media creation and ISO-based USB installation.^3^
    2. Do not reuse or modify the suspect ISO.
    3. Inspect the replacement media before booting. Account for all possible installation-image formats:
    dism /Get-WimInfo /WimFile:D:\sources\boot.wim
    dir D:\sources\install.*
    dism /Get-WimInfo /WimFile:D:\sources\install.wim
    

    If the media contains install.esd, substitute that filename. If it contains split install.swm, install2.swm, and so on, record those filenames instead. DISM’s image-information command lists the images and indexes contained in a WIM.^4^

    If a newly downloaded Microsoft ISO has the identical pairing and failure, preserve both ISO filenames and metadata for the report rather than assuming the pairing itself is the defect.

    2. Determine what Setup actually cannot detect

    At the driver prompt, press Shift+F10 and run:

    diskpart
    list disk
    list volume
    exit
    type X:\Windows\Panther\setuperr.log
    notepad X:\Windows\Panther\setupact.log
    

    list volume identifies the USB drive letter, which may not be D: in WinPE.

    • Internal SSD absent from list disk: follow the storage-driver branch below. Microsoft documents that when Setup cannot locate the target disk, the installation environment may lack the required disk/controller driver.^5^
    • Internal SSD present: this is not simply an invisible-storage-controller case. Preserve X:\Windows\Panther\setupact.log and setuperr.log; X:\Windows\Panther is the documented log location before Setup can access the destination drive.^6^
    • USB/media volumes also missing or unreadable: prioritize replacement media and inspect setupact.log for source-file or device-enumeration failures rather than loading an SSD driver.

    Copy the logs to the USB using its actual drive letter:

    mkdir E:\SetupLogs
    copy X:\Windows\Panther\setupact.log E:\SetupLogs\
    copy X:\Windows\Panther\setuperr.log E:\SetupLogs\
    

    3. If the SSD is absent, load the matching Dell storage driver

    Obtain the Latitude 5300 2-in-1 storage/Intel Rapid Storage driver from Dell Support, extract it so the .inf, .sys, and .cat files are visible, and copy the extracted folder to USB.

    At the Setup prompt:

    1. Select Load driver.
    2. Browse to the extracted folder.
    3. Select the x64 driver matching the currently active BIOS storage mode—RAID/RST or AHCI.
    4. Continue only if the internal SSD appears.

    If manual loading succeeds, permanently add that package to a writable copy of boot.wim. Run these commands from an elevated Command Prompt on a working technician PC, not from the failing WinPE session:

    mkdir C:\W11Media C:\Mount
    robocopy D:\ C:\W11Media /E
    dism /Get-WimInfo /WimFile:C:\W11Media\sources\boot.wim
    dism /Mount-Image /ImageFile:C:\W11Media\sources\boot.wim /Index:2 /MountDir:C:\Mount
    dism /Image:C:\Mount /Add-Driver /Driver:C:\DellStorage /Recurse
    dism /Unmount-Image /MountDir:C:\Mount /Commit
    

    Before running the mount command, confirm that index 2 is identified as the Windows Setup image; otherwise use the index shown for Setup. DISM supports recursively adding INF-based driver packages to an offline image.^7^

    Recreate the USB from the serviced local folder rather than modifying the existing USB in place.

    4. Report a probable regression

    If the replacement Microsoft ISO fails while the SSD is visible—or an older 26H2 ISO still works—submit a Feedback Hub report containing:

    • Dell model and BIOS version.
    • ISO filename and download date.
    • boot.wim and installation-image metadata.
    • list disk/list volume results.
    • setupact.log and setuperr.log.
    • Whether the older 26H2 media succeeds.

    Feedback Hub supports recording reproduction steps and attaching diagnostics/files.^8^


    References

    1. Windows 11 release information
    2. Windows 11, version 26H2 known issues and notifications | Microsoft Learn
    3. Install Windows from a Flash Drive
    4. Uses the DISM command to list information about all images contained in a specified WIM, VHD, or FFU file.
    5. Install a boot-start driver
    6. Windows Setup Log Files and Event Logs
    7. DISM Driver Servicing (.inf) Command-Line Options
    8. Send feedback to Microsoft with the Feedback Hub app | Microsoft Support
    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.