Slashdot Mirror


Driver Update Can Cause Vista Deactivation

KrispySausage writes "After weeks of grueling troubleshooting, I've finally had it confirmed by Microsoft Australia and USA — something as small as swapping the video card or updating a device driver can trigger a total Vista deactivation. Put simply, your copy of Windows will stop working with very little notice (three days) and your PC will go into "reduced functionality" mode, where you can't do anything but use the web browser for half an hour."

4 of 875 comments (clear)

  1. Re:To all potentials looking to Vista as a solutio by LBArrettAnderson · · Score: 0, Flamebait

    Warn me about what? I've been using Vista for 5 months and haven't had a single problem with it. It has all of the functionality of XP, Linux, and OS X, plus a bit more. I've been nothing but satisfied with Vista.

    What did you want to tell me?

  2. Re:GO AWAY! by nuzak · · Score: 0, Flamebait

    Thanks for reminding me why you're still part of a foes list as long as my arm. I don't even particularly Linux, but you're just pathetic. I hope it never works for you.

    --
    Done with slashdot, done with nerds, getting a life.
  3. Re:Fool me once..... by harrkev · · Score: 0, Flamebait

    Oh noes! People complain that XP was insecure by default. Then, they fix this, and you complain that it makes your life a little more difficult?

    Taking advantage of the insecurity of XP is kind of like taking advnatage of a bug. Don't complain when it goes away.

    --
    "-1 Troll" is the apparently the same as "-1 I disagree with you."
  4. Re:Fool me once..... by NoOneInParticular · · Score: 0, Flamebait
    Okay, so you're saying that elevating privileges through CreateProcess() was a security risk, while elevating privileges through ShellExecute() is not? And that because the real security risk is the ability to redirect stdout? That's the only reasoning in which your comment makes sense.

    Microsoft fucked up security in XP, then they fix it halfway in Vista, and then it's the application developers fault that they couldn't foresee which half would be fixed?