This is just a rant but maybe others are having similar problems…
My issue with Windows Pro 10 is I can’t stop it from rebooting. It seems like it’s constantly updating and rebooting, requiring me to constantly startup Hassio manually.
However… Rebooting would be ok if I could get Virtualbox to start Hassio via either a batch file or startup or via task scheduler. When I try either, Hassio launches but it never finishes booting up fully. It just gets stuck on startup. Can manually startup without any issues though. So anyways, thinking about switching to Linux to have more control over my setup. Any thoughts/suggestions?
From what I read, that’s a common setup. It’s not running in windows, it’s running in a VM within windows, which should be fine since it has it’s own OS.
Should be fine, as long as you don’t reboot too much. If you don’t use the PC for anything else, I suggest using proxmox instead of virtualbox on linux.
Windows is fine for VM, as long as it is the server version of the operation system.
The workstation version will restart a lot more than what HA likes, due to updates being installed automatically and requiring a reboot of the entire system.
Correct, doesn’t make much of a difference if using proxmox, windows server or any other solution, once the host system does require a reboot the virtual machines become unavailable and since running lots of virtual machine on my syno aswell as some on a windows server the past shows that both are next to equal in downtimes.
Though if windows server I wouldn’t use virtualbox, tried that once and replaced it using HyperX since it works as designed.
And right because of these downtimes I switched from a virtualized HA onto separate hardware, not to mention I’m not interested in wasting additional time to take care about updating it’s underlying OS manually. Since then it runs smoothly on it’s own and didn’t ask for a restore for more but 2 years now. Rock solid if you ask me. Virtualizing may offer some advantages when it comes to the snapshot capabilitites given, but reinstalling one from scratch and restoring the last update also works without problems. Tested recently when I did setup a testsytem besides the productive one.
Other things aside, you can stop it from auto installing updates and rebooting. Run gpedit.msc and go to Computer Configuration/Administrative Templates/Windows Components/Windows Update and then:
Configure Automatic Updates: double click, enable, and select option “2”
No auto-restart with logged on users for scheduled automatic updates installations: double click and enable
and reboot PC. I’m not sure if there are any other settings that need to be changed (I configured my system ~6 years ago), but it’s 100% doable.
Oh I tried those and no matter what I do, Home Assistant starts up but will not finish the start-up process. It’s like it gets stuck half-way through. But if I start it up manually, works everytime. I don’t know if this is a virtualbox issue or what but I’m pretty stumped on it.
If the device is not used for anything else, you could just install HAOS on it directly. I bought a cheap intel NUC which came with Windows 10 and did just that - it runs HAOS really nicely
