The origin of Vista version 6000 explains that Win7 also complies with

All things are for a reason, Win7 versions 7600.16384 and 7600.16385 are also proven.

First of all, how is the build number of 7600?

The first point is to be divisible by 100. This is the practice since xp 2600. Regarding this convention, there is still a story, because before xp, the build number is one plus one, and never skipped, but the period of xp came from the exchange to the boss, so it was 100. This practice of divisibility is brought to windows. There is no technical reason for this, purely for the sake of good.

So why not 7300? There is a technical reason here. The final build number must be divisible by 16. This is for service packs. The QFE team reserves the last 4 bits of the build number as the number of the service pack (of course this is the requirement for Vista to come out). For example, Vista 6000, sp1 is 6001, sp2 is 6002, and can do up to 16 sp. Therefore, the initial rtm build number of win7 must also be divisible by 16. So because the last build was already 7271, the most recent one is divisible by 100, and the number that can be divisible by 16 is 7600, and sp1 is 7601. Although 7777 is a good number, it does not meet the conditions.

The next eligible one is 8000, so why not 8000? The reason here is that build number is also a limited resource, the maximum number of builds supported by Windows API GetVersion It is 16383. Considering the needs of the next n years, you can't jump the build number at random. Otherwise, after a few more releases, the build number will be used up, and it will be troublesome.

Finally talk about the minor build number, which is QFE version, why is 16384. This is mainly the requirement of QFE. The 14th bit of RTM's minor number must be 1. This is a basis for the hot fix to judge. In this case, the minimum minor number that satisfies the condition is 2^14=16384. Vista rtm's first build was also 16384, and later it became a problem with 16386. It doesn't matter if this sum can be divisible.

By the way, one problem is that after n years, when the build number of Windows reaches 10000, a lot of software will have problems, similar to the y2k problem.