Thats exact the same thing the german support told me. Let me add for vista X64 Sp1 that you may be, after setting msconfig to normal boot, you can't boot anymore with an error 0xC000000E winload.exe. (That happened to me)
This is may be a vista bug, however it seems, that the boot configuration of the standard boot drive is lost. If you read here some threads you will read, that some useres are angry because they had to do a new system setup... so i think this is also related to my expirience.
What you should have, before you do a clean install is the Vista CD from which you can boot or a norton Ghost rescue system (Vista PE).
Do not a repair from the Vista CD! What you have to do is in the repair menu to open the dos prompt.
From the Dos you call bcdedit.exe which liss the bootentries.
In the second part of this list you will see two entries:
device partition=C:
osdevice partition=C:
where C: is your boot drive where winload.exe is located in \windows\system32
If you have behind device and osdevice no, or other entries just set them to your boot drive:
bcdedit set {current} device partition=C:
bcdedit set {current} osdevice partition=C:
Now you can reboot and Vista should be able to boot again.
You know, I wonder how much percent of the users it's not staying enabled and how much it's simply working.
Mine is working, at least it was and stays enabled, but I do have other issues then...
However, if mine DOES work and so for many people it doesn't,
I wonder what must be on my computer that lets it work.
I mean, this thing is like a mix of parts of say 2 to 7 years old,
so say generally about 5 years old.
And I've had it running in "one install" for like 2 years now, even though I (try to) keep it clean.
And the thing is stuffed with all kinds of software too.
I reckon that the more stuff is on a computer (and also the longer it's used),
the better it work, as in the "more compatible" it gets.
Same thing as my previous computer, I could play ANYTHING on it, like media and such.
The moment I switched my files to this newer and better computer, I could barely play anything.
Also, I recently used someone's brand new laptop, the thing would barely work. 
So, that's just what it seems like to me...
"I reckon that the more stuff is on a computer (and also the longer it's used),
the better it work, as in the "more compatible" it gets.
Same thing as my previous computer, I could play ANYTHING on it, like media and such.
The moment I switched my files to this newer and better computer, I could barely play anything.
Also, I recently used someone's brand new laptop, the thing would barely work. "
Whilst I would love you to be correct, software is not like machinery and does not have (nor should it need) a 'wearing in' period! 
I can understand from your experiences why you would think so, but that is just NOT how it works I'm afraid!
It is possible that their could be some common combination of applications that is interfering with SetPoint and causing the problem, but I am not about to go uninstalling programs that I use everyday just to find out when we have no idea where to start.
Unless Logitech bother to get back to us with some helpful information (ie, things to check that don't involve a clean uninstall and reinstall of Setpoint, as we KNOW that doesn't work!) we are very unlikely to figure this out.
