Tested and confirmed based on a complaint in the public forums....
http://www.blender.org/forum/viewtopic.php?t=20117
ex: Using blender-2.57b-release-windows32.exe
Installed Blender into a custom folder, in my case c:\tmp which contained several hundred temporary files and folders.
Launched the Uninstaller, which asked if I wanted to recursively delete the files within the 2.57/plugins 2.57/python and 2.57/scripts sub-directories
I selected YES each time, then it continued until it had deleted -everything- in the c:\tmp directory.
This would be particularly destructive if it had been somewhere other than a directory full of expendable temporary files.
Description
Event Timeline
If you installed with C:\tmp as the installdir, then yes, the installdir gets completely removed - Installing into a dir without a creating a subdir, so installing directly into a directory that's already used sounds like an odd thing to do anyway. I'll make sure that the installer gets clear notice that the _installation directory_ gets recursively deleted. And on install that one should ensure there is _at least one_ subdir for Blender alone, not containing previous files.
Until it was mentioned in the forums, I had not paid close attention to how the custom install worked.
I had usually just installed it the standard manner, which creates its own Blender directory under Program Files.
I guess I assumed that it would create its own Blender directory in whatever location you chose... now I am surprised that it doesnt.
I guess I also assumed that an 'uninstaller' would remove a list of installed files, not just *.* on the install directory.
Fixed the installer to only delete files that were installed, leaving the others intact.