Support

OpenHuizeBox is maintained as an open-source alpha project. Response times are best-effort; there is no paid support tier and no SLA. What there is: a structured triage process and a set of known issues with published fixes.

Is your question already answered?

Before filing a report, skim the FAQ — it covers what OpenHuizeBox is, who it's for, whether it needs a kernel driver, what platforms work, whether it phones home, and what detector coverage to expect.

Before filing a report

Confirm you are on the latest alpha release — Help → About should read v0.1.0-alpha.localN · base VirtualBox 7.2.7.
Reproduce with a fresh VM derived from a known profile. dell_optiplex_7080.json is the baseline.
Attach VBox.log, Host.log, and the output of VBoxManage showvminfo <vm> --machinereadable.
If the issue is a driver / signing / boot problem, also attach the relevant entries from Event Viewer → Windows Logs → System for VBoxSup or CodeIntegrity.

Where to report

Bugs, regressions, packaging: GitHub issues — github.com/zhihuiyuze/OpenHuizeBox/issues. Use the Bug report template.
Feature requests: GitHub issues, Feature request template. Please read governance first — requests whose primary applicability is out-of-scope are closed without discussion.
Security advisories: GitHub → Security → Advisories (shortcut) for private disclosure. Do not post security-sensitive reports in the public issue tracker.
Governance & scope disputes: GitHub issue tagged governance, or email zhihuiyuze@gmail.com with subject prefix [GOVERNANCE].

Triage and response times

Severity	Initial acknowledgement (best effort)
Security (high)	≤ 72 hours
Build failure	≤ 1 week
Bug	≤ 2 weeks
Feature request	next sprint retro (monthly)
Governance	≤ 2 weeks, or cross-referenced in the next release notes

Known issues & gotchas

VBoxSup won't start, error 183 (ERROR_ALREADY_EXISTS). Another VBox-family driver is still registered. sc stop <name> and sc delete <name> for the conflicting service, reboot, retry. The installer's orphan-driver scan handles known names automatically.
VM power-on fails with VERR_LDR_IMAGE_HASH. A ring-0 module wasn't signed with the same CA as VBoxSup.sys. Re-run build\install_ohb_driver.ps1 — it signs every *.r0 alongside the driver.
“Cannot resolve VM name” when applying a profile. You opened Settings from File → Preferences (the global dialog) rather than from an existing VM. Close, right-click a VM and pick Settings.
Windows file properties still show Oracle strings. A source build was started without wiping *.res. Run build\local_build.ps1 -Clean, or file a bug with the RC log attached.
Smart App Control blocks the installer. Temporarily disable Smart App Control in Windows Security during install, or wait for the EV-cert / Microsoft-attested build (planned 0.5.0).

Community

There is no official chat channel. Technical discussion happens on GitHub Discussions. Commercial / support-contract inquiries are out of scope for now — this is a research project, not a product.