Add another one to the list-
If these updates invalidate old clones each time Pro is upgraded, it is going to be a pain to keep rebuilding them each time. Especially if you have specific environments for processes and can't remember what packages you have installed in them... being able to rename the clones at the time of cloning would be a lot better than the default clone1, clone2 etc... add the option to export the env to a yml or something that the users can use to rebuild the env's when needed, without having to go through conda to do so.
Running as administer didn't work- my pkg folder is empty with exception of cache. Still get the failed to clone env error:
ERROR conda.core.link:_execute_actions(337): An error occurred while installing package 'defaults::ipykernel-5.1.2-py36h39e3cac_0'.
LinkError: post-link script failed for package defaults::ipykernel-5.1.2-py36h39e3cac_0
running your command again with `-v` will provide additional information
location of failed script: C:\Users\Mine\AppData\Local\ESRI\conda\envs\arcgispro-py3-clone1\Scripts\.ipykernel-post-link.bat
==> script messages <==
<None>
Attempting to roll back.
LinkError: post-link script failed for package defaults::ipykernel-5.1.2-py36h39e3cac_0
running your command again with `-v` will provide additional information
location of failed script: C:\Users\Mine\AppData\Local\ESRI\conda\envs\arcgispro-py3-clone1\Scripts\.ipykernel-post-link.bat
==> script messages <==
<None>
