title: Ubuntu 20.04 LTS host "VBoxClient: The virtualbox kernel service is not running" after logging into Ubuntu
body: <p>I'm running Oracle VirtualBox VM 6.1 on an Ubuntu 20.04 LTS host.</p>
  <p>The guest OS is Windows 10.</p>
  <p>After booting up the computer and logging into my user account, I get a grey window that pops up at the top of the desktop that says: <code>VBoxClient: The virtualbox kernel service is not running...</code></p>
  <p>Mind you, this is without starting VirtualBox; this message just pops up almost immediately after logging into my desktop.</p>
  <p>I can, however, start VirtualBox and run my guest OS without problems.</p>
  <p>I have updated the Ubuntu OS several times since installing it, and I've reinstalled VB to keep it up to date.</p>
  <p>What is causing this message to appear?</p>
  <p>I ran <code>sudo grep -i virtualbox /var/log/boot.log</code> in the terminal and got</p>
  <pre><code>Starting VirtualBox Web Service...
  [FAILED] Failed to start VirtualBox Web Service.
           Starting VirtualBox Web Service...
  [FAILED] Failed to start VirtualBox Web Service.
           Starting VirtualBox Web Service...
  [FAILED] Failed to start VirtualBox Web Service.
           Starting VirtualBox Linux kernel module...
  [  OK  ] Started VirtualBox Linux kernel module.
  </code></pre>
  <p>as the output.</p>
  <p>So, it appears that the kernel module is staring properly but not the kernel service.</p>
  <p>When I run  <code>ls /etc/modules-load.d</code></p>
  <p>I get <code>cups-filters.conf  modules.conf</code> as the output.</p>
  <p>If I open modules.conf, I get</p>
  <pre><code># /etc/modules: kernel modules to load at boot time.
  #
  # This file contains the names of kernel modules that should be loaded
  # at boot time, one per line. Lines beginning with &quot;#&quot; are ignored.
  </code></pre>
  <p>So, it appears that <em>no</em> kernel modules are being loaded at boot time.</p>
  <p>I really don't know what to make of all this.</p>
  <p>I get an error message that doesn't seem to really affect the function of VirtualBox.</p>
  <p>But, it doesn't seem that the error message should exist because the kernel module is starting.</p>
  <p>Though, it seems that that should not be possible as no modules are being loaded at boot time at all.</p>
  <p>What's causing this problem, and how do I remedy it?</p>
  <p>I don't want that message to pop up anymore.</p>
  <p>Thanks....</p>