-
Notifications
You must be signed in to change notification settings - Fork 49
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"Error: (0x80004002) No such interface supported" after updating Windows 11 (Beta insider channel) #51
Comments
I'm afraid I'm seeing the same issue: the latest update broke it 🤦 |
Yeah, I figured I could live with a few bugs in the beta program but didn't expect it would break something so crucial to my workflow! |
Broken here too. Since this update will be live for standard users of Windows 11 soon, I'd love to have it fixed. I'm using: |
I imagine this explains why the window moving feature doesn't work anymore. |
Looks like VirtualDesktop.cs has been updated, and VirtualDesktop11-23H2.cs should work, see VirtualDesktop/issues/67. I'm not sure how to do this, though, can you point me in the right direction and I can try to do a PR to test this |
This is as far as I got. Providing as a diff rather than a pull request because I'm not really prepared to go further (and I never actually forked the repo):
My usage of VD.ahk is limited to exactly four methods: getNameFromDesktopNum, goToDesktopNum, MoveWindowToDesktopNum, and getCurrentDesktopNum. This works for those methods. I have absolutely no idea if any of the others work or not with this change and have no reasonable means of testing. But maybe it'll help. Basically I started with "it looks like they changed a lot of the function params back to the way they had them in Win10" (based on staring very very hard at that VirtualDesktop.cs project code) and started trial-and-error switching to those instead. |
Updating another machine revealed that I was guessing the version numbers wrong. So I gave in and forked it. https://github.com/Viqsi/VD.ah2 |
Seems to be working for me (Win11 10.0.22631), super appreciate the efforts! |
It's not just the build number, it's the build revision as well; that's what makes this so annoying. 10.0.22631.2134 and earlier revisions are fine with the Old Ways, but 10.0.22631.2283 is not. I suspect the change happened with the preview release 10.0.22631.2215 (and that's what I checked for in the fork), but don't have actual confirmation of that as I don't do preview releases. |
Hmm, I did just see an update (in the Release Preview channel), so hopefully that doesn't complicate things. At any rate, I am on 10.22631.2361 now, and I believe VD stopped working for me on 10.0.22631.2050. |
Thanks @Viqsi! :) I've applied the update to _VD.ahk, basically the same diff but without the new |
Just a heads up to the others in this thread that the GUID for the COM has also changed with this months release. Fix in this PR #62 |
So far as I can tell this was resolved with 02f37bf. (The referenced commit above presumably fixed it for the AHKv1 version; this one fixes it for the v2 version). At least, I tested it and it Works For Me on build 22631.3155, so I've closed the PR from my fork and will be doing a pull shortly (read: as soon as I get around to it, if I get around to it ;) ). |
After getting served KB5028256, VD.ah2 no longer works. Line 37 throws "Error: (0x80004002) No such interface supported". I'm afraid I don't have the technical knowledge to do much digging, but I'll do what I can if provided direction.
The text was updated successfully, but these errors were encountered: