Recommended Posts

The article lists plausible reasons though. And Microsoft hasn't officially announced they are going to do the RTM release today. All we know is they planned to release it to technet/MSDN today. But that announcement is several weeks old?

Are you just slow??? Seriously, it's like you haven't been keeping up? Win 7 has already RTM a couple weeks ago. OEMs are already testing it on their systems.

Guess this means Server 08 R2 should go up today as well. Look forward to testing how RDP goes between it and W7 machine. The changes in theory sound good.

Server 2008 R2 is apparently going RTW a "couple of weeks" after Win 7 RTW. So afraid you probably won't be seeing that today

This isn't a public release download like Beta 1 - crash; RC1 - semi-crash "I found this download link 6 hours early so neowin users that were up-to-date and didn't wait got their downloads easy and fast"

This is technet/msdn users only.

but I agree we'll see.

Are you just slow??? Seriously, it's like you haven't been keeping up? Win 7 has already RTM a couple weeks ago. OEMs are already testing it on their systems.

That's different than releasing it to Technet/MSDN customers though. If you know there is a serious flaw in the code, why unleash it on professionals who are going to do more than test installs against hardware?

I hope it happens today for those excited by the release. But I am not sure I would want to risk using it on any of my systems until they have patched the flaw.

I hope it happens today for those excited by the release. But I am not sure I would want to risk using it on any of my systems until they have patched the flaw.

Yes because God help you if your system eats up a lot of memory while you're doing a check disk on non-system drive before a patch can be released. You're right, it's not worth the risk.

That's different than releasing it to Technet/MSDN customers though. If you know there is a serious flaw in the code, why unleash it on professionals who are going to do more than test installs against hardware?

I hope it happens today for those excited by the release. But I am not sure I would want to risk using it on any of my systems until they have patched the flaw.

First - do you even know what chkdsk does? Second - if yes, do you use it? Third - if yes, are you using it during peak hours or during downtime?

FYI: MS is aware of this and they deemed it as by design and if anything they are leaving it up to a 0-day Windows Update. If you are really following that blog, then read the original and what Sinofsky wrote. The point is, it's not a serious flaw and it's release is not going to be stalled.

Risk? Really, like if you answered no to any of the questions above you are going to now go chkdsk/r by mistake or just for the heck of it? You can keep waiting then, cause the patch won't come until Oct 22nd.

Big risk, because I may accidently run chkdsk /r on a non system volume.

As big a risk as accidentally running format c: on my disk.

That's different than releasing it to Technet/MSDN customers though. If you know there is a serious flaw in the code, why unleash it on professionals who are going to do more than test installs against hardware?

I hope it happens today for those excited by the release. But I am not sure I would want to risk using it on any of my systems until they have patched the flaw.

Let's not blow this ridiculous bug out of proportion here! Good lord. You're making it sound like anyone who installs this is going to have imminent data loss and hard drive corruption. It's a bug that 99.9% of people will NEVER SEE. This is why it escaped detection in the beta cycles to begin with. Since we are aware of the bug, we can all simply "not do that" and be fine. Really, the overreaction to this is mind boggling.

Let's not blow this ridiculous bug out of proportion here! Good lord. You're making it sound like anyone who installs this is going to have imminent data loss and hard drive corruption. It's a bug that 99.9% of people will NEVER SEE. This is why it escaped detection in the beta cycles to begin with. Since we are aware of the bug, we can all simply "not do that" and be fine. Really, the overreaction to this is mind boggling.

+1

Like I implied before, it's not something that just happens or that you could easily do on accident.

You know a good way to check your disk of errors is to format it. You can't have any errors if their's no data. Format! you know you want to. Just do it, you don't need to chkdsk, everything is great. Your drive doesn't have any issues it's just tired of running XP and WANTS YOU TO FORMAT IT!!!

Like a memory leak to BSOD is anything new. If you are scared of a little memory leak and BSOD then you shouldn't be using Windows and should be on technet or msdn.

Bit early for christmas don't you think?

Christmas? What's that? This is Windowsmas. Everyone knows that this isn't actually the day Windows was born but as long as we keep the true spirit in our hearts I think Balmer will approve.

Yes because God help you if your system eats up a lot of memory while you're doing a check disk on non-system drive before a patch can be released. You're right, it's not worth the risk.

lolz...

I'm wondering, is this just a kind of "MS haters" thing? People desperately wanting this product to fail?

This bug does not appear consistently. It does not damage a system. A user has to go out of his way to create the conditions where this bug MIGHT appear, and the bug occurs in a diagnostic tool (as opposed, say, to a frequently-used end user app), under a certain specific condition.

How is this a "showstopper", exactly?

Christmas? What's that? This is Windowsmas. Everyone knows that this isn't actually the day Windows was born but as long as we keep the true spirit in our hearts I think Balmer will approve.

What is this - a Seinfeld episode? Windowsmas for the rest of us? Hahaa

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

    • No registered users viewing this page.
  • Posts

    • Microsoft OneDrive is getting a simple yet much needed feature by Sayan Sen Microsoft has been steadily expanding OneDrive’s file management capabilities over the years, including for shared content and shortcuts, although it has had its flaws, too. The cloud storage platform introduced support for folder shortcuts several years ago, allowing users to pin frequently accessed shared folders from OneDrive, SharePoint, and Teams. Now, Microsoft is refining that experience further with a new way to organize those shortcuts as revealed in a recent Microsoft 365 roadmap addition. Previously, shortcuts added through the “Add shortcut to My files” option would appear alongside all other files and folders in the root of a user's OneDrive. And although it's meant to be useful, this approach could also create clutter along the way, especially for heavy users who may have to work with large numbers of shared folders across multiple projects and teams on their systems. This is where Microsoft’s latest feature comes in, as it is looking to address this inconvenience by giving users the option to place new shortcuts inside a dedicated “Shortcuts” folder instead. The feature is designed to keep shortcut links organized into a single location instead of scattering throughout the main OneDrive directory. Hence, the idea is to make navigation and usability easier and simpler. The first time a user chooses this option, OneDrive will automatically create the folder, and to help make it stand out from the other folders, the Shortcuts folder will have a distinct visual identity featuring a unique color and a building-style icon. That being said, the new Shortcuts will behave just like any other folder in OneDrive, and as such, users will be able to move it to a different location, rename it, share it with others, or remove it entirely if they prefer a different structure. You can view the entry on the Microsoft 365 roadmap website here. Currently, the feature is in the "in development" phase, but the tech giant expects the rollout to start next month (July 2026). Do keep in mind, though, that new feature rollouts often get delayed.
    • 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.
  • 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
      60
    5. 5
      Nick H.
      54
  • Tell a friend

    Love Neowin? Tell a friend!