F5F Stay Refreshed Hardware Desktop The connection isn't visible during the initial setup process.

The connection isn't visible during the initial setup process.

The connection isn't visible during the initial setup process.

P
PvpSkilzz
Junior Member
13
01-02-2023, 08:15 PM
#1
I recently assembled my initial machine (Ryzen 5 7600, ASRock B650M Pro RS WiFi MoBo, 2 TB WD SN580 SSD, 2x16 GB G.Skill Flare X5 DDR5-6000, AMD Radeon RX 6700XT, Seasonic Focus GX-750 power supply) and faced a challenge when I needed to reinstall Windows (long journey). Suddenly, no WiFi networks appear, stopping me from proceeding. Additionally, when attempting to use the command prompt to proceed with setup, I’m unable to type. This isn’t a keyboard problem since it previously worked and even opened the prompt successfully. After inspecting the PC, the WiFi card was properly seated. I’m uncertain about the next steps.
P
PvpSkilzz
01-02-2023, 08:15 PM #1

I recently assembled my initial machine (Ryzen 5 7600, ASRock B650M Pro RS WiFi MoBo, 2 TB WD SN580 SSD, 2x16 GB G.Skill Flare X5 DDR5-6000, AMD Radeon RX 6700XT, Seasonic Focus GX-750 power supply) and faced a challenge when I needed to reinstall Windows (long journey). Suddenly, no WiFi networks appear, stopping me from proceeding. Additionally, when attempting to use the command prompt to proceed with setup, I’m unable to type. This isn’t a keyboard problem since it previously worked and even opened the prompt successfully. After inspecting the PC, the WiFi card was properly seated. I’m uncertain about the next steps.

V
valentijn10000
Junior Member
49
01-03-2023, 01:10 PM
#2
This typically occurs if the chipset or Wi-Fi drivers aren't installed or copied into the installation files. NOTE: Microsoft hasn't fixed the issue allowing the command prompt in the newest installer. I heard someone mention a workaround before.
V
valentijn10000
01-03-2023, 01:10 PM #2

This typically occurs if the chipset or Wi-Fi drivers aren't installed or copied into the installation files. NOTE: Microsoft hasn't fixed the issue allowing the command prompt in the newest installer. I heard someone mention a workaround before.

T
ThereWas
Member
137
01-03-2023, 02:29 PM
#3
I resolved it, likely due to a driver problem. The fix I implemented should align with what’s needed.
T
ThereWas
01-03-2023, 02:29 PM #3

I resolved it, likely due to a driver problem. The fix I implemented should align with what’s needed.