I installed WinBoat in my OS 17.3 with hopes of running an old Windows program. To get it installed, each item on its menu needed to have a green arrow instead of a red x. I did that. I chose the Win 10 vs Win 11. Then on the next boot, Zorin constantly makes the same noise as when starting up. Zorin now runs very slow and hangs up.
Following advice on google searches, I uninstalled WinBoat. No changes. I ran 'top' in terminal. It showed 'windows' was running. Using the docker 'rm' command to remove 'windows' wouldn't work, as it said the container was still running.
Please advise on how to get rid of the virtual Windows.
Hi,
Thanks for the reply. System Monitor shows three things running: 1. tracker-miner-fs3, 2. gnome-system-monitor, 3. brave, and none take more than 2% of CPU. Windows thing is no longer there, so I most likely did get rid of it.
So... Something else is causing the constant 'seeking'. Timeshift isn't scheduled for a snapshot, so probably isn't doing it. I'm stumped, so any suggestions?
I used Brave A.I. search engine via Mojeek which came back with (I used ubuntu 24.04 in search criteria as Zorin is a fork of same):
"The slow boot in Ubuntu 24.04 is likely caused by the WinBoat container failing to stop properly or remaining active due to a known auto-start bug (Issue #474) or a confinement issue preventing access to ~/.winboat/ (Issue #340).
To resolve this, you should:
Disable Auto-Start : Check the WinBoat configuration and deactivate the "Auto Start Container" option, as leaving it enabled can cause the guest to autostart and delay boot.
Clear Residual Connections : If the VM is on an external drive, ensure it is disconnected and WinBoat is fully closed (pkill -f winboat ) before saving settings to prevent the container from being deleted or remaining active.
Verify Docker Access : Ensure Docker permissions are correctly set by running sudo chgrp docker /var/run/docker.sock and sudo chmod 660 /var/run/docker.sock , then reboot to confirm WinBoat services initialize correctly.
Check System Logs : Use systemd-analyze blame to identify if winboat or related Docker services are the primary bottleneck, as stale services can add significant time to the boot sequence.
This suggests that Winboat puts itself in 'Startup Applications'.
Once you get logged in, enter 'Startup Applications' in the Menu Search Bar and see if there is a Winboat/container listed there - then uncheck it and delete it. Just a guess on my part based on what came back from the search.