xtrabit racing Posted July 31, 2009 Share Posted July 31, 2009 (edited) Reliable sources say that Microsoft will release updates through Windows Update to fix some bugs, but one of those updates will change the build string from: 7600.16385.090713-1255 to 7600.16399.x86fre.win7_gdr.090722-1835. No reason has been given by Microsoft for the change. Will the build released on August 6th on Technet/MSDN/Connect already come with the new build number? I have no idea... Edited July 31, 2009 by warwagon Link to comment Share on other sites More sharing options...
deletedxyz Posted July 31, 2009 Share Posted July 31, 2009 I wondered what change warranted a significant change in build number. :/ Link to comment Share on other sites More sharing options...
Pupik Posted July 31, 2009 Share Posted July 31, 2009 I'm calling bull****, until those updates will appear on the actual Windows Update. Link to comment Share on other sites More sharing options...
Gio Takahashi Posted July 31, 2009 Share Posted July 31, 2009 I highly doubt this, but we'll see. The screenshot in the thread looks pretty legitimate, I can't tell if its fake or not. Oh well. Not gonna get freaked out over sub build number. Link to comment Share on other sites More sharing options...
+Audioboxer Subscriber² Posted July 31, 2009 Subscriber² Share Posted July 31, 2009 (edited) No, just no. No what? The updates are on the web and it does change the build number ;) (not my screenshots) Edited July 31, 2009 by Audioboxer Link to comment Share on other sites More sharing options...
Gio Takahashi Posted July 31, 2009 Share Posted July 31, 2009 Yeah, but unless those updates are actually official, it's just a bit suspicious to me. Link to comment Share on other sites More sharing options...
Kupo-Cheer Posted July 31, 2009 Share Posted July 31, 2009 Well, they'll eventually want to plug up that OEM certificate problem that can be exploited by piraters. Not sure if it is related to this issue or not, though; it's pure speculation. Link to comment Share on other sites More sharing options...
+Audioboxer Subscriber² Posted July 31, 2009 Subscriber² Share Posted July 31, 2009 Yeah, but unless those updates are actually official, it's just a bit suspicious to me. They have signed certificates. Internal leak, they can be uninstalled, but I guess it's just best to wait for Windows Update to kick in if you're worried. ps. Dead Soul, probably best not to link directly to that forum, contains content Neowin doesn't allow... Link to comment Share on other sites More sharing options...
Gio Takahashi Posted July 31, 2009 Share Posted July 31, 2009 They have signed certificates.Internal leak, they can be uninstalled, but I guess it's just best to wait for Windows Update to kick in if you're worried. Ah, okay. Thanks. Link to comment Share on other sites More sharing options...
BoDEAN Posted July 31, 2009 Share Posted July 31, 2009 Talking about hotfixes for " unreleased " OS will result in a WARNING . Just a heads up. Already received one, and all I did was ask for a PM from someone. Link to comment Share on other sites More sharing options...
+Audioboxer Subscriber² Posted July 31, 2009 Subscriber² Share Posted July 31, 2009 Talking about hotfixes for " unreleased " OS will result in a WARNING . Just a heads up. Already received one, and all I did was ask for a PM from someone. Did you ask for hotfixes or for the OS? It is against the rules to spread links to a finalized OS that is not in beta form any more (in this case Windows 7 RTM). I never knew hotfixes were banned also :blink: Removed my links above until further clarification. Link to comment Share on other sites More sharing options...
BoDEAN Posted July 31, 2009 Share Posted July 31, 2009 Did you ask for hotfixes or for the OS?It is against the rules to spread links to a finalized OS that is not in beta form any more. I never knew hotfixes were banned also :blink: Removed my links above in case. I asked for " someone to PM the link to the hotfix"..............result.....................warning. Link to comment Share on other sites More sharing options...
Malisk Posted July 31, 2009 Share Posted July 31, 2009 This is a General Distribution Release (GDR), so some sort of wide-scale update for something presumably important. Here's more info about what a GDR can be (under "More information"): http://support.microsoft.com/kb/824994 Software updates that address widespread critical issues, such as security vulnerabilities, and that are broadly released by Microsoft are also known as general distribution releases (GDRs). These software updates include the following: * security updates * critical updates * updates * update rollups * drivers * feature packs These software updates are created in a development environment that is separate from hotfixes. Link to comment Share on other sites More sharing options...
null_ Posted July 31, 2009 Share Posted July 31, 2009 It's not uncommon for a QFE to change the build string, it usually happens whenever a QFE changes the kernel itself (ntoskrnl.exe). Nothing to get excited over. Also, I wouldn't recommend that anyone install these until they are made public through official distribution channels, such as Windows Update or Microsoft Download. This will happen once they have been put through full regression testing, etc. With MSDN/TechNet and Connect testers getting their hands on the bits next week, I wouldn't be too surprised if these pop up on August 11th (patch tuesday). Link to comment Share on other sites More sharing options...
+Warwagon MVC Posted July 31, 2009 MVC Share Posted July 31, 2009 OP torrent link removed. Do not post download links to Windows RTM in this thread. Doing so will get you a warning. Link to comment Share on other sites More sharing options...
code.kliu.org Posted July 31, 2009 Share Posted July 31, 2009 It's not uncommon for a QFE to change the build string, it usually happens whenever a QFE changes the kernel itself (ntoskrnl.exe). Nothing to get excited over. QFT. Surprised it took so long for someone to set the record straight. Hotfixes have always bumped the QFE portion of the 4-part version (major.minor.build.QFE) of whatever file they update. We saw this in 2K, XP, 2K3, Vista, etc. This is as old as ... as ... something really old. The version that is reported when you look at a about dialog or the registry is taken from the file version of the kernel, so if a hotfix happens to update the kernel, then the updated file version will show up in the registry and about dialog. The only thing that's interesting about this is that MSFT is already prepping hotfixes for RTM. I guess we'll see what they are come Patch Tuesday on August 11. Link to comment Share on other sites More sharing options...
Gio Takahashi Posted July 31, 2009 Share Posted July 31, 2009 It's not uncommon for a QFE to change the build string, it usually happens whenever a QFE changes the kernel itself (ntoskrnl.exe). Nothing to get excited over. I figured that this would be the case. It just seems to make the most sense to me. Link to comment Share on other sites More sharing options...
hdood Posted July 31, 2009 Share Posted July 31, 2009 Well, they'll eventually want to plug up that OEM certificate problem that can be exploited by piraters. Not sure if it is related to this issue or not, though; it's pure speculation. It's impossible. The same thing has been possible for years and years. They cannot block certificates, because that would also block hundreds of millions of legitimate users. Link to comment Share on other sites More sharing options...
MagicAndre1981 Posted July 31, 2009 Share Posted July 31, 2009 (edited) it's a GDR update, not a LDR (Hotfix). And the build is not changed, it is still 16385. When the kernel is updates the BuildLabEx String is updated to the version of the new kernel. // Edit: fixed typo Edited July 31, 2009 by MagicAndre1981 Link to comment Share on other sites More sharing options...
ToneKnee Posted July 31, 2009 Share Posted July 31, 2009 it's a GDR update, not a LDR (Hotfix). And the build is not changed, it is still 16385. When the kernel is updates the BuildLabEx String is updated to the version of the new kernel. Link to comment Share on other sites More sharing options...
MagicAndre1981 Posted July 31, 2009 Share Posted July 31, 2009 sorry, buildnumber fixed. Link to comment Share on other sites More sharing options...
ToneKnee Posted July 31, 2009 Share Posted July 31, 2009 sorry, buildnumber fixed. It's okay, it's to stop the idiots from getting build numbers confused etc. Link to comment Share on other sites More sharing options...
kazuyette Posted July 31, 2009 Share Posted July 31, 2009 ZOMG ! A QFE changed the build number of teh kernel ! Kwik let's call teh Fox News !!:!111!!! Link to comment Share on other sites More sharing options...
M.F.D.K Posted July 31, 2009 Share Posted July 31, 2009 ZOMG ! A QFE changed the build number of teh kernel ! Kwik let's call teh Fox News !!:!111!!! Fox News too busy with Windows 8 leaked builds. Link to comment Share on other sites More sharing options...
kazuyette Posted July 31, 2009 Share Posted July 31, 2009 Fox News too busy with Windows 8 leaked builds. Yeah ! I forgot aboot those leaks of Win8 :D Link to comment Share on other sites More sharing options...
Recommended Posts