You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I'm working on a Windows10-1909-corporate-pc, where system policies are strict and administrative access is restricted: The install script pyenv-win/libexec/pyenv-install.vbs fails on line 115 at If objfs.FileExists(msi) Then objfs.DeleteFile msi.
If I comment out this single line, everything works as expected. (Besides not deleting the install-file of course).
Unfortunately I don't know what policy exactly is blocking the deletion of the object. I'm still running pyenv as a local admin though.
In my point of view pyenv should also run completely without any administrative privileges. Maybe there is another way of using the installPaths or something is wrong with the file permissions.
Proposal: Having a try, catch/except around that line and issue a message when failed, would fix the problem. (Ok, it's a more or less dirty workaround). On old vb-versions an On Error Resume Next might help, but I'm in no way proficient in vb-scripts :-)
Regards,
The text was updated successfully, but these errors were encountered:
When I'm working on a Windows10-1909-corporate-pc, where system policies are strict and administrative access is restricted: The install script
pyenv-win/libexec/pyenv-install.vbs
fails on line 115 atIf objfs.FileExists(msi) Then objfs.DeleteFile msi
.If I comment out this single line, everything works as expected. (Besides not deleting the install-file of course).
Unfortunately I don't know what policy exactly is blocking the deletion of the object. I'm still running pyenv as a local admin though.
In my point of view pyenv should also run completely without any administrative privileges. Maybe there is another way of using the installPaths or something is wrong with the file permissions.
Proposal: Having a try, catch/except around that line and issue a message when failed, would fix the problem. (Ok, it's a more or less dirty workaround). On old vb-versions an
On Error Resume Next
might help, but I'm in no way proficient in vb-scripts :-)Regards,
The text was updated successfully, but these errors were encountered: