running unsigned drivers, or installing on a machine without a TPM, or setting up an offline account on the Home edition.
I don't see anything in Windows 11 that makes it more of a walled garden compared to Windows 10.Īll the security measures can be bypassed by a technical user if need be, e.g. So some tech journals probably monitor intel for new articles and now they are copying from each other with no one checking if the news is older than moldy bread.Įdit: looking at SA-00315 i wonder if DX12 ever only worked on those chips because it gracefully overflowed some buffersĮdit2: mmh the big new thing in DX12 were low level APIs.Īs far as I can see, these are all legitimate security features that will help protect the users (e.g. One more thing: the article linked here has a "lastModifieddate" metatag of - did they set the wrong publishing date in their CMS? hahaha. with a small-print of "mostly but not completely".Įdit2: it seems intel was under pressure at the time to push drivers that fix game crashes in triple-A games on win10 on haswell. When looking at old patch notes, those chips for some time did officially feature DX12. Note that those chips are two years older then DX12 which was released july 2015 together with win10.Įdit: however intel silently changed the list of supported APIs their forum staff is linking. And intels support staff responded with "that chip does not officially support dx12". People have been complaining about dx12 not working with that driver on haswell in early 2020 on their forums. The bugs fixed disclosed some time later in.
0 kommentar(er)
