Don't blame IE, blame the websites. IE now identifies as Gecko, which breaks the browser targeting scripts a lot of websites use, these scripts are worthless since IE10 already, and with IE11 even more so, IE is fully HTML5 spec compatbile. For developers this is a clear message, create HTML5 sites, not webkit/gecko websites right now we have the same dilemma we had with IE6.. developers should use a standard not special flake implementions. This is Microsofts atempt to drive the HTML5 spec forward as a standard without browser targeting scripts and css code. Though ofc MS has some still some -ms- tags, because not everything is part of the standard yet, especially stuff like their sizing for snap res, and stuff like the new animation boxes to create picture boxes that are smooth and accelerated. While Developers can use this and ms tries to get that into the standard, it's especially there for HTML5 apps on the Store.
Yes, on Web sites I get lots of DEBUG errors now, so much bad coding... then how does one work around it... FF is not so good for me either... never got use to that. but Chrome has done a pretty good job. on the crap sites... so many have pissy Certificates, and bad code.. at least MDL so far I have not had one ERROR here... So Thanks to the Web site here...
could someone remind me when the update version of 8.1 comes out? the non-iso release that is. there is going to be one or did I imagine someone saying there will be a MSU?
October 18 yes there will be an upgrade through Windows Store (available for Retail/OEM licenses only) make sure you install update KB2871389 (it updates store components and prepare it for Windows 8.1 release notification)
Install 8.1 Enterprise and you solved the problem. EDIT: There is no way to download WMP 12, but you can download from MS Download Center Media Feature Pack for Windows 8 N editions (I think it works on 8.1 too).
Or just wait for official release of windows 8.1 and hopefully Media Feature Pack for N and KN versions of Windows 8.1 will be released also.
Im getting a load of entries in event logs saying this: The Desktop Window Manager is experiencing heavy resource contention. Reason : CPU resources are over-utilised. Diagnosis : A sharp degradation in Desktop Window Manager responsiveness was observed. Anyone else? Any fix ?