title: Error after `vagrant halt; vagrant up`
body: <p>I am setting up a Ubuntu 15.04 VM on Win7 using Vagrant 1.7.4 and VBox 5.0.0.</p>
  
  <p>On the first <code>vagrant up</code> I can ssh into the machine using <code>vagrant putty</code> and everything is setup correctly and works. When I run <code>vagrant halt</code>, the VM shuts down gracefully without error messages.</p>
  
  <p>However, when I try to restart the VM using <code>vagrant up; vagrant putty</code>, the machine is in a strange state. For example, the default synced folder <code>/vagrant</code> is empty, even though the second <code>vagrant up</code> call prints this message:</p>
  
  <p><code>default: /vagrant =&gt; C:/Users/ArneUser/numecs/dev_env</code></p>
  
  <p>Also, this <code>vagrant up</code> call prints the following message in PowerShell:</p>
  
  <pre><code>The following SSH command responded with a non-zero exit status.
  Vagrant assumes that this means the command failed!
  
  /sbin/initctl emit --no-wait vagrant-mounted MOUNTPOINT=
  
  Stdout from the command:
  
  Stderr from the command:
  
  stdin: is not a tty
  bash: line 2: /sbin/initctl: No such file or directory
  </code></pre>
  
  <p>I am running a really basic setup just to test for this error, so I don't think the mistake is in my provisioning script. Some pointers in the right direction would be appreciated. </p>