zed-industries/zed · error
failed to initialize Windows platform
Error message
failed to initialize Windows platform
What it means
current_platform constructs the OS backend; on Windows, WindowsPlatform::new failure (window class registration, DirectWrite/D3D initialization, etc.) is unwrapped since the app cannot run without a platform. The expect surfaces the backend's initialization error at startup.
Source
Thrown at crates/gpui_platform/src/gpui_platform.rs:67
/// Call this before running the application in a wasm_bindgen entrypoint.
#[cfg(target_family = "wasm")]
pub fn web_init() {
console_error_panic_hook::set_once();
gpui_web::init_logging();
}
/// Returns the default [`Platform`] for the current OS.
pub fn current_platform(headless: bool) -> Rc<dyn Platform> {
#[cfg(target_os = "macos")]
{
Rc::new(gpui_macos::MacPlatform::new(headless))
}
#[cfg(target_os = "windows")]
{
Rc::new(
gpui_windows::WindowsPlatform::new(headless)
.expect("failed to initialize Windows platform"),
)
}
#[cfg(any(target_os = "linux", target_os = "freebsd"))]
{
gpui_linux::current_platform(headless)
}
#[cfg(target_family = "wasm")]
{
let _ = headless;
Rc::new(gpui_web::WebPlatform::new(true))
}
}
/// Returns a new [`HeadlessRenderer`] for the current platform, if available.
#[cfg(feature = "test-support")]
pub fn current_headless_renderer() -> Option<Box<dyn gpui::PlatformHeadlessRenderer>> {View on GitHub (pinned to f4178619ac)
Solutions
- Check the inner WindowsPlatform error log for the failing subsystem (D3D device, DirectWrite, window class)
- Verify GPU drivers and DirectX runtime are installed and current
- Run on a supported Windows version with a working desktop session
Defensive patterns
Strategy: fallback
When it happens
Trigger: Thrown at crates/gpui_platform/src/gpui_platform.rs:67 when the library encounters an invalid state.
Common situations: See trigger scenarios.
AI-assisted analysis of zed-industries/zed@f4178619ac (2026-08-20).
Data as JSON: /api/errors/ac9a8edffc477586.
Report an issue: GitHub.