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

    • Simple answer is yes, you will still get the Windows updates and as long as browser is up to date, you will be good. Only thing secure boot does is protect you against boot level threats and make it harder to install other OS's. I've been looking into this pretty thoroughly lately myself as wifes computer has secure boot disabled plus my other, older computers that run Linux, don't have secure boot enabled. Have seen all kinds of questions about this on the Linux Mint and MX Linux forums. Just don't suddenly enable secure boot now.
    • How many other companies will follow Ford's lead? Or, have they already gotten lazy and become enslaved to AI--and now can't figure out how to get out of that mess.
    • Why would any self-respecting intelligent person follow any recommendation by Donald's GOP administration? With almost two years of fabrications, deceit, and blatantly illegal behavior, why believe them now? They had best be gone after the November 2026 election, so we'll wait and see.
    • AltSendme 0.4.1 by Razvan Serea AltSendme is a minimal, cross-platform application designed for fast, secure, and private peer-to-peer file transfers. It allows users to send files or entire directories directly between devices without relying on cloud servers, accounts, or any personal information. Everything is encrypted end-to-end using modern protocols like QUIC and TLS 1.3, ensuring both strong security and low-latency performance. Transfers are verified with BLAKE3 for data integrity, and interrupted downloads automatically resume, making the experience reliable even on unstable connections. You can transfer anything—images, videos, documents, and more. Integrity checks are performed on both ends, so your files are automatically verified for correctness during both sending and receiving. AltSendme works seamlessly across local networks or long-distance links, capable of saturating multi-gigabit connections for extremely fast delivery. With built-in NAT traversal and encrypted relay fallback, it connects devices almost anywhere. The app integrates with the Sendme CLI and will soon support mobile and web platforms. Fully free and open-source, AltSendme offers a lightweight, privacy-first alternative to traditional cloud-based services, removing size limits, upload costs, and unnecessary data exposure. AltSendme 0.4.1 changelog: Release Highlights Self-hosted relays: Run your own iroh relay so transfers don't rely on public infrastructure. Includes a full deployment template in deploy/relay/ with Docker Compose for a VPS and configuration examples for production use. Fly.io support: One-click deploy template for Fly.io, including a quick-start config (fly.dev.toml) for testing without a custom domain, plus production setup with Let's Encrypt and your own hostname. Relay settings UI: New Settings → Network panel to choose how AltSendme connects: automatic public relays, custom self-hosted URLs (with optional auth token), or disabled. Test connections, verify latency, and see live relay status in the footer. Disable relays: Turn off relay servers entirely when you only need same-network transfers (e.g. LAN). Direct connections only. No relay hop required when devices can reach each other. Android graduates from beta: Android is now part of the regular release cycle alongside desktop. APKs ship with each version (universal, arm64, and armv7). Other improvements Private relay access control via shared auth token Relay fallback notifications when a custom relay is unreachable Broadcast mode toggle in sharing settings Android release build fixes (split-per-ABI APKs, universal APK preservation) UI polish: mobile safe-area insets, dropzone layout, transfer progress animation Bug fixes for minification-related serialization issues and system tray icon loading What's Changed feat(relay): add relay status functionality and settings UI (a120cdf) feat(relay): implement custom relay server configuration and verification (51276c7) feat(relay): add configuration for private relay access and enhance observability features (48fbabf) feat(relay): enhance relay URL validation, display connection status (d4fffa0) feat(relay): add RelayChangeGuard component and enhance relay-related translations (16ba514) feat(broadcast): add toggle setting for broadcast mode in sharing UI (ca6d977) fix(relay): correct QUIC discovery port, pin image, templatize fly.dev (52a2ba5) fix: More broken serialization due to minification (67491a9) fix(android): preserve true universal APK across per-ABI builds (e9f256f) fix(ui): conditional safe-area insets padding on mobile (1182f0e) refactor(transfer): CircularRing component animation fix (944572b) chore(android): drop x86 and x86_64 release APKs, keep universal+arm64+armv7 (34ada0b) Download: AltSendme 0.4.1 | ARM64 | ~9.0 MB (Open Source) Download: AltSendme for MacOS | Android Links: AltSendme Home Page | GitHub | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • You are mostly right about the ephemeral nature of it. As I mention in the article, if you dont add a second device or take a backup of your account before uninstalling it, then yes you will lose access to your account. That said, in terms of actual user experience when you sync multiple devices your message history carries across and there's also a Saved Messages chat like there is on Telegram to send messages and attachments between your installs. But yh, what you point out are correct and its not trying to emulate Messenger or Telegram.
  • Popular Contributors

    1. 1
      +primortal
      495
    2. 2
      +Edouard
      225
    3. 3
      PsYcHoKiLLa
      150
    4. 4
      Steven P.
      75
    5. 5
      FloatingFatMan
      71
  • Tell a friend

    Love Neowin? Tell a friend!