02-04-2010 02:46 PM - edited 02-04-2010 02:49 PM
Yes my version is the latest 220.127.116.11.
I always run the registry scanner check and then the registry defragger. With the new version installed I ran the scanner and then the reg-defragger. It asked to reboot and when I did the windows need to activate box popped up first. It re-acitavated and all was fine. I have not run the NU since.
* NU was the only thing run before this. And it happened on the reboot that the NU registry requested.
02-04-2010 02:49 PM
Would you be willing to double check? I just want to know if the same thing occurs with 118 as opposed to 116 that you noted before.
02-04-2010 03:06 PM
Ok it rebooted fine and did not ask for reactivation. which is good.
But that does not explain why it did it the first time after the latest NU update was installed and the registry defragger and scanner was run. ? As it happened on the reboot that NU requested?
02-04-2010 06:44 PM
You're correct that doesn't explain what happened originally. Windows activation is tied to the hardware configuration and fingerprint of the system. Microsoft doesn't really reveal all of the data points used. That said, defragging the registry shouldn't impact that fingerprint. Same with the registry cleanup. The only potential way I could see it happening is if there was a piece of software that was partially cleaned up in the registry that indirectly impacted the fingerprint. The only way I can think of determing if NU caused this would be to either have the scan logs before and after the reboot or to reproduce the issue with NU.