Try this link.
Also read this article relating to Intel NIC optimisation. There are performance issues with Hyper-V.
thank you i will try this
I found a bit of time to get things going and I have not had any issues, everything worked as expected.
tested on Windows 10 Pro and Windows 10 Wst (normal Windows license)
- Download and unzip official HAOS image for Hyper-V
- Attach HAOS image to Hyper-V using Quick Create
using default settings
HAOS started with no issues having picked up an internal DHCP IP-address
because it is DHCP you can see there is no IP-address under Networking
This setup should work flawlessly if using an external switch; when I get a bit of time will try it.
As expected HAOS can be installed using an external switch.
My external switch using a laptop wireless Intel NIC (using only defaults)
I noticed when I created my first VM using the Default Switch and then tried to create another VM using an external switch HAOS failed to initialise with the below error. To fix it I rebooted the laptop having deleted all VMs created. I then proceeded to create the VM using external switch above with no issues.
So to conclude the issues experienced with HAOS and Hyper-V have something to do with machine configurations and nothing to do with either HAOS or Hyper-V.
Forgot to mention because the IP-address is DHCP you will not see and IP-address in the Networking status of the HAOS VM.
I also changed the IP-address to static and everything works. Here is the command:
net update eth0 --ipv4-method static --ipv4-address 192.168.2.123/24 --ipv4-gateway 192.168.2.1 --ipv4-nameserver 8.8.8.8
and you can then follow with HA onboarding through the browser:
One last note. Even if you enable Guest services for the HAOS VM, Hyper-V will not display the IP-address static or dynamic. Uncertain why.
Ok nice thank you, i’ll re-test
I compared my settings to yours,
Had to uncheck this check box :
external switch > extensions > Microsoft Azure VPS Switxh Filter Extension
now i see the web page, but is is looping inside à WARNING :
22-07-15 17:12:06 WARNING (MainThread) [supervisor.homeassistant.core] Error on Home Assistant installation. Retry in 30sec
22-07-15 17:12:36 WARNING (MainThread) [supervisor.jobs] ‘Updater.fetch_data’ blocked from execution, no supervisor internet connection
22-07-15 17:12:36 WARNING (MainThread) [supervisor.homeassistant.core] Error on Home Assistant installation. Retry in 30sec
22-07-15 17:13:06 WARNING (MainThread) [supervisor.jobs] ‘Updater.fetch_data’ blocked from execution, no supervisor internet connection
22-07-15 17:13:06 WARNING (MainThread) [supervisor.homeassistant.core] Error on Home Assistant installation. Retry in 30sec
Ok i re-downloaded vhdx,
then got to default network,
net update eth0 --ipv4-method auto --ipv6-method auto --ipv4-nameserver 1.1.1.1
net info
finally OK : http://homeassistant.local:8123
Fantastic. Enjoy HA. It is an amazing platform made by amazing and dedicated to the cause people. If you like HA please consider subscribing to Nabu Casa as it help keep this open-source project alive and is a little reward to people who dedicate tons of hours onto the platform.
1 Like
When on the default switch HA don’t see lan devices.
I switched on the external and run command to configur via static ip via my internet box getway.
net update eth0 --ipv4-method static --ipv4-address 192.168.1.90/24 --ipv4-gateway 192.168.1.1
–ipv4-nameserver 192.168.1.100,1.1.1.1
192.168.1.90/24 : new ip in my internet box lan
192.168.1.1 : internet box getway
192.168.1.100 : pi-hole dns on nas, the internet box uses it as first dns
1.1.1.1 : cloud flare dns
Finally it added this second config and it worked, now HA OS see devices in the lan.
When i started on default network, it updated HA OS, perhaps this helped to make external net work.
Also changed hostnale to hass in the HA OS network settings.
Added local dns name hass.l for 192.168.1.90 in the pi-hole local dns names list.
Now i can acces Hyper-V HA OS on :
192.168.1.90:8123
hass.local:8123
hass.l:8123
Thank you for your help,
Best regards 
Default switch should not be used with HA as it is only of use when you want to communicate with other VMs (I used it only as a quick example to prove that HA has no issues with Hyper-V). External switch is the way to go as HA can discover devices on your physical network.
Glad everything working for you. Enjoy HA.
1 Like
