New
#11
Thank you sir :) much better, both my other computers still on 1511 no problems, just the one older laptop updated to 1607. I'll probably start trying Edge as my default browser on the 1607 update.
Thank you sir :) much better, both my other computers still on 1511 no problems, just the one older laptop updated to 1607. I'll probably start trying Edge as my default browser on the 1607 update.
Verizon just bought Yahoo assets, so nothing would surprise me....
Log In - The New York Times
The interesting part of this whole thing is on my desktop W10 Home, and my laptop (Dell Latitude E6420) W10 Pro there's no problem. Yahoo webmail has the full feature mode enabled on both those, they're W10 1511.
The one with the problem is a laptop Dell Latitude E6400, W10 Pro 1511 was fine, no problems until I updated to 1607 last week, and now only basic mode is available on Yahoo webmail. Earlier posts' in this thread show what I found going through a few clicks, I'm going to update my other computers, either the desktop, laptop, or both this week.
We'll see how that goes, I did try Edge for a bit on the laptop with the Anniversary update and it seemed better than it was, might be able to move to it full time.
My problem is minor compared to some I've seen and posted on, I guess I'm lucky in that sense :)
Resurrected this thread because I've found a workaround/fix for this problem, as it turns out it is a Microsoft problem. Happened to see a topic on a Yahoo Forum titled "Yahoo Mail switches to Basic view after installing Windows 10 Anniversary Update" I've posted a screen shot of the post below. I did what was suggested and it worked immediately on both computers that had this problem. Tools > Compatibility View settings uncheck "Use Microsoft compatibility lists"
Now the problem is actually resolved thanks to Arcazeon on the Yahoo Forum
![]()
use this work around I did and it works
Those that use IE11 on Yahoo and have updated to the AU
Sorry about post did not see that there were two pages
Np lawnmower :) since I had marked this one solved due to no known fix at the time, I wanted to make a new thread for those that might not look at a solved thread.
My main objective was to get it out there so people would see it, I was sure I wasn't the only one having this problem.