I didn’t plan to write this. Honestly, I was just setting up a quick lab VM to test some remote management scripts. But halfway through the install, I hit a few snags that reminded me—this stuff isn’t as “plug and play” as the docs make it sound. So here’s my real-world walkthrough of getting Windows Server 2022 Core running on Hyper-V.
Why Server Core?
I’ve always preferred Core for lab environments. It’s lean, boots fast, and doesn’t nag me with GUI updates. Plus, it forces me to stay sharp with PowerShell. This time, I needed a nested Hyper-V setup to test some automation scripts. Server Core felt like the right call.
Running this on my daily driver: a ThinkPad P15 with 32GB RAM, 1TB SSD, and Windows 11 Pro. Hyper-V is enabled, and I’ve got a couple of external switches configured for VM networking.
My Setup:
- Grab the ISO
Downloaded the Windows Server 2022 ISO from Microsoft’s Evaluation Center. If you’ve done this before, you know the drill. Just make sure you’re not grabbing some outdated build from a mirror site—been burned by that before.
- Enable Hyper-V
I used Server Manager this time. Could’ve done it via PowerShell, but I was multitasking and didn’t want to mistype a flag.
Install-WindowsFeature -Name Hyper-V -IncludeManagementToolsRestarted the host. Hyper-V Manager popped up like it was waiting for me.
- Create the VM
In Hyper-V Manager:
- Generation 2 (UEFI boot)
- 4GB RAM (dynamic memory on)
- 60GB VHDX
- External switch for networking
I usually go with 80GB disks, but this was just a test box. If you’re planning to install roles later, don’t skimp on disk space.
- Mount the ISO
VM settings → SCSI Controller → DVD Drive → Add → Browse to ISO. Straightforward.
- Boot and Install
Started the VM. The screen stayed black for a good 20–30 seconds. Thought it froze. Then the setup screen appeared—finally.
Selected “Windows Server 2022 Core” and let it do its thing. No GUI, just the essentials.
- First Login
Logged in with the default Administrator account. No desktop, no Start menu—just a blinking cursor. Ran sconfig to set hostname, IP, and join domain. If you’ve never used sconfig, it’s like a Swiss Army knife for Core.
- Nested Hyper-V (Optional)
Wanted to test nested virtualization, so I installed Hyper-V inside the Core VM:
Install-WindowsFeature -Name Hyper-V -IncludeManagementToolsRestarted the VM. Created a test VM inside it—worked fine. Not blazing fast, but good enough for lab work.
What Tripped Me Up
- Boot delay: That black screen after starting the VM? Totally normal. But the first time, I thought the VM was bricked.
- Networking: Default switch is fine for internet, but for domain joins or static IPs, go with an external switch.
- Dynamic memory: Works well, but keep an eye on memory pressure if you’re nesting VMs.
Final Thoughts
Server Core isn’t for everyone. If you’re used to clicking through GUIs, it’ll feel like stepping into the Matrix. But once you get the hang of it, it’s fast, clean, and surprisingly powerful.
I’ve used this setup to test scripts, simulate production roles, and even run lightweight containers. If you’re experimenting with nested Hyper-V or just want a minimal server footprint, give Core a shot.
Ever tried running nested Hyper-V inside Server Core? Or hit a weird bug during setup? Drop a comment—I’d love to hear how others are using Core in their labs.
