Digest initialization failed: initialization error when running vagrant up

[UsamaKhan]

I am getting an error when running vagrant up using the prepackaged 2022 box.

Command output:

$ vagrant up --provider virtualbox 2022-box
Bringing machine '2022-box' up with 'virtualbox' provider...
==> 2022-box: Preparing master VM for linked clones...
    2022-box: This is a one time operation. Once the master VM is prepared,
    2022-box: it will be used as a base for linked clones, making the creation
    2022-box: of new VMs take milliseconds on a modern system.
==> 2022-box: Importing base box 'StefanScherer/windows_2022_docker'...
==> 2022-box: Cloning VM...
==> 2022-box: Matching MAC address for NAT networking...
==> 2022-box: Checking if box 'StefanScherer/windows_2022_docker' version '2022.06.10' is up to date...
==> 2022-box: Setting the name of the VM: windows-docker-machine_2022-box_1687182170828_40583
==> 2022-box: Clearing any previously set network interfaces...
==> 2022-box: Preparing network interfaces based on configuration...
    2022-box: Adapter 1: nat
    2022-box: Adapter 2: hostonly
==> 2022-box: Forwarding ports...
    2022-box: 3389 (guest) => 3389 (host) (adapter 1)
    2022-box: 5985 (guest) => 55985 (host) (adapter 1)
    2022-box: 5986 (guest) => 55986 (host) (adapter 1)
    2022-box: 22 (guest) => 2222 (host) (adapter 1)
==> 2022-box: Running 'pre-boot' VM customizations...
==> 2022-box: Booting VM...
==> 2022-box: Waiting for machine to boot. This may take a few minutes...
    2022-box: WinRM address: 127.0.0.1:55985
    2022-box: WinRM username: vagrant
    2022-box: WinRM execution_time_limit: PT2H
    2022-box: WinRM transport: negotiate
An error occurred executing a remote WinRM command.

Shell: Cmd
Command: hostname
Message: Digest initialization failed: initialization error

System: macOS Ventura 13.4 (22F66)
Vagrant: 2.3.7

[ltullman]

Getting the same error. Vagrant 2.3.7, VB 7.0.8, macOS 13.4

[ltullman]

I ended up downgrading vagrant to 2.3.4 hashicorp version and it seems to be getting past the error. Installer is here:https://releases.hashicorp.com/vagrant/2.3.4/

[UsamaKhan]

Looks like downgrading to 2.3.4 solved it for me as well. @StefanScherer it may be beneficial to add a tested on version for vagrant in the readme.

[craftydomops]

Downgrading vagrant to version 2.3.4 also worked for me.

[JunielKatarn]

Downgraded vagrant to version 2.3.4 from 2.3.7 fixed the error.