Slashdot Mirror


Microsoft Delays Windows 10 Spring Creators Update Because of 'Higher Percentage of BSODs' (bleepingcomputer.com)

Microsoft has admitted that it had to postpone the release of Spring Creators Update, the upcoming major update to its Windows 10 desktop operating system due to technical issues. BleepingComputer notes: More precisely, Microsoft says it encountered a higher percentage of Blue Screen of Death (BSOD) errors on PCs, the company's Insiders Program managers said in a blog post yesterday. Microsoft says that instead of shipping the Springs Creators Update faulty as it was, and then delivering an update later to fix the issues, it decided to hold off on deploying the defective build altogether. The OS maker says it will create and test a new Windows 10 build that also includes the BSOD fixes, and ship that one instead of Windows 10 Insider Preview Build 17134, the build that was initially scheduled to be launched as the Spring Creators Update on April 10, last week.

108 comments

  1. Wow, incredible, someone pinch me by Anonymous Coward · · Score: 0

    Is it true? Does a major software vendor actually care more about quality than meeting deadlines?

    I swoon.

    1. Re:Wow, incredible, someone pinch me by bigman2003 · · Score: 0

      Dammit...I hate to read this.

      I was on the fast ring. About a month ago I got a BSOD. So I did the smart thing, and I went out and bought a new computer. I was NOT going to wrestle with figuring out how to get a new copy of Windows, etc.

      Stupid BSOD.

      --
      No reason to lie.
    2. Re:Wow, incredible, someone pinch me by Streetlight · · Score: 1

      Was your new computer an Apple device? No bad updates there, right?

      --
      In a time of universal deceit, telling the truth is a revolutionary act. George Orwell
    3. Re:Wow, incredible, someone pinch me by jawtheshark · · Score: 1
      Are you trolling?

      Look, I'm a Linux user, but if you've got a Windows 10 resulting from a Windows 7 or Windows 8(.1) upgrade (or the Windows Store), you have a digital entitlement. In any other case, you should have a product key. A digital entitlement is (relatively) cool in the sense that you simply boot with the Windows 10 ISO, which you can download directly from Microsoft, when a product key is asked, you say "skip" and after installation, your copy auto-activates the digital entitlement. This is even relatively flexible: hardware changes like hard disks/ssds/optical drives do not seem to be included in the digital entitlement hash. So, upgrading from HDD to SSD is no problem with a digital entitlement.

      As said, any other way of acquiring Windows 10 gives you a product key which you can use on the hardware it's coupled to. If you do not have a product key, well, perhaps you should do some introspection. It's not as if getting Windows 10 keys is very expensive, especially if you live in Europe

      --
      Ahhh...the great dumpster continuum. Many a free computer will be found there. -- sowth (748135)
    4. Re:Wow, incredible, someone pinch me by bigman2003 · · Score: 1

      Not trolling.

      I have one computer at home. My desktop. It bluescreened on boot. Can't do anything. No way to download Windows, activate, whatever.

      It was getting old, so I figured "Well, it is about time anyway, this is just the thing that pushed me over the edge to buying a new computer". I bought an inexpensive Dell...which I would recommend that people do NOT do! Only 2 SATA connections, and only one SATA power cable- the other connection is for the DVD drive that I will never use. (I have since bought more cables, but still have not installed more drives, because I hate doing this stuff)

      I really didn't want to spend my weekend getting frustrated with OS installs, so I just bought a new computer.

      It's a tale of woe that I put out there because this is the situation people are put in. If my wife didn't use the computer for her work, I probably would have said, "Ah screw it...I don't need a computer" or I would just install Ubuntu. But you know, Adobe.

      I've been a 'tech professional' for over 20 years. And I really have absolutely zero interest in messing around with my computer. Microsoft did not lose my business because of this, but I did look at the iMac. Or, if BestBuy carried the Mac Mini, I probably would have bought that.

      But next time, I won't do the same thing again. (Read my post history if you care to...I am a long time Microsoft fan. But dropping Windows phone, and now a blue screen on my desktop, I'm ready to say goodbye)

      This is how they will lose a lot of market share.

      --
      No reason to lie.
    5. Re: Wow, incredible, someone pinch me by Anonymous Coward · · Score: 0

      Amen brother. Good luck.

    6. Re:Wow, incredible, someone pinch me by Anonymous Coward · · Score: 0

      So you already owned one Windows license, Microsoft took a proactive, unnecessary action that broke it, and your first instinct was to march out and buy another Windows license?

      Somewhere out there a *** just spontaneously came in his pants and doesn't know why.

    7. Re:Wow, incredible, someone pinch me by stooo · · Score: 1

      Yep.
      MS wants exactly the right percentage of BSODs.
      Not more.
      Not less.
      the goal for BSOD today is 14.6%.

      --
      aaaaaaa
    8. Re:Wow, incredible, someone pinch me by jawtheshark · · Score: 1
      Ok, I see. Basically:
      • Your computer was due for replacement
      • You did not have a second computer to download the ISO
      • You did not have time, nor motivation to fix it yourself.

      That is fair enough. These are (relatively) good reasons to spend money on a new computer. However, that was besides the point: Your original statement was that you didn't want to wrestle with Microsoft to get a working and activated copy of Windows. As much as I hate to say it, Microsoft finally does the right thing and allows re-installation from an ISO you can get with them. Not only that, their (end-user) licensing has been simplified so that a re-installation is not the headache it once used to be. Your statement was simply factually untrue.

      Even if you only had only that computer, as a tech professional, you surely had a bootable Linux somewhere. This would have allowed you to boot the machine, go download the Windows 10 ISO, and make a bootable USB or burn it to disc. From there, you could have reinstalled the machine. I'm just saying. I understand you were angry and probably didn't have the time, but the machine could have been salvaged pretty easily.

      Still, the above would have taken a few hours. Hours which you didn't want to spend. So, I understand.

      As for the two SATA connectors and lack of cables in your new machine. OEMs always go with the most bare bones they can get away with. Two SATA is common, limited power supplies too. My experience is that you best do not buy a computer on a hunch, without research. I have done quite a few time and pretty much always something ends up annoying me endlessly. As often, taking decisions while angry, are usually bad decisions.

      Good luck with your new computer. However, if you really want to leave the Windows world entirely, take that old computer slam a distro of your choice on it and start using it. I did that a decade ago, and never looked back. The main "trick" is not to look back and decide to look for the "Linux" way of doing things and eventually look for alternative programs.

      --
      Ahhh...the great dumpster continuum. Many a free computer will be found there. -- sowth (748135)
    9. Re:Wow, incredible, someone pinch me by Gr8Apes · · Score: 1

      I hope GP reads this as a continuation of yours.

      In his defense, installing MS's OS takes more than a couple of hours, few is not a word I'd use in relation to these installs. I do agree with your assessment of a new PC. You never buy OEM bottom of the barrel unless all you're needing is a web browser, email, and perhaps some document editing. In his case he needs Adobe, I'll assume PS at the minimum. For that, I'd have bought no less than a Core i7 with 16GB RAM as a bare minimum. Given that it's a Windows machine, I'd probably go with 32GB. I'd also have an M.2 SSD in it for the system at least. It wouldn't have been anywhere near the cheapest option.

      What gets me is that if you're on the fast ring, there's a few things you do to protect yourself:

      • Have another computer as a backup
      • Have a cloned HD copy at hand in case something goes haywire
      • Use a second non system disk for all data, preferably backed up regularly to an external device.

      because the fast ring will fail as it is an unstable branch.

      --
      The cesspool just got a check and balance.
    10. Re:Wow, incredible, someone pinch me by jawtheshark · · Score: 1
      I just happen to have installed Windows 10 on a HP ProBook 4340S. It normally runs Ubuntu from a 275GB SSD. I had trouble with Garmin Express under Virtualbox, and wanting to exclude problems caused by visualization, I snagged a 32GB SSD I had lying around, burned a freshly downloaded Win10 1709. The exercise from downloading burning the DVD (using Ubuntu) to finishing the install and testing Garmin Express (Still doens't work as expected.) was 1h30 tops. Two system devices had a warning sign, but I didn't bother because everything I actually needed worked. Not sure what they were, everything seemed to work. Windows 10 was activated with its digital entitlement. I have now swapped back to my original SSD, because my test is done. Technically, an unactivated Windows 10 would be more than fine enough to do tests like these.

      Granted, for many people you can add another couple of hours to setup the desired software and disabling/enabling all stuff Windows 10 gets wrong in the default settings... but, if you're after a working computer, you can get one really quickly these days. We are far far far away from setting aside two days to configure a Windows machine.

      --
      Ahhh...the great dumpster continuum. Many a free computer will be found there. -- sowth (748135)
    11. Re:Wow, incredible, someone pinch me by Gr8Apes · · Score: 1

      I just happen to have installed ... Win10 1709. The exercise ... was 1h30 tops.

      Glad to see that MS got down to a mere 90 minutes to install the OS with basic defaults. </sarcasm>

      Granted, for many people you can add another couple of hours to setup the desired software and disabling/enabling all stuff Windows 10 gets wrong in the default settings... but, if you're after a working computer, you can get one really quickly these days. We are far far far away from setting aside two days to configure a Windows machine.

      So, it's not actually installed yet, it's just the base, now you get to "tweak" all the crap to actually get it to a real working state. And only then would I worry about installing software.

      I just recently did a full fresh install of OSX 10.12 on a mini. It took 60 minutes total to install the OS, migrate the old 10.10 system to the new system and then get the latest updates for all software. Fully configured system with heavy personalized modifications ready to go. If I'd skipped the migration as I did on another system, it took about 50 minutes, including installing all necessary software.

      Ubuntu was about 45 minutes for the various things I needed setup. I should mention I had to google a few of those. Mint was less than 30.

      If you're catching the drift that I'm not impressed with MS's performance here, you'd be spot on. There's no excuse for their OS to be this user unfriendly. Perhaps win 10's next release could focus on user friendliness? Right, that's right up there on their priority list, right behind user privacy and security.

      --
      The cesspool just got a check and balance.
    12. Re:Wow, incredible, someone pinch me by jawtheshark · · Score: 1
      Point was: compared to the past, it's become much better. I used to count two days to configure a Windows machine. Today, half a workday should suffice. However, I usually refuse. As you might have understood it was a quick and dirty test in order to exclude a potential problem.

      On a decent connection, from PXE to fully installed (all applications included) for Ubuntu is 20 minutes. Been there, done that.

      --
      Ahhh...the great dumpster continuum. Many a free computer will be found there. -- sowth (748135)
  2. Thanks Microsoft by Anonymous Coward · · Score: 0

    Haven't seen a BSOD in months (except from faulty hardware).

    Thanks?

    1. Re:Thanks Microsoft by jellomizer · · Score: 4, Interesting

      I havn't seen a BSOD in Windows in over a decade now myself.

      I have had major processes get stuck, slowing the PC to a crawl, forcing me to reboot to fix it. Random bits of hardware not detecting only for me to reenable it (Wi-Fi, Touchscreen mostly).

      The last time I got a BSOD was over a decade ago and I think it was on Windows XP.

      --
      If something is so important that you feel the need to post it on the internet... It probably isn't that important.
    2. Re:Thanks Microsoft by Anonymous Coward · · Score: 0

      No,XP very stable OS, it was with 2000 and old

    3. Re:Thanks Microsoft by dunkelfalke · · Score: 1

      I've seen the IRQL_NOT_LESS_OR_EQUAL every now and then.

      --
      "It's such a fine line between stupid and clever" -- David St. Hubbins, Spinal Tap
    4. Re:Thanks Microsoft by Malizar · · Score: 2

      Sounds like my system. Every month or so the Windows update messes up my wifi or my display driver. Generally takes anywhere from 30 minutes to 2 hours to get my computer back to working correctly.

    5. Re:Thanks Microsoft by Anonymous Coward · · Score: 2, Insightful

      This is probably because the new default is to just reboot when Windows crashes.

      tl;dr: Windows doesn't "BSOD" anymore unless you explicitly ask it to display the BSOD screen.

    6. Re:Thanks Microsoft by DigiShaman · · Score: 1

      Oh, I had to deal with an MS botched patch that was applied last month that resulted in a BSOD every time someone logged off a PC, shutdown, or initiated a reboot. The message was SESSION_HAS_VALID_POOL_ON_EXIT' 0x00000ab. Clearly this was a software kernel panic, not HW which is normally you see with faulty storage or RAM. Occasionally, a buggy device driver can cause one too. But no, this bug was the direct fault of Microsoft!

      FYI you can apply the fix via KB4099467 however.

      --
      Life is not for the lazy.
    7. Re:Thanks Microsoft by PsychoSlashDot · · Score: 1

      Yeah, that was a fun one, especially on a terminal server.

      --
      "Oh no... he found the .sig setting."
    8. Re:Thanks Microsoft by Opportunist · · Score: 1

      ...which is usually a sign of faulty hardware and/or drivers.

      --
      We used to have a Bill of Rights. Now, with the rights gone, all we have left is the bill.
    9. Re:Thanks Microsoft by TheRealMindChild · · Score: 1

      I swear everyone forgets what a turd XP was before SP2

      --

      "When life gives you lemons, don't make lemonade. Make life take the lemons back!" -- Cave Johnson
    10. Re:Thanks Microsoft by Anonymous Coward · · Score: 0

      Yep, also lots of bad code that didn't break until hyper threading appeared.

    11. Re:Thanks Microsoft by jellomizer · · Score: 1

      Windows XP, Windows 2000 both were based of the NT kernel. Vs Windows up to ME which were still based on DOS So compared to All the consumer level windows versions up to ME. XP was quite stable of an OS, and so was Windows 2000.
      But I argue that Windows 2000 was just a re-branded NT 5. As it wasn't really targeted towards the consumer market.

      But XP based off NT... But targeted towards the Desktop Home user. Had a lot of problems especially early on. Compatibility problem with old DOS and Windows 16bit apps.
      Also during this time, Home users were migrating from dialup to Broadband internet. This has opened their PCs up to the first time, to a nearly always connected internet for viruses and junk to get in.

      When XP was released it was a rough time for users.

      --
      If something is so important that you feel the need to post it on the internet... It probably isn't that important.
    12. Re:Thanks Microsoft by Megol · · Score: 1

      No BSOD and no crash here since forever. Last problem: graphics driver, second to last problem: graphics driver. Don't remember when that happened, 6 or 8 years ago perhaps?

      Graphics drivers still partially crash from time to time but killing the program (game) and then restarting it works fine without rebooting.

      Oh, there is one other hardware related problem: since a BIOS update (well, UEFI...) there are some power management problems. Solved by changing some Windows settings so that it uses traditional hibernation, a few seconds slower boot but it works. The problem is the hardware manufacturer that don't think new BIOS updates are worth it for a computer that's more than a year old.

    13. Re:Thanks Microsoft by FatdogHaiku · · Score: 1

      I avoid Windows drivers for my hardware unless there is no OEM driver.
      If the latter is the case, then I need to reconsider my hardware choices...
      Unless of course the hardware is MS branded, in which case I REALLY need to reconsider my hardware choices...

      --
      You have the right to remain sentient. If you give up the right to remain sentient, you will be elected to public office
    14. Re:Thanks Microsoft by Anonymous Coward · · Score: 0

      I have a server at home that is running 24/7 for 6 months now and it never, ever crashed

    15. Re:Thanks Microsoft by Anonymous Coward · · Score: 0

      Lucky You, I've recently got 70 new Lenovo laptop BSOD'ing due to a Microsoft update not compatible with Lenovo drivers.

    16. Re: Thanks Microsoft by Anonymous Coward · · Score: 0

      Windows 2000 shat all over xp for years. Whql drivers killed 2000 because Microsoft needed to force people onto xp.

    17. Re:Thanks Microsoft by thegarbz · · Score: 1

      I havn't seen a BSOD in Windows in over a decade now myself.

      While rare, they aren't quite that rare. Though I did see a Windows 10 BSOD for the first time a few months back. They have QR codes now... for some reason.

      As for Windows XP being the last I call shenanigans, or were you mysteriously in a coma from January 2007 to July 2009? ... Or more likely PTSD has caused you to wipe Windows from those 2.5 years from you mind.

    18. Re:Thanks Microsoft by Anonymous Coward · · Score: 0

      I also had a BSOD free decade until Windows10 was forced into my work PC. And during last year of it, I have had at least one BSOD a month. And of course the contemporary BSOD is also completely useless, as it only has a QR-code, which contains a generic "microsoft.com/suckstobeyou" -URL, not a detailed error code as previous ones had. Good luck debugging any of the issues anymore.

    19. Re:Thanks Microsoft by Anonymous Coward · · Score: 0

      Personal experience is that getting stuck in an endless boot loop is the new BSOD. I preferred BSOD: at least then you can proceed toward a solution after hitting reset, but when you can't even boot the damn computer you're pretty well snookered.

    20. Re:Thanks Microsoft by ayesnymous · · Score: 1

      I've gotten about 10 BSODs in 3 months with the new HP ZBook they gave me at work. It'd be a lot more than that if I hadn't stopped putting it into sleep/hibernate mode. All different crash codes too.

    21. Re:Thanks Microsoft by dunkelfalke · · Score: 1

      Yep, probably the Soundblaster XFi. I am too cheap to replace it with something better, but too spoiled for the onboard sound.

      --
      "It's such a fine line between stupid and clever" -- David St. Hubbins, Spinal Tap
    22. Re:Thanks Microsoft by Opportunist · · Score: 1

      Don't replace it with one from the Asus Xonar line, they (and even more their drivers) are about as crappy.

      --
      We used to have a Bill of Rights. Now, with the rights gone, all we have left is the bill.
    23. Re:Thanks Microsoft by dunkelfalke · · Score: 1

      Thanks for the warning - the Xonar line was the only reasonable alternative I had in mind.

      --
      "It's such a fine line between stupid and clever" -- David St. Hubbins, Spinal Tap
    24. Re:Thanks Microsoft by Opportunist · · Score: 1

      I have one. It's ok, it works, no BSODs, but the drivers are bulky, unwieldy and don't really deliver anything beyond basic functionality. Their 5.1/7.1 functionality is a joke compared to the SB XFI I had before.

      Then again, at least the Xonar is stable, so...

      --
      We used to have a Bill of Rights. Now, with the rights gone, all we have left is the bill.
    25. Re:Thanks Microsoft by Anonymous Coward · · Score: 0

      Holy shit Batman! 6 months!!!

      Even by Windows standards, that isn't all that impressive.

    26. Re:Thanks Microsoft by toddestan · · Score: 1

      The default in Windows now when it BSOD's is to reboot. Of course, if it just boots up into another BSOD, that's how you get the reboot loops. If it's more of the random fluke BSOD, you just come back and see your computer restarted (oh, must have been Windows Update...again....). That's how people claim that they've not seen a BSOD in years. You can turn that nonsense off if you want, though I wouldn't trust Windows 10 to not ignore it and do whatever it wants regardless of the setting.

  3. Deploying bad releases? by danomac · · Score: 1

    I find it quite disturbing that they were even considering releasing this obviously faulty build and fixing it later. Do they not care about the name brand? It's already got people pissed off as it is.

    1. Re:Deploying bad releases? by Anonymous Coward · · Score: 0

      The issue wasn't known about when the build was scheduled for release, it was discovered two or three weeks ago.

      So I suppose to answer your question, they do seem to care about the brand, since they decided to delay the release and instead work on a new build.

    2. Re:Deploying bad releases? by jellomizer · · Score: 2

      Well Microsoft haters will hate. Chances are this BSOD is a fairly rare condition, and sending out an update at would introduce the BSOD vs the additional benefits of the update is a decision that will need to be made.

      For all products there is a point where someone will need to say "this isn't perfect, but it is good enough". Because the cost of the flaw is minor while the improvements are great.

      So Microsoft did the responsible thing Considered releasing a product that could possibly BSOD, or make people wait for a big set of improvements which could allow people to hack into their systems, or break something else. They figured the BSOD condition was common enough to not release it.

      --
      If something is so important that you feel the need to post it on the internet... It probably isn't that important.
    3. Re:Deploying bad releases? by The+MAZZTer · · Score: 1

      Why do you think it was obviously faulty? "Higher than normal percentage of BSoDs" sounds to me like it takes into account BSoDs caused by non-Microsoft software and drivers. Microsoft can't be expected to hold up a release until they fix everyone else's buggy code. Using simple statistical analysis they determined that the % of BSoDs was higher in the new build, meaning there was likely a BSoD bug present in their own code, which they then rightly sought out to fix.

    4. Re:Deploying bad releases? by Anonymous Coward · · Score: 0

      yes,if use only xp and 7(sp1)

    5. Re:Deploying bad releases? by UnknownSoldier · · Score: 1

      > Well Microsoft haters will hate.

      /sarcasm Let's just label people and ignore the reasons WHY MS gets so much hate!

    6. Re:Deploying bad releases? by Mashiki · · Score: 3, Informative

      Wouldn't surprise me if it's related to driver rollouts. There's a lot of complaints in the fast and slow channels over MS once again deciding to force driver updates on everything. Not only was windows rolling back drivers in some cases, but rolling out drivers that people were using that made their system stable and then overwriting newer signed drivers with MS 'certified' drivers like on a new OS install. It's the biggest thread in the driver section and has been for quite awhile.

      --
      Om, nomnomnom...
    7. Re:Deploying bad releases? by omnichad · · Score: 1

      Yes. With each new twice-yearly release, all the Microsoft drivers have their dates bumped to match the OS build date, even when nothing is changed or fixed. Even if you block/hide a particular driver via Windows update, the "new" driver from the next build gets auto installed again.

    8. Re:Deploying bad releases? by omnichad · · Score: 1

      Higher than normal means that they pushed out earlier releases, despite causing a fair number of BSODs. The number of errors is just much higher this time around. The high number of issues caused by an automatic update should be near zero, even after accounting for third party software. And that really was the case for service packs in all earlier releases of Windows.

      The new updater constantly makes bad assumptions, especially regarding the layout and size of EFI system partitions. The number one cause of a blue screen after an update seems to be a broken boot configuration that Windows also can't fix with it's automatic startup repair.

    9. Re:Deploying bad releases? by Anonymous Coward · · Score: 0

      I find it quite disturbing that they were even considering releasing this obviously faulty build and fixing it later. Do they not care about the name brand? It's already got people pissed off as it is.

      Seems like you're one of those people who just hate for the sake of hating. The bug was only discovered at the last minute and they instantly decided to delay release. They never considered releasing it with knowledge of this bug, only prior.
      I've been using win10 as primary OS since the first public beta, and I only had it crash a couple times -- before win10 was even on the market. Never since.

    10. Re:Deploying bad releases? by Anonymous Coward · · Score: 0

      I have about 2k workstations I am responsible for updates, and remediating update issues.

      even 1% means I likely have 20 workstations I have to go fix now.

    11. Re:Deploying bad releases? by jellomizer · · Score: 1

      That is why Microsoft decided not to push the update.
      It it was 0.1% chance then you would likely have 2 workstations. Or if it were 0.05% then you would have one.

      That is why Microsoft evaluated the risk.

      However lets say you have 40 work stations you need to fix. And the patch fixes that problem. So you are down to 20. Wouldn't that be a better solution.

      The point was the poster was complaining how bad Microsoft is for even considering not holding off the update. My point is there are factors which could allow consecration.

      --
      If something is so important that you feel the need to post it on the internet... It probably isn't that important.
    12. Re: Deploying bad releases? by Anonymous Coward · · Score: 0

      3 weeks before release isn't last minute. Sorry bunk.

    13. Re:Deploying bad releases? by Anonymous Coward · · Score: 0

      Windows fanbois have been telling us for about 5 years that either (a) Windows never gets BSODs any more or (b) Windows only gets BSODs for hardware faults.

      Maybe they'll shut the fuck up now?

    14. Re:Deploying bad releases? by Insanity+Defense · · Score: 1

      Well Microsoft haters will hate. Chances are this BSOD is a fairly rare condition, and sending out an update at would introduce the BSOD vs the additional benefits of the update is a decision that will need to be made.

      For all products there is a point where someone will need to say "this isn't perfect, but it is good enough". Because the cost of the flaw is minor while the improvements are great.

      So Microsoft did the responsible thing Considered releasing a product that could possibly BSOD, or make people wait for a big set of improvements which could allow people to hack into their systems, or break something else. They figured the BSOD condition was common enough to not release it.

      The cost of the flaw is not minor to the poor sap whose computer is screwed with an update they aren't allowed to block even if they KNOW their computer will be affected by it. Give the OWNERS of the computers back the CONTROL of the computers which is theirs by rights as the OWNER of that machine.

    15. Re:Deploying bad releases? by Anonymous Coward · · Score: 0

      I find it quite disturbing that they were even considering releasing this obviously faulty build and fixing it later. Do they not care about the name brand? It's already got people pissed off as it is.

      Being a graybeard, I find it quite disturbing that they didn't release this obviously faulty build and fixing it later.

  4. Well, That's Nice by rally2xs · · Score: 5, Interesting

    Meanwhile, the update that I got about 10 days ago broke the ability of this computer to do the "no password required" bootup. It would give an error message and tell me unless I logged out and then logged in myself, my creations wouldn't be accessible in the future. Or something like that. Ran a few diagnostics / fixes such as scannow and it passed fine. So now, rather than run around and try to find the cause, I'm just waiting for the next update to fix it. The laptop is working fine, no problems with no-password bootup. Its just that a month ago, while on a cross-country trek from Virginia to Arizona, something happened (probably another update) and the keyboard and touchpad stopped working. Then, 2 days later, it magically began working again. (Probably another update.) Win 10 computers are getting to be really unreliable because of the updates dicking with them all the time.

    1. Re:Well, That's Nice by cloud.pt · · Score: 3, Interesting

      I'm not sure if sarchasm or an actual story. I like the comment either way. The fact a W10 computer can start updating itself without prompt or UI, when connected to whatever network (which might be a Starbucks for all we know), is one of the most scary things ever. And I don't mean security-wise, I mean: "here I go do my once-in-a-lifetime presentation to the money suits with my Windows laptop. YAY! FINGERS CROSSED hoping the fact I'm in a different time-zone with different busy hours, and the fact I didn't set this new WIFI to metered can doesn't get me a reboot, or that Delivery Optimization doesn't resource hog BITTORRENTING updates just as I'm about to seal the deal".

    2. Re:Well, That's Nice by rally2xs · · Score: 2

      Both of my Win 10 problems are absolutely true, and I even forgot one. There was another one a few months ago with the laptop, a Surface Pro 4 that I bought last summer, that all of a sudden booted up with a completely black screen. Since I bought it at Best Buy last summer and also bought a 2 year "extended warranty", I just took it to Geek Squad and let them wrestle with it. They had it fixed in a few hours, so I picked it up that night. But the tech said that yes, another update went south, and caused it. Yep, Win 10 is unreliable.

    3. Re:Well, That's Nice by Anonymous Coward · · Score: 0

      Been getting that one at a school recently. Fun stuff.

      Also fun is the "update" that bricks the shell open functions on specific accounts. So the Run dialog works, The command prompt / Power shell works, directly clicking on the exe works, but using a shortcut is broken on both the start screen, desktop, and taskbar. No shortage of cluster f bombs being dropped over that here. Even better is when it's your boss' machine, and even deleting the user profile doesn't work. But log in as anyone else and it works perfectly. Still fixing that one.

      For another one, I got a "could log in" but no desktop or task bar issue. Programs would run but you had to run the task manager to launch them given that the run dialog was also borked. That one resisted two system restores, and required a reset to fix.

      Windows 10 is crap.

    4. Re:Well, That's Nice by thegarbz · · Score: 1

      The fact a W10 computer can start updating itself without prompt or UI

      It can't, and hasn't done so since the first Windows 10 release. What will happen now is that you set active hours during which it will never restart, you also tick the notification box so all you get is a notification telling you that on your next restart it will update, and that will also tell you the exact time it scheduled for the out of hours restart, and even provide you with an option for delaying it, which you can for up to a month.

      Seriously if your presentation is interrupted due to a windows update, you deserve to be laughed off stage at this point.

      Mind you the way you talked about resource hogging BITTORRENTING as if it isn't a good thing that your local network doesn't send every single request to the internet ... on a feature you can disable no less, we should all be laughing at you anyway, regardless if your presentation is interrupted or not.

      Learn to computer. It's not that hard.

    5. Re:Well, That's Nice by Anonymous Coward · · Score: 0

      I swear win10 detects urgency - like you have to finish x right now, shut down and catch a plane - and deliberately chooses that time to install the slowest, most bloated, buggiest "don't turn off the computer" updates.

    6. Re:Well, That's Nice by cloud.pt · · Score: 1

      So, this prosaic "presenter" will 90% of the times have a managed PC with Win10 Pro, and as likely have an enterprise management suite (e.g. Airwatch) enforcing policies through Administration Templates for Windows update and whatnot, which the user can't control. He won't be able to set any of those policies, and he won't ever get a prompt to an update his company doesn't even know might happen, well, "because Microsoft".

      And the way I talked about higging by p2p updates is pretty fair - if you don't know how heavy the kind of "Delivery Optimization" p2p-scheme is on resources you probably never used it. I have all CPU and Traffic settings to their minimum and it still slows my PC every damn time it decides to kick in. The fact it doesn't send every request to the internet also tells me how it forfeits trust in valid internet CAs for authentication, and is instead trusting local computers just because they "appear" to have Windows 10 installed with what appears to be a valid update. Get that key leaked, or, you know, "lent" to a 3-letter US state agency and you got yourself a pretty easy attack vector on anyone with access to your local network: "hey W10-Alice-PC, keylog.dll will install in System32, it comes signed with the MS hardcoded public key, and since we're not using a root CA to mediate this request, it is not a request, so just do it. KTHXBYEBBQROASTED"

      I have a CS degree and I find Win10 hard to control. I use Linux daily, and I don't see any of these problems on hotplug, unnattended updates. I wonder how often you laugh at the non-computer savvy, since you appear to demand knowledge and "vassalage" to certain corporate interests in ways that clearly hint you have interests in this "stupid computing" yourself. Is that you Satya?

    7. Re:Well, That's Nice by thegarbz · · Score: 1

      Funny your complaints are the same about my remotely administered Windows 7 machine. Just because you may not be the one who doesn't know how to use the settings in their computer doesn't mean that someone else isn't a complete buffoon. The problem is the same, you're effectively complaining about not knowing how to use settings which have a full paragraph dedicated to explaining each of them.

      Also the way you talk about CAs just shows you have fundamentally no idea what you're talking about, especially when it comes to sending data. The source of the data is completely irrelevant if you can independently verify it as authentic. You need internet access to access a CA to determine your own piece of software you are verifying yourself (speaking from the software's perspective here) is valid? You need to revisit some of your CS classes. The same also applies to the entire CS process. Or do you think that when I hit Preview and Submit on this sorry conversation that my browser will send DST a request on over the internet before forwarding this message to Slashdot servers.

      Also congratulations, you may also somehow have been the first person to accuse Windows 10 of not talking continuously to Microsoft. I'm not sure how you managed to justify making that post to yourself.

      I have a CS degree and I find Win10 hard to control.

      Says it all really. ... About the degree I mean.

      I wonder how often you laugh at the non-computer savvy

      Considerably less than I laugh at the "computer savvy" people. The non-computer savvy people somehow just use their computers. It's the experts that can't seem to figure it out.

  5. Windows 10 Spring Creators Update 2018 by PingSpike · · Score: 4, Funny

    Windows 10 Spring Creators Update 2018:

    Coming the Winter of 2019.

    1. Re:Windows 10 Spring Creators Update 2018 by keith_nt4 · · Score: 1

      Well it's marked funny but if MS actually took 18 months to release a truly polished build...I for one would be okay with that.

      --
      "UNIX is very simple, it just needs a genius to understand its simplicity." -Dennis Ritchie
    2. Re:Windows 10 Spring Creators Update 2018 by HyperQuantum · · Score: 1

      Giving a whole new meaning to the meme:

      Brace yourselves
      Winter is coming

      --
      I am not really here right now.
  6. showing of some... by Anonymous Coward · · Score: 0

    real amateurism. Nice job MS.

    The fact that something like this can happen should make everybody wonder about what MS is doing really, they don't even seem to know themselves.

    Just more confirmation of our suspicions.

  7. Poor naming of service packs by Anonymous Coward · · Score: 0

    They really need to stop letting their marketing dept name their software updates. Calling all of their different OS builds "Creators Update" creates nothing but confusion and does nothing to properly identify the build/version number.

    1. Re:Poor naming of service packs by Anonymous Coward · · Score: 0

      They really need to stop letting their marketing dept name their software updates.

      Microsoft needed to get rid of their marketing dept years ago. Decades ago. They've done nothing but cause confusion and the stupidity of their advertising has become legendary.

      Windows is a product that gets installed by OEMs on 90% of all computers sold. There's no need for marketing. There's no need for clever names. Give it a version number/build number. Done.

  8. Microsoft's software quality dropping fast by the_skywise · · Score: 4, Interesting

    I've got a SP4 and with whatever update they forced on me last week the windows all think I'm in vertical orientation after it sleeps and won't expand greater than the margin (even though I've left the keyboard attached, have the options set to desktop mode only and the desktop itself is still in desktop orientation!).
    The only way to fix it is a reboot!
    Microsoft - we updated your computer while you slept - figure out what we broke today! What fun!

  9. Pff! Sounds like an unfounded rumor! by Gravis+Zero · · Score: 2

    I've been using the latest Win10 update and my computer is justttttttttttttttttttttttttttttttttttttttttttttttttttttttttttttttttttttt

    --
    Anons need not reply. Questions end with a question mark.
    1. Re:Pff! Sounds like an unfounded rumor! by DarkRookie · · Score: 2

      Just what?
      Don't leave us in suspense.

      --
      The millennial that doesn't like most of the stuff designed for millennials.
    2. Re:Pff! Sounds like an unfounded rumor! by Anonymous Coward · · Score: 1

      Patience young Jedi, it takes a few hours to re-install Windows 10.

  10. Bullshit by DarkRookie · · Score: 1

    They aren't delaying it for BSODs. Why do they care. They release updates like that all the time.
    What broke is the user tracking software. That is why they are delaying it.

    --
    The millennial that doesn't like most of the stuff designed for millennials.
  11. Quarterly release and agile by Anonymous Coward · · Score: 0

    This is what it brings you. Software is not done on a schedule. It is done when it is done. Too many companies are like - ship it on the date, high five and move on, but there is no point in MS doing that because windows is free these days.

  12. Windows 7 says... by Anonymous Coward · · Score: 0

    Have fun with that 'new' windows.

  13. Most of the BSOD's targetted People of Color by Anonymous Coward · · Score: 0

    Just like those racist bigot White Male programmers to create a RACIST computer program that unfairly and systematically opresses proud strong women of Color!

    Makes me sick

  14. That's sort of the question, isn't it? by RyanFenton · · Score: 2

    What happens when they have buildings filled to the brim with software engineers working on projects/components, but each new component has a small chance of adding a new bluescreen on a subset of machines?

    The whole point of Windows 10 was supposed to be that it was the end-state, the stage where all further upgrades would be updates to this. But lashing another sail onto the boat doesn't seem to be adding the thust expected, or bring the income desired.

    They really wanted the Windows Store to be the future too - just like Metro was going to be the perfect union of touch-phone interfaces and desktop interactions (well, by forcing everything to just be touch-phone, and insulting anyone that disagreed).

    But no one uses Windows Store. It most certainly is not an improvement on the flawed Apple store or other marketplaces.

    Then there's the data gathering. I'm sure they market that information to folks (in aggregate) - but I'm also pretty sure that they aren't going to see the returns they might dream about for selling access to that information, compared to their dreams of being some super-Google.

    Probably the biggest source of instability has been the DRM and protection systems. Locks and keys designed to, well, lock things up on anything being off tend to... lock things up. And there's teams of teams constantly working on those.

    Windows is still a money machine. PC sales aren't at peak at the instant, but there's still mountains of money for selling OS licenses on most new systems.

    So, they bounce between ideas still - cross compatibility with XBox game images - but they link it with Windows Store, so it's basically like signing a cult marriage contract. Strait up ports of some games, but the same Store logic kills that idea. Tools to help manage things - but they keep making the interface Metro compatible, so folks drop it as soon as they can find a better tool.

    The overall story is that they still have folks there dreaming that their failed pet ideas are still the future, an unlimited income stream that just needs tweaking. They need to identify that, and get past those folks - especially if they're managers.

    Then be OK with just making the best OS they can, without trying to loop everything back into some infinite income stream. The golden goose is good enough - work on the nest, NOT a butcher shop.

    Ryan Fenton

    1. Re:That's sort of the question, isn't it? by jwegman · · Score: 1

      Amen!

    2. Re:That's sort of the question, isn't it? by Anonymous Coward · · Score: 0

      It begs the question why on FB was called on the carpet about privacy last week. What about the other tech giants?

    3. Re:That's sort of the question, isn't it? by Anonymous Coward · · Score: 0

      No, it RAISES the question.

  15. Microsoft Windows 10 by Anonymous Coward · · Score: 0

    Spring Creators Mess Update..... err... MASS MASS... oh never mind.

  16. Re:Moscow Donald delays Russia sanctions by Anonymous Coward · · Score: 0

    ms spy to russ?))

  17. Poor Quality By Design by nateman1352 · · Score: 1

    At least Microsoft learned from the botched deployment of RS2 (aka Redstone-2, or the "Creators Update") which didn't work well on anything older than Skylake for several months. Looks like it is going to take them similar amounts of time to stabilize RS4 (Spring Creators Update... I wish they would just call it RS4 instead of coming up with meaningless marketing names) but at least they won't hold people's machines hostage in the meantime.

    This is a natural consequence of the new world order Microsoft established with Windows 10. Now, the more money you pay for your Windows license, the more stability you get. At the bottom rung is the "insiders" who can actually install Windows totally for free. But they will always and forever be using beta releases, never will they be on a officially released version. Instead of paying MSFT with money, you pay them by giving away free QA. Next up is the people with the "Home" license. Most people are in this category. They get the newest release forced up their butt every 6 months. Next up if you paid for the "Pro" license you get a checkbox that lets you delay the newest release until another release is given after that. Finally, if you pay through the teeth for an enterprise license, then you get the Windows 7 level of service, highly tested stable releases every 3 years.

    1. Re:Poor Quality By Design by DigiShaman · · Score: 1

      I would love to get a Enterprise edition as it doesn't contain all that telemetry bloatware. In fact, Enterprise is truly a successor to Windows 7 Pro.

      For those that are using Windows 10 Home and Pro, check out O&O ShutUp10. The real irony is that O&O is a Microsoft Gold Certified Partner LOL =)

      --
      Life is not for the lazy.
    2. Re:Poor Quality By Design by Opportunist · · Score: 1

      So, the more you pay, the later you have to install their software.

      Odd. In most other markets, you'd pay a premium to be first.

      --
      We used to have a Bill of Rights. Now, with the rights gone, all we have left is the bill.
    3. Re:Poor Quality By Design by omnichad · · Score: 1

      I've never even seen the term RS2, but I much prefer the simple version numbers like 1709 with the month and year, even if the month code is a lie.

    4. Re:Poor Quality By Design by omnichad · · Score: 1

      They're following the antivirus markets - free/cheap users are guinea pigs.

    5. Re:Poor Quality By Design by ckatko · · Score: 2

      I have Windows Enterprise.

      It's just as shitty as my Pro computers. Half the "privacy" features you think you can disable, break other essential parts of the operating system... like Windows Update.

    6. Re:Poor Quality By Design by thegarbz · · Score: 1

      At least Microsoft learned

      But did they? You're talking about a supposedly tested release that pasted through the insider program was designated as RTM and then pulled on the day of public release.

      It doesn't sound like they learned anything. It sounds like they majorly dodged some bullet and their QC process is still as fucked up as it has always been. No surprise mind you. It took them close to 14 months to fix the problem turning on their own premium Surface Pro 3 computer when a Surface Pro 4 keyboard was attached, a device they not only listed as compatible but wrote a specific SP3 driver for.

  18. diversify by Anonymous Coward · · Score: 2, Funny

    This is why I have Windows, MacOS, and Linux computers at home -- hopefully at least one group of them works at any given time

    1. Re:diversify by Anonymous Coward · · Score: 0

      This is the best advice!

    2. Re:diversify by Anonymous Coward · · Score: 0

      I've tried the same solution but finally I kicked Windows out, there were always problems with it.

  19. How many? by Anonymous Coward · · Score: 0

    They've had how many years to get this right?

  20. Congratulations YOU. YOU are the WORLD. by Anonymous Coward · · Score: 0

    Congratulations YOU. YOU are the WORLD.

    Captcha: allele

  21. Thinking back to by Virtucon · · Score: 1

    When they laid off most of their QA folks

    I get end-user testing, early preview releases are a good thing, I preach it and live it but frankly these wholesale massive semi-annual fuck-overs to add one or two "features" is annoying as fuck. Every time there's hardware compatibility problems, delays in releasing them because they're refreshing the whole fucking planet. I get that they want to unify frameworks, that's good but for god's sake stop with this 1GB+ downloads and installs that fail over and over again until they finally get it right. Hopefully this should serve as a wake-up to Redmond that they're fucking over their customers and like me a lot of them are minimizing their exposure to Windows OS at least on the desktop.

    --
    Harrison's Postulate - "For every action there is an equal and opposite criticism"
  22. Microsoft's Windows is a toy. by Anonymous Coward · · Score: 0

    Face it already.
    Microsoft's Windows is a toy.
    A broken one.
    And for rather retarded kids.

  23. Am I the only one who thinks "agile" is stupid on by iampiti · · Score: 1

    Am I the only one who thinks "agile" is a stupid metodology to use on an OS?
    It's supposed to be stable. How does this benefit Microsoft?

  24. Windows only fit to run under *nix VM by Anonymous Coward · · Score: 0

    Essentially, the summary of most of the comments above is that windows 10 is unfit for any serious use (unless - possibly - you get the "Extremely Expensive Entrprise Edition"

    Meanwhile, you can, for example, get 10-year supported, ultra-stable CentOS version for free.

    It's pretty clear now that if you use your PC for anything serious, you should run Linux (or *BSD) on the bare metal and if you *must* have Windows applications, run them in a VM. This means you should be able to roll back bad updates to the last VM snapshot.
    Assuming (a) you have sufficient RAM and (b) don't run any software that is no good in a VM, can any Windows advocate show reasons why you should *not* run Windows 10 under a Linux VM in order to mitigate the sort of issues described above (not just the current, avoided issue, all the other issues they detail)?

  25. Typical lame. by Anonymous Coward · · Score: 0

    Junkware.

    Bull Shit Over Dose

    The OS sucks sorry but it's not even news.

  26. Windows Update Blocker + by Anonymous Coward · · Score: 0

    Windows Update MiniTool =FTW!!!

    Seriously, after having my computer caught multiple times in endless loops of downloading some huge update that doesn't work for whatever reason then re-downloading, ad nauseum, the 2 mentioend tools have given me full control to download what updates I want and block the rest.

    As a long-time Microsoft user/?fan? I'm forced to ask: Microsoft, WHAT THE F*CK ARE YOU THINKING!?! Way to pi$$ off your customers.

  27. Re:Am I the only one who thinks "agile" is stupid by MerlinTheWizard · · Score: 1

    You're not. But how does this benefit Microsoft? That's not quite the right question to ask. Microsoft will benefit as long as people buy their products. Whether it has something to do with their stability remains to be seen.

  28. You know Microsoft by rsilvergun · · Score: 1

    it's OK by me if the update has a lower percentage of BSODs. You can just add some more in a point release.

    --
    Hi! I make Firefox Plug-ins. Check 'em out @ https://addons.mozilla.org/en-US/firefox/addon/youtube-mp3-podcaster/
  29. Shanghai QA Center strikes again! by Anonymous Coward · · Score: 0

    Seriously, once the Shanghai QA center became the responsible point for Windows Update QA (and thus firing all the old guard QA testers in Redmond because they cost too much), everything has gone downhill.

    At least some of the testers have moved on to various exploit shops...

  30. Whats the point of beta/insider testing? by Anonymous Coward · · Score: 0

    Wait, so isn't the point of having 1000000's of insider/beta testers (like my father, he loves it) supposed to screen/pickup anything major like this?

    How can they release a major update that's so broken?

  31. Blue Screen Returns by Daralantan · · Score: 1

    I always remember a few years ago when they did.... Windows 8? They were bragging that the BSOD was gone........ ...Because it would now be red. Reminds me of when they got rid of the 360's red ring of death - by removing the ring.