![]() |
|
Welcome to Vista Banter. You are currently viewing our boards as a guest which gives you limited access to view most discussions, articles and access our other FREE features. By joining our free community you will have access to ask questions and reply to others posts, upload your own photos and access many other special features. Registration is fast, simple and absolutely free so please, join our community today! If you have any problems with the registration process or your account login, please contact contact support. |
|
|||||||
| Performance and Maintainance of Windows Vista A forum for performance and maintenance tasks in Windows Vista. (microsoft.public.windows.vista.performance_maintainance) |
|
|
LinkBack | Thread Tools | Display Modes |
|
|||
|
Anyone know a fix for the error Windows was unable to open service
WdiServiceHost for writing on local computer |
|
|||
|
It's set to manual and has no dependencys also the start stop buttons
are greyed out the recovery tab gives this error Windows was unable to open service WdiServiceHost for writing on local computer. On Fri, 20 Feb 2009 06:32:47 -0500, "Rick Rogers" wrote: Hi, It may be the service itself or a missing dependency. Normally, this service is not set to start automatically but rather manually (on demand). Run services.msc from the start/search line and scroll down to the Diagnostic Service Host. Double click it and check the settings to ensure it's set for manual. On the Recovery tab, you may want to set the first failure option to restart the service. |
|
|||
|
Followup I get this in eventviewer The Diagnostic Service Host service failed to start due to the following error: A privilege that the service requires to function properly does not exist in the service account configuration. You may use the Services Microsoft Management Console (MMC) snap-in (services.msc) and the Local Security Settings MMC snap-in (secpol.msc) to view the service configuration and the account configuration. On Fri, 20 Feb 2009 06:32:47 -0500, "Rick Rogers" wrote: Hi, It may be the service itself or a missing dependency. Normally, this service is not set to start automatically but rather manually (on demand). Run services.msc from the start/search line and scroll down to the Diagnostic Service Host. Double click it and check the settings to ensure it's set for manual. On the Recovery tab, you may want to set the first failure option to restart the service. |
|
|||
|
On Fri, 20 Feb 2009 20:25:43 -0500, "Rick Rogers"
wrote: What account shows as being used on the logon tab of the service's properties? It should be Local Service - have you disabled any of the system accounts? It is Local Service and I haven't disabled any accounts. I think I'm missing a file/folder for it. |
|
|||
|
On Fri, 20 Feb 2009 20:25:43 -0500, "Rick Rogers"
wrote: What account shows as being used on the logon tab of the service's properties? It should be Local Service - have you disabled any of the system accounts? I deleted the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\WdiServiceHost\Security key and the start button is no longer gryed out but I now get this error when I click the start button... |
|
|||
|
To get the start stop buttons to stop being greyed out. I put it back
though because it didn't help. On Sat, 21 Feb 2009 16:11:44 -0500, "Rick Rogers" wrote: Why did you delete that? |
| Thread Tools | |
| Display Modes | |
|
|