windows de-activated and wont re-activate

windows de-activated and wont re-activate

Post by TWF4aW11cz » Thu, 26 Jul 2007 13:00:01


Windows said it needs to reactivate windows due to a hardware change,
although I never changed anything. And when it tries to re-activate, it says
the product key is already in use and needs another one. Please help!
 
 
 

windows de-activated and wont re-activate

Post by GreenieLeB » Thu, 26 Jul 2007 13:08:31


You have to use the telephone activation method.

 
 
 

windows de-activated and wont re-activate

Post by The poster » Thu, 26 Jul 2007 23:12:31


Yet another example where buggy MS DRM inconveniences the paying
customer. This is doing nothing st stop piracy.

--
Priceless quotes in m.p.w.vista.general group:
http://www.yqcomputer.com/

"Only religious fanatics and totalitarian states equate morality with
legality."
- Linus Torvalds
 
 
 

windows de-activated and wont re-activate

Post by Cal Bear ' » Fri, 27 Jul 2007 00:23:10

Use phone activation

--
I Bleed Blue and Gold
GO BEARS!
 
 
 

windows de-activated and wont re-activate

Post by Alia » Fri, 27 Jul 2007 00:43:50


Sick of this crap? Try Ubuntu, an Open Source OS. It's free. www.ubuntu.com

Alias
 
 
 

windows de-activated and wont re-activate

Post by Fran » Fri, 27 Jul 2007 01:22:12


Yeah, try a stupid toy os..great idea...hahaha...good for kiddies like
you...hahaha...lol!
Frank
 
 
 

windows de-activated and wont re-activate

Post by Alia » Fri, 27 Jul 2007 01:47:23


Your jealously of people who can install a decent OS like Ubuntu and you
can't is showing, Frankie Boy.

Alias
 
 
 

windows de-activated and wont re-activate

Post by MVP Window » Thu, 02 Aug 2007 19:45:58

On Wed, 25 Jul 2007 09:12:31 -0500, The formerly Nina DiBoy




Before jumping in with guns blazing, I'd have asked whether there had
been any hardware changes, and what these were.

If there had been hardware changes, and these were in excess of
Vista's scarce-documented change thresholds, then the DoS payload is
working as designed.

If there had been hardware changes, and these were not in excess of
Vista's scarce-documented change thresholds, then the DoS payload is
buggy. Hey MS - "DoS payload" and "buggy"; pick ONE.

If there had been no hardware changes at all, then the DoS payload is
*really* buggy, and we need to chase this a lot harder.

So... more details, original poster?



Trsut me, I won't make a mistake!
 
 
 

windows de-activated and wont re-activate

Post by Alia » Thu, 02 Aug 2007 20:00:28


The OP wrote, and I quote:

"Windows said it needs to reactivate windows due to a hardware change,
although I never changed anything."

--
Alias
To email me, remove what's invalid
 
 
 

windows de-activated and wont re-activate

Post by bWF4aW11cz » Fri, 03 Aug 2007 11:54:01

Thank you everyone for the help. Activating it by telephone fixed the
problem. For those who were requesting more details...I never changed any
hardware, I didn't open my case or even add new software. During normal use
I got the message unexpectedly.
 
 
 

windows de-activated and wont re-activate

Post by MVP Window » Fri, 03 Aug 2007 19:54:24


Generally, this situation is resolved by phoning the activation line,
asking to speak to a human, and telling that human that the PC you are
attempting to activate the product is in fcat the same PC that it is
currently activated on.

The bug is not that the activation code tells you the license is in
use (it is, it's on the PC that "changed").

The bug is that an unchanged PC is detected as having been "changed so
much" that it is seen as a different PC.

That's the part I'd want to drill down into.



Possible "changes" include BIOS and driver updates that can break
previous assumptions as to what the hardware is "called".

Such "changes" are not real hardware changes of course, and that the
DoS payload can't tell the difference, is a serious limitation

Courts are too fallible for many nations to allow the irreversible
death penalty, and a system that can't tell the difference between
software and hardware changes is too fallible for a DoS payload, IMO.

OTOH, maybe this thing is so buggy (or exploitable) that the payload
hatched when there really were no changes at all. If the system
cannot safeguard itself against malware that can trigger a false
alarm, then it is too insecure for a DoS payload, IMO.



The most accurate diagnostic instrument
in medicine is the Retrospectoscope