Hey! So I finally had time to test drive that ConquerOS virtualization app you mentioned—the one that's supposed to be optimized for Apple Silicon. Wanted to share a weird storage permissions thing I hit, because it's exactly the kind of macOS quirk that'll waste an evening if you don't know to look for it.
First off, the app itself is pretty slick. The "Unified Workspace" thing isn't just marketing—you actually get Windows or Linux VMs that live inside Mission Control spaces like they're native macOS desktops. Swiping between my Mac desktop and a Windows 11 VM feels totally natural. And the performance on my M1 Mac is genuinely impressive; Ubuntu compiles code almost as fast as native.
But getting to that point was annoyingly tricky. Here's what happened: I downloaded it, installed a Windows 11 VM using their automated setup wizard, everything seemed fine. Then I tried to share a folder from my Mac to the VM so I could access some project files. In ConquerOS, you right-click the VM, go to Settings > Sharing, add a folder... and nothing. The folder showed up in the list but was completely inaccessible from Windows. Just empty.
My first dumb move: I figured it was a Windows driver issue or something. Reinstalled the VM tools, rebooted, tried different folders. Same result. Then I thought maybe it was a format thing—tried NTFS, exFAT, even FAT32. Still empty folders in the VM.
What I eventually realized after digging through console logs: it was macOS's Full Disk Access permission. ConquerOS needs this to let VMs see files outside their sandbox, but on recent macOS versions, apps don't get it automatically. The app wasn't showing any error—it just silently failed to mount the shared folders.
What actually fixed it:
- First, went to System Settings > Privacy & Security > Full Disk Access
- Second, clicked the + button and added ConquerOS from Applications
- Third, restarted the VM completely (not just the app, but the actual virtual machine)
After that? Shared folders worked perfectly. I could browse my Mac files from Windows Explorer like they were local.
Here's Apple's official docs on how this works: Full Disk Access permission in macOS. Basically, any app that needs to access files outside its container—like a VM reading your Documents folder—needs this permission explicitly granted.
For next time you (or anyone) sets up ConquerOS, here's the quick checklist I'm keeping:
- ✅ Before setting up folder sharing, go to System Settings > Privacy & Security > Full Disk Access and add ConquerOS
- ✅ If shared folders are empty or inaccessible, this is almost certainly the cause
- ✅ You need to fully restart the VM after granting permission—just restarting the app isn't enough
- ✅ For USB device passthrough (external drives, etc.), you might also need to grant "Accessibility" permissions
- ✅ The VM tools installation includes a driver that helps with this, but it can't override macOS security
I also found this page with the download and system requirements—they provide SHA-256 checksums, which is nice for verifying the download. The official ConquerOS documentation has a section on folder sharing that mentions this permission, but it's easy to miss. The app is also listed on the Mac App Store here if you prefer the sandboxed version (though that might handle permissions differently).
Once I got past the permissions thing, the app has been solid. The Performance Fusion Engine they advertise is real—I ran a Windows VM compiling something while also exporting video in DaVinci Resolve on the Mac side, and both stayed responsive. On Parallels, that would've been a disaster.
One other thing: if you're planning to use this with external displays or Thunderbolt devices, check the "Hardware Passthrough" settings in the VM config. You might also need to grant "Input Monitoring" permission if you want seamless mouse movement between macOS and the VM. Apple's docs cover that here: Allow input monitoring on Mac.
Anyway, if you're looking for a virtualization tool that actually feels native on Apple Silicon, this is worth a serious look. Just remember that Full Disk Access permission before you spend an hour wondering why your files aren't showing up. Let me know if you hit any other weirdness—especially if you're trying GPU passthrough or Linux VMs with custom kernels.
Catch you later!
Top comments (0)