I call this the "self-destruct" feature in UM3.
until I see some blog post , troubleshooting documentation regarding this problem, I assume it is just a design bug and they will not admit it.
sadly it happened to me with 2 different machines.
from my experience, if you are a big customer (more than 2 machines) the local rep will make some effort to fix your machine, if not, then ...
just sharing my pain and frustration