F5F Stay Refreshed Hardware Desktop Your computer's media driver is not installed during the Windows 11 setup process.

Your computer's media driver is not installed during the Windows 11 setup process.

Your computer's media driver is not installed during the Windows 11 setup process.

Y
YangYang
Member
131
02-28-2023, 03:37 PM
#1
I'm working on several new builds using a MSI MEG Z690 Ace with 14th gen Intel processors (14700 & 14900). I'm installing Windows 11 for the first time. The 4TB SSD is located in the m2_1 slot, and Linux is successfully detecting it. When launching the Windows installer and selecting "Install Now," I encounter an error: all available drivers from the support page were unzipped to a FAT32 pendrive, but nothing appears relevant—no chipset drivers or M2-specific ones found. The process stops before any installation, with most entries labeled as bundled executables. I also tried installing drivers directly from the pendrive, but it still doesn't recognize anything. Could you find more detailed logs or guidance to identify which drivers are missing? Have others faced similar issues? It's unclear exactly which ones are needed for this setup.
Y
YangYang
02-28-2023, 03:37 PM #1

I'm working on several new builds using a MSI MEG Z690 Ace with 14th gen Intel processors (14700 & 14900). I'm installing Windows 11 for the first time. The 4TB SSD is located in the m2_1 slot, and Linux is successfully detecting it. When launching the Windows installer and selecting "Install Now," I encounter an error: all available drivers from the support page were unzipped to a FAT32 pendrive, but nothing appears relevant—no chipset drivers or M2-specific ones found. The process stops before any installation, with most entries labeled as bundled executables. I also tried installing drivers directly from the pendrive, but it still doesn't recognize anything. Could you find more detailed logs or guidance to identify which drivers are missing? Have others faced similar issues? It's unclear exactly which ones are needed for this setup.

T
Trembling
Junior Member
3
03-01-2023, 05:06 PM
#2
I apologize for the confusion; navigating CMD.exe isn't my usual path and it's causing some trouble... However, I found that pressing Shift + F10 takes me straight back to cmd.exe, and there are installer logs in X:\Windows\panther. I'm checking setupact.log, which appears to be the main file being written to. After using the "Rescan" option in the dialog, I noticed relevant entries about PnP—Plug-and-Play, which seems to handle hardware driver matching automatically. It looks like this might be the system's way of managing drivers, though I'm not sure if it helps with the current issue. There are also warnings in the logs indicating that no driver packages were found on my thumb drive, but there don't seem to be any initial errors that would prevent the driver dialog from appearing.
T
Trembling
03-01-2023, 05:06 PM #2

I apologize for the confusion; navigating CMD.exe isn't my usual path and it's causing some trouble... However, I found that pressing Shift + F10 takes me straight back to cmd.exe, and there are installer logs in X:\Windows\panther. I'm checking setupact.log, which appears to be the main file being written to. After using the "Rescan" option in the dialog, I noticed relevant entries about PnP—Plug-and-Play, which seems to handle hardware driver matching automatically. It looks like this might be the system's way of managing drivers, though I'm not sure if it helps with the current issue. There are also warnings in the logs indicating that no driver packages were found on my thumb drive, but there don't seem to be any initial errors that would prevent the driver dialog from appearing.

S
stockchief7
Member
172
03-09-2023, 05:31 AM
#3
Well this was a good example of a rubber duck debug... After searching a bunch of the suspicious logs from the installer, I came across the following links [1] [2] The installer flash drive is corrupted; I created it on linux with dd, which evidently cannot be done. I used a tool called WoeUSB which allowed me to create usable boot media from linux. Here's the command: # Sub in your iso file and flash drive destination. Don't screw this up. sudo woeusb --device Win11_23H2_English_x64v2.iso /dev/sda
S
stockchief7
03-09-2023, 05:31 AM #3

Well this was a good example of a rubber duck debug... After searching a bunch of the suspicious logs from the installer, I came across the following links [1] [2] The installer flash drive is corrupted; I created it on linux with dd, which evidently cannot be done. I used a tool called WoeUSB which allowed me to create usable boot media from linux. Here's the command: # Sub in your iso file and flash drive destination. Don't screw this up. sudo woeusb --device Win11_23H2_English_x64v2.iso /dev/sda