A Homework PC Shouldn't Need Disaster Recovery. This One Got It Anyway.

A family Windows 11 PC can run inside Proxmox VE with GPU passthrough and separate backups, but disaster recovery is only useful if someone can restore it quickly. One parent built that arrangement around schoolwork and gaming, turning a familiar desktop into a small virtualized service.

The reported system combined a mini PC, a Windows guest, direct graphics and USB access, and a recovery plan. It shows what one family configured, not a measured proof that every hardware failure can be recovered without disruption.

How can Proxmox protect a family homework PC?

Proxmox can separate the Windows desktop from its host and make backup-based recovery easier, provided the backup can actually be restored.

The parent already had experience running Proxmox for everyday homelab duties: OPNsense, Docker, network storage, and Plex. A new school year created a different kind of requirement. The children needed a machine that could run normal Windows applications, handle schoolwork, and support games when the work was finished. The parent, however, was picturing the inevitable late-night call about a broken update, a suspicious download, or a system that simply refused to start. Rebuilding a physical Windows installation at that moment sounded exhausting. So a Minisforum HX99G, previously a capable personal computer, was reassigned to the family. Proxmox became the underlying host, and Windows 11 became the children's desktop running inside a virtual machine.

For the step from ordinary desktop installation to a managed host, use the Proxmox install walkthrough as a baseline.

The clever part is that the children aren't being asked to understand any of this. They see a monitor, keyboard, and mouse attached to a computer, just as they would with an ordinary PC. Windows runs locally, with its own physical graphics and peripheral devices passed into the guest. Behind that normal-looking desktop sits Proxmox Backup Server, or PBS, which can restore the Windows virtual machine after serious trouble. Important files have another layer of protection through Synology Drive and Veeam Community Edition. A VM restore and file recovery solve different problems. The setup tries to address both rather than assuming one backup mechanism can magically solve every sort of loss.

That separation also explains why the design attracted attention. A simple snapshot can be useful for rolling back a mistake, but it doesn't offer the same protection as an independently stored backup when the original host or storage fails. In this arrangement, PBS protects the virtual operating-system disk. The dedicated 2TB NVMe drive passed into Windows is for games and isn't included in those backups, deliberately avoiding the cost and storage overhead of repeatedly copying a huge game library. If a restore becomes necessary and the game drive survives, Steam can rediscover its files. Those games remain at risk if the drive fails.

Can a Windows VM behave like a normal gaming PC?

Passing compatible GPU and USB devices into a Windows guest can make the virtual machine feel like a local desktop.

Getting the system to feel like a normal computer required more than placing Windows inside Proxmox. The HX99G's Radeon RX 6600M is passed directly to the guest, along with USB controllers, Wi-Fi and Bluetooth hardware, and the separate NVMe drive. Proxmox starts first, then launches the Windows VM automatically. Once Windows loads, the physical monitor shows its output and the attached keyboard and mouse behave like ordinary Windows devices. There is no mandatory remote-desktop session between the children and the machine sitting in front of them. The family gets a local-first computer with virtualization hidden underneath it, and remote access is an extra capability rather than the main way to use it.

Remote use comes from an Apollo and Artemis streaming setup with hardware acceleration, accessed through Tailscale. That means the machine can also act as a gaming or work computer away from the desk. One commenter initially assumed the children were accessing Windows over ordinary remote desktop and worried about gaming responsiveness. The parent clarified that local use is direct GPU output, while the streaming tools are reserved for remote sessions. Others began thinking aloud about Raspberry Pi clients, inexpensive Dell Wyse boxes, old Intel Compute Sticks, or even classic Sun Ray terminals. A project built to avoid technical chaos had become a magnet for more technical possibilities.

Of course, invisible complexity is still complexity. The parent described early passthrough problems, including a ReBAR-related Code 43 issue on the RX 6600M and a need to bind the NVMe device to vfio before the regular NVMe driver claimed it. There are also everyday surprises. Shutting down Windows stops the virtual machine, but Proxmox remains on and the display loses its Windows output. The host can still be managed remotely, and the parent considered options such as starting the VM through the web interface, triggering it through Home Assistant, or connecting a physical button to the Proxmox API. The host's power button already handles a clean shutdown, while Wake-on-LAN can bring the machine back and let Windows start automatically. Ordinary power-button behavior suddenly has a design document.

Does extra virtualization make a family PC more reliable?

Virtualization adds recovery options but also introduces host, hardware-assignment and administrator dependencies.

Many reactions celebrated the project precisely because it was excessive. A few parents wanted a practical guide so they could try a similar arrangement. Another enthusiast considered using a spare desktop to alternate between a Windows VM and a Linux-based gaming environment. The conversation quickly became technical: a GPU can be assigned to one running guest, but sharing a single gaming GPU across several simultaneously active desktops is a different and more restrictive problem. If two virtual machines take turns, the hardware can potentially be reassigned between them after one shuts down. If both must run at once, separate graphics resources may be the more realistic answer.

The recovery design should follow a Proxmox backup plan with restore testing, not only an attractive VM snapshot schedule.

The pushback was just as revealing. One person who worked with VDI professionally described it as frustrating and suggested a Chromebook instead. Another argued that Windows itself was the problem and preferred Linux. A different parent described using Kubuntu with Windows applications tucked away in a VM; someone else proposed Kasm and disposable sessions that could be thrown away after use. They're alternative answers to the same household question: how do you keep a child's computer usable without becoming its permanent repair technician? If the children already have Chromebooks and still need particular Windows applications or Steam games, though, replacing the operating system doesn't automatically meet the requirement. Convenience depends on whose convenience is being measured.

Then came the sharper warnings. Commenters pointed out that some school assessment tools, including Respondus LockDown Browser and Honorlock in certain configurations, may reject virtual machines. Another warned that games with anti-cheat systems can detect virtualized environments and create compatibility or account risks. Those concerns undermine the comforting assumption that a guest Windows installation will behave exactly like a physical one in every situation. The parent acknowledged the test-taking issue and suggested fallback options, including the family's Chromebooks where supported, a separate physical Windows machine, or temporarily running Windows directly on hardware. Compatibility can defeat an elegant recovery plan.

Security brought its own temptation. One commenter suggested application restrictions; another floated Active Directory, centralized logging, and tools such as Wazuh or Graylog. The parent had already placed the children on standard user accounts, but the discussion threatened to turn a homework station into a security operations lab. Restore too recent a version and the problem may come back; restore too old a version and valuable work can disappear. File versioning and repeated PBS backups offer choices, but someone still has to choose the right recovery point. A system designed to replace emergency troubleshooting with restoration may simply relocate the hard decisions to a different screen.

Is Proxmox disaster recovery worth the complexity at home?

Use a virtual desktop for schoolwork only if the person supporting it can restore it faster than a simpler PC would take to fix.

The most interesting disagreement isn't whether Proxmox can do the job. The original setup demonstrates one way to make a virtual machine feel like an ordinary Windows desktop, with the caveat that the parent had to solve real passthrough and operational problems along the way. The disagreement is over what counts as simpler. To someone comfortable with hypervisors, restoring a VM from PBS may feel easier than diagnosing an unpredictable Windows installation. To a family without that experience, maintaining a Proxmox host, backup server, passthrough configuration, and remote access stack could be the nightmare. Complexity hasn't disappeared. It has been moved from the children's day-to-day experience into the hands of the person willing to maintain it.

That trade becomes easier to understand once the design is viewed as a family decision rather than an abstract technology contest. The parent wanted the children to have a normal Windows environment, access to school applications, a decent gaming machine, and a way back from the damage that ordinary computer use can cause. The children don't need to know what vfio does or how a restore point is selected. Meanwhile, the technically inclined adult gets a project that doubles as a learning exercise, complete with spare capacity for more virtual machines if the urge becomes irresistible.

Perhaps the funniest part is that several people reacted as though overengineering were its own reward. The parent admitted that curiosity was part of the motivation and joked about how tempting it would be to keep adding infrastructure. Yet the practical risks are real: incompatible exam software, anti-cheat restrictions, unusual shutdown behavior, the absence of game-drive backups, and the need to distinguish a clean recovery point from a compromised one. It is a very particular response to a very familiar fear. The next time homework is due and Windows misbehaves, the family may discover whether all that preparation buys a peaceful evening. The person who built it, at least, will have a much more interesting recovery story than reinstalling Windows.

I would use this at home only where the builder can demonstrate a complete restore before school deadlines. If nobody wants to maintain the host, a conventional Windows PC with automatic document backups is the safer family choice.