Heroku CLI hangs on Windows 10

Question

I use Heroku CLI on Windows 10. The first day after installing it works just fine, but on the next day (or so) it just hangs after launch:

C:\Users\{User}>heroku

and that's all. No output to console, no logs (no error.log). It lasts forever (not 120 sec like here: Heroku CLI Unresponsive)

I reinstalled CLI on 10.10.2017. Today is 14.10, my folder contains the following files: folder view before cleaning The autoupdate.log contains:

[2017-10-10T13:36:14+03:00] starting `C:\Program Files (x86)\Heroku\bin\\heroku.cmd update --autoupdate` from
heroku-cli: Updating CLI... already on latest version: 6.14.34-1fcf80e
heroku-cli: Updating plugins... done
[2017-10-11T22:36:40+03:00] starting `C:\Program Files (x86)\Heroku\bin\\heroku.cmd update --autoupdate` from logs
heroku-cli: Updating CLI... already on latest version: 6.14.34-1fcf80e
heroku-cli: Updating plugins... Waiting for all commands to finish
heroku-cli: Updating plugins... done
[2017-10-14T01:13:34+03:00] starting `C:\Program Files (x86)\Heroku\bin\\heroku.cmd update --autoupdate` from logs
heroku-cli: Updating CLI... already on latest version: 6.14.34-1fcf80e
heroku-cli: Updating plugins... Waiting for all commands to finish

What have I tried:

• uninstall and install again - this one works, but I don`t want to do this every day
• running as administrator
• waiting all night long
• using different commands (heroku --version, heroku update etc)
• delete folder ..\AppData\Local\heroku

After deleting the folder and running command 'heroku update' the following files & folders were created, but console still hangs: folder view after cleaning

The autoupdate.log consists now of 1 line:

[2017-10-14T19:39:02+03:00] starting `C:\Program Files (x86)\Heroku\bin\\heroku.cmd update --autoupdate` from update

I waited for an hour since and now writing this question here. Has anyone faced such an issue? What can be done?

Update Finally I made it work after a few days by reinstalling CLI several times and deleting the autoupdate files, but cannot say precisely which of my actions had true effect. If you face the same issue you can start with the Malik`s answer.

Answer 1

I encountered the same problem when I run $ heroku login on GitBash for Windows.

I tried the accepted answer above but to no avail. What solved it was just to use Windows Command Prompt instead of GitBash and all problems were solved.

I'm just adding this answer here in case someone has done the same thing like I did.

Answer 2

Using GitCMD instead of GitBash solved the problem for me.