Winboat
Winboat
winboat is considered a type of VM that supposedly handles many Windows applications. It could very well mark next year as the year Linux takes over (similar to how W10 EOL happened). It's still in beta, and I find it overly optimistic. You’ll need a W11 ISO and configure RAM/cores. It functions like a standard VM but shares the same limitations (resource use, etc.).
I’m running MX Linux 25 on an i7-6700 with 16GB RAM. The issue might stem from insufficient RAM or cores. Some problems I face and hope to fix:
- I set it up without a local W11 ISO, but now it uses their remote version in a browser. How can I switch back to a local one?
- The connection is unstable; the container frequently crashes.
- I planned to uninstall and reinstall, but documentation is missing.
- ChatGPT commands suggested removing Winboat, but after reinstalling it still showed the same settings (no local W11).
- I noticed briefly that I could see remote activity on both monitors, but RDP blocked me.
- I saw a Windows session on one screen, but it reported an issue with remote access.
Could anyone use this in real life with two monitors? Is there a way to activate Windows properly for these VMs?
- Could the OS installation require activation?
- What exactly happens with these Windows emulators? They seem dependent on official ISO files.
So far, this product is being touted as a solution for needing Windows apps, but its beta state, poor support, and frequent glitches make it less appealing. I’m prepared to try running the required software even if it’s not perfect. This experience might be more about my setup than the tool itself.
In the year of Linux, set up a Windows virtual machine and test RemoteApp to simulate Microsoft Office functionality on Linux. The setup lacks visual effects or performance boosts, just adding extra layers to enhance your experience.
This approach isn't unique—WinBoat follows similar strategies, as seen with WinApps. Several other projects have tackled comparable challenges. It keeps your GPU separate from the Windows virtual environment and lacks true 3D acceleration. Merging it would be necessary, but relying on OpenGL alone would require passing through translation layers like wined3d, which often sacrifice performance and precision. Your RDP setup likely won't function as expected because these tools alter registry settings to target individual windows instead of the full desktop. Unless you're targeting something specific like MS Office, it's largely ineffective. For anti-cheat concerns, AntiCheats already monitors VM environments, making such modifications risky. Ultimately, it remains Windows running inside QEMU/Linux with KVM, offering a streamlined setup but still constrained by the same limitations.
It feels like a strict rule about not eating meat on Fridays is a bit religious. That clearly bothers people. Then they say fish isn’t meat, so they can still eat it on Fridays. If I run Linux on my home desktop, I’d use a Windows version to run a VM for remote work and connect to a W11 PC at work. Just to show everyone: "I’m not giving up on MS!" Linux seems perfect for everyday use, but desktops are too complicated if you occasionally need Windows tools. Dual-booting adds more hassle with maintenance and setup. Still, I sometimes have to restart my PC in BIOS to switch boot settings, jumping between apps nonstop—10 times a day! Yet I still hope solutions like Winboat improve in the future."
For a Windows VM experience using VMWare Workstation, it's now available with 3D acceleration included. If you're using Intel or AMD processors, check the VMware documentation at the provided link. Otherwise, expect GPU pass-through via QEMU/LibVirt KVM or a less stable alternative in VirtualBox.
Wouldn't it be better to use the Linux version of VMWare and then launch W11? Would that function smoothly on both screens without any borders or issues? I tried using a VMWare machine in W11 to test Linux distributions, but it didn’t display full screen or work well across both monitors. It also struggled with performance overhead. When I connected remotely from Windows, the two monitors displayed exactly like me sitting at my desk, with no distracting borders.
I don't fully align with this perspective. Most attention is directed toward Server and Workstation areas, while the rest of the community primarily creates content outside corporate support. Many of us struggle with user interfaces; much work begins in terminal commands and configuration files. Some prioritize simplicity through a graphical interface, but others stick to it for its ease of use. No one wants restrictions, which is why tools like WinBoat exist even if they don’t address the core needs. They aim to help, though their solutions may not match what users expect or what developers envision. Yes, I’m not familiar with multi-monitor setups, but fullscreen mode is available. I only use it occasionally for software development. Minimizing performance impact requires specific configurations—such as qemu/libvirt, KVM, GPU passthrough, and isolation techniques. Ideally, your system should be tailored to avoid resource conflicts; otherwise, it’s mainly about convenience. This is the approach I rely on most. I don’t have much experience with dual monitors either, since I usually work on a single screen, but you can still connect monitors directly to the GPU that feeds the VM, bypassing look-glass entirely.
it's a reverse Windows subsystem on Linux. Citrix functions like another way to run remote applications. Instead of just connecting to the desktop, you send specific app windows from a VM to the host, letting them communicate as normal programs. Essentially, it acts like a window into an RDP session for an app inside a virtual machine. Around 2020 Microsoft promoted this approach for businesses, enabling them to deploy apps across multiple VMs in a tightly managed setup. Users can now connect 50 remote clients to just a few VMs for a single application. It appears to run locally but is actually remote. This technology is especially useful for specialized software needing on-prem databases due to low latency requirements. Suddenly, companies don’t need to be physically present in an office—clients can manage software from anywhere, even outside the main office. Previously, I handled software installations manually for clients, but now it’s possible to install everything overnight across VMs.