Vista - Activation After BIOS Update

HI Robert,

I added the extra for anyone else who had a question on re activating Vista.

"Robert Robinson" wrote:

> 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.
>

Robert Robinson wrote:
>
> It is my understanding that Microsoft modifies a motherboard's BIOS code
> as part of the activation process. I installed a factory recommended

Incorrect, MS does NOT modify your PC's bios.

--
http://www.bootdisk.com/

"Plato" wrote:

> Robert Robinson wrote:
> >
> > It is my understanding that Microsoft modifies a motherboard's BIOS code
> > as part of the activation process. I installed a factory recommended
>
> Incorrect, MS does NOT modify your PC's bios.
>
> --
> http://www.bootdisk.com/
>
>
> I updated my BIOS several weeks ago and no reactivation was requested by Microsoft. I am running Vista Ultimate 32 bit. Something else has triggered the reactivation.

C.B.

Alias wrote:

> 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!
>
> Alias

Yep, MickeyMouse users have to be very careful about mod'ing their systems.
A BIOS update or a new case fan can bring the wraith of Ballmer on you!

Love and Kisses,
Doris

--
My Microsoft Hero (he loves this company!) ... http://tinyurl.com/yp9cn2
Title Says It All ... http://tinyurl.com/2ssodl

Doris Day - MFB wrote:

> Alias wrote:
>
>
>>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!
>>
>>Alias
>
>
> Yep, MickeyMouse users have to be very careful about mod'ing their systems.
> A BIOS update or a new case fan can bring the wraith of Ballmer on you!
>
> Love and Kisses,
> Doris
>

Only if the user is an unmitigated idiot like you!
(smirk)
Frank

I came across a BIOS update for a Gigabyte board three years ago stating
that Windows would have to be re-installed after the update.. the changes
were enough that it as good as constituted a different computer..


"Alias" <aka@aka.cl> wrote in message news:f1vc73$lfh$1@aioe.org...
> 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!
>
> Alias

--


Mike Hall
MS MVP Windows Shell/User
http://msmvps.com/blogs/mikehall/

I updated bios after ultimate upgrade and I was not popted to reactivate it.
"Mamamegs" <mamamegs@wilgeenmail.invalid> wrote in message
news:mn.53847d7555a68339.72151@wilgeenmail.invalid...
> 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)
>
> www.vistabits.nl
>
> MSN:
> _*mamamegs@gmail.com*_
>
>

Tom

Much depends upon what changes to BIOS are made..


"tomlives2000" <mail@mail.com> wrote in message
news:6oN0i.17441$YL5.15714@newssvr29.news.prodigy.net...
>I updated bios after ultimate upgrade and I was not popted to reactivate
>it.
> "Mamamegs" <mamamegs@wilgeenmail.invalid> wrote in message
> news:mn.53847d7555a68339.72151@wilgeenmail.invalid...
>> 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)
>>
>> www.vistabits.nl
>>
>> MSN:
>> _*mamamegs@gmail.com*_
>>
>>
>

--


Mike Hall
MS MVP Windows Shell/User
http://msmvps.com/blogs/mikehall/

Robert Robinson wrote:
> It is my understanding that Microsoft modifies a motherboard's BIOS code
> as part of the activation process.


Where'd you get that idea? So such thing occurs.


>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.

Blame someone else. Accusing Microsoft of this is simply absurd.


--

Bruce Chambers

Help us help you:
http://dts-l.org/goodpost.htm
http://www.catb.org/~esr/faqs/smart-questions.html

They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety. -Benjamin Franklin

Many people would rather die than think; in fact, most do. -Bertrand Russell

Based on the many forum messages about activation, it appears that no
one outside of an appropriate Microsoft group really knows the details
of the activation process.
It is likely that OEM installations involve some Microsoft operating
system related customization of the BIOS, but I agree that this may not
be correct.
A number of people have independently confirmed that a BIOS upgrade may
require a re-activation. The BIOS changes that might trigger a
re-activation are unknown to me.

On a slightly different subject, we have done a "bare metal"
(Microsoft's definition, not mine) restore after using Windows Server
2007's "Backup", which, incidentally, is a great program. I am ashamed
to say that I don't remember if this restore required an activation. I
was so pleased that it worked flawlessly that I didn't pay attention to
a possible activation request.
An interesting question is whether or not such a restore would work if
there had been a significant hardware change; for example, replacing a
motherboard. I do know that that you must have the same number of hard
drives and that each of these must have a capacity equal to or greater
that that of the original drives. There may be some additional technical
limitations.