RSS | SoundCloud | YouTube | iTunes | Google Play
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.
Sign up for our new free newsletter to get three time-saving tips each Friday — and get free copies of Paul Thurrott's Windows 11 and Windows 10 Field Guides (normally $9.99) as a special welcome gift!
"*" indicates required fields
pargon
Premium Member<p>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. </p><p><br></p><p> 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 </p>