On Wed May 14 15:39:02 2025 +0000, Alfred Agrell wrote:
I think it's more likely to be a STATUS_BUFFER_OVERFLOW than the weirdo mac name, though both feel fairly farfetched to me. Maybe the best solution is what Jinoh is saying, simply skip the guesswork and keep it as a plain old integer. And yes, we usually use broken() for strange behaviors that changed in newer Windows.
Regardless, IMO it's clear their intention was to return an `E_POINTER`, as evidenced in the Windows 11 test.
I don't think `broken()` is appropriate here. It's usually used when a small percentage of VMs differ in their behavior and the test fails as a result. In this case, all the Windows 10 VMs that support `CreateDispatcherQueueController()` return this specific `HRESULT`.
Changing the comment to `win10 22h2` is fine by me if @rbernon approves.