crc: Can't install on Windows 10. Stuck on 'Please reboot your system and run 'crc setup' to complete the setup process'

CRC version: 2.6.0+e7251680 OpenShift version: 4.10.22 Podman version: 4.1.0

Windows Build: 21H2 (Build 19044.1826)

After rebooting, I get the installer, after entering the pull secret I get an error without any more details than “reboot again”. This repeatedly happens on reboot.

2022-08-02 15_08_44-Red Hat OpenShift Local

Running crc setup from admin powershell after reboot also does not change anything.

About this issue

  • Original URL
  • State: open
  • Created 4 years ago
  • Comments: 19 (10 by maintainers)

Most upvoted comments

I got a similar issue and I found out that crc using the USERNAME env variable to resolve the Group membership. In my case I got a domain user but USERNAME only contains the USER part and the domain was in a USERDOMAIN env variable. After setting the env variable USERNAME=%USERDOMAIN%%USERNAME% before starting crc setup and crc start, this solved my problem: crc found the hyper-v group membership and all went well.

I had the same issue, the domain name was not taken into account in the pre-flight check, but the user is indeed correctly in the group membership. I could solve it by bypassing the pre-flight check: crc config set skip-check-user-in-crc-users-and-hyperv-admins-group true

This is still an issue in

PS C:\Program Files\Red Hat OpenShift Local> crc version
CRC version: 2.30.0+b6532a
OpenShift version: 4.14.3
Podman version: 4.4.4

(W10 Pro witch active SVM and Hypervisor-V)

Had to do the same "crc config set … " trick as mentioned before and voila, for the first time a saw the “downloading” part.

PS C:\Program Files\Red Hat OpenShift Local> crc config set skip-check-user-in-crc-users-and-hyperv-admins-group true
Successfully configured skip-check-user-in-crc-users-and-hyperv-admins-group to true
PS C:\Program Files\Red Hat OpenShift Local> crc setup
INFO Using bundle path C:\Users\h5\.crc\cache\crc_hyperv_4.14.3_amd64.crcbundle
INFO Checking minimum RAM requirements
INFO Checking if current user is in crc-users and Hyper-V admins group
WARN Skipping above check...
INFO Checking if CRC bundle is extracted in '$HOME/.crc'
INFO Checking if C:\Users\h5\.crc\cache\crc_hyperv_4.14.3_amd64.crcbundle exists
INFO Getting bundle for the CRC executable
INFO Downloading bundle: C:\Users\h5\.crc\cache\crc_hyperv_4.14.3_amd64.crcbundle...
330.50 MiB / 4.35 GiB [---------------->___________________________________________________________________________________________________________________________________________________________________________________________________________________] 7.42% 38.86 MiB/s

I got a similar issue and I found out that crc using the USERNAME env variable to resolve the Group membership. In my case I got a domain user but USERNAME only contains the USER part and the domain was in a USERDOMAIN env variable. After setting the env variable USERNAME=%USERDOMAIN%%USERNAME% before starting crc setup and crc start, this solved my problem: crc found the hyper-v group membership and all went well.

I had the same issue, the domain name was not taken into account in the pre-flight check, but the user is indeed correctly in the group membership. I could solve it by bypassing the pre-flight check: crc config set skip-check-user-in-crc-users-and-hyperv-admins-group true