crc: [BUG] Starting CRC (1.6) hangs on Ryzen CPU due to LUKS encryption

General information

• OS: Windows
• Hypervisor: Hyper-V
• Did you run crc setup before starting it (Yes/No)?

CRC version

crc version: 1.6.0+8ef676f
OpenShift version: 4.3.0 (embedded in binary)

CRC status

Machine 'crc' does not exist. Use 'crc start' to create it.

CRC config

<empty>

Host Operating System

OS Name:                   Microsoft Windows 10 Pro
OS Version:                10.0.18363 N/A Build 18363
OS Manufacturer:           Microsoft Corporation
OS Configuration:          Standalone Workstation
OS Build Type:             Multiprocessor Free

Steps to reproduce

1. install 1.5
2. crc stop
3. crc delete
4. delete .crc dir
5. install crc 1.6
6. crc setup
7. crc start -n 1.1.1.1 --log-level debug

No Idea what is wrong with 1.6. Also Tried:

• Disable Hyper-V and remove Hyper-V network adapter
• total network reconfigure with netcfg -d
• disabled a lot of running background processes
• disabled windows 10 firewall
• installed all windows 10 update
• total refresh install of windows 10

Unfortunately without any positive results.

Ended up with running CRC 1.5 again. Runs without problems out of the box

Expected

Crc to startup

Actual

Keeps saying 
 C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe -NoProfile -NonInteractive ( Hyper-V\Get-VM crc ).state
(crc) DBG | [stdout =====>] : Running
(crc) DBG |
(crc) DBG | [stderr =====>] :

With 1.5 the admin question pop up if you trust the network command shell

I also got a different system Windows 10 system (same version) where I can not reproduce it.

EDIT

It is a bug for the Ryzen CPU family. See:

https://bugzilla.redhat.com/show_bug.cgi?id=1806532

EDIT 2 + Solution

Solved by updating the BIOS. See: https://github.com/code-ready/crc/issues/1035#issuecomment-592410871