It is my understanding that Microsoft modifies a motherboard's BIOS code
as part of the activation process. I installed a factory recommended
BIOS update and Windows Server 2007 now wants to be re-activated.
Modifying BIOS code is a risky process. Any failure, as from a power
outage, floppy read error or software glitch, can result in an
inoperable BIOS. Correcting this problem requires either a new EEPROM IC
or "factory" re-programming of the existing IC. In the interim, the
computer is completely disabled.
Microsoft's modification of BIOS code is an unwarranted, hazardous
intrusion of customer owned hardware.
It makes a note of the BIOS make and version.. when YOU updated the BIOS,
the details that the OS had noted will have changed, so the installation
assumes it is on a different computer, and therefore requires activation..
"Robert Robinson" <robbiex@bellsouth.net> wrote in message
news:uJCGZ3vkHHA.1624@TK2MSFTNGP02.phx.gbl...
> It is my understanding that Microsoft modifies a motherboard's BIOS code
> as part of the activation process. I installed a factory recommended BIOS
> update and Windows Server 2007 now wants to be re-activated.
> Modifying BIOS code is a risky process. Any failure, as from a power
> outage, floppy read error or software glitch, can result in an inoperable
> BIOS. Correcting this problem requires either a new EEPROM IC or "factory"
> re-programming of the existing IC. In the interim, the computer is
> completely disabled.
> Microsoft's modification of BIOS code is an unwarranted, hazardous
> intrusion of customer owned hardware.
on 10-5-2007, Robert Robinson supposed :
> It is my understanding that Microsoft modifies a motherboard's BIOS
> code as part of the activation process. I installed a factory
> recommended BIOS update and Windows Server 2007 now wants to be
> re-activated.
> Modifying BIOS code is a risky process. Any failure, as from a power
> outage, floppy read error or software glitch, can result in an
> inoperable BIOS. Correcting this problem requires either a new EEPROM
> IC or "factory" re-programming of the existing IC. In the interim,
> the computer is completely disabled.
> Microsoft's modification of BIOS code is an unwarranted, hazardous
> intrusion of customer owned hardware.
As far as I know this is only being done with OEM versions and not by
MS
but by the OEM. I could be wrong though.
--
Mamamegs.
I reject your reality and substitute my own.
(Adam Savage)
> It is my understanding that Microsoft modifies a motherboard's BIOS code
> as part of the activation process. I installed a factory recommended
> BIOS update and Windows Server 2007 now wants to be re-activated.
> Modifying BIOS code is a risky process. Any failure, as from a power
> outage, floppy read error or software glitch, can result in an
> inoperable BIOS. Correcting this problem requires either a new EEPROM IC
> or "factory" re-programming of the existing IC. In the interim, the
> computer is completely disabled.
> Microsoft's modification of BIOS code is an unwarranted, hazardous
> intrusion of customer owned hardware.
>
Mamamegs wrote:
> on 10-5-2007, Robert Robinson supposed :
>> It is my understanding that Microsoft modifies a motherboard's BIOS
>> code as part of the activation process. I installed a factory
>> recommended BIOS update and Windows Server 2007 now wants to be
>> re-activated.
>> Modifying BIOS code is a risky process. Any failure, as from a power
>> outage, floppy read error or software glitch, can result in an
>> inoperable BIOS. Correcting this problem requires either a new EEPROM
>> IC or "factory" re-programming of the existing IC. In the interim, the
>> computer is completely disabled.
>> Microsoft's modification of BIOS code is an unwarranted, hazardous
>> intrusion of customer owned hardware.
>
> As far as I know this is only being done with OEM versions and not by MS
> but by the OEM. I could be wrong though.
>
Thanks to both for the follow-up.
I don't know the details of how the operating system activation
interacts with the BIOS. It is possible that the Microsoft mandated
modifications only apply to OEM products.
There should not be any need to re-activate after a BIOS update.
Presumably, the motherboard and CPU IDs are unchanged. In this instance,
there were no differences whatsoever in the hardware configuration.
A different question about activation involves the use of external SATA
drives. We haven't had a problem with connecting and disconnecting a
single SATA drive, but wonder if using multiple external SATA drives
might trigger a re-activation.
"Robert Robinson" <robbiex@bellsouth.net> wrote in message
news:OUYMw5wkHHA.208@TK2MSFTNGP05.phx.gbl...
> Mamamegs wrote:
>> on 10-5-2007, Robert Robinson supposed :
>>> It is my understanding that Microsoft modifies a motherboard's BIOS code
>>> as part of the activation process. I installed a factory recommended
>>> BIOS update and Windows Server 2007 now wants to be re-activated.
>>> Modifying BIOS code is a risky process. Any failure, as from a power
>>> outage, floppy read error or software glitch, can result in an
>>> inoperable BIOS. Correcting this problem requires either a new EEPROM IC
>>> or "factory" re-programming of the existing IC. In the interim, the
>>> computer is completely disabled.
>>> Microsoft's modification of BIOS code is an unwarranted, hazardous
>>> intrusion of customer owned hardware.
>>
>> As far as I know this is only being done with OEM versions and not by MS
>> but by the OEM. I could be wrong though.
>>
> Thanks to both for the follow-up.
> I don't know the details of how the operating system activation interacts
> with the BIOS. It is possible that the Microsoft mandated modifications
> only apply to OEM products.
> There should not be any need to re-activate after a BIOS update.
> Presumably, the motherboard and CPU IDs are unchanged. In this instance,
> there were no differences whatsoever in the hardware configuration.
>
> A different question about activation involves the use of external SATA
> drives. We haven't had a problem with connecting and disconnecting a
> single SATA drive, but wonder if using multiple external SATA drives might
> trigger a re-activation.
Activating does not alter the BIOS. Activation is triggered by hardware
changes. The changes are cumulative. Changes are tracked. Each change is
worth a certain number of points which varies according to what is changed.
Once you hit a certain number you have to activate. In your case the BIOS
update caused Windows to think something had changed, The point total of
this change plus previous ones was calculated and activation was triggered.
I don't know of any source of a reliable formula for tracking or calculating
when activation will occur. Adding removing SATA drives may be a
contributing factor depending on how your SATA controller handles them.
Mike Hall MVP wrote:
> It makes a note of the BIOS make and version.. when YOU updated the
> BIOS, the details that the OS had noted will have changed, so the
> installation assumes it is on a different computer, and therefore
> requires activation..
The fact is, though, it isn't a different computer and the activation is
therefore FLAWED and should be discontinued!
YOU understand wrong. Microsoft never modifies bios code.
--
Regards,
Richard Urban
Microsoft MVP Windows Shell/User
(For email, remove the obvious from my address)
Quote from George Ankner:
If you knew as much as you think you know,
You would realize that you don't know what you thought you knew!
"Robert Robinson" <robbiex@bellsouth.net> wrote in message
news:uJCGZ3vkHHA.1624@TK2MSFTNGP02.phx.gbl...
> It is my understanding that Microsoft modifies a motherboard's BIOS code
> as part of the activation process. I installed a factory recommended BIOS
> update and Windows Server 2007 now wants to be re-activated.
> Modifying BIOS code is a risky process. Any failure, as from a power
> outage, floppy read error or software glitch, can result in an inoperable
> BIOS. Correcting this problem requires either a new EEPROM IC or "factory"
> re-programming of the existing IC. In the interim, the computer is
> completely disabled.
> Microsoft's modification of BIOS code is an unwarranted, hazardous
> intrusion of customer owned hardware.
As I have too much time on my hands I do a lot of guinea pigging ( testing
for others ) and I have changed many a motherboard and cpu while running both
XP pro and Vista and this is what I have found based on genuine Intel MoBo's
not other makes or rebadged boards.
1. If you have to replace you MoBo and you do it with the same board you
don't have to re activate. If you upgrade the board you do naturally.
2. You can change your CPU to whatever you want without having to re activate.
3. You can add or remove any card or memory without having to re activate.
4. I have done numerous BIOS updates without it effecting Windows ( whatever )
5. I have also done Intel hardware updates without any effect to activation.
I have found this to be true for both OEM and Original copies of the O/S.
Now I don't know if this answers questions or creates more, but 3 cpu's and
5 MoBo's should be enough changes to make this statement.
"Richard Urban" wrote:
> YOU understand wrong. Microsoft never modifies bios code.
>
> --
>
>
> Regards,
>
> Richard Urban
> Microsoft MVP Windows Shell/User
> (For email, remove the obvious from my address)
>
> Quote from George Ankner:
> If you knew as much as you think you know,
> You would realize that you don't know what you thought you knew!
>
> "Robert Robinson" <robbiex@bellsouth.net> wrote in message
> news:uJCGZ3vkHHA.1624@TK2MSFTNGP02.phx.gbl...
> > It is my understanding that Microsoft modifies a motherboard's BIOS code
> > as part of the activation process. I installed a factory recommended BIOS
> > update and Windows Server 2007 now wants to be re-activated.
> > Modifying BIOS code is a risky process. Any failure, as from a power
> > outage, floppy read error or software glitch, can result in an inoperable
> > BIOS. Correcting this problem requires either a new EEPROM IC or "factory"
> > re-programming of the existing IC. In the interim, the computer is
> > completely disabled.
> > Microsoft's modification of BIOS code is an unwarranted, hazardous
> > intrusion of customer owned hardware.
>
>
Bob wrote:
> As I have too much time on my hands I do a lot of guinea pigging ( testing
> for others ) and I have changed many a motherboard and cpu while running both
> XP pro and Vista and this is what I have found based on genuine Intel MoBo's
> not other makes or rebadged boards.
> 1. If you have to replace you MoBo and you do it with the same board you
> don't have to re activate. If you upgrade the board you do naturally.
> 2. You can change your CPU to whatever you want without having to re activate.
> 3. You can add or remove any card or memory without having to re activate.
> 4. I have done numerous BIOS updates without it effecting Windows ( whatever )
> 5. I have also done Intel hardware updates without any effect to activation.
>
> I have found this to be true for both OEM and Original copies of the O/S.
>
> Now I don't know if this answers questions or creates more, but 3 cpu's and
> 5 MoBo's should be enough changes to make this statement.
>
> "Richard Urban" wrote:
>
>> YOU understand wrong. Microsoft never modifies bios code.
>>
>> --
>>
>>
>> Regards,
>>
>> Richard Urban
>> Microsoft MVP Windows Shell/User
>> (For email, remove the obvious from my address)
>>
>> Quote from George Ankner:
>> If you knew as much as you think you know,
>> You would realize that you don't know what you thought you knew!
>>
>> "Robert Robinson" <robbiex@bellsouth.net> wrote in message
>> news:uJCGZ3vkHHA.1624@TK2MSFTNGP02.phx.gbl...
>>> It is my understanding that Microsoft modifies a motherboard's BIOS code
>>> as part of the activation process. I installed a factory recommended BIOS
>>> update and Windows Server 2007 now wants to be re-activated.
>>> Modifying BIOS code is a risky process. Any failure, as from a power
>>> outage, floppy read error or software glitch, can result in an inoperable
>>> BIOS. Correcting this problem requires either a new EEPROM IC or "factory"
>>> re-programming of the existing IC. In the interim, the computer is
>>> completely disabled.
>>> Microsoft's modification of BIOS code is an unwarranted, hazardous
>>> intrusion of customer owned hardware.
>>
Hi Bob and Kerry,
I don't want to drag this out, but do want to emphasize that the only
change that triggered the re-activation was a BIOS update. There were no
other modifications. The hardware were the same dating from the time of
the original, clean install of the OS.
Activation After BIOS Update 
Linear Mode
