[Bug]: graphics_capture example panics with HRESULT 0x800401FD (Object is not connected to server)

[Atliac]

Describe the bug 🐛
When running the provided graphics_capture example using v2.0.0-alpha.7 (main branch), the application panics with a Windows API error.

The error message is:
Screen capture failed: GraphicsCaptureApiError(WindowsError(Error { code: HRESULT(0x800401FD), message: "Object is not connected to server" }))

This occurs at line 122 in examples\graphics_capture.rs.

Expected behavior 📝
The example should initialize the Graphics Capture API, start a capture session, and run without crashing.

OS 🤖

• Version: [e.g. 10]
• Build[e.g. 22H2]

Additional context ➕

cargo run --example graphics_capture
    Finished `dev` profile [unoptimized + debuginfo] target(s) in 0.14s
     Running `target\debug\examples\graphics_capture.exe`

thread 'main' (15604) panicked at examples\graphics_capture.rs:122:30:
Screen capture failed: GraphicsCaptureApiError(WindowsError(Error { code: HRESULT(0x800401FD), message: "Object is not connected to server" }))

[Lolotronop]

One of my "users" is having the same issue
Works fine on windows 11 24H2 (my main dev machine) and whatever my laptop is running on, probably a version prior
Broken on windows 10 22H2
v2.0.0-alpha.7

[Lolotronop]

After some debugging I found that it fails on this line with the item.Size()? call, not even getting to the Direct3D11CaptureFramePool::Create call

windows-capture/src/graphics_capture_api.rs

Line 179 in 38ea964

let frame_pool = Direct3D11CaptureFramePool::Create(&direct3d_device, pixel_format, 1, item.Size()?)?;

I will try to investigate why that happens, but most likely that is beyond my virtually non-existent windows API knowledge

[Lolotronop]

This only happens if you use the PickedGraphicsCaptureItem directly from the GraphicsCapturePicker::pick_item() on windows 10
The Window and Monitor structs work fine as items provided to Settings, e.g. with Window::from_contains_name
So this is a bug with how PickedGraphicsCaptureItem handles being transferred from the GraphicsCapturePicker to GraphicsCaptureApiHandler. Why that is the case exactly - I don't know, some Windows threading/context shenanigans, probably

For the time being, I'm using this abomination as a workaround. This doesn't handle the case for All displays, but that's fine for me

let picked = GraphicsCapturePicker::pick_item().unwrap().unwrap();
let name = picked.item.DisplayName().unwrap().to_string();
if let Ok(window) = Window::from_contains_name(&name) {
    Capture::start(Settings::new(
        window,
        CursorCaptureSettings::Default,
        DrawBorderSettings::Default,
        SecondaryWindowSettings::Default,
        MinimumUpdateIntervalSettings::Default,
        DirtyRegionSettings::Default,
        ColorFormat::Rgba8,
        flags,
    ))
    .expect("Screen capture failed");
} else if name.contains("Display") {
    if let Ok(display_numbr) = name.split("Display").collect::<Vec<&str>>()[1].parse::<u32>() {
        if let Ok(display) = Monitor::from_index(display_numbr as usize - 1) {
            Capture::start(Settings::new(
                display,
                CursorCaptureSettings::Default,
                DrawBorderSettings::Default,
                SecondaryWindowSettings::Default,
                MinimumUpdateIntervalSettings::Default,
                DirtyRegionSettings::Default,
                ColorFormat::Rgba8,
                flags,
            ))
            .expect("Screen capture failed");
        }
    }
}