PyCharm installer 2017.3 Community/Professional not working

Answered

The installer is unable to continue after the location prompt. However, no error is shown and you cannot cancel the installation.



Note that the instruction at the top changes but not the UI. The same behavior is present when starting as admin. No directories are created but the JetBrains directory is already created because WebStorm is installed.

Windows 10 Pro 64bit (10.0.16299)

9 comments

Please try to re-install PyCharm from https://www.jetbrains.com/pycharm/download/. Does the problem remain?

0

Yes, the problem remained.
Installing from cmd with /S worked.

0

After a windows reinstall the problem was not present anymore

0

The same problem happened to me.

 

0

Hi Zhan410,

Have you tried above solutions? What's the result?

0

I have come across this problem as well. I even tried navigating to the folder where the installer was in cmd just as Drunken3agle said worked for him, but did not work for me.
Then, out of curiosity, I just tried running the installer as administrator by right-clicking the installer. That worked! I hope this helps others too, until the issue is resolved.

0

When you run the installer, normally the Windows should ask if you want to allow the installer to make changes to your device. However some Windows systems are configured to decline this request by default. In that case running as administrator explicitly will be a solution.

0

Not in my case, Andrey. I have UAC, AV and everything else configured to allow me to make changes however I like. On top of that, I have "developer mode" enabled, while that may not have any play in it... So that being said, I don't believe that it has anything to do with anyone's system, but rather just a problem with the installer itself. But, I'm no expert, so perhaps there's something I missed, but as far as I'm aware, I haven't missed anything...

0

Understood. However, so far I wasn't able to reproduce the issue on Windows 10. If running as Administrator explicitly is working for you, this is definitely a permission issue. I would suggest to check the Windows security logs and monitor for the events while you reproduce the issue.

0

Please sign in to leave a comment.