TriAngular

Was going to post it on MSDN but here seemed better, since I first complained (here) about not being able to update Windows 10 on my ASUS AMD-A10 M11BB (a VERY common, powerful, and affordable computer sold at Best Buy for 3+ year, starting near the end of Windows 8). Thank you Microsoft (and Best Buy?)! You finally updated my ASUS A10 M11BB to the latest version, only noticed it because of a new "red screen of death" due to ASUS's failure to update the BIOS (still, was stable for days now), I still 100% support your choice though to protect my security. And thank you to LInus and the awesome team supporting you, you guys are great!

It's more than just great news for jailbreaking... This exploit is going to allow unsigned iOS version installation (I'll finally have good battery life on my SE again by downgrading to 12.4.1) or even the installation of other operating systems!

I didn't have graphics drives issues upgrading to 1607, my network card wasn't supported (and some other devices, audio, etc). Either way you don't stand for that, if you are ASUS, you make sure that one way or another updates are made or hardware is recalled as defective. Edit: It was being sold at Best Buy while Windows 10 was already released!! So they were selling crap that they knew couldn't be upgrade!?!?!? Who do I sue? Edit2: Also at what point do you blame Microsoft? They couldn't come up with a software workaround? It worked fine in Windows 8! So frustrating, and I know there is at least 50,000 of these computers out there, they sold at Best Buy for almost two years, and I sold about 100 of them myself, probably 500 as a store! ;( Edit3: I am going to try a reinstall, thanks for the reinstall advice, from the others (needs a reset anyways).

Score one here, I can't believe I missed this! Hopefully fixes the blue screens of death probably not the update issue though. But while doing that all this other great advice appeared!

Did all that... Their driver on their web site have not been updated since before Windows 10 build 1607 was released (the build I can't update too). I've been trying to update this almost two years now. I'll check the memory, the last blue screen was memory management related. Some extra bits of info... Microsoft used to let me try to update to 1607, it has been running on this computer before. I used to have to manually roll it back because the network drivers were not supported. But a newer update process will roll it back to 1507 automatically if critical drivers are not supported.

on an From 2013-2016 I was working at Best Buy as a Computer Sales Associate. I just loved the ASUS A10 3.7GHz Model #M11BB Desktop (came with Windows 8.0 originally), even purchased one myself. It only costed $500 and was the best performance for the price at the time (and at Best Buy). It was at my store for almost 2 years, and I probably sold 100 of them myself... but then Windows 10 came out. They even continued to sell the computer at Best Buy, and indeed it is compatible with Windows 10 up to build 1507 (very old), if you don't mind the daily blue screens of death. When Windows 10 build 1607 came out it changed something to do with drivers, and it broke the updates for the ASUS M11BB. ASUS phone support's official response is that the hardware doesn't support Windows 10! Considering the overlap with the release of Windows 10, that is some REALLY bad support IMHO. More like they didn't want to support the driver changes that took place between Windows 10 builds 1507 and 1607. If I had a faster computer to run Windows 10 on, I would just run Linux on the M11BB, it LOVES Linux. I would love to see this horrible travesty brought to light on a future episode, or at least talked about here. You guys have enough power to make them fix this for the 50,000 people that are just screwed now. Also if anyone knows how I can hack this thing to update it, that information would be greatly appreciated as well!

Too far, hmmm...Full Borg assimilation or loss of individuality. After a bodily death, connect my brain up to VR, I'm cool with that!

I've tested this simple web site I made with four iOS browsers: Safari, Firefox, Chrome, and Edge. What the webpage does is count the number of touch events (or taps). Chrome and Edge both register all taps... but with Safari and Firefox, five quick taps shows as three (two events were dropped). Tested before and after iOS 13 update (no difference). The test device is an iPhone SE. I suspect Firefox is using Safari's JIT compiler, while Edge and Chrome probably each use their own JIT compilers. Can anyone else reproduce this issue?