I've got the same issue. Is this a VVM or Handcent issue? Is Handcent mistaking a VVM message notification from Verizon incorrectly? Or did Verizon change something on their end? I agree with the OP, it seems to have started with the last Handcent update.