Windows 7 build number "changed"

[DJG]

My first WEI reassessment right after rebooting with the updates resulted in ... a BSOD! Woo-hoo!

I reset & rebooted and no problems since then. My WEI hasn't changed though, which is fine. The booting does seem to take less time while the screen goes black before the login screen appears.

One very noticeable change: the memory diagnostics option in the Windows boot menu is gone! Why? I liked that option there. You can still get the mem diag on reboot by using the Mem Diag utility in the Sys Admin folder, but that was so handy. I frankly can't see the logic behind removing it.

Can anybody else who did the updates confirm their Mem Diag option is gone from the Windows boot menu? Or did the BSOD eat my MemDiag?

 

[Zidane24]

My first WEI reassessment right after rebooting with the updates resulted in ... a BSOD! Woo-hoo!

I reset & rebooted and no problems since then. My WEI hasn't changed though, which is fine. The booting does seem to take less time while the screen goes black before the login screen appears.

One very noticeable change: the memory diagnostics option in the Windows boot menu is gone! Why? I liked that option there. You can still get the mem diag on reboot by using the Mem Diag utility in the Sys Admin folder, but that was so handy. I frankly can't see the logic behind removing it.

Can anybody else who did the updates confirm their Mem Diag option is gone from the Windows boot menu? Or did the BSOD eat my MemDiag?

lmao lmao lmao...that first line absolutely got me there

 

[poin2]

no, lol. when u BUY Windows in October it will be 16399 (unless anymore of these hotfixes are released in the meantime, lol)!

I'd expect the updates might start showing up on Windows Update after the broader August 6 release, and assumably they should make it to OEM's in time to get slipstreamed into their own installs.

BUT, if they've already started actually "manufacturing" from the RTM build, 16385 would still be what shows up in October.

Whatever shows up on Technet/MSDN should be the main public build. When IT people evaluate things, they need to know in advance if they're going to be applying hotfixes to the official release and exactly what they are, etc. If they're already slipstreamed into the August 6 release, I'd expect it's a sign they made it in time for the October 22 release, too.

But otherwise the shelves will hold 16385. They have to really truly get things manufactured, and after RTM, hotfixes are supposed be hotfixes, not things that can still get integrated into the original gold master.

 

[DJG]

Well, that boot update sucks if you're into OC'ing. I used to go to the BIOS, make changes to my OC config, exit the BIOS, then select mem diagnostics in the Win boot menu to get a first check of my settings. If it was NFG, just ESC to the BIOS again, tweak the OC, then again hit the mem test in the Win boot menu. I can keep doing that tweak-check cycle real quick over & over without booting Windows up.

Now I have to boot Windows with a good config, select the mem test util in Windows, reboot, change the config to the new one in the BIOS, now the mem test will start after the BIOS exit. But if I have to tweak again, I have to go back to the BIOS, reset to a good config again and go through the whole boot into Windows cycle again ... this is progress??? :mad2::mad2::mad2:

 

[Tews]

Well, that boot update sucks if you're into OC'ing. I used to go to the BIOS, make changes to my OC config, exit the BIOS, then select mem diagnostics in the Win boot menu to get a first check of my settings. If it was NFG, just ESC to the BIOS again, tweak the OC, then again hit the mem test in the Win boot menu. I can keep doing that tweak-check cycle real quick over & over without booting Windows up.

Now I have to boot Windows with a good config, select the mem test util in Windows, reboot, change the config to the new one in the BIOS, now the mem test will start after the BIOS exit. But if I have to tweak again, I have to go back to the BIOS, reset to a good config again and go through the whole boot into Windows cycle again ... this is progress??? :mad2::mad2::mad2:

Hey, you chose to download and install unknown files from a site well... I wont go into it .. so you really have no one to blame but yourself .... go complain on the site where you got the "updates"..

 

[DJG]

Hey, you chose to download and install unknown files from a site well... I wont go into it .. so you really have no one to blame but yourself .... go complain on the site where you got the "updates"..

Relax, Tews - I'm well aware of the dangers of the bleeding edge :shock:.

But if this reflects the state of the "final final", then it does suck if you OC and liked the convenience of what is a very nice mem test built into Windows.

I guess I should've put a :sarc: and ... .

Maybe they figured for the mainstream they didn't want the test there? And I wonder if there's some way of enabling it. I couldn't find anything obvious in BCDEDIT or MSCONFIG.

I can always restore the backup image I made two minutes before I applied the updates . But then that might be gone in Oct when the updates hit. Oh, well. Maybe in the Windows 7 Ultimate Overclockers Edition :roflmao:

 

[harpua]

If you don't like the effects of any particular update, can't it be uninstalled?

 

[HamidFULL]

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?!

 

[Zidane24]

Relax, Tews - I'm well aware of the dangers of the bleeding edge :shock:.

But if this reflects the state of the "final final", then it does suck if you OC and liked the convenience of what is a very nice mem test built into Windows.

I guess I should've put a :sarc: and ... .

Maybe they figured for the mainstream they didn't want the test there? And I wonder if there's some way of enabling it. I couldn't find anything obvious in BCDEDIT or MSCONFIG.

I can always restore the backup image I made two minutes before I applied the updates . But then that might be gone in Oct when the updates hit. Oh, well. Maybe in the Windows 7 Ultimate Overclockers Edition :roflmao:

Laughing about an Overclockers Edition...you just gave me an idea for a new build to consult the rest of LiZi about

 

[DJG]

If you don't like the effects of any particular update, can't it be uninstalled?

Yes, you can. In Win Update there's an option for listing all applied updates and removing one. In situations like this I prefer to make a system image backup before the updates (only takes me a bit over a minute) which would (IMO) provide me with a cleaner "before" than undoing an update.

However, since this update touches both the boot manager AND the kernel, I probably want whatever fix they did to the kernel, so the boot mem test option becomes a secondary consideration.

Simul-Post Edit :

Laughing about an Overclockers Edition...you just gave me an idea for a new build to consult the rest of LiZi about

Cool! Bring it on! or out, or off, or something ...

 

[knuckles84]

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.

 

[harpua]

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.

 

[HamidFULL]

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?

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?!

 

[HamidFULL]

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?!

 

[knuckles84]

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??

 

[Dinesh]

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.

 

[johnwillyums]

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

 

[xendrome]

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.

 

[DataMan47]

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!

 

[swarfega]

@xendrome: well said tbh.