Slashdot Mirror

← Back to Stories (view on slashdot.org)

Microsoft Temporarily Suspends Availability of Windows 10 Builds

Posted by samzenpus on from the that's-it-for-now dept.

Mark Wilson writes: If you haven't already downloaded Windows 10 build 10162 or 10166, you're now too late. Microsoft has suspended the availability of these two builds — previously available on the Slow and Fast rings respectively — in the run up to the big launch day in a couple of weeks' time. As we edge closer and closer to the RTM build of Windows 10, Microsoft is now asking Windows Insiders to stick with the build they currently have installed for the time being. Anyone who hasn't upgraded to these latest preview builds is out of luck. As well as disabling upgrading through Windows Update, Microsoft is also suspending ISOs and activation.

4 of 106 comments (clear)

  1. Dammit by slashdot_commentator · · Score: 2, Interesting

    I botched up my disk drive's EFI partition while trying to install Windows 10. By the time I resolve all my problems, I may not be able to activate the damn install!

    --
    There is no America. There is no democracy. There is only IBM and AT&T and DuPont, Dow, General Electric, and Exxon
    1. Re:Dammit by Anonymous Coward · · Score: 0, Interesting

      I am a long time Linux User and hardcore video gamer i have 4 desktops 2 laptops 1 sever (win home server 2011/freeNAS for backups and media streaming) all dual booting *nix/Win, but i have to admit Win 10 is real sleek and shiny, runs fast and works well, is backwards compatible as always with Windblows and i am finally looking forward to upgrading all my Win 7 machines when it is released.

    2. Re:Dammit by slashdot_commentator · · Score: 3, Interesting

      I think everyone reading this is has been in that boat sometime or another.

      Nah, in my case, it was my own damn fault. I should have been more familiar with EFI/UEFI issues before starting. I've been a long time linuxer, so I was counting on my outdated MBR/dualbooting and ntfsclone dumps to get me through. The first snag was that Windows 10 would not install on my secondary drive for some reason, because it already had an EFI partition, which somehow made it unsuitable for booting. (I know this may sound incorrect to some; I'm just relating my first hand experience.) It was the relative sluggishness of the Windows install menu that made me accidentally delete a partition important to my OS drive and then hilarity ensued...

      wbadmin backup? You're talking 8.1, right? Nope, windows 7 here at home. Yeah, I've been able to mount all my intact partitions, so I haven't lost data, but I'm working on repairing EFI partitions and restoring the relevant hidden system drive dump to the correct partition. Actually, I was doing the book learning I should have done before attempting anything, and then Microsoft now "mentions" they're shutting down the preview activations.

      Well, I've mentioned elsewhere that I was able to get my 10162 build installed & activated today (different machine), so one day soon I'll be back to square one.

      --
      There is no America. There is no democracy. There is only IBM and AT&T and DuPont, Dow, General Electric, and Exxon
  2. Wonder what MS might be adding for the RTM build.. by mlts · · Score: 3, Interesting

    In the past, there were last minute "gotchas" which MS tossed in right before a build went RTM. In the antediluvian past, it was removing direct MS-DOS access in Windows ME, with XP, it was the Secure Audio Path (which was a DRM stack which required all audio drivers to be signed, in order to prevent programs like TuneBite from existing.)

    I wonder what is going to be tossed in at the last minute. Hopefully nothing too headache-forming.