F5F Stay Refreshed Hardware Desktop Guide for Windows 11 Setup/Encountering Issues

Guide for Windows 11 Setup/Encountering Issues

Guide for Windows 11 Setup/Encountering Issues

Pages (3): Previous 1 2 3 Next
L
Lord_Whis
Member
70
01-03-2022, 04:09 PM
#11
The BIOS lists the drive, but Pop OS runs smoothly on it. The same USB works fine, yet the Windows installation causes problems. I’ll test another M.2 slot later and update you.
L
Lord_Whis
01-03-2022, 04:09 PM #11

The BIOS lists the drive, but Pop OS runs smoothly on it. The same USB works fine, yet the Windows installation causes problems. I’ll test another M.2 slot later and update you.

N
Nerdben
Member
112
01-03-2022, 05:13 PM
#12
I also tried another M.2 and received the same message.
N
Nerdben
01-03-2022, 05:13 PM #12

I also tried another M.2 and received the same message.

C
Chester09
Senior Member
491
01-03-2022, 11:49 PM
#13
If you can switch to another operating system, the M.2 slot works fine and the drive functions properly. This was my note to verify the drive’s operation. Would you like me to run the command "lspic -nn" in Pop OS and share the output? Perhaps we can determine the device details by vendor and ID. The vendor code should be 1022 for AMD, which should align with the IDs in the driver *.inf file. It’s possible the drivers currently installed don’t match. Could you provide the result list? Once we identify the correct driver plan, we can proceed with further actions. I’ve attempted to verify the drivers included with my installation media by executing these commands: I opened the Windows 11 installation media in cmd as administrator and ran "dism /Get-WimInfo /WimFileBig Grin:\sources\install.esd" – the output showed Windows 11 Pro with index 5. I created a directory at "C:\temp\mount" to store the image, extracted the ISO to "C:\temp\install.wim", and mounted it. The driver list displayed all entries, including the need to remove outdated drivers (see "DISM.exe /Image:C:\temp\mount /Remove-Driver /Driver:[OEM???].inf"). I couldn’t locate any AMD storage drivers on the media that would block loading from the MOBO site. I unmounted the image and applied the changes with "dism /Unmount-Image /MountDir:C:\temp\mount /commit". Because the USB is formatted FAT32, I split the install.wim file into parts up to 4000 MB. I renamed the original file to install.esd.old and copied all SWM files to a backup location. After testing, Windows 11 installed successfully using this media.
C
Chester09
01-03-2022, 11:49 PM #13

If you can switch to another operating system, the M.2 slot works fine and the drive functions properly. This was my note to verify the drive’s operation. Would you like me to run the command "lspic -nn" in Pop OS and share the output? Perhaps we can determine the device details by vendor and ID. The vendor code should be 1022 for AMD, which should align with the IDs in the driver *.inf file. It’s possible the drivers currently installed don’t match. Could you provide the result list? Once we identify the correct driver plan, we can proceed with further actions. I’ve attempted to verify the drivers included with my installation media by executing these commands: I opened the Windows 11 installation media in cmd as administrator and ran "dism /Get-WimInfo /WimFileBig Grin:\sources\install.esd" – the output showed Windows 11 Pro with index 5. I created a directory at "C:\temp\mount" to store the image, extracted the ISO to "C:\temp\install.wim", and mounted it. The driver list displayed all entries, including the need to remove outdated drivers (see "DISM.exe /Image:C:\temp\mount /Remove-Driver /Driver:[OEM???].inf"). I couldn’t locate any AMD storage drivers on the media that would block loading from the MOBO site. I unmounted the image and applied the changes with "dism /Unmount-Image /MountDir:C:\temp\mount /commit". Because the USB is formatted FAT32, I split the install.wim file into parts up to 4000 MB. I renamed the original file to install.esd.old and copied all SWM files to a backup location. After testing, Windows 11 installed successfully using this media.

M
MrAzazazaza
Member
222
01-04-2022, 04:39 AM
#14
I’ll check it later today when I can concentrate. I also saw earlier that the USB might be the issue. It seems to be quite old—maybe version 1.1—and there’s a chance it could be 2. Would it be better to switch to a USB 3.2 and test it?
M
MrAzazazaza
01-04-2022, 04:39 AM #14

I’ll check it later today when I can concentrate. I also saw earlier that the USB might be the issue. It seems to be quite old—maybe version 1.1—and there’s a chance it could be 2. Would it be better to switch to a USB 3.2 and test it?

S
Symphora
Member
177
01-04-2022, 05:30 AM
#15
I cannot locate any information about USB in that subject. Please run "lspci -nn" in Pop OS and share the output so we can determine the relevant hardware.
S
Symphora
01-04-2022, 05:30 AM #15

I cannot locate any information about USB in that subject. Please run "lspci -nn" in Pop OS and share the output so we can determine the relevant hardware.

S
ServoRo
Junior Member
15
01-04-2022, 07:00 AM
#16
The instruction was received.
S
ServoRo
01-04-2022, 07:00 AM #16

The instruction was received.

H
Hypersnake
Member
208
01-04-2022, 11:20 PM
#17
I doubt the "SSD Controller [126f:2263]" won't load a proper driver on Windows. Let's see how it behaves if you disable the checkbox to hide incompatible drivers during the driver search while installing. If a "Standard NVM Express Controller" appears, choose it. If not, navigate to X:\Windows\System32\DriverStore\FileRepository\stornvme.inf_amd64_???????????? and load the drivers.
H
Hypersnake
01-04-2022, 11:20 PM #17

I doubt the "SSD Controller [126f:2263]" won't load a proper driver on Windows. Let's see how it behaves if you disable the checkbox to hide incompatible drivers during the driver search while installing. If a "Standard NVM Express Controller" appears, choose it. If not, navigate to X:\Windows\System32\DriverStore\FileRepository\stornvme.inf_amd64_???????????? and load the drivers.

L
Letterman7171
Junior Member
3
01-06-2022, 08:58 AM
#18
Here are the Durocher listings for the pre-install driver recommendations from Gigabyte. None of these resolved the problem and only displayed the original error message. I also attempted the directory you mentioned, which contained the driver list, but it didn’t work either.
L
Letterman7171
01-06-2022, 08:58 AM #18

Here are the Durocher listings for the pre-install driver recommendations from Gigabyte. None of these resolved the problem and only displayed the original error message. I also attempted the directory you mentioned, which contained the driver list, but it didn’t work either.

G
gaLact1cfLea
Member
194
01-06-2022, 09:28 AM
#19
Yes, we have another M.2 drive available for testing.
G
gaLact1cfLea
01-06-2022, 09:28 AM #19

Yes, we have another M.2 drive available for testing.

T
T5lyn
Junior Member
33
01-06-2022, 03:59 PM
#20
Sorry, I don't understand.
T
T5lyn
01-06-2022, 03:59 PM #20

Sorry, I don't understand.

Pages (3): Previous 1 2 3 Next