Solved Event Log Error 1023 .Net Runtime (OneApp.IGCC.WinService.exe) Intel Graphics Drivers?

Just built a new Windows 11 workstation with an ASUS Prime z790-A featuring Intel 770 Graphics.

Here is currently installed driver version (OEM from ASUS):



The PC is working very well - but I do keep getting this specific Event Viewer error at each restart:

Description: A .NET application failed.
Application: OneApp.IGCC.WinService.exe
Path: C:\Windows\System32\DriverStore\FileRepository\igcc_dch.inf_amd64_b347022cd0d38bb1\OneApp.IGCC.WinService.exe
Message: You must install or update .NET to run this application.

App: C:\Windows\System32\DriverStore\FileRepository\igcc_dch.inf_amd64_b347022cd0d38bb1\OneApp.IGCC.WinService.exe
Architecture: x64
Framework: 'Microsoft.WindowsDesktop.App', version '7.0.0' (x64)
.NET location: C:\Program Files\dotnet\

No frameworks were found.

Learn about framework resolution:
Troubleshoot app launch failures - .NET

To install missing framework, download:
Download .NET 7.0 Desktop Runtime (v7.0.15) - Windows x64 Installer

This message goes on and on about installing the .NET 7.x runtime - which I HAVE already done. But the error persists.

I found the actual service in Services - I see it is set to Automatic but I try to start it - it fails with another super long obscure error message.

Finally - I can confirm I can open the Intel Graphics Control center normally from the Start menu and all is well.

So - what exactly does this service do and is it necessary for normal operations?

Secondary Q: What is best practice for those of us using Intel Graphics? Go with OEM or Intel WHQL (like at the top of this board)?

Appreciate any insight.

Cheers

Sonic.

Managed to resolve this issue after finally getting the right combinations of .NET 7.x runtimes installed

But my main question remains - OEM or Intel branded drivers for a third party motherboard?

Best practices or performance reasons?

B

SonicMojo said:

OEM or Intel branded drivers for a third party motherboard

Click to expand...

Folks have varied opinions when it comes to the source and methods of updating drivers. My own personal preference for drivers in general is first the OEM, second Intel, and absolutely as a very last resort, Windows Update.....And never, never, ever from any driver updater app.

I have disabled including drivers with windows update. I use my OEM's updating tool to manually scan my system once a month and let it install any drivers/uefi bios updates it finds.
That said, I will veer from this if I experience a problem with graphics. I'll use Intel Driver Support Assist tool to scan for and install its latest driver.
If I'm not having a problem with graphics, I'll wait until any new Intel driver hits the OEM's server which usually shows up there within a month or so of Intel releasing it. Either way, I am comfortable using my OEM updating app or Intels' to acquire my drivers. Neither has ever steered me wrong or screwed me up yet.

glasskuter said:

Folks have varied opinions when it comes to the source and methods of updating drivers. My own personal preference for drivers in general is first the OEM, second Intel, and absolutely as a very last resort, Windows Update.

I have disabled including drivers with windows update. I use my OEM's updating tool to manually scan my system once a month and let it install any drivers/uefi bios updates it finds.
That said, I will veer from this if I experience a problem with graphics. I'll use Intel Driver Support Assist tool to scan for and install its latest driver.
If I'm not having a problem with graphics, I'll wait until any new Intel driver hits the OEM's server which usually shows up there within a month or so of Intel releasing it. Either way, I am comfortable using my OEM updating app or Intels' to acquire my drivers. Neither has ever steered me wrong or screwed me up yet.

Click to expand...

I tend to stick with OEM too - but in the case - this setup was completely screwed. How could this driver package (along with its fairly useless baggage) not know to pack some sort of .NET package along for the ride?

This was a major PITA to figure out.

S

There's a port that .NET apps use to communicate with each other on the same device. Until relatively recently, that same Intel service would open that port in exclusive mode, so other .NET apps could not communicate. It would seem their .NET developers need some additional training.