Well, Windows doesn't even have a version of Zero Install, so it must have been something else
that messed it up. I'm not terribly familiar with Windows, but as I understand it,
installation works basically the same way as with RPM or dpkg:
- You get a package file, containing executable code (e.g. "setup.exe" or "preinst.sh").
- You run the executable code with admin/root privileges.
- The code makes whatever changes it feels like to your system.
Obviously, that's likely to mess up your system. However, I don't see how that applies to Zero
Install. In fact, Zero Install seems to be the exact opposite of the Windows/RPM/Debian
approach. Could you clarify what exactly you're worried about?