If crc is not creating a VM even after setup, and you’re using Windows 11 with Hyper-V, here’s how you can check the logs and troubleshoot the issue:
โ 1. View Detailed Logs from CRC
Run this command to get verbose debug logs:
crc start -l debug
or for even more detailed logging:
crc start --log-level debug
This will print detailed steps of what crc is doing, where it’s failing, and may show VM or Hyper-V issues.
โ 2. Check Log Files Manually
CRC stores logs in this location on Windows:
C:\Users\<your-username>\.crc\logs
Code language: HTML, XML (xml)
Check the latest folder in that directory for a file like:
crc.log
Code language: CSS (css)
You can open it in Notepad or any text editor to see detailed setup/start information.
โ 3. Confirm Prerequisites
Letโs double-check a few required things:
| Item | Check |
|---|---|
| โ Hyper-V installed | Run Get-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V-All in PowerShell |
| โ User is in Hyper-V Administrators Group | Run net localgroup "Hyper-V Administrators" |
| โ Virtualization Enabled in BIOS | Check from Task Manager โ Performance โ CPU |
| โ Installed CRC with Installer | Make sure you used the .msi installer, not just a ZIP |
If any of these aren’t properly configured, CRC won’t be able to start the VM.
โ 4. Manually Check Hyper-V VM
Check if a CRC VM was created but failed to start:
Get-VM
You may see something like crc listed. If it’s there but “Off” or in a failed state, try:
Start-VM -Name crc
And if that fails, get the error:
Get-VM -Name crc | Get-VMIntegrationService
โ 5. Clean Up and Retry (if needed)
If everything fails, you can try resetting and starting fresh:
crc cleanup
crc setup
crc start --log-level debug
Here is a Complete OpenShift Local (CRC) Troubleshooting Guide tailored for Windows (especially Windows 11), covering installation, VM, daemon, logs, and networking issues โ all in one place:
โ Complete OpenShift Local (CRC) Troubleshooting Guide for Windows
๐งฐ 1. Basic CRC Setup Checklist (Before Troubleshooting)
| Requirement | Notes |
|---|---|
| OS | Windows 10/11 Pro, Enterprise, or Education (Hyper-V required) |
| RAM | Minimum 9 GB free (16 GB total preferred) |
| Disk Space | At least 35 GB free |
| Virtualization | Must be enabled in BIOS |
| Hyper-V Installed | Required โ CRC won’t work with VirtualBox |
| Admin Rights | Must run CRC setup and start as Administrator |
| CRC Installed via MSI | Always use the official Windows .msi installer |
| Reboot Performed | After install โ mandatory |
๐ ๏ธ 2. Installation & Setup
โ Correct Installation Steps:
crc cleanup
crc setup
Always reboot after installation.
๐งช 3. Common Issues and Fixes
โ Issue 1: CRC Daemon Not Running
Error:
Is 'crc daemon' running? Cannot reach daemon API
Code language: JavaScript (javascript)
Fix:
# Open PowerShell as Admin
crc daemon
Code language: PHP (php)
Keep this terminal open while you run
crc startin another one.
โ Issue 2: No VM is created
Fix:
- Confirm virtualization:
Get-VM
- Retry clean setup:
crc cleanup
crc setup
crc daemon
crc start --log-level debug
โ Issue 3: Hyper-V Not Enabled
Fix: Run as Admin:
Enable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V -All
Then reboot.
โ Issue 4: Podman or oc not found
Fix: Check:
dir C:\Users\<your-user>\.crc\bin
Code language: HTML, XML (xml)
If missing, re-run:
crc setup
โ Issue 5: DNS/Networking Failures
Fix:
- Add
api.crc.testingand*.apps-crc.testingto hosts file:
notepad C:\Windows\System32\drivers\etc\hosts
Add:
192.168.130.11 api.crc.testing
192.168.130.11 console-openshift-console.apps-crc.testing
Code language: CSS (css)
Replace 192.168.130.11 with the output of:
crc ip
๐งพ 4. Useful CRC Commands
| Purpose | Command |
|---|---|
| Setup CRC | crc setup |
| Start cluster | crc start --log-level debug |
| Stop cluster | crc stop |
| Delete everything | crc delete |
| Cleanup cache/machines/logs | crc cleanup |
| Show status | crc status |
| Get CRC IP | crc ip |
| Open dashboard | crc console |
๐ 5. Log File Locations
Manual Log Inspection:
C:\Users\<your-user>\.crc\logs\crc.log
Code language: CSS (css)
Look for errors like:
- โVM creation failedโ
- โDaemon not reachableโ
- โFailed to mount diskโ
๐ฆ 6. Bundle File Missing or Corrupt
If crc shows:
Bundle not found: crc_hyperv_xxx.crcbundle
Code language: CSS (css)
Fix:
- Download bundle manually: https://developers.redhat.com/content-gateway/rest/mirror/pub/openshift-v4/clients/crc/latest/
- Place in:
C:\Users\<your-user>\.crc\cache
Code language: HTML, XML (xml)
๐ 7. Accessing the Cluster
- Run:
crc console
Code language: JavaScript (javascript)
- Login with:
- Username:
kubeadmin - Password: found at:
C:\Users\<your-user>\.crc\cache\...<bundle>\kubeadmin-password
- Username:
- Get
octool path:
crc oc-env
๐ก 8. Tips & Best Practices
| Tip |
|---|
Always run crc in PowerShell (Admin) |
Do not move .crcbundle file after setup |
| Avoid running CRC inside a VM |
| Check Windows Defender or antivirus โ it can block Hyper-V or crc.exe |
| Ensure enough free RAM + Disk Space |
๐ 9. When All Else Fails
- Update CRC to the latest version
- Re-download the bundle
- Reset:
crc delete
crc cleanup
Code language: JavaScript (javascript)
- Reboot
- Start again
I’m Rajesh Kumar, a DevOps, SRE, DevSecOps, Cloud, and Platform Engineering expert passionate about sharing practical knowledge, real-world experiences, and industry best practices. I have worked at Cotocus and regularly write about technology, travel, investing, health, product reviews, and digital marketing through my various platforms.
I publish technical articles at DevOps School, travel stories at Holiday Landmark, stock market insights at Stocks Mantra, health and fitness guidance at My Medic Plus, product reviews at TrueReviewNow, and SEO and digital marketing strategies at Wizbrand.
Find Trusted Cardiac Hospitals
Compare heart hospitals by city and services โ all in one place.
Explore Hospitals