Hi, so, I was eventually told by @James_Britt what the problem was.
The issue was that I had used GitHub actions to create the .XRNX and the zip package actually also had .git/ and .github/ folders in it. So removing them turned out to be impossible since “they weren’t supposed to be there”.
If a script creator creates a .xrnx which is kinda valid (=works) but hard to remove, then it’d be pretty swell if there was some way of informing the user on what to do, or a way to inform the script creator - what was the issue and how can they fix it
When I tested this nothing was open. I suspect the uninstaller has trouble with dot files and folders.
It might delete all files then delete the tool folder, but if the the dot files were missed (because they are theoretically “hidden” files) then an error would occur deleting the folder because it is not empty. But what’s interesting is that after the uninstall fails the tool folder appears to have all the original files anyway; it is not as though some files were deleted and the dot files remained.