Recommended Posts

stated in a chat today that Beta 2 is coming, and thats when people will get the media released to them via mail. I never got any yet and they said major milestones only come in the mail (I opted for it) and yeah.

But build numbers don't mean much it seems, 5372 may seem like a low #, but each number doesn't mean one bug fixed, I forget how it works but its confusing.. thanks for the info Andy13

Edited by Simon

damn... vista dont excite me anymore. probably 5372 will have all windows component (ie,defender,mail,dvd maker,wmp11,calendar etc) to be fully working or at least 95% usable. and probably some minor polishing on the UI as well. i hate the feeling when i can say "err, i think i saw beta 2 back in early april.. oh wait, thats 5342" :wacko:

They are already running compiles in the winmain branch that are in the 537x range. Beta 2 will most DEFINETELY be higher than 537x. If they somehow don't give us a build by the end of this month, and then don't have much else to say; and, for some odd reason, Beta 2 is a 537x-range build, I'll be deeply surprised.

And lastly, remember guys, its THURROT. There's no reason to believe him over a straight, un-edited, quote from Microsoft in the NGs. When they say it, I'll believe it.

Given the fiasco surrounding 5365, its hard to believe they'll give it to us. But I'll give Thurrot the little benefit of the doubt, since Donnelly said something like "we're not giving 5365 to you today". Nevertheless, I'd take Thurrot's words with more than a grain of salt. I'd take them with the entire salt shaker.

Edited by the_ubernated

For MS to have time to stabilize the beta 2 build, I believe they'd need to branch it at least about a month before its release, which isn't too far from now (it basically IS pretty much now), which would make a build like that possible. Of course, "winmain" builds would be much further ahead at the time, but MS won't take a build from that branch and just release it at release day. ;)

That's at least what's usually happened with the CTP builds, and why CTP build numbers are clearly lower than the bleeding edge builds at the time of the CTP release. One can't point at where Microsoft will be in a month from now and say "these builds will be much higher" if discussing a stabilized build like Beta 2. In build tag speech, you only can if talking about winmain and not idx builds.

As for Thurrott, I have no problem with his predictions; they should just be taken like any early estimates. I have no doubt he's actually getting these numbers from actual Microsoft employees, however, things change, and Thurrott usually assumes his readers are aware of that. More often than not, they aren't, which leads to all these flames on Neowin for not nailing down the details correctly and "lying to us" when the most likely causes are change of plans and not nearly as many evil intents to mislead either from him or Microsoft.

Edited by Jugalator
calm ubernated

I thought the whole post they made sounded very calm and they have the right to say whatever they want. If he wants to say a few words about Paul Thurrott, then he can. I think lately little Paul has proven how much of a jerk he is and if people have something they want to say about him then let them.

Like I said in the comments on the frontpage about Pauls new rant. He ranted and got a suppossed build number for beta 2 from someone at Microsoft. He whined like the little kid he is to get something out of them. That's how he works and it's sad. With how immature he is now, I could only imagine what he was like as an actual kid.

As far as that build number being beta 2, it just doesn't sound right. Then again it really wouldn't surprise me if it was right. They use old builds as the releases all the time. Just look at the Internet Explorer 7 Beta 2 that JC leaked compared to the older and official build Microsoft released. But I thought for sure that BETA 2 would be a 54XX build since it wouldn't be out until May.

Edited by NightmarE D
This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Are they marketed as an entry into astronomy or astrophotography? I do astrophotography. With big rigs, lots of computers, cables and headaches. I love it. And by learning this ridiculously complex hobby, I’ve learned about the objects I’m shooting. Astronomy followed from photography.
    • Microsoft confirms Recycle Bin bug across all versions of Windows by Usama Jawad A couple of days ago, we reported that the latest Patch Tuesday update has seemingly resulted in a lot of issues for many users, including OneDrive and Dropbox access problems, BitLocker recovery lockouts, and BSODs. Although Microsoft is yet to acknowledge these bugs, it has confirmed another, relatively smaller issue across all supported versions of Windows. In an update on its Windows Release Health Dashboard, Microsoft has confirmed that after installing June's Patch Tuesday update (KB5094126), you'll experience unexpected behavior when leveraging Recycle Bin. Basically, when you attempt to delete an item from the Recycle Bin, the confirm dialog will show you the internal file name of that content rather than the actual name. For example, the file may be named abc.png, but the confirm dialog will ask if you're sure that you want to permanently delete $Rxxxxx.png from the Recycle Bin. This is pretty much it for the scope of the bug itself; it just displays the wrong name in the confirm dialog. The correct name will be shown in the list view of the Recycle Bin and if you restore the file, it will return with the correct name as well. This issue affects pretty much all supported versions of Windows client and server, including: Client: Windows 11, version 26H1; Windows 11, version 25H2; Windows 11, version 24H2; Windows 11, version 23H2; Windows 10, version 22H2; Windows 10 Enterprise LTSC 2021; Windows 10 Enterprise LTSC 2019; Windows 10 Enterprise LTSB 2016 Server: Windows Server 2025; Windows Server 2022; Windows Server 2019; Windows Server 2016; Windows Server 2012 R2; Windows Server 2012 As things currently stand, Microsoft is working on a concrete solution that will be released in a "future" Windows update. It remains to be seen if the firm will wait till the next Patch Tuesday or roll out an out-of-band (OOB) fix. The good news is that commercial customers can deploy a workaround right now, but they will have to reach out to Microsoft Support for Business for additional details.
    • They said by this time everyone will have flying cars. WELL...
    • A study by physicist Henry Tye of Cornell University suggests that the universe may not expand forever. Instead, it could eventually stop expanding, begin contracting and end in a "Big Crunch" roughly 20 billion years from now. Maybe not as we now know that time can flow backwards.
    • Of course. Simply reverse the polarity.
  • Recent Achievements

    • Week One Done
      Jordan Smith earned a badge
      Week One Done
    • Reacting Well
      BizSAR earned a badge
      Reacting Well
    • First Post
      AndreaB earned a badge
      First Post
    • Week One Done
      Huge Trailer earned a badge
      Week One Done
    • Week One Done
      Classifyskilleducation earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      578
    2. 2
      +Edouard
      184
    3. 3
      PsYcHoKiLLa
      75
    4. 4
      Michael Scrip
      72
    5. 5
      neufuse
      64
  • Tell a friend

    Love Neowin? Tell a friend!