-
Notifications
You must be signed in to change notification settings - Fork 26
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
Auto start not working #175
Comments
Same issue here, it does not auto start, even with the pull request installed |
Win 10 here. What is described above is how it started for me. Then I discovered that I did not have the aerial.scv on my system (don't know how that happened). Got it, right-clicked and Installed, but it still won't run. When I come back to the PC, I get a blue screen (NOT the BSOD, just a blue screen) that I have to Ctrl-Alt-Del to get out of, and that brings me back to the Lock Screen. I did try to un-and-re-install, but same results. Just added this here because it was the closest description, and I'm sure I did something on my end to mess it up. I have a laptop on Win 10 with a fresh Win 10 install that it works flawlessly on. So, yeah, I'm sure I messed something up. |
TEMPORARY WORKAROUND BELOW I tried installing the aerial.scv as I thought it was it but nothing changed and other troubleshoots changed nothing again. All of those conditions are perfect for me, if you want to you can change them I guess. I don't understand enough of AHK so when you see |
I have Aerial set to run on startup, but it does not do so (successfully). Maybe it's trying and failing?
I also have it set to auto-start after 5 minutes but it does not do so.
I have manually run Aerial, then I have to manually start the screensaver from the Windows system tray.
I'm running the newest version of Aerial, and the most current windows 11 pro. This has been consistent over the last few / six months at least?
There was a windows update around mid-year (I think?) that broke some other stuff; maybe Aerial was affected?
The text was updated successfully, but these errors were encountered: