Which version of Office 2016 I have?
up vote
9
down vote
favorite
I'm trying to understand which version of Office 2016 I have.
I click File and then Account. Here is the screenshot:
As you could see, the build number under "About Word" button is 9029.2167.
However, when I click this button, the new window appears, and the build number in this window is different: 9029.2106. Why?
microsoft-office
asked Dec 1 at 18:30
john c. j.
16513
add a comment |
up vote
9
down vote
favorite
I'm trying to understand which version of Office 2016 I have.
I click File and then Account. Here is the screenshot:
As you could see, the build number under "About Word" button is 9029.2167.
However, when I click this button, the new window appears, and the build number in this window is different: 9029.2106. Why?
microsoft-office
asked Dec 1 at 18:30
john c. j.
16513
add a comment |
up vote
9
down vote
favorite
up vote
9
down vote
favorite
I'm trying to understand which version of Office 2016 I have.
I click File and then Account. Here is the screenshot:
As you could see, the build number under "About Word" button is 9029.2167.
However, when I click this button, the new window appears, and the build number in this window is different: 9029.2106. Why?
microsoft-office
asked Dec 1 at 18:30
john c. j.
16513
I'm trying to understand which version of Office 2016 I have.
I click File and then Account. Here is the screenshot:
As you could see, the build number under "About Word" button is 9029.2167.
However, when I click this button, the new window appears, and the build number in this window is different: 9029.2106. Why?
microsoft-office
microsoft-office
asked Dec 1 at 18:30
john c. j.
16513
asked Dec 1 at 18:30
john c. j.
16513
edited Dec 1 at 18:36
asked Dec 1 at 18:30
john c. j.
16513
asked Dec 1 at 18:30
john c. j.
16513
asked Dec 1 at 18:30
john c. j.
16513
16513
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
up vote
8
down vote
accepted
This is the same version, distributed on two channels with a difference of
several days between the two.
The first was the
Office Insider Monthly (Targeted) v1802 build 9029.2106
from Feb. 20.
The second was the
Office 2016 & Office 365 Monthly Channel v1802 build 9029.2167
from Feb. 26.
The Insider version predates the Monthly version by almost one week.
What we have here is an amusing gaff by the Office developers.
The version number was entered correctly as the Monthly one
in the About Word title,
but in the dialog called up by that button it remained the Insider version.
In the official Microsoft
Update history for Office 365 ProPlus (listed by date),
there is only mentioned the Monthly version, since the Insider version
is not an official release.
answered Dec 1 at 19:17
harrymc
250k10257552
"What we have here [skipped] remained the Insider version." - Yeah! And after I manually updated the Office, the numbers are still different. Madness!
– john c. j.
Dec 1 at 20:39
4
Are they updating version numbers in dialog boxes manually??? At the very least this bug indicates that the version number comes from more than one single piece of metadata, which is quite silly.
– Lightness Races in Orbit
Dec 2 at 0:42
@LightnessRacesinOrbit: It means that these are separate modules that do not have common code. Agreed: This is not good practice.
– harrymc
Dec 2 at 7:56
@harrymc The modules should still take this metadata from a single source in the build system!
– Lightness Races in Orbit
Dec 2 at 14:59
add a comment |
up vote
2
down vote
One is the original version, the other is the update version (channel). Please refer to this article: https://social.technet.microsoft.com/Forums/en-US/a86b9b5a-47b1-4e7d-8759-dc0e4282369c/how-to-decode-office-365-proplus-buildversion-numbers?forum=Office2016ITPro
Please correct me if any errors in my answer.
answered Dec 1 at 18:58
RT2709
898
Hmm. It is possibly correct, however the provided link is about Office 365, instead of 2016. Anyway, I upvoted it. Let's wait some time, probably someone have another answers.
– john c. j.
Dec 1 at 19:05
I agree (& cheers, John!) I checked mine, it also presents 2 different numbers, the number "within About Word" is a smaller number than the one before "Click-to-Run".
– RT2709
Dec 1 at 19:14
2
@johnc.j. Office 2016 is simply a specific Office 365 release. This is the correct answer
– Ramhound
Dec 1 at 20:05
add a comment |
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
8
down vote
accepted
This is the same version, distributed on two channels with a difference of
several days between the two.
The first was the
Office Insider Monthly (Targeted) v1802 build 9029.2106
from Feb. 20.
The second was the
Office 2016 & Office 365 Monthly Channel v1802 build 9029.2167
from Feb. 26.
The Insider version predates the Monthly version by almost one week.
What we have here is an amusing gaff by the Office developers.
The version number was entered correctly as the Monthly one
in the About Word title,
but in the dialog called up by that button it remained the Insider version.
In the official Microsoft
Update history for Office 365 ProPlus (listed by date),
there is only mentioned the Monthly version, since the Insider version
is not an official release.
answered Dec 1 at 19:17
harrymc
250k10257552
"What we have here [skipped] remained the Insider version." - Yeah! And after I manually updated the Office, the numbers are still different. Madness!
– john c. j.
Dec 1 at 20:39
4
Are they updating version numbers in dialog boxes manually??? At the very least this bug indicates that the version number comes from more than one single piece of metadata, which is quite silly.
– Lightness Races in Orbit
Dec 2 at 0:42
@LightnessRacesinOrbit: It means that these are separate modules that do not have common code. Agreed: This is not good practice.
– harrymc
Dec 2 at 7:56
@harrymc The modules should still take this metadata from a single source in the build system!
– Lightness Races in Orbit
Dec 2 at 14:59
add a comment |
up vote
8
down vote
accepted
This is the same version, distributed on two channels with a difference of
several days between the two.
The first was the
Office Insider Monthly (Targeted) v1802 build 9029.2106
from Feb. 20.
The second was the
Office 2016 & Office 365 Monthly Channel v1802 build 9029.2167
from Feb. 26.
The Insider version predates the Monthly version by almost one week.
What we have here is an amusing gaff by the Office developers.
The version number was entered correctly as the Monthly one
in the About Word title,
but in the dialog called up by that button it remained the Insider version.
In the official Microsoft
Update history for Office 365 ProPlus (listed by date),
there is only mentioned the Monthly version, since the Insider version
is not an official release.
answered Dec 1 at 19:17
harrymc
250k10257552
"What we have here [skipped] remained the Insider version." - Yeah! And after I manually updated the Office, the numbers are still different. Madness!
– john c. j.
Dec 1 at 20:39
4
Are they updating version numbers in dialog boxes manually??? At the very least this bug indicates that the version number comes from more than one single piece of metadata, which is quite silly.
– Lightness Races in Orbit
Dec 2 at 0:42
@LightnessRacesinOrbit: It means that these are separate modules that do not have common code. Agreed: This is not good practice.
– harrymc
Dec 2 at 7:56
@harrymc The modules should still take this metadata from a single source in the build system!
– Lightness Races in Orbit
Dec 2 at 14:59
add a comment |
up vote
8
down vote
accepted
up vote
8
down vote
accepted
This is the same version, distributed on two channels with a difference of
several days between the two.
The first was the
Office Insider Monthly (Targeted) v1802 build 9029.2106
from Feb. 20.
The second was the
Office 2016 & Office 365 Monthly Channel v1802 build 9029.2167
from Feb. 26.
The Insider version predates the Monthly version by almost one week.
What we have here is an amusing gaff by the Office developers.
The version number was entered correctly as the Monthly one
in the About Word title,
but in the dialog called up by that button it remained the Insider version.
In the official Microsoft
Update history for Office 365 ProPlus (listed by date),
there is only mentioned the Monthly version, since the Insider version
is not an official release.
answered Dec 1 at 19:17
harrymc
250k10257552
This is the same version, distributed on two channels with a difference of
several days between the two.
The first was the
Office Insider Monthly (Targeted) v1802 build 9029.2106
from Feb. 20.
The second was the
Office 2016 & Office 365 Monthly Channel v1802 build 9029.2167
from Feb. 26.
The Insider version predates the Monthly version by almost one week.
What we have here is an amusing gaff by the Office developers.
The version number was entered correctly as the Monthly one
in the About Word title,
but in the dialog called up by that button it remained the Insider version.
In the official Microsoft
Update history for Office 365 ProPlus (listed by date),
there is only mentioned the Monthly version, since the Insider version
is not an official release.
answered Dec 1 at 19:17
harrymc
250k10257552
edited Dec 1 at 19:49
answered Dec 1 at 19:17
harrymc
250k10257552
answered Dec 1 at 19:17
harrymc
250k10257552
answered Dec 1 at 19:17
harrymc
250k10257552
250k10257552
"What we have here [skipped] remained the Insider version." - Yeah! And after I manually updated the Office, the numbers are still different. Madness!
– john c. j.
Dec 1 at 20:39
4
Are they updating version numbers in dialog boxes manually??? At the very least this bug indicates that the version number comes from more than one single piece of metadata, which is quite silly.
– Lightness Races in Orbit
Dec 2 at 0:42
@LightnessRacesinOrbit: It means that these are separate modules that do not have common code. Agreed: This is not good practice.
– harrymc
Dec 2 at 7:56
@harrymc The modules should still take this metadata from a single source in the build system!
– Lightness Races in Orbit
Dec 2 at 14:59
add a comment |
"What we have here [skipped] remained the Insider version." - Yeah! And after I manually updated the Office, the numbers are still different. Madness!
– john c. j.
Dec 1 at 20:39
4
Are they updating version numbers in dialog boxes manually??? At the very least this bug indicates that the version number comes from more than one single piece of metadata, which is quite silly.
– Lightness Races in Orbit
Dec 2 at 0:42
@LightnessRacesinOrbit: It means that these are separate modules that do not have common code. Agreed: This is not good practice.
– harrymc
Dec 2 at 7:56
@harrymc The modules should still take this metadata from a single source in the build system!
– Lightness Races in Orbit
Dec 2 at 14:59
"What we have here [skipped] remained the Insider version." - Yeah! And after I manually updated the Office, the numbers are still different. Madness!
– john c. j.
Dec 1 at 20:39
"What we have here [skipped] remained the Insider version." - Yeah! And after I manually updated the Office, the numbers are still different. Madness!
– john c. j.
Dec 1 at 20:39
4
4
Are they updating version numbers in dialog boxes manually??? At the very least this bug indicates that the version number comes from more than one single piece of metadata, which is quite silly.
– Lightness Races in Orbit
Dec 2 at 0:42
Are they updating version numbers in dialog boxes manually??? At the very least this bug indicates that the version number comes from more than one single piece of metadata, which is quite silly.
– Lightness Races in Orbit
Dec 2 at 0:42
@LightnessRacesinOrbit: It means that these are separate modules that do not have common code. Agreed: This is not good practice.
– harrymc
Dec 2 at 7:56
@LightnessRacesinOrbit: It means that these are separate modules that do not have common code. Agreed: This is not good practice.
– harrymc
Dec 2 at 7:56
@harrymc The modules should still take this metadata from a single source in the build system!
– Lightness Races in Orbit
Dec 2 at 14:59
@harrymc The modules should still take this metadata from a single source in the build system!
– Lightness Races in Orbit
Dec 2 at 14:59
add a comment |
up vote
2
down vote
One is the original version, the other is the update version (channel). Please refer to this article: https://social.technet.microsoft.com/Forums/en-US/a86b9b5a-47b1-4e7d-8759-dc0e4282369c/how-to-decode-office-365-proplus-buildversion-numbers?forum=Office2016ITPro
Please correct me if any errors in my answer.
answered Dec 1 at 18:58
RT2709
898
Hmm. It is possibly correct, however the provided link is about Office 365, instead of 2016. Anyway, I upvoted it. Let's wait some time, probably someone have another answers.
– john c. j.
Dec 1 at 19:05
I agree (& cheers, John!) I checked mine, it also presents 2 different numbers, the number "within About Word" is a smaller number than the one before "Click-to-Run".
– RT2709
Dec 1 at 19:14
2
@johnc.j. Office 2016 is simply a specific Office 365 release. This is the correct answer
– Ramhound
Dec 1 at 20:05
add a comment |
up vote
2
down vote
One is the original version, the other is the update version (channel). Please refer to this article: https://social.technet.microsoft.com/Forums/en-US/a86b9b5a-47b1-4e7d-8759-dc0e4282369c/how-to-decode-office-365-proplus-buildversion-numbers?forum=Office2016ITPro
Please correct me if any errors in my answer.
answered Dec 1 at 18:58
RT2709
898
Hmm. It is possibly correct, however the provided link is about Office 365, instead of 2016. Anyway, I upvoted it. Let's wait some time, probably someone have another answers.
– john c. j.
Dec 1 at 19:05
I agree (& cheers, John!) I checked mine, it also presents 2 different numbers, the number "within About Word" is a smaller number than the one before "Click-to-Run".
– RT2709
Dec 1 at 19:14
2
@johnc.j. Office 2016 is simply a specific Office 365 release. This is the correct answer
– Ramhound
Dec 1 at 20:05
add a comment |
up vote
2
down vote
up vote
2
down vote
One is the original version, the other is the update version (channel). Please refer to this article: https://social.technet.microsoft.com/Forums/en-US/a86b9b5a-47b1-4e7d-8759-dc0e4282369c/how-to-decode-office-365-proplus-buildversion-numbers?forum=Office2016ITPro
Please correct me if any errors in my answer.
answered Dec 1 at 18:58
RT2709
898
One is the original version, the other is the update version (channel). Please refer to this article: https://social.technet.microsoft.com/Forums/en-US/a86b9b5a-47b1-4e7d-8759-dc0e4282369c/how-to-decode-office-365-proplus-buildversion-numbers?forum=Office2016ITPro
Please correct me if any errors in my answer.
answered Dec 1 at 18:58
RT2709
898
answered Dec 1 at 18:58
RT2709
898
answered Dec 1 at 18:58
RT2709
898
answered Dec 1 at 18:58
RT2709
898
898
Hmm. It is possibly correct, however the provided link is about Office 365, instead of 2016. Anyway, I upvoted it. Let's wait some time, probably someone have another answers.
– john c. j.
Dec 1 at 19:05
I agree (& cheers, John!) I checked mine, it also presents 2 different numbers, the number "within About Word" is a smaller number than the one before "Click-to-Run".
– RT2709
Dec 1 at 19:14
2
@johnc.j. Office 2016 is simply a specific Office 365 release. This is the correct answer
– Ramhound
Dec 1 at 20:05
add a comment |
Hmm. It is possibly correct, however the provided link is about Office 365, instead of 2016. Anyway, I upvoted it. Let's wait some time, probably someone have another answers.
– john c. j.
Dec 1 at 19:05
I agree (& cheers, John!) I checked mine, it also presents 2 different numbers, the number "within About Word" is a smaller number than the one before "Click-to-Run".
– RT2709
Dec 1 at 19:14
2
@johnc.j. Office 2016 is simply a specific Office 365 release. This is the correct answer
– Ramhound
Dec 1 at 20:05
Hmm. It is possibly correct, however the provided link is about Office 365, instead of 2016. Anyway, I upvoted it. Let's wait some time, probably someone have another answers.
– john c. j.
Dec 1 at 19:05
Hmm. It is possibly correct, however the provided link is about Office 365, instead of 2016. Anyway, I upvoted it. Let's wait some time, probably someone have another answers.
– john c. j.
Dec 1 at 19:05
I agree (& cheers, John!) I checked mine, it also presents 2 different numbers, the number "within About Word" is a smaller number than the one before "Click-to-Run".
– RT2709
Dec 1 at 19:14
I agree (& cheers, John!) I checked mine, it also presents 2 different numbers, the number "within About Word" is a smaller number than the one before "Click-to-Run".
– RT2709
Dec 1 at 19:14
2
2
@johnc.j. Office 2016 is simply a specific Office 365 release. This is the correct answer
– Ramhound
Dec 1 at 20:05
@johnc.j. Office 2016 is simply a specific Office 365 release. This is the correct answer
– Ramhound
Dec 1 at 20:05
add a comment |
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1380024%2fwhich-version-of-office-2016-i-have%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
