Problem with igfxCUIService2.0.0.0 on every bootup

Hi this issue was first posted 4 years ago by @ginz for an earlier Intel driver version 1.0.0.0 (unresolved)

I am running Intel UHD GPU driver package version 27.20.100.8336 (brand new) and get now the following Information in Event viewer after each boot (4x). I downloaded the DCH driver package from Intel Support as the Acer Support driver was one year old (legacy).

Log Name: Application
Source: igfxCUIService2.0.0.0
Date: 18/07/2020 4:45:24 pm
Event ID: 0
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: Acer-Aspire-5
Description:
The description for Event ID 0 from source igfxCUIService2.0.0.0 cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event:

Received Post Shell Event 1


Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="igfxCUIService2.0.0.0" />
<EventID Qualifiers="0">0</EventID>
<Level>4</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2020-07-18T08:45:24.936563900Z" />
<EventRecordID>58323</EventRecordID>
<Channel>Application</Channel>
<Computer>Acer-Aspire-5</Computer>
<Security />
</System>
<EventData>
<Data>Received Post Shell Event 1
</Data>
</EventData>
</Event>

Tried to stop/disable Intel(R) HD Graphics Control Panel Service to no avail (same message pops up)
Anyone has an idea what causes this, can I ignore it?
Frank

@FrankW - I get this too, but mine is an older laptop (i5 based), with Intel HD 4600. My graphics driver is from January 2020 though (20.19.15.5126), but I was getting this before, so a subtle issue (not a fatal error, it seems to recover I think). I will research more and post here if I find anything useful. IMHO: Many Event Log entries are "clutter" and possibly caused by lack of defensive code in Windows routines, or timing issues, or mismatch between DLL modules.

igfxCUIService.exe is a file that comes with the Intel graphics driver. Try re-installing or updating the Intel graphics driver to see if that solves the problem.

TDOZ said:

@FrankW - I get this too, but mine is an older laptop (i5 based), with Intel HD 4600. My graphics driver is from January 2020 though (20.19.15.5126), but I was getting this before, so a subtle issue (not a fatal error, it seems to recover I think). I will research more and post here if I find anything useful. IMHO: Many Event Log entries are "clutter" and possibly caused by lack of defensive code in Windows routines, or timing issues, or mismatch between DLL modules.

I uninstalled the Intel HD Graphics panel in Device Manager and after booting the Intel HD GP in Services was gone, so was the error. There is a newer Intel G. panel in Windows Store that does not cause the error but those panels are not doing anything (redundant). Reinstalling the Intel HD or UHD drivers won't stop the error, I tried that.

Install the latest driver from Intel website.

Downloads for Intel(R) UHD Graphics 620

@FrankW - as @FreeBooter is saying, there is a new one just released on the 18th AUG for that UHD hardware (version 27.20.100.8587). It may well fix the issue. HOWEVER: the problem may just be in the GUI extension side, as I think the internal call for the "igfxCUIservice2.0.0.0.exe" is actually a script error, as that item does not exist on many systems. Download "AgentRansack" (a really good and quick file search service), and in expert mode, in the search box put "igfxCUIservice*" (without the quotes), and see for yourself.

By the way, if that download does NOT install, it may be a bad build, as I found one for my setup released on the same day, and it will not install, and downloading the ZIP file version, it will not expand using ANY unzip utility. It gives a 0x80004005 error with one item, so does not continue. I have opened a case with Intel for that, still awaiting an answer.