Timeout when starting git bash #59
Comments
I wonder, why users are trying to update protected location (ProgramFiles) with 7z package?? |
Well, ConEmu said there was a new update available and asked if I wanted to install it. I answered "yes". That's all I did. Should I not have updated? |
I mean, how ConEmu appeared first time in ProgramFiles? Yep, you've copied it there manually. But if the installer was used originally - it will be always used for updating. And in that case there will be no problems with elevating/demoting. And then, Windows task sheduler will not be used. And then, it will not show timeouts. The ConEmu task can't start in 20 seconds. Really? That is you've imformed about. |
I used ConEmuSetup.141221.exe to install ConEmu. Previous auto updates have worked just fine. |
If you are using installer for updating - then the sheduler must not be used. Describe all steps with screenshots to understand your situation. |
Can I downgrade to for example 150209 to make it detect the update to 150215 automatically again? Otherwise I'll try to remember to take screenshots next time you publish a new version of ConEmu But just to be clear, when updating I'm not doing anything manually, I'm just clicking OK/Next on a bunch of dialog boxes. I don't know what ConEmu downloads in the background or what it runs. |
Yep. Just now 150216 was released |
Just drop installer on the ConEmu tab bar |
What is the "bunch of dialogs automatically poped up and closed" like? Is that installer pages or not? |
I updated my previous post with more images OS is Win 8.1 64 bit |
Can reproduce with OS being Win 8.1 64bit - exact same thing as what is described in the post with the screenshots, ie just saying "yes" to automatic update and then follow the path... Now at 150218[64] and I've had the issue for the past few updates. In the EventLog, MsiInstaller reports that the install went fine. Once the alert windows have been closed everything seems to work OK. |
I don't even have to close the alert windows. Everything seems to work OK right away. |
That message is shown by non-interactive instance. So, there is almost no effect with interactive instance. |
I believe 150224 will fix that |
Looks good, just upgraded to 150224 and did not get the error. Thanks! |
Yesterday I got the 150209 update, and after that I got this error message:
Today I got the 150215 update, but I still get the same error
I get that dialog box twice, but after just clicking OK on both of them everything seems to work fine.
The text was updated successfully, but these errors were encountered: