Home / diagnostic service host failed to start Diagnostic service host failed to start 06/04/2021 Very constant logging of:"The Diagnostic Service Host company faibrought about start due to the adhering to error: A privilege that the organization calls for to function appropriately does not exist in the organization account configuration. You may usage the Services Microsoft Management Console (MMC) snap-in (services.msc) and the Local Security Setups MMC snap-in (secpol.msc) to watch the company configuration and the account configuration."Checking Service condition it mirrors the business faults also prior to start:SERVICE_NAME: WdiServiceHost TYPE : 20 WIN32_SHARE_PROCESS STATE : 1 STOPPED WIN32_EXIT_CODE : 0 (0x0) SERVICE_EXIT_CODE : 0 (0x0) CHECKPOINT : 0x0 WAIT_HINT : 0x0The Same logon account (Local Service) is offered for DPS (Diagnostic Policy Service) and also it starts without a hitch.Morten RossSaturday, January 10, 2009 11:35 AM Answers 1 Sign in to vote Since your question or comment has gone unanswered, you have the right to send your research to the advancement team in this thcheck out. Have Comments around Windows 7 Beta Rating short articles helps other usersMark L. Fergukid MS-MVP Monday, February 16, 2009 8:53 PM All replies 0 Sign in to vote I have actually the very same difficulty.You watching: Diagnostic service host failed to startThe domain the client is joined to is making use of the Vista Security Guide team plans (i.e. User Rights Assignments from GPO Accelerator), which are allso being applied to Windows 7 test devices. Tuesday, January 20, 2009 6:21 PM 1 Sign in to vote Because your question or comment has actually gone unanswered, you have the right to send your research to the advancement team in this thread. Have Comments about Windows 7 Beta Rating short articles helps various other usersMark L. Ferguchild MS-MVP Monday, February 16, 2009 8:53 PM1 Sign in to vote I have the exact same problem. Windows 7 RC It started when I joined the mechanism to my domain so I"m guessing it has actually somepoint to execute through the domain policy. Update: Checked User Rights assignment on a non-domain Win7 PC and discovered the Profile System Performance Policy had actually the user NT SERVICEWdiServiceHost . Added this user to my domajor policy. It appeared to slow-moving dvery own the amount of times the error is logged yet hasn"t stopped it completely. Wednesday, May 6, 2009 5:40 PM2 Sign in to vote If you take a look at HKEY_LOCAL_MACHINESYSTEMCurrentControlSetservicesWdiServiceHostRequiredPrivileges, you"ll view that the service calls for (among others) the SeSystemProfilePrivilege privilege, but LocalService, which it is running under, does not have actually this privilege (at leastern on my computer in our firm domain). I have actually refixed this by providing SeSystemProfilePrivilege to the LocalService account (bereason I was not enabled to usage the Local Security Policy applet, I provided ntrights.exe from the Windows Resource Kit). It appears to work-related fine at the minute, however I am afrassist the privilege is going to be rerelocated instantly tomorrow when syncing information from the domain...Monday, July 13, 2009 4:36 PM7 Sign in to vote Hi...You need to modify team policy settings... edit Computer Configuration -> Policies -> Windows Settings -> Security Setups -> Local Policies -> User Rights Assingment -> Profile mechanism performance ... Check Define these settings and include Administrators and also NT SERVICEWdiServiceHostHelped for me...kaspikTuesday, July 21, 2009 8:32 AM0 Sign in to vote Adding wdiServiceHost to domajor policy was additionally the answer for us (many thanks kaspik) on a fresh W7 test box.Tuesday, August 25, 2009 10:14 PM5 Sign in to vote For me, the deal with was to include "LOCAL SERVICE" in the accounts offered that defense ideal, "Profile system performance" in the correct doprimary plan (in our case, the default domain policy.)It only had "Administrators" detailed. I tried the "WdiServiceHost" and also "Local System" - yet either acquired the "can"t be verified" as soon as presolving with "NT Service" or through NT AUTHORITY", and also acquired group plan handling errors once not prefixing through anypoint.After including "LOCAL SERVICE", I ran gpupdate /force on the clients, however still had to reboot before the Event ID 7000 errors stopped.Friday, November 13, 2009 10:36 PM0 Sign in to vote For us I found that the line in question have to actually be:=> Profile device performance – Administrators, NT ServiceWdiServiceHost, Local ServiceNote: this readjust alone will certainly still create the stream of device errors logged / Creating a brand-new error detailed below.__________________________________________________________________________Event ID: 7000 - WdiSystemHostGeneral:The Diagnostic Service Host service faicaused start due to the complying with error:The account mentioned for this business is various from the account mentioned for various other services running in the same procedure.See more: Windows 7 Secrets__________________________________________________________________________The below instructions perform but sheight all device produced errors on this concern.1. Go to Start and also click Run then kind Services.msc then press enter.2. Now ideal click the "Diagnostic Policy Service" and also go to properties. Now under the "Log On" tab inspect if "This account" has been schosen and utilizing the "Local Service" is selected for it. Note that if you have to readjust this; when it asks for the "Local Service" password, sindicate delete what is there and also hit use.3. Similarly check for "Diagnostic Service Host" company if and also go to properties. Now under the "Log On" tab check if "This account" has actually been selected and also using the "Local Service" is schosen for it. Keep in mind that if you need to change this; when it asks for the "Local Service" password, sindicate delete what is there and also hit apply.See more: Solved: Dell Inspiron 2-In-1 Screen Rotation Settings, Correcting Screen Rotation Settings4. Now right click the "Diagnostic System Host" and go to properties. Now under the "Log On" tab examine if "Local System account" is selected and also make sure that the "Allow business to connect through desktop" is NOT schosen. 5. If any kind of of the alternatives previously declared do not match, then you might wish to apply the settings directed and check if the problem is readdressed.