Vagrant not working on Japanese Windows OS - Encoding problem

[JordanJapan]

Vagrant version

2.2.4

Host operating system

Windows 8.1 (Japanese)

Debug output 1

Bringing machine 'default' up with 'virtualbox' provider...
==> default: Importing base box 'ubuntu/trusty64'...
C:/HashiCorp/Vagrant/embedded/gems/2.2.4/gems/childprocess-0.6.3/lib/childprocess/windows/process_builder.rb:43:in `join': incompatible character encodings: Windows-31J and UTF-8 (Encoding::CompatibilityError)

Debug output 2

Bringing machine 'default' up with 'virtualbox' provider...
==> default: Importing base box 'ubuntu/trusty64'...
C:/HashiCorp/Vagrant/embedded/gems/2.2.4/gems/vagrant-2.2.4/plugins/providers/virtualbox/driver/base.rb:408:in `block in execute': invalid byte sequence in UTF-8 (ArgumentError)

Description

I'm new to using this and I was following a video online. However, when I got the step of using vagrant up, I got an encoding error (debug 1). After looking around, I tried changing command prompt's code page to 65001 from 932. Unfortunately, a new error occurred (debug 2)

Is there a clean and simple solution to just make it work or even better automatically set the encoding as needed? Thanks.

[briancain]

Hey there @JordanJapan - could you please provide the full output of running vagrant up --debug in a gist? Thanks!

[JordanJapan]

Hello. Thanks for the reply.

When I tried that command a lot of output appeared and I couldn't copy it all. I was looking for a way to try outputting the entire log to a file, but with command prompt it refuses to do so even with the redirect command.

vagrant up --debug > c:\file.txt

It only copies the first 2 lines of the debug output. Is there another way to output to a log file in Windows? Thanks in advance.

[briancain]

@JordanJapan - you should be able to do something like....

vagrant up --debug 2>&1 | Tee-Object -FilePath ".\vagrant.log"

Hopefully that works!

[JordanJapan]

Alright. The above command wasn't working in command prompt, but I installed Power Shell after reading about it and I got a file this time. Same errors still occur, however.

I attached the .txt file with the complete output.

Thanks for taking the time to help.

log.txt

[briancain]

Thanks for the information! I will put this issue in our next milestone so that we can try to fix it in the next release. ❤️

[voxik]

Isn't childprocess 1.x the solution?

enkessler/childprocess#134

[soapy1]

Hey there,
thanks for submitting this issue. I've tried to recreate this on a windows 10 machine with no success. It seems like there is some extra support for language encodings that aren't available on windows 8. Closing this issue but if this is still a problem or updating to windows 10 does not resolve this please open a new issue.

[ghost]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.