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.
- 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^
- Do not reuse or modify the suspect ISO.
- 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:
- Select Load driver.
- Browse to the extracted folder.
- Select the x64 driver matching the currently active BIOS storage mode—RAID/RST or AHCI.
- 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
- Windows 11 release information
- Windows 11, version 26H2 known issues and notifications | Microsoft Learn
- Install Windows from a Flash Drive
- Uses the DISM command to list information about all images contained in a specified WIM, VHD, or FFU file.
- Install a boot-start driver
- Windows Setup Log Files and Event Logs
- DISM Driver Servicing (.inf) Command-Line Options
- Send feedback to Microsoft with the Feedback Hub app | Microsoft Support