Thank you so much for your help Alvaro.
I did actually try creating the /vagrant directory in the VM from which I
made the box and when I run it, there was a complaint when it made /vagrant.
Not sure if this is a bug because though the output lists the command, it
gives no output.

==> default: Machine booted and ready!
==> default: Checking for guest additions in VM...
==> default: Mounting shared folders...
    default: /vagrant => D:/Vagrant_examples/mint182_base
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!
mkdir -p /vagrant
Stdout from the command:

Stderr from the command:
PS D:\Vagrant_examples\mint182_base>

So I am guessing that when it created /vagrant, the output (either stdout
or stderr) was "already exists" but this is not displayed.
No problems though, I can remove /vagrant in the original VM and create a
new box.

This mailing list is governed under the HashiCorp Community Guidelines - Behavior in violation of those guidelines may result in your removal from this mailing list.

GitHub Issues:
IRC: #vagrant on Freenode
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB