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

    • The sweet release of death has never looked more appealing.
    • Meh, just another dongle-haven downgrade compared to my Surface Pro 7+. Whenever I decide to upgrade in the next decade or so, it certainly won't be another microslop Surface with this enshitification trend they've been having after the Surface Pro 7+. Hopefully a future generation of the Framework 12 will be a real upgrade...
    • This could exactly be how our Sun ends but it's not as simple by Sayan Sen Image by Drew Rae via Pexels An international team led by Université de Montréal (University of Montreal) PhD student Érika Le Bourdais has found that the ancient white dwarf star LSPM J0207+3331 is still pulling in planetary debris, even though it has been cooling for about three billion years. White dwarfs are dense, Earth-sized stellar remnants left behind when Sun-like stars exhaust their nuclear fuel and shed their outer layers. The star, located 145 light-years away in the constellation Triangulum, is the oldest and coldest white dwarf known to have a surrounding disk of dust. The star was first spotted in 2019 by a citizen scientist through the Backyard Worlds: Planet 9 project. Its cool temperature immediately suggested that it was very old, since white dwarfs gradually lose heat over time. Using the W. M. Keck telescopes in Hawaii, astronomers later confirmed that the star shows infrared signals consistent with dust rings formed by asteroids breaking apart under its strong gravity. Such infrared excesses occur when a star emits more infrared light than expected, often because warm dust surrounding it absorbs and re-radiates energy. “This discovery challenges our understanding of planetary system evolution,” said Le Bourdais. “The fact that we still see planetary debris being accreted three billion years after the star became a white dwarf suggests that asteroids, comets, and even planets can remain in orbit around these stars for a very long time.” Spectroscopic analysis—a technique that studies light to identify the chemical elements present in an object—revealed thirteen heavy elements in the star’s atmosphere: sodium, magnesium, aluminium, silicon, calcium, titanium, chromium, manganese, iron, cobalt, nickel, copper, and strontium. Normally, heavy elements sink quickly in hydrogen-rich white dwarfs, making them hard to detect. “We expected to see only a few elements, but we found dozens!” explained Le Bourdais. The research paper adds more detail. The absence of carbon features suggests the debris came from a carbon-volatile-depleted source. The abundance pattern shows slight deficits of magnesium and silicon compared to iron but otherwise resembles Earth-like material. This points to a differentiated rocky body—one whose materials have separated into distinct layers such as a metallic core and rocky mantle—with a metallic core fraction higher than Earth’s. In other words, the star is accreting the remains of a large rocky object, similar in structure to Earth or the asteroid Vesta. “White dwarfs offer one of the only ways we can directly measure the composition of exoplanets,” said Patrick Dufour, co-author and professor at Université de Montréal. “When planetary debris come too close, they are torn apart by the star’s gravity and end up polluting its atmosphere, leaving a detailed chemical fingerprint of its composition.” The team also detected weak Ca II H & K line core emission, making this only the second known isolated polluted white dwarf to show this feature. These are specific spectral signatures produced by ionised calcium and can indicate unusual physical activity in a star’s upper atmosphere. The finding suggests that extra physical processes may be happening in or above the star’s upper atmosphere. The study stresses the importance of including heavy elements in model atmosphere calculations, since leaving them out can distort the inferred structure and lead to inaccurate stellar parameters. Earlier work suggested the star’s infrared excess came from two dust rings. The new analysis shows that a single silicate dust disk—a ring composed largely of rock-forming minerals rich in silicon and oxygen—can explain the observed signal at 11.6 μm, simplifying the picture of the system’s structure. The question of how debris ended up falling into the star so late remains open. One idea is that giant planets in the system slowly destabilised smaller bodies over billions of years. Another possibility is that a passing star disturbed the orbits of debris. “Future observations with the James Webb Space Telescope or archival data found in the European Space Agency’s Gaia mission could help distinguish between a planetary rearrangement and the gravitational effect of a close stellar encounter,” said John Debes, co-author and researcher at the Space Telescope Science Institute. Dufour noted that hydrogen-rich white dwarfs are the most common type, and the coolest among them are the oldest stars in the galaxy. “We didn't have the habit of looking for signs of accretion in them. This unique case motivates us to expand our search to more of these stars.” The findings show that even after billions of years, planetary systems can remain active and complex. Substantial accretion events—the gradual accumulation of surrounding material onto a celestial object—can still occur long after a star’s death, offering a rare window into the composition and fate of distant worlds. Source: University of Montreal, IOPScience This article was generated with some help from AI and reviewed by an editor. Under Section 107 of the Copyright Act 1976, this material is used for the purpose of news reporting. Fair use is a use permitted by copyright statute that might otherwise be infringing.
    • Doesn't DDG mainly use Bing?
  • 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
      485
    2. 2
      PsYcHoKiLLa
      228
    3. 3
      Skyfrog
      70
    4. 4
      FloatingFatMan
      58
    5. 5
      neufuse
      56
  • Tell a friend

    Love Neowin? Tell a friend!