# Problem when using Pluto (UnauthorizedAccess on Windows)

**URL:** <https://discourse.julialang.org/t/problem-when-using-pluto-unauthorizedaccess-on-windows/109265>\
**Category:** Pluto\
**Tags:** question, pluto\
**Created:** [January 25, 2024, 4:48pm UTC](https://discourse.julialang.org/t/problem-when-using-pluto-unauthorizedaccess-on-windows/109265 "2024-01-25T16:48:46Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![MHaensel](https://avatars.discourse-cdn.com/v4/letter/m/47e85d/32.png) [@MHaensel](https://discourse.julialang.org/u/MHaensel)\
**Post date:** [January 26, 2024, 12:43pm UTC](https://discourse.julialang.org/t/problem-when-using-pluto-unauthorizedaccess-on-windows/109265/5 "2024-01-26T12:43:52Z")

</div>

As an update: In the end, I managed to sort the thing out by renaming the powershell profile `profile1.ps1`, which was put there by Python Anaconda, essentially following the solution for [this discourse thread](https://discourse.julialang.org/t/what-does-conda-have-to-do-with-pluto-notebooks/85117).

I am still a bit wondering what was going on though, I had an anaconda installation way before the problem described above appeared.

---

_[View the full topic](https://discourse.julialang.org/t/problem-when-using-pluto-unauthorizedaccess-on-windows/109265)._