Vista Interim Build To Be Released Monday!


Recommended Posts

Interim Build To Be Released Monday! We are proud to announce that build 5365 is going to be released on Connect this Monday. This build is an Interim build which will include several bug fixes and some UI changes. It will feature as well the updated Internet Explorer UI. Also expected are better driver support and some optimizations to make Aero Glass run more smoothly. Also from what I heard is the Media Center has a better refined look and runs a lot smoother. Also there will be more gadgets and lots of bugs with them will be fixed as well in this build. Also the install may also be faster and optimized as well in this build. We think this is a great preview to see what’s to come of Beta 2 of Windows Vista.

New in build 5365:

*Sidebar Fixes/More Gadgets

*Improved Driver Support

*Welcome Center Changed (Updated)

*Several Bug Fixes

*Improved Install (Faster etc..)

(More info to come soon about improvements.)

For you anxious testers we expect to see this build around 1:00 PM EST Time.

Source:

http://www.hdrive.org/index.php?subaction=...t_from=&ucat=2&

I dont think it would be plubic, the BETA 2 might be, but i'm not sure. I just decided to post this so all of you can be aware of this,

Enjoy! :D

UPDATE: Now can be found on the Front page. Please contune to post coments! on both the front page, and this fourm :D

Edited by Tech_Kid_2006

Gonna get the screenshots hopefully later today for everyone to enjoy :D

And maybe something else :whistle: :rofl: (I get sniped by microsoft if I told you the link lol) :laugh:

Oh forgot Neowin would get there ninjas after me to if I did that lol

Wait till sometime in the (evening?) Monday PST time (@ Redmond). What? You didn't think that Redmond would be nice enough to just stick to good ole' GMT time releases, did you? :laugh:

And yeah, this won't be public, it will be interim, but won't be dubbed a "CTP" either.

But FYI, I don't expect it to be 5365. Why? Oh, just a little someone told us testers that 5361 was "old"...I wouldn't expect 5365 to be released. And besides, the 5365 rumors were instigated by Thurrot. He's usually no on the mark, but he's always close. But not on the mark. So I'm betting we'll see something even higher..

P.S Im the source and got my info from Microsoft so it is true but as you all know who the hell knows they may change it by like one build number you all know Microsoft. :laugh: :p

Oh and sorry about the EST Time guess Im not considerate of other sorry bout that I'll give GMT and PST time on there to but why should I?

The time thing is just a guess cause it seems its the exact time that microsoft released there other builds except for the past interim depends on if they have server problems etc.

P.S Holy just noticed how many answers you guys need lol!

Oh, just a little someone told us testers that 5361 was "old"

All builds they release to testers are "old" but it depends on what you call old.Cause they might of had this build compiled in february with a different build number and brought the stuff from that build into this one etc.

Trust me very confusing!

Edited by hypatech

"Im the source and got my info from Microsoft so it is true"

So tell me why we should believe you. You're proof is simply not there; whereas we (the testers) all do in fact have confirmation from Wendy about certain things.

The time reference wasn't regarding you're site's statement, but I will say that going around and plugging your own site is downright silly (See your posts at JCXP and AeroXp, which you just happened to join quite recently :shifty:). If its really worth anything, then the community (and not the adminstrators) will spread the news through the grapevine. Otherwise it seems like a publicity stunt.

They don't just "change one build number" -- if anything, the digit(s) will be changed, as a result of a re-compile.

No, this build won't have been compiled in Feburary. That's why the f'ing build tags have date and time stamps. Obviously you don't understand that each build has different components, of which may or may not have been worked on at different times, but ultimately, with each successive build, the raw code is re-compiled in the virtual lab.

No, its not confusing. You just make it seem that way.

And for the record, I don't know why you're so happy with yourself. Thurrot speculated and told us on the 14th in his WinInfo Short Takes that 5365 was being considered. So don't be giddy about your post on the 16th that is more rambling than news. Yea, kthks.

Edited by fisherman909

well sorry ok got the info on it on the 9th so ya!

Had to get permission to post it first!!!From Microsoft! :yes:

Well anyways :angry:

I will hopefully get the screenshots soon! :cry:

Gonna play Battlefield 2 for a bit now :yes: :D

