Slashdot Mirror

← Back to Stories (view on slashdot.org)

Microsoft Discovers Blocking Bug and Delays the Release of Windows 10 Spring Creators Update (betanews.com)

Posted by msmash on from the blessing-in-disguise dept.

The next big update for Windows 10 has been delayed while Microsoft rushes to fix a newly-discovered bug. From a report: Known variously as Windows 10 version 1803, Cumulative Update for Windows 10 Version Next, Redstone 4 and Windows 10 Spring Creators Update, it was widely thought that the update had reached RTM and was on the verge of rolling out. However, this last-minute discovery means there will be a little longer to wait.

4 of 83 comments (clear)

  1. Good on them! by Anonymous Coward · · Score: 3, Insightful

    Good on them! This is a refreshing change from their usual practice of releasing Windows 10 updates on-time but with bugs that break some or all functionality.

  2. Re:Window's ain't done until Google wont run by Anonymous Coward · · Score: 2, Insightful

    Probably couldn't reinstall Candy Crush after the user uninstalled it for the fifth time

  3. Re: Window's ain't done until Google wont run by Anonymous Coward · · Score: 2, Insightful

    No it is not. MS keeps booting my machine nightly telling me it is installing latest win10. Just get to 82% done blows off and rollsback. Wipe machine and directly install win10 and goes though all the work and locks up in the boot. Reinstall working version. All drives are 64bit and current. It kepts reinstall win10 upgrade assistance after I deleted it.

    WIN10 broken by design. Was leaving that machine to support win10 printing and 3D printing. But us totally unusable since it goes thought this update loop every time anyone logs on.

    Thank you MS for the good work.
    PS they do not know ehat is wrong either. .

  4. Re:Window's ain't done until Google wont run by JoeyRox · · Score: 3, Insightful

    You do realize that even from the very first release of Windows 10, you could configure it to prompt you to reboot instead of doing it automatically right?

    No, I don't realize that because it's patently incorrect. First, the very first release of Windows 10 did not have this feature, as documented here. Second, the "feature", as described online, doesn't actually work, nor does the group policy method either.

    You can nurse your various irrational reasons for disliking Microsoft, Windows, and whatever else all you want, no one here will really give two craps. Just don't crap all over threads with pointless posts that serve only to boost your own ego.

    With the time you wasted trying to insult me you could have done a little research first and saved yourself some embarrassment.