Sequetial Updates?

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hi,

Just wondering why WD Beta 2, since install, went from signature update #
1.13.1272.4 to 1.13.1276.3 [I got notified by task bar icon and Windows
Update to install - which I did manually using the fix on the 'known issues'
page], and now today [a wek or so later] I have a task bar icon [and Windows
Update] notifying me to download and install signature # 1.13.1276.16.

This seems a backwards step sequetially speaking....any ideas why?

Incidentally, the signature # 1.13.1276.16 failed to install anyway. The
Event Viewer Application Log only states that the update failed because of
'configuration failure' and source 'Msi installer'.
 
Spelling correction: sequential

:

Hi,

Just wondering why WD Beta 2, since install, went from signature update #
1.13.1272.4 to 1.13.1276.3 [I got notified by task bar icon and Windows
Update to install - which I did manually using the fix on the 'known issues'
page] , and now today [a wek or so later] I have a task bar icon [and Windows
Update] notifying me to download and install signature # 1.13.1276.16.


This seems a backwards step sequentially speaking....any ideas why?


Incidentally, the signature # 1.13.1276.16 failed to install anyway. The
Event Viewer Application Log only states that the update failed because of
'configuration failure' and source 'Msi installer'.
 
I don't have an explanation on hand as to why the update would be failing,
but I would like to comment on whether the version number is sequential or
not.

A version number in Windows is generally represented in the following
format:

[MajorVersion].[MinorVersion].[BuildNumber].[RevisionNumber]

For any given version number, any of the four components can be incremented
to create a version number that is sequentially greater than the previous
version number.

So, the version number "1.13.1276.16" is in fact greater than "1.13.1276.3",
because the revision number (16) is larger than the previous version (3),
and all of the other components (the major version, minor version and build
number) are the same.

Therefore, sequentially speaking it is a new version and is not a "backwards
step."

I'll admit it may be a bit confusing, but for now rest assured that the
version number did indeed increase according to how version numbers are
generally handled in Windows.

As for why the build number did not increase this time, and only the
revision number did, we probably need to adjust our release process to be a
little more consistent here.

Thanks

-Mike
 
Thanks for pointing that out Mike...I had it in my mind that the sig # were
using decimal system.

I managed update the sig # 1.13.1276.16 install though, only by using the
Start>Run 'Msiexec /x {A5CC2A09-E9D3-49EC-923D-03874BBD4C2C}' method to
remove the previous signature.

Thanks for dropping by Mike.

Rgds

Julien


Mike Treit said:
I don't have an explanation on hand as to why the update would be failing,
but I would like to comment on whether the version number is sequential or
not.

A version number in Windows is generally represented in the following
format:

[MajorVersion].[MinorVersion].[BuildNumber].[RevisionNumber]

For any given version number, any of the four components can be incremented
to create a version number that is sequentially greater than the previous
version number.

So, the version number "1.13.1276.16" is in fact greater than "1.13.1276.3",
because the revision number (16) is larger than the previous version (3),
and all of the other components (the major version, minor version and build
number) are the same.

Therefore, sequentially speaking it is a new version and is not a "backwards
step."

I'll admit it may be a bit confusing, but for now rest assured that the
version number did indeed increase according to how version numbers are
generally handled in Windows.

As for why the build number did not increase this time, and only the
revision number did, we probably need to adjust our release process to be a
little more consistent here.

Thanks

-Mike

julienfamilyman said:
Hi,

Just wondering why WD Beta 2, since install, went from signature update #
1.13.1272.4 to 1.13.1276.3 [I got notified by task bar icon and Windows
Update to install - which I did manually using the fix on the 'known
issues'
page], and now today [a wek or so later] I have a task bar icon [and
Windows
Update] notifying me to download and install signature # 1.13.1276.16.

This seems a backwards step sequetially speaking....any ideas why?

Incidentally, the signature # 1.13.1276.16 failed to install anyway. The
Event Viewer Application Log only states that the update failed because of
'configuration failure' and source 'Msi installer'.
Click to expand...
Click to expand...
 
Back
Top