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
Unable to launch GCS on Windows 11 Pro #799
Comments
Three possibilities:
For number 1, upgrading your video drivers may help. If OpenGL 3.2+ is definitely supported, then a reboot can often clear things up. For number 2, assuming you can't locate it in the Task Manager to kill it for some reason, a reboot of your system will flush it out. For number 3, checking the GCS log file for any errors reported and then sending that info to me to examine would be helpful. |
|
Logfile attached, tho, this is complainging about timeouts hitting Github... |
OK, one other thing that this reminded me of... on Windows only, I've seen a strong correlation between machines that have this problem and those that report a failure to communicate with GitHub in the logs. What's weird is that it only seems to occur on Windows machines, and only a subset of them. Neither Linux nor macOS have any problem with that particular failure -- and the code certainly indicates that none of them should. Anyway, two things have fixed this for previous people that had the problem:
If neither of those help but you're still seeing the failure to communicate with GitHub, try fixing that issue (i.e. some vpn software will cause this, so turning off the vpn stops the failure). For some cases, doing that magically fixed the issue. None of this should be needed. The code in question runs on a background thread and the rest of the code doesn't care if it ever completes or not... why a failure to connect with GitHub is causing the failure on a small subset of Windows machines (and none of the Windows machines I have access to) is still a mystery to me. I'll continue to look for the actual cause, but it has been eluding me for a very long time now, so I'm not optimistic. |
I have this issue, too: Edit: PS - My desktop PC setup is roughly:
|
PS |
It shouldn't -- and certainly doesn't on any other platform. So far, I've been unable to find a reason to explain the behavior that is exhibited on some Windows machines. |
My logfile repeats over and over:
So the updater before the actual app launch failed critically? Strange, to have working a browser for github.com, but not an automated call to api.github.com route in the same timeframe. |
While that is indeed an error, it isn't a fatal one. GCS will just continue on, as that check is done in the background. It can fail for a number of reasons, the two most common being you don't have network access or you have turned on a VPN and it is preventing access to github. Regardless, that shouldn't actually be an issue -- but I have had a few scattered reports that fixing the network issue also fixes the weird launch problem on Windows. I can't confirm, as I can't replicate the problem. |
Application executes and appears in task manager but does not present either its window, nor does it appear on the Taskbar. I'm using the -s and -l switches to point both at my google drive instance. Works fine on my Microsoft Surface running Windows 10, but no love on my desktop (Win11 pro) from the same location, using the same .json settings.
The text was updated successfully, but these errors were encountered: