Comment 55 for bug 1874453

@haggan-era, could you open a new bug on this issue? Please provide the following information:

1. version of Windows, vagrant, virtualbox, and Ruby in use on the Windows computer
2. the Vagrantfile used to create the new .box
3. any steps to reproduce the issue.

On first smell it seems like a Ruby on Windows issue handling File::NULL. that was added Ruby 1.9.3 I think. I'd surmise that if you took the Vagrantfile, and ran the operation there, it'd work fine. Give that a try. If it is translating the object to a specific path reference, then that means File::NULL is platform dependent on creation of the box.