You can post code snippets by wrapping them into three backticks ```, so I don’t think it’s a bug of the forum.
Please edit your post with the code formatting and it should display the raw output.
Based on the error message I guess you don’t have access rights in C:\Users\Sylvain ARD\.conda\envs\yolact\Scripts in order to execute the file.
I’m not familiar with the rights management of Windows, but maybe you could check the access rights of this folder in the explorer?
Are you able to install any other conda packages?
If not, it seems to be a conda/Windows issue and I would recommend to create an issue in their repository so that the devs can have a look at it.
I unzipped cudatoolkit archive and found .cudatoolkit-post-link.bat
this is its content :
rem post install EULA message; `pre-link.bat` does not show message and shows warning
echo "By downloading and using the CUDA Toolkit conda packages, you accept the terms and conditions of the CUDA End User License Agreement (EULA): https://docs.nvidia.com/cuda/eula/index.html" >> %PREFIX%\.messages.txt
%PREFIX% is not defined so it try to get message.txt from root of the disk and fail with access denied
I tried to set PREFIX in environment variables, that is the batch file works outside of anaconda without denied access but when I try to install cudatoolkit I have always a denied access, apparently anaconda redefine %PREFIX% for each environment and it is a bad value
rem post install EULA message; `pre-link.bat` does not show message and shows warning
echo "By downloading and using the CUDA Toolkit conda packages, you accept the terms and conditions of the CUDA End User License Agreement (EULA): https://docs.nvidia.com/cuda/eula/index.html" >> %PREFIX%\.messages.txt
by :
rem post install EULA message; `pre-link.bat` does not show message and shows warning
echo "By downloading and using the CUDA Toolkit conda packages, you accept the terms and conditions of the CUDA End User License Agreement (EULA): https://docs.nvidia.com/cuda/eula/index.html"
Good to hear you’ve solved the issue.
Since we are not directly supporting (and testing) the binaries with cudatoolkit=10.0, this might be an issue with these binaries in particular.