So ttyl guys just pm me with any concerns etc!

Oh and just read his article does it say monday no! And he bs's through the article as usual lol :laugh: :rofl: :yes:

"The software giant considers the May CTP build as both Beta 2 and Release Candidate 0 (RC0)." wtf :blink:

Beta 2 is well Beta 2 lmao :laugh: :sleep:

OMG!!! I dont wanna flame but ur #%^&*( :angry: me off!

The official source has requested I dont say his name since Neowin dosnt like him since this community can be very mean at times! :rolleyes:

And what Im saying about the february thing oh nvm dont wanna stir things up :no:

Edited by hypatech

Of course you had to get permission. What other excuse would you come up with? (Not to mention your lack of proof)

About the Monday bit. You weren't first with that either. Wendy confirmed Monday in a post in the NGs on Saturday.

So you know, keep talking to yourself about the little exclusivness, go plug your website at all the nice forums you can find, and in a later part of life you will realize you have erred.

[edit] Two words. Anger management:laugh:. People who are secure in their beliefs have no reason to get angry. That's why I'm laughing at you instead.

About RC0/Beta 2. Alchin told Thurrot that that will indeed be the way Microsoft will announce it. But, you know, I challenge you to convince me that you have sources in Microsoft that are higher up than Alchin. And quit calling it the "May CTP", if it was a friggin' CTP, if wouldn't be called Beta 2 either, eh? Again, further proof that you don't have an accurate understanding of Microsoft's naming conventions, and how builds are released.

Anyways, you better get back to your game. You were leaving, apparently....

Edited by fisherman909

ugghhh :no:

for your info I got the news about the new build and release date on April 6th then told close friends on the 9th then told the public yesterday!

Man I just try to be nice then everone just #$%%^& me off :angry:

Lets see my history:

1.Info on WLM 3 months before WLM comes out and offering invites to Neowinians throught the Beta Recruitment Program.People dont beleive me but all my claims come true!

2.Beta Recruitment Program 2006-Offering Vista invites gets shut down because of flaming etc and turned into a disaster.

3.And now Im just trying to offer some info to people and get the news out there about the new build and changes etc!

And Guess what happens Disaster all of them! This is the third time Im thinking of just telling Neowin Member to(you now what) and bye!

Just trying to offer what I can!

If I remember correctly, this build won't be mailed to you - it's not going to be coined a CTP build, it'll just be an interim build. Microsoft only sends out major milestones (Beta 1, and eventually Beta 2), and occasionally a CTP build they think it worthy. So for now just wait for the download.

Edited by fisherman909

hypatech: Please stop, it's one thing to express your opinion and its the other, to post info, with out having proff. I know, you are a bit up set with fisherman909, but i have to go with him, next time, if you are gona post info like this, please put proff, ( ie; screenshots, links, etc) on what you are talking about.

well sorry ok got the info on it on the 9th so ya!

Had to get permission to post it first!!!From Microsoft! :yes:

Well anyways :angry:

I will hopefully get the screenshots soon! :cry:

Gonna play Battlefield 2 for a bit now :yes: :D

So ttyl guys just pm me with any concerns etc!

Oh and just read his article does it say monday no! And he bs's through the article as usual lol :laugh: :rofl: :yes:

"The software giant considers the May CTP build as both Beta 2 and Release Candidate 0 (RC0)." wtf :blink:

Beta 2 is well Beta 2 lmao :laugh: :sleep:

OMG!!! I dont wanna flame but ur #%^&*( :angry: me off!

The official source has requested I dont say his name since Neowin dosnt like him since this community can be very mean at times! :rolleyes:

And what Im saying about the february thing oh nvm dont wanna stir things up :no:

There's no WTF here, the May CTP is indeed Beta 2 and RC0 at once. Like a normal beta, it'll be public and everything...

Off-topic:

Smiley madness for you, right? It's unreadable! :laugh:

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • VS Code 1.123 introduces massive upgrades for persistent AI developer workflows by Paul Hill Microsoft has just released Visual Studio Code 1.123 alongside its annual developer conference, Build 2026. This release, as always, has a heavy focus on advanced AI agent integration and making the built-in browser more robust. Notably, this update brings big sync changes that keep your AI agents persistent across sessions. With this update, VS Code now supports cross-machine syncing for chat histories, touched files, repository contexts, and related PRs via GitHub accounts, tying users even more into Microsoft’s developer ecosystem. This update also introduces the new /chronicle command that allows you to query past sessions using natural language, generate instant standup reports, and get personal productivity insights. Microsoft has also made some improvements to network-dependent operations, it explains: “When a terminal command that is run by a local agent requires access to domains that are not configured as allowed domains, the command is automatically retried inside the sandbox with unrestricted network access. After that, if it still fails, it falls back to unsandboxed execution. This allows network-dependent operations such as git fetch to finish, while keeping filesystem protections in place.” Microsoft has not stopped there; in this update, it also allows developers to drag, drop, and pin multiple agent sessions side-by-side for easy code comparisons in real-time. It also introduces the Research Agent, accessible via /research. This is a read-only, depth-optimized tool that gets data from the web, local codebase, and GitHub to give you a Markdown report on complex APIs or unfamiliar code. Now, let’s talk about the integrated browser and some security enhancements. VS Code 1.123 features enhanced screenshot capture tools that allow for targeted Area Screenshots and Full Page Screenshots to send layout context instantly to AI chat. The address bar has also been revamped, supporting favorite pages and tab management. Finally, on the security front, this update introduces a safety-first two-hour delay on third-party extension auto-updates to safeguard against compromised or buggy releases. This release is now available for Windows, Mac, and Linux. If you have VS Code, keep an eye out for the update availability notification. If you still don’t have VS Code, you can get it here.
    • I'm hoping with the Surface Pro 12, I can use either USB-C for my Xreal One Pro glasses. With my Surface Pro 11 OLED X Elite, I have to plug them into the top port. The bottom port will power it, but nothing shows on the screen. Maybe it's my setting. When I plug in the glasses, I have it output only to the glasses. So maybe I need to turn on both displays with it in the top port, then switch the glasses to the bottom port and set it to output only to the glasses. And then hopefully Windows remembers the settings for either the top port and bottom port (one of the awesome features of Windows where it remembers the exact configuration when plugging in external monitors.
    • Forgive my ignorance, but the only difference I see here is that a USB-A is now a USB-C, so there are two of them. For the modern age (and I'd argue since 2020), most products would now come with USB-C as an option, if not the default. Display, charging, devices, etc on TWO connectors, sometimes all combined! So having 2 of those powerful ports is great for something this size! Meanwhile my Surface Pro (5) has a single USB-A port which I cannot even get display out to, instead relying on some Surface Connect dock which I don't have. That is a poor experience, not to mention expensive and not compatible with other devices. Thank God USB-C is mainstream!
    • wow. that color finally comes to Surface Pro. was always a little jelly when a friend had the sandstone Surface Laptop. I wonder how different this dune is from the sandstone. I'll be getting the dune version. always thought black and platinum were a little boring. I'll still have access to my blue Surface Pro 11 as it'll be a hand-me-down.
    • Looks a very subjective aren't they!? I like its simple design. I love the way Apple designs their products with function over form, minimalization, and simplicity over cluttered complex designs. Many, not all, of their products follow this trend, and the device becomes a tool rather than dominating the space. I do not however like their OS. I have never bought a Apple product, and while I'd consider the Neo for my wife, I am hoping there are better alternatives out there when her failing MacBook Pro 2017 finally stops. Fischer-Price is famously plastic, garish, and poorly made. Basically you're describing the Window Laptops the Neo competes against! This is how product design should be, and what Apple have often followed in recent years: https://tenprinciples.design/
  • Recent Achievements

    • One Month Later
      B2Proxy earned a badge
      One Month Later
    • One Year In
      MadMung0 earned a badge
      One Year In
    • Week One Done
      jefred earned a badge
      Week One Done
    • Apprentice
      JoeyNeo went up a rank
      Apprentice
    • Week One Done
      oliviaexpo earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      482
    2. 2
      PsYcHoKiLLa
      227
    3. 3
      Skyfrog
      70
    4. 4
      FloatingFatMan
      58
    5. 5
      Nick H.
      54
  • Tell a friend

    Love Neowin? Tell a friend!