Windows 7 build number "changed"

Page 12 of 16 FirstFirst ... 21011121314 ... LastLast

  1. Posts : 48
    Windows 7 / Linux Mint
       #111

    HamidFULL said:
    Finally whats the fact!?

    1. 16385 is a Beta release
    2. RTM is 16385 and we could update our OS via windowsupdate to 16399
    3. RTM and final release is 16399

    PS : may we get another build like 16400 soon?!
    16385 is RTM an do not change anymore!!!! Windows 7 has not stopped to be maintained, so MS will make updates and fixes, to mark them they must change something in the version number!. October 22 you got 16385, but with the updtes perhaps included (and the updates not yet leaked).
    Every windows has those updates, but why are those not in Windows Updates?? That has a simple reason! 16385 is only leaked and not official released by MS, so the Updtes are the same case they are only leaked. If MS will add they in the Windows Update, they will leak themself the Updates.

    An other faq is that if an Fix for the cracks is released befor the final version is out, the Hackers have more time to find other Solutions to crack Windows 7.
      My Computer


  2. Posts : 1,011
    Windows 7 Ultimate x64 (Retail)
       #112

    I believe the simple reason these updates are not yet appearing on Windows Update is because these are presently classified as "Hot Fixes" which means they (MS) haven't finished fully testing them yet. When they have, they will likely appear on WU assuming they don't discover any issues with the Hot Fixes.
      My Computer


  3. Posts : 3
    Windows Vista Ultimate x64 SP1 --> SP2 soon! | XP Pro x86 SP3
       #113

    knuckles84 said:
    16385 is RTM an do not change anymore!!!! Windows 7 has not stopped to be maintained, so MS will make updates and fixes, to mark them they must change something in the version number!. October 22 you got 16385, but with the updtes perhaps included (and the updates not yet leaked).
    Every windows has those updates, but why are those not in Windows Updates?? That has a simple reason! 16385 is only leaked and not official released by MS, so the Updtes are the same case they are only leaked. If MS will add they in the Windows Update, they will leak themself the Updates.

    An other faq is that if an Fix for the cracks is released befor the final version is out, the Hackers have more time to find other Solutions to crack Windows 7.
    Thanks for explains! :)
    just two notes on your post + some new questions :
    ...to mark them they must change something in the version number!...
    which type of updates will affect on windows version? well, I installed many Patches on my XP but just a few of them changed the build number like "XP roll update"

    and MS confirmed that 16385 is RTM?
    harpua said:
    I believe the simple reason these updates are not yet appearing on Windows Update is because these are presently classified as "Hot Fixes" which means they (MS) haven't finished fully testing them yet. When they have, they will likely appear on WU assuming they don't discover any issues with the Hot Fixes.
    of course may it is ...

    PS : MSDN release could be 16399 or higher?!
      My Computer


  4. Posts : 3
    Windows Vista Ultimate x64 SP1 --> SP2 soon! | XP Pro x86 SP3
       #114

    Got a shock!!!

    I found this picture on the web [seems picture is provided by MSDN users that have build 16399 ISO]

    What!! when you installed OS from the ISO there would be some installed updates as the control panel report!! its ok?! or just a stupid hacker integrated patches into 16385 to make another ISO?!
    Attached Thumbnails Attached Thumbnails Windows 7 build number "changed"-14vmkq1.jpg  
      My Computer


  5. Posts : 48
    Windows 7 / Linux Mint
       #115

    HamidFULL said:
    which type of updates will affect on windows version? well, I installed many Patches on my XP but just a few of them changed the build number like "XP roll update"
    I'm sure that the Patches that you have installed on XP have change some of the version numbers, but perhaps not they, they you controll normaly. Or do you controle every dll exe..... after and Update??
      My Computer


  6. Posts : 8,476
    Windows® 8 Pro (64-bit)
       #116

    HamidFULL said:
    Got a shock!!!

    I found this picture on the web [seems picture is provided by MSDN users that have build 16399 ISO]

    What!! when you installed OS from the ISO there would be some installed updates as the control panel report!! its ok?! or just a stupid hacker integrated patches into 16385 to make another ISO?!
    No need to panic mate. That's absolutely fine.
      My Computer


  7. Posts : 4,663
    Windows 7 Home Premium 64 bit
       #117

    Hi all. Installed these updates yesterday and I just ran my WEI thing and I've gained a point on processor and memory scores.
    Subjectively feels "snappier" too.

    Best wishes, John
      My Computer


  8. Posts : 98
    Windows 7 RTM
       #118

    HamidFULL said:
    Finally whats the fact!?

    1. 16385 is a Beta release
    2. RTM is 16385 and we could update our OS via windowsupdate to 16399
    3. RTM and final release is 16399

    PS : may we get another build like 16400 soon?!
    This is the type of FUD that doesn't need to be continually posted here...

    I can't understand how some of you still think 16385 isn't RTM. Those updates are not meant for your systems, even if they are, not yet. The previous poster got a BSOD on running WEI. I bet he hasn't had a BSOD yet, now thanks to these beta/untested/unsupported updates, he gets one.

    So please, stop worrying about these updates, 16385 will be the build posted on Technet/MSDN. If a NEW build is compiled, it has to be re-voted on, as before with the RC to RTM builds. This IS NOT GOING TO HAPPEN, OEM's already have the code, it's DONE, DONE, DONE, DONE....... DONE... So please, stop. kthx.
      My Computer


  9. Posts : 149
    Windows 7 Pro (MSDN)
       #119

    HamidFULL said:
    PS : MSDN release could be 16399 or higher?!
    No.

    1) Because 16385 is RTM.

    2) Because 16399 comes from a test update (none of the "real" updates are 16399; they are 16401, etc., and most importantly, none of the "real" updates will update the kernel EXE, so your system will still report 16385!)

    You will notice that every 16399 file is from a low-# KB (the test updates that are not "real") (and that every low-# KB is 16399). This means that the test updates were all made from the same buildset (makes sense) and that every 16399 file is from a test update, not a real update!
      My Computer


  10. Posts : 4,925
    Windows 7 Professional 64-bit
       #120

    @xendrome: well said tbh.
      My Computer


 
Page 12 of 16 FirstFirst ... 21011121314 ... LastLast

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 12:53.
Find Us