Hello, I am a Korean user.
Building VHDX for "test" (this may take several minutes)...
Detected ISO language: en-US
Even though I ran a Windows ISO file in Korean, it recognizes it as English.
I downloaded the ISO file from the official Microsoft page.
Perhaps because of this, an English keyboard is installed every time, causing the inconvenience of having to manually configure Korean input settings. I hope this can be improved.
The host allocated 192.168.42.2, but applying it inside the guest via netsh failed.
Root Cause
The guest's network adapter is named in the localized language (이더넷 instead of Ethernet). The agent appears to build the netsh command assuming the English adapter name Ethernet, so the name lookup fails on a localized OS.
Workaround
Running the following manually inside the guest restores connectivity:
netsh interface ip set address name="이더넷" static 192.168.42.2 255.255.255.0 192.168.42.1
netsh interface ip set dns name="이더넷" static 8.8.8.8
(On an English-locale guest the adapter is named Ethernet; substitute the localized name accordingly.)
Suggested Fix
Reference the adapter by interface index or GUID instead of a hardcoded English name — e.g. resolve the adapter via Get-NetAdapter / interface index and pass that to netsh — so it works regardless of OS locale.
Hello, I am a Korean user.
Building VHDX for "test" (this may take several minutes)...
Detected ISO language: en-US
Even though I ran a Windows ISO file in Korean, it recognizes it as English.
I downloaded the ISO file from the official Microsoft page.
Perhaps because of this, an English keyboard is installed every time, causing the inconvenience of having to manually configure Korean input settings. I hope this can be improved.
The host allocated
192.168.42.2, but applying it inside the guest via netsh failed.Root Cause
The guest's network adapter is named in the localized language (
이더넷instead ofEthernet). The agent appears to build the netsh command assuming the English adapter nameEthernet, so the name lookup fails on a localized OS.Workaround
Running the following manually inside the guest restores connectivity:
(On an English-locale guest the adapter is named
Ethernet; substitute the localized name accordingly.)Suggested Fix
Reference the adapter by interface index or GUID instead of a hardcoded English name — e.g. resolve the adapter via
Get-NetAdapter/ interface index and pass that to netsh — so it works regardless of OS locale.