Difference between revisions of "Windows 8 build 8600"

From BetaWiki
Jump to navigation Jump to search
m
Line 4: Line 4:
 
|compiled = 2012-07-??
 
|compiled = 2012-07-??
 
}}
 
}}
'''Windows 8 build 8600''' is an unleaked build of [[Windows 8]]. It was listed by some sources to be the RTM build, but was later scrapped. <ref>https://www.neowin.net/news/windows-8-rtm-build-to-be-8600-new-images-surface</ref> However, it is certain that this build is fake, since RTM build numbers has to be divisible by 16 by the servicing stack, but this build number which was supposed to be an RTM build isn't divisible by 16. This is further supported by blog posts by Microsoft employees.<ref>https://docs.microsoft.com/en-us/previous-versions/technet-magazine/jj663498(v=msdn.10)</ref>
+
'''Windows 8 build 8600''' is an unleaked build of [[Windows 8]]. It was listed by some sources to be the RTM build, but was later scrapped. <ref>https://www.neowin.net/news/windows-8-rtm-build-to-be-8600-new-images-surface</ref> However, it is certain that this build is fake, since RTM build numbers have to still be a whole number after this math <Insert build number here>/16 by the servicing stack, but this build number which was supposed to be an RTM build does not meet this requirement. This is further supported by blog posts by Microsoft employees.<ref>https://docs.microsoft.com/en-us/previous-versions/technet-magazine/jj663498(v=msdn.10)</ref>
  
== References ==
+
==References==
 
<references />
 
<references />

Revision as of 23:07, 26 March 2020

6.2.8600
Build of Windows 8
No image available
OS family
Architecture
Compiled2012-07-??
Timebomb
Works in

Windows 8 build 8600 is an unleaked build of Windows 8. It was listed by some sources to be the RTM build, but was later scrapped. [1] However, it is certain that this build is fake, since RTM build numbers have to still be a whole number after this math <Insert build number here>/16 by the servicing stack, but this build number which was supposed to be an RTM build does not meet this requirement. This is further supported by blog posts by Microsoft employees.[2]

References