The Sams Report: Houston, We Have an 1809

Posted on November 9, 2018 by Brad Sams in Podcasts, The Sams Report with 11 Comments

On this episode of the Sams Report, 1809 is creating headaches for everyone and it’s time Microsoft addresses the quality issue with its development practices.

RSS | SoundCloud | YouTube | iTunes | Google Play



Tagged with

Join the discussion!

BECOME A THURROTT MEMBER:

Don't have a login but want to join the conversation? Become a Thurrott Premium or Basic User to participate

Register
Comments (13)

13 responses to “The Sams Report: Houston, We Have an 1809”

  1. Avatar

    ChiWax

    I have 3 Windows machines that I'm using each day in some way. Two are running 1809 and the third is running 19H1. According to this podcast I willingly install and run "crap" on my machines. Wow.

  2. Avatar

    Thomas Parkison

    Brad Sams in the video mentioned that the OEM partners don't want to burn Microsoft. Well, I for one think that they should. Burn Microsoft, let the whole damn world know that they have morons at the helm!!! That will in turn cause their stock to take a hit and maybe... just maybe, if Microsoft takes enough of a financial hit that idiot that they have as CEO will be shown the door and someone who doesn't have shit for brains will take over and clean that company up because it desperately needs to be cleaned up.

  3. Avatar

    jules_wombat

    Microsoft is certainly a Long way from "Code Complete"

  4. Avatar

    RonH

    AFAIK, 1809 was never pushed out. you had to seek it out to get it. I only know one person besides myself who has it. We are lucky to not have any issues I guess..


    Does the public even know about 1809? Why would manufacturers release products that need 1809 before it is released publicly?


    I don't feel too bad for the few manufacturers that are affected by this. How many crappy machines have they al released over the years that were the cause of people hating windows that was due to underpowered hardware?

    • Avatar

      ChiWax

      I've unfortunately had the pleasure of selling both great machines and "crap" machines made by many of MS partners. They've produced and sold millions of actually poor machines all over the world. Yet Microsoft having issues with an unknown update(except to bloggers) and it's a swarmy and juvenile story.


  5. Avatar

    pargon

    I updated a surface pro 3, a 6 year old core i5 laptop, a 5 year old core i5 desktop and a brand new ryzen 7 rig to 1809, have experienced zero issues, except apparently they had pulled the update by that time and media hadn't reported it yet so I have a build number watermark still. The build is rock solid. But it's normal for this site to make 8 articles about Microsoft messing up some code for early adopters. I don't know of anyone on this site that has actually experienced the problem though lol and yet apple pushed an update to everyone that BRICKS YOUR DEVICE, not just makes you restore from a backup you should have done....and apple has reports of doing this almost every year. The hypocracy of tech media, including thurrott is rather absurd.


    It's not the update speed that's the problem at all, it's the process they use of not ensuring quality code from planning to integration, it's always been a bad process and still is. Microsoft needs to switch to a different build system where each change is immediately tested and works

  6. Avatar

    waethorn

    #firethenutjob, Satay Nutella


    Hire more QA testers

  7. Avatar

    Angusmatheson

    Microsoft does not really care about its OEM partners - if it did, it would not make surface computers to compete with them. And it was really about kick starting the 2 in 1 - they have done that - but they have continue to back new surfaces and even expanded the line to include a traditional laptop. All of which compete with their “partners.” And when there is real risk - like making a device that runs ARM - they put Intel in their device and let the others run the risk of the putting out computers on a new architecture. So when there are problems like 1809 is delayed - Microsoft’s surface Go does fine and the OEMs get screwed with their trail blazing new ARM devices. The Surface computers are great. But they prove the Microsoft doesn’t really care about helping the OEMs. That they are screwing over the OEMs by delaying and not communicating about 1809 is to be expected. They aren’t really partners. Microsoft and the OEMs are now competitors.

  8. Avatar

    Greenberry Woods

    I thought the issues with 1809 are only happening when upgrading existing machines, which were using obscure features. The new machines are not being upgraded and therefore should not have the issues with 1809. Am I wrong? I'm not trying to defend Microsoft. They should have caught these issues and fixed them before releasing 1809.

Leave a Reply