Vista Build 5365 released too testers on connect


Recommended Posts

5365 is running so smooth here! Animations and Aero Glass are working with NO slowdowns. The only problem I have at the moment is when a Windows Security message pops up and my screen flashes for about 2 seconds before and after I click it. Any workarounds? Thanks

^^ You can anonymously report bugs through MBC if your so inclined; even if your not a BT. You just won't be able to access feedback etc.

No, bad idea.

Microsoft often asks for additional information regarding bugs which is directed at the person who posted that bug. If you're not in the beta then there's no way to respond to these requests. The bug will eventually be closed but it is a big waste of time for MS beta staff.

been using this build on a couple of my pcs, its is stable for the most part but the ics does not work. the widows secuirty were it switches you to a other screen is a pain in the neck and sometimes does not work. got deamon tools working and office 12 beta now works(jusr problem with black boards on it and not showing glass)

No, bad idea.

Microsoft often asks for additional information regarding bugs which is directed at the person who posted that bug. If you're not in the beta then there's no way to respond to these requests. The bug will eventually be closed but it is a big waste of time for MS beta staff.

It might seem useless to you, but its more pro-active than bitching at a forum, which nobody can guarantee will be read by Microsoft. :blink:

If they didn't want to "waste time" (in your words) with anonymous bug reports, they wouldn't have given users the option. No two ways about it.

Why is it that I never received the link to download the 5365 build from connect. I've been a member on connect as well as the OEM System Builder site for some time now. I am also pre-registered for beta testing. I've received all the other builds prior to this one. Any help would be great.

Why is it that I never received the link to download the 5365 build from connect. I've been a member on connect as well as the OEM System Builder site for some time now. I am also pre-registered for beta testing. I've received all the other builds prior to this one. Any help would be great.

I don't think I can help you, but if I were you, I would go to the newsgroups and ask it there. Maybe someone from the team will help you? Or you could always send an email to the adres provided on connect.

^^ He's correct. Wendy will be more than happy to help appropriate members, provided that you email them with your problems to the email address listed on the Longhorn/IE 7 Beta page -- they don't have staff sitting there all day working out who's permissions etc have been screwed up.

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

    • No registered users viewing this page.
  • Posts

    • I don't understand the vision. Do people really want to buy a new computer from Dell with 6 browsers installed? We all keep asking for Microsoft to stop having so much junk on their OS, and adding a bunch of browsers seems to go against that. Ideally, we would just be asked what browser we want during OOBE but Google is just going to pay Dell a bunch of money to include Chrome. Additionally, would you want your phones to start including all the browsers too when you get them? The only thing I ever wanted was to be able to uninstall IE or edge and I believe you are now able to. I do agree that microsoft needs to chill with their "are you sure you don't want to try edge before you install chrome" ads when going to download chrome.
    • The funny thing here is that like 70% or so of the web browser users use 'Google Chrome' as web browser. What I don't understand is that why on earth would ANYONE choose 'Google Chrome' on Windows when 'Microsoft Edge' is not just better in most things, but it's already there right out of the box for the Windows users. Microsoft Edge has less data collection (yes, that's a fact), less RAM usage and is more optimized for Windows (as it's a Microsoft product) right out of the box. I'm sure you will come with the argument of bloat in Microsoft Edge. Sure, but most of that can be fixed with a simple tool (there are many good ones out there for this). Yes, that require a couple of clicks in the same way as it requires several clicks to install 'Google Chrome'. And I'm sure you really love the 4 GB of AI-slop 'Google Chrome' is downloading without you agreeing to it. Fun right? Sure, the way Microsoft is pushing Microsoft Edge on users might not be the best way of doing it and might need to change. But I would never choose 'Google Chrome' over 'Microsoft Edge' today anyways. I'm sure there was a period back in the days when 'Google Chrome' actually was better in most things, but that period is not today.
    • JetBrains rolls out IntelliJ IDEA update with Markdown preview fixes and more by David Uzondu Image via JetBrains IntelliJ 2026.1.3 from JetBrains has landed, bringing several highly requested bug fixes that target common UI glitches and terminal rendering issues. If you run tmux inside the integrated terminal, the IDE no longer renders the cursor above the active line. The Markdown preview bug, which was fixed in this release, had annoyed developers for quite some time, as the preview pane failed to render images saved outside the project directory. Instead of displaying the actual image, the IDE simply showed a broken image icon, a problem that stuck around for two years before this update. Over on Windows, developers running WSL can now use wsl.exe to spin up their environments without losing terminal functionality. In previous builds, launching a terminal shell with something like wsl.exe -d ubuntu inside a Windows-based project broke both shell integration and active process detection. Other bug fixes in this release include: An issue where Gradle sync incorrectly reported success as a failure on WSL when using Gradle 9.5.0. A syntax highlighting bug that flagged valid Java for-loop initialization blocks with multiple statements as incorrect. A warning bug that triggered a false non-null local variable alert when using JSpecify annotations. A database generation bug that hid the option to use a DELETE statement instead of a TRUNCATE checkbox. A Kotlin highlighting failure where an assertion error in the Gradle redundant library inspection broke error highlighting. A UI bug where the ComboBox popup lacked a maximum height restriction. A Snowflake syntax error where DataGrip failed to support the "create temp" command. A Svelte syntax parsing failure that incorrectly flagged quotes inside inline expressions. A VCS repository manager deadlock that triggered thread pool exhaustion. A memory leak where the LazyTree component kept all previous versions of a tree in memory. IntelliJ 2026.1.3 is the third bug fix release for the IntelliJ 2026.1 series. The first one landed back in April with a fix for the WSL Python interpreter freeze, another fix for guest participants using Emmet abbreviations, and corrected WildFly server deployment errors.
    • That stupid annoying Sign in with Google on all these sites now... get the fk outta here
    • I was just being silly based on David Uzondu's comment ☺️
  • Recent Achievements

    • Collaborator
      Asgardi earned a badge
      Collaborator
    • Conversation Starter
      mobandz earned a badge
      Conversation Starter
    • Apprentice
      fernan99 went up a rank
      Apprentice
    • One Month Later
      nothanks earned a badge
      One Month Later
    • One Month Later
      B2Proxy earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      469
    2. 2
      PsYcHoKiLLa
      243
    3. 3
      Skyfrog
      79
    4. 4
      FloatingFatMan
      73
    5. 5
      Michael Scrip
      60
  • Tell a friend

    Love Neowin? Tell a friend!