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

    • Nobody is buying a PS5 only for playing Until Dawn 2. Their loss.
    • If you actually used it instead of responding like a petulant child you might be surprised. I switched from Google some time ago and have been very satisfied.
    • I am one of the first people to use the DXVK technology. In the channel below you can see some videos that I have made using this technology, including Assassin's Creed Odyssey. https://www.youtube.com/@nahum7995/videos Assassin's Creed Odyssey experienced several bugs and technical issues during its first months after release. It launched with its own fair share of funny but frustrating glitches. I ran it on DXVK 9 days after its release and I played it for many hours but didn't see a single significant bug on Linux. Assassin's Creed Odyssey is widely celebrated for pushing the franchise in bold new directions and specifically for nailing several elements better than any other title in the AC series: Player Choice & Branching Narrative, The Mercenary & Cultist System, Mythological Integration, Overpowered Combat Abilities, Open World Exploration But what I'm trying to point out is that this game wasn't quite playable on most windows systems, until a few months after its release when most of the bugs were fixed. However, on Linux it ran completely flawless from day one, although DXVK had seen little development and refinement at the time. What do you think the situation will be in 2026 now that most bugs and glitches of DXVK have been completely eliminated? This is information from Google about these situations that I am quoting. In many cases, using DXVK (a translation layer that converts DirectX 9, 10, or 11 into Vulkan) can result in more stable frame times and higher performance than native Windows rendering. This happens primarily by bypassing driver overhead and multithreading draw calls that were previously restricted to a single CPU core. Older APIs (like DirectX 9 and 11) are largely single-threaded on the CPU side. DXVK translates these calls to Vulkan, which is highly multi-threaded. This reduces CPU-bound stuttering on weaker processors. In certain cases, GPU manufacturers (especially AMD) have significantly better and more modern Vulkan drivers than they do for legacy DirectX. Vulkan gives developers—and in this case, the translation layer—closer control over how resources are held in VRAM. This can prevent micro-stutters and sudden frame drops during chaotic gameplay. Yes, certain games, particularly older DirectX 9 to 11 titles, can run with fewer crashes on DXVK than on native Windows. By intercepting DirectX draw calls and translating them into the modern, highly efficient Vulkan API, DXVK bypasses the limitations and poor driver support that cause instability in aging game engines. PlayStation 1, PlayStation 2 and PlayStation 3 can be easily and perfectly emulated on Linux. In fact, modern Linux emulators offer high-performance upscaling, widescreen patches, and automatic controller mapping out of the box.                                                                                                                                                                                                                                                                                                                                 PlayStation 1/2/3 games look drastically better on Linux thanks to resolution upscaling. Furthermore, it is also a fact that you cannot play many fun games on Windows either, isn't it? - The Nintendo Switch has an extensive library of exclusive games. - PlayStation has an extensive library of exclusive games - Android has "mobile-exclusive" games, meaning they are exclusive to mobile devices (iOS and Android) and aren't available on PC or consoles. And finally, it is also the case that in the next five years there will be games that millions of people will say you absolutely must play and that they want to play this specific game that released a few days ago. However, the other side of this story is that currently, absolutely no one cares that they cannot play these upcoming games right now.
    • Flameshot 14.0 RC3 by Razvan Serea Flameshot is a free and open-source, cross-platform tool to take screenshots with many built-in features to save you time. Using Flameshot is as simple as launching, dragging the selection box to cover the area you want to capture, making annotations as needed in on-screen and saving the shot to your computer, all with a very simple and straightforward interface. Flameshot allows users to simply upload their screenshots directly to the cloud in order to easily share it with others. You can upload your image directly to Imgur with a single click and share the URL with others. In-app screenshot editing - You can choose to add an arrow mark, highlight text, blur a section (blur or pixelate an area), add a text, draw something, add a rectangular/circular shaped border, add an incrementing counter number, and add a solid color box with Flameshot's built-in editing tools. Command-line interface (CLI) - Flameshot has several commands you can use in the terminal without launching the GUI via a command line interface. The command line interface lets you script Flameshot and use it as the subject of key binds. Flameshot 14.0 RC3 changelog: Translations update from Hosted Weblate by @weblate in #4612 Translations update from Hosted Weblate by @weblate in #4619 Fix pin position on Windows for scaled screen by @ElTh0r0 in #4614 Cmake Analyzers by @ElTh0r0 in #4613 Translations update from Hosted Weblate by @weblate in #4632 fix(macos): prevent config tab content from rendering behind tab bar by @Mitnitsky in #4627 fix(macos): use CGRequestScreenCaptureAccess instead of grabWindow for permission request by @Mitnitsky in #4617 Fix KDE Plasma keyboard shortcut config file by @ElTh0r0 in #4637 fix(macos): fix clipboard copy failing from tray and GUI by @Mitnitsky in #4629 feature(macos): show dock icon when config window is open by @Mitnitsky in #4628 Option to disable tray icon on Windows by @ElTh0r0 in #4634 Translations update from Hosted Weblate by @weblate in #4642 fix(macos): make fullscreen capture overlay configurable by @Mitnitsky in #4622 Update GH actions using Node.js 24 by @ElTh0r0 in #4660 fix issue with screen selection in non interactive mode by @borgmanJeremy in #4667 Uniformize both spec files + ninja build openSUSE by @QuentiumYT in #4658 screengrabber: pass non-empty parent_window to xdg-desktop-portal by @artefaktor93 in #4664 Allow multiple flameshot GUI instances (fix for #3177) by @ElTh0r0 in #4680 Unify Linux ARM CI into Linux CI (also drop QEMU) by @theofficialgman in #4702 respect system proxy settings by @borgmanJeremy in #4674 Replace ifdef LINUX with UNIX to include BSD systems by @ElTh0r0 in #4700 Download: Flameshot 14.0 RC3 | 18.1 MB (Open Source) Download: Flameshot Portable | 53.0 MB Links: Flameshot Home Page | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
  • Recent Achievements

    • One Month Later
      nothanks earned a badge
      One Month Later
    • 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
  • Popular Contributors

    1. 1
      +primortal
      490
    2. 2
      PsYcHoKiLLa
      233
    3. 3
      Skyfrog
      78
    4. 4
      FloatingFatMan
      68
    5. 5
      Michael Scrip
      58
  • Tell a friend

    Love Neowin? Tell a friend!