I am sorry for the trouble @fdavidg. I know when this post was written you were using n8n desktop 0.216.2. Are you also seeing this problem when using a more recent version of n8n via Docker?
Keep in mind that you’d need to update your path accordingly. When using the -v C:\Users\fdavidg\.n8n:/home/node/.n8n option in your docker run command, the C:\Users\fdavidg\.n8n path on your desktop machine would be available to your n8n docker container as /home/node/.n8n.
If this problem keeps happening, can you confirm if you are seeing any error message in your terminal confirming what might have gone wrong?