Diagnostic Service Host error 7023.

Topic

New Reply

I don’t know if I need your help or not but here’s the issue: ever since I installed the April 2021 cumulative update, my Event Log has shown a pair of errors 7023, on startup. The explanation given in properties is “the WdiServiceHost service terminated with the following error: The requested control is not valid for this service.” When I checked the pertinent service it is set on automatic but it is not running, and the start area is greyed out.

A copy of the error looks like this:

Log Name: System
Source: Service Control Manager
Date: 4/19/2021 2:26:00 PM
Event ID: 7023
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: DESKTOP-SCFKLGJ
Description:
The WdiSystemHost service terminated with the following error:
The requested control is not valid for this service.
Event Xml:
<Event xmlns=”http://schemas.microsoft.com/win/2004/08/events/event”&gt;
<System>
<Provider Name=”Service Control Manager” Guid=”{555908d1-a6d7-4695-8e1e-26931d2012f4}” EventSourceName=”Service Control Manager” />
<EventID Qualifiers=”49152″>7023</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8080000000000000</Keywords>
<TimeCreated SystemTime=”2021-04-19T18:26:00.8612268Z” />
<EventRecordID>10322</EventRecordID>
<Correlation />
<Execution ProcessID=”856″ ThreadID=”984″ />
<Channel>System</Channel>
<Computer>DESKTOP-SCFKLGJ</Computer>
<Security />
</System>
<EventData>
<Data Name=”param1″>WdiSystemHost</Data>
<Data Name=”param2″>%%1052</Data>
<Binary>570064006900530079007300740065006D0048006F00730074000000</Binary>
</EventData>
</Event>

Candidly I have no idea what this explanation says about my computer or whether or not the error is consequential to the operation of my computer. All I know is that it comes up very day twice at startup. I am at a loss as to what to do, if anything, because my computer shows no other errors except for the inconsequential DCOM 10016 warnings which I have been told to ignore. In the meantime my computer has no issues. It starts up quickly and I can go to all the sites I regularly visit without any problems.

Peace, CAS

Reply | Quote

Replies

That seems to be part of the Windows diagnostic services.
As long as everything seems to be running I would ignore the error.

cheers, Paul

1 user thanked author for this post.

CAS

Reply | Quote

According to the info at the Windows 10 Service Defaults website, the default setting for the WdiServiceHost service (Diagnostic Service Host) should be manual, not automatic.

The description for the service indicates “In Windows 10, it’s started only if the user, an application or another service starts it.” so your error might be because windows is trying to automatically start it on boot up instead of waiting for whatever other process would manually start it.

On my PC (Windows 10 Pro 20H2 without the April update installed) both the WdiServiceHost service (Diagnostic Service Host) and the WdiSystemHost service (Diagnostic System Host) are set for “manual” while the DPS (Diagnostic Policy Service) that actual uses them is set to automatic.

You should check to see if changing your services to those same settings gets rid of the error.

2 users thanked author for this post.

CAS, doriel

Reply | Quote

the default setting for the WdiServiceHost service (Diagnostic Service Host) should be manual, not automatic.

I agree, good observation. If there is automatic setting, it could cause the error in event log. Because this service should be “triggered”, not automatically started on the boot of Windows.

Dell Latitude 3420, Intel Core i7 @ 2.8 GHz, 16GB RAM, W10 22H2 Enterprise

HAL3000, AMD Athlon 200GE @ 3,4 GHz, 8GB RAM, Fedora 29

PRUSA i3 MK3S+

1 user thanked author for this post.

CAS

Reply | Quote

CAS wrote:
The requested control is not valid for this service.” When I checked the pertinent service it is set on automatic but it is not running, and the start area is greyed out.

Which pertinent service is not running? WdiServiceHost alias Diagnostic Syetem Host?
It cantbe started manually. Mine is grayed too. you cant satrt this on your own.

Lets learn czech! 🙂 The screenshot says:

“System error 5”
“Access denied”

Dell Latitude 3420, Intel Core i7 @ 2.8 GHz, 16GB RAM, W10 22H2 Enterprise

HAL3000, AMD Athlon 200GE @ 3,4 GHz, 8GB RAM, Fedora 29

PRUSA i3 MK3S+

1 user thanked author for this post.

CAS

Reply | Quote

Sometimes it seems best when things are working just to leave well enough alone. The setting will remain at automatic. As you read on you will see how I reached that conclusion.

I have tried setting the diagnostic service host to manual and the error still appears. I’ve disabled it with the same result. It doesn’t seem to matter what the setting is because the error seems to always appear. In fact, when I set it to manual I get a  bonus; a Kernel-Event Tracing error that looks like this:

Log Name: Microsoft-Windows-Kernel-EventTracing/Admin
Source: Microsoft-Windows-Kernel-EventTracing
Date: 4/19/2021 7:21:39 PM
Event ID: 2
Task Category: Session
Level: Error
Keywords: Session
User: SYSTEM
Computer: DESKTOP-SCFKLGJ
Description:
Session “PerfDiag Logger” failed to start with the following error: 0xC0000035
Event Xml:
<Event xmlns=”http://schemas.microsoft.com/win/2004/08/events/event”&gt;
<System>
<Provider Name=”Microsoft-Windows-Kernel-EventTracing” Guid=”{b675ec37-bdb6-4648-bc92-f3fdc74d3ca2}” />
<EventID>2</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>2</Task>
<Opcode>12</Opcode>
<Keywords>0x8000000000000010</Keywords>
<TimeCreated SystemTime=”2021-04-19T23:21:39.9997026Z” />
<EventRecordID>49</EventRecordID>
<Correlation />
<Execution ProcessID=”4″ ThreadID=”336″ />
<Channel>Microsoft-Windows-Kernel-EventTracing/Admin</Channel>
<Computer>DESKTOP-SCFKLGJ</Computer>
<Security UserID=”S-1-5-18″ />
</System>
<EventData>
<Data Name=”SessionName”>PerfDiag Logger</Data>
<Data Name=”FileName”>
</Data>
<Data Name=”ErrorCode”>3221225525</Data>
<Data Name=”LoggingMode”>8388736</Data>
</EventData>
</Event>

I’ve reached the same conclusion as Paul so I’m just going to ignore these errors. I’ve read about registry fixes to keep the error from appearing but nothing that actually “fixes” it. (I’m not messing with my registry just to clean up my event log.)  Thanks to all of you for responding.

Peace, CAS

P>S>Just so you know, I always run a search for other “fixes” and review them before coming to this site for answers because I don’t like to waste your time. I’ve never gone wrong with anything that’s been suggested here.

Reply | Quote