Skip to content
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

General instability problems on Windows 11 #40

Open
moghingold opened this issue Dec 18, 2024 · 1 comment
Open

General instability problems on Windows 11 #40

moghingold opened this issue Dec 18, 2024 · 1 comment

Comments

@moghingold
Copy link

OS: Windows 11 Enterprise
Version: 23H2
Build: 22631.4460

After installing Accessibility Viewer successfully, it is very unstable. Every single action I try to perform with it -- opening it, moving its window, resizing its window, activating it, etc, all actions cause the application to become unresponsive. If only performing exactly one action, leaving the application unattended for some time (longer than 30 seconds, less than 5 minutes) will eventually let it get itself un-stuck, so it is technically still usable, but only with tremendous patience and willingness to ignore its instability and the limits that puts on on its use.

As an aside, are there any command line options I can add to the shortcut that will enable logs or anything like that, so that I can provide you with more useful information than "it's unresponsive and unstable"?

Thank you in advance if you are able to look into this. I find aViewer to be an irreplaceable application and am currently trying to get its use approved company-wide by my employer's product intake team. Knowing that the latest version works reliably on the latest major Windows release would make that case far easier to make.

@moghingold
Copy link
Author

Per testing by @playmer, the blob in the Develop branch does not exhibit the instability of the release version. However, I am unable to install it on a work-approved machine because it is automatically blocked by Windows Smart Scan (presumably due to not being a signed release?)

If a new release could be prepared that fixes compatibility with Windows 7 and up, I would be very grateful for your attention to this matter, especially seeing as the required code changes have evidently already been completed.

Thank you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant