Asura Deva Jun 18, 2019 @ 1:58pm
Steam Event viewer Error logs
Hi,

Has anyone else started to notice some event viewer logs with steam?
Ever since around the start of June i see in event viewer 2 Error logs:

A timeout was reached (30000 milliseconds) while waiting for the Steam Client Service service to connect. - Event ID 7009
The Steam Client Service service failed to start due to the following error:
The service did not respond to the start or control request in a timely fashion. - Event ID 7000

It has happend on both of my computers 1 being Windows 1903 other 1809 build.
On 1903 i mainly run games and stuff like that (All seems to be working fine but as soon as steam does its update for a newer version those event viewer logs get pasted).
On my 1809 build i did a fresh install of windows and steam and yet those errors still pop up. So it can't be a computer or windows problem since a windows that has nothing on but steam still produces its error.

I have tried using both Beta client and regular client - no difference.

Any ideas what causes those errors and any fix for it?( Once again will say that nothing seems to be broken but those Errors do sound alarming)

Something went wrong while displaying this content. Refresh

Error Reference: Community_9734361_
Loading CSS chunk 7561 failed.
(error: https://community.fastly.steamstatic.com/public/css/applications/community/communityawardsapp.css?contenthash=789dd1fbdb6c6b5c773d)
Showing 1-6 of 6 comments
[CaN'i CaCcIa] Joe Sep 18, 2019 @ 10:49am 
Hi!
I've got the same two event IDs when I launch Steam client (I run it on Windows 10 1903). I'm searching around for a way to increase client's wait timeout and, in the meanwhile, I read somewhere that if you run Steam with administrator's privileges you won't get those errors again: I tried it and it worked.
I hope this helps.
Bye :)
ReBoot Sep 18, 2019 @ 10:53am 
Is there something wrong with Steam, does something not work? You know, "error" messages can be a part of a normal workflow.
[CaN'i CaCcIa] Joe Sep 18, 2019 @ 11:09am 
I found a wait to increase services' timeout:
registry key
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control
value (if doesn't existe, create DWORD type)
ServicesPipeTimeout
I set this at 40000.
Now I restart PC and will tell... stay tuned

***DISCLAIMER***
I am not responsible for physical or mental damage caused by these modifications: make them at your own risk!
Last edited by [CaN'i CaCcIa] Joe; Sep 18, 2019 @ 11:18am
[CaN'i CaCcIa] Joe Sep 18, 2019 @ 11:19am 
Ok, Steam client timeout error is no more but appeared tons of event ID 10005 related to wuauserv (I don't know if it's related to this registry modification or not).
So, I'll rollback and will launch Steam with admin privileges.

EDIT: hmm... On second thought, I'll leave the modification and see if those IDs 10005 will be back again 'cause they appeared only after the 2nd reboot (they were not at 1st and 3rd reboot). I'll keep it under observation.
Last edited by [CaN'i CaCcIa] Joe; Sep 18, 2019 @ 11:32am
Asura Deva Sep 18, 2019 @ 8:25pm 
Those errors randomy dissapeared for me atm. Now they sometimes appear as a "warning" in Logs but not as "Error" so i guess regular Windows processing.
I restored a previous system image but I kept having those 10005 wuauserv errors, so I think that steam modification (service timeout) was not the culprit (and worked as well).
Yes, "regular" Windows processing.
Showing 1-6 of 6 comments
Per page: 1530 50

Date Posted: Jun 18, 2019 @ 1:58pm
Posts: 6