Microsoft released some Patch Tuesday fixes last November but has only today admitted they have been causing errors with Intel graphics hardware running DirectX or Direct3D applications. The issues were introduced with KB5019980 / KB5019961 for Windows 11 users and KB5019959 for Windows 10 users, notes Neowin. Microsoft’s KB releases target known Windows quirks and wrinkles, yet this isn’t the first time that they have come with their own crop of issues.
The Microsoft-induced DirectX or Direct3D application bugs are described as intermittent, which might be one of the reasons why they persisted for so long without even an official workaround. Microsoft said, "After installing KB5019980, you might receive an error with apphelp.dll on Windows devices using Intel graphics drivers with versions 220.127.116.1163 up to 18.104.22.1680.” Additionally, it explained, “This issue might happen intermittently and affects apps which use DirectX or Direct3D to render part or all of their content.” It appears to be the case that apphelp is being an app hindrance.
Looking on the bright side, Microsoft now admits and acknowledges this apphelp.dll bug, and while it says that a resolution will be in an upcoming update, there is a workaround that affected users can try.
Microsoft says the apphelp.dll bug affecting DirectX and Direct3D titles can usually be sidestepped by applying the latest Intel drivers. It recommends users “install an Intel graphics driver with a later version than 22.214.171.1240.” That driver was released back in December 2021, so we are pretty sure Intel Arc discrete graphics users aren’t clinging to this outdated software. However, depending on processor generation, some PCs might not offer newer graphics drivers for iGPUs.
On the topic of Intel graphics drivers, we have been pleased to report the sterling progress the new entrant into the PC dGPU market has made in recent weeks/months. Only last week, Intel released a new graphics driver providing a fantastic DX9 performance uplift – targeting an area where the launch driver was very weak.
Stay on the Cutting Edge
Join the experts who read Tom's Hardware for the inside track on enthusiast PC tech news — and have for over 25 years. We'll send breaking news and in-depth reviews of CPUs, GPUs, AI, maker hardware and more straight to your inbox.
Mark Tyson is a Freelance News Writer at Tom's Hardware US. He enjoys covering the full breadth of PC tech; from business and semiconductor design to products approaching the edge of reason.
SOS, DD with updates.Reply
I'm not the only one who saw that "Critical Error" image at the top of the article and heard it in the voice of the turrets from Portal, am I?Reply
You're probably one of the few.King_V said:I'm not the only one who saw that "Critical Error" image at the top of the article and heard it in the voice of the turrets from Portal, am I?
All I heard was the Win95 "ding" from the error popup.
For reference: RkeXUifHY6gView: https://www.youtube.com/watch?v=RkeXUifHY6g