Vagrant up won't start?

Question

Windows

Windows 10 PRO, CPU virtualization is enabled in BIOS settings, OS username = "Name", Cyrillic.
I looked at a bunch of guides, they write the same everywhere, here is an example https://www.sitepoint.com/getting-started-vagrant-... , installed VirtualBox , created a folder on the disk, went there via CMD , vagrant init files were created, vagrant init ubuntu/trusty64 installed, now vagrant up

D:\sandbox\vagrant>cd D:\Vagrant

D:\Vagrant>vagrant init
`Vagrantfile` already exists in this directory. Remove it before
running `vagrant init`.

D:\Vagrant>vagrant init ubuntu/trusty64
`Vagrantfile` already exists in this directory. Remove it before
running `vagrant init`.

D:\Vagrant>vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Importing base box 'ubuntu/trusty64'...
D:/Soft/Vagrant/embedded/gems/gems/childprocess-0.6.3/lib/childprocess/windows/process_builder.rb:43:in `join': incompatible character encodings: Windows-1251 and UTF-8 (Encoding::CompatibilityError)
        from D:/Soft/Vagrant/embedded/gems/gems/childprocess-0.6.3/lib/childprocess/windows/process_builder.rb:43:in 
     .... куча текста подобного
        from D:/Soft/Vagrant/embedded/gems/gems/vagrant-1.9.8/lib/vagrant/batch_action.rb:82:in `block (2 levels) in run'

ERROR
in console:

D:\Vagrant>vagrant ssh
VM must be created before running this command. Run `vagrant up` first.

Please tell me how is it right?
I also tried: https://habrahabr.ru/post/251529/
I completed the vagrant up item, everything was installed, the console closed, then I opened it again, and registered vagrant up again in the .homestead folder, knocked out a lot of text

....
   from D:/Sandbox/Vagrant/embedded/gems/gems/vagrant-1.9.8/lib/vagrant/action/runner.rb:66:in `block in run'
        from D:/Sandbox/Vagrant/embedded/gems/gems/vagrant-1.9.8/lib/vagrant/util/busy.rb:19:in `busy'
...

Then I try to go through Putty, which I also set up according to the guide, gives an ERROR :
Network error: Connection Refused!

Answer 1

Reinstalling Windows 10 with the English language pack without any junk from the off site - helped. The problem was related to Cyrillic in the paths. Editing the registry and creating an additional user did not help.

Answer 2

It's probably too late, but still, we managed to start it on ru Windows, in VirtualBox we set the default path for creating machines by default (any), for example, I have D:\VirtualMachine.
VARGANT_HOME set to the same place as the path for VirtualBox, that is, D:\VirtualMachine
in CMD, before running commands, write chcp 1251