Hi, I still have a login problem: XP is hanging after typing in the user and password at the login screen. In this time is the login screen visible ("Settings are loaded") what takes about 30 to 40 seconds. In the eventviewer is after every boot an entry with ID = 7011 which is explained as "Timeout (30000ms) waiting for a transaction response from the Windows Steady State Service". I deactivated every service which is also started during the login, I uninstalled the virus scanner - nothing helped. Regards, Stefan.

Hi Stefan, does the issue occur on every user on the computer? Have you tried reinstalling Windows SteadyState?

Hi, it occurs on every user (administrator and "protected" users). I'm not sure about reinstalling but I think I did it shortly after the first installation. Regards, Stefan.

Fast update ... Reinstalling did not help!

HI, I have the same problem on all 7 computers in our library that SteadyState has been installed on. I have them set to have a logon disclaimer screen, and if hey are left idle without being logged on, they come up more quickly, as the SteadyState process must "fix" itself after a short period of time.

Dear Shean Zu, will there be any update? My problem is still unsolved ... Regards, Stefan.

Hi Stefan, you can also try the following workaround and check the result: 1. Run your RegEdit 2. Locate: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Windows SteadyState 3. Replace the value of DependOnGroup (from blank) with "C:\WINDOWS\System32\wscsvc.dll" 4. Restart your System Hope this helps!

Hi Sean Zhu, it does not help - the service can't be started. In the Eventviewer I can find the following entry: "The service Windows SteadyState depends on group c:\windows\system32\wscsvc.dll. But no member of this group has been started." (Translated from German) Regards,Stefan.

Hi Stefan, let's try to start wscsvc service and check the result: 1. Click start, go to run. 2. Type services.msc and press enter. 3. Locate Security Center on the right panel. 4. Start the service and set startup type to "Automatic". If the service cannot be started, please let me know the error. 5. Then, lets restart the computer and check the result.

Hi Sean Zhu, I did what you wrote. The security center service is started without any errors. The startup type was already "Automatic". But Windows SteadyState isn't running (as like described before) and there are again the entries in the eventviewer. I tried to start the SteadyState service from services.msc but there comes the error 1068 with the (from german translated description) "The service Windows SteadyState could not be started. The dependend service or the dependend group could not be started". But the security center is running and the path to de wscsvc.dll is also correct. Regards, Stefan.

Hi Stefan, based on the error message, let's check the following two dependent services and see if they can be started: Windows Management Instrumentation Remote Procedure Call (RPC) If any of the above service cannot be started, please let me know the error message. If they can be started successfully, lets check SteadyState service again.

Hi Sean Zhu, if these are the services "winmgmt" and "RpcSs" (my OS is in German) - both are running without any error. SteadyState can't be started - there is still the same error.

Hi Sean Zhu, no answer anymore?

Hi Sean Zhu, is there really no help?

Hi, WesternStone, you can try setting the Windows steadystate service to manual instead of automatic. Do not put additional item in the depency group except the original two: Windows Management Instrumentation Remote Procedure Call (RPC) It works for me. No more delay when booting and the service started normally. I am using xp home. WesternStone wrote: Hi Sean Zhu, is there really no help?

Hi Singa, I already read this advise somewhere else and I didn't try it because it sounds a little bit stupid to me: "Switch the Windows SteadyState Service from automatic start to manual and will be started and will work better!" But it helps! Thank you very much for your help!!! @Microsoft: Can anybody explain this strange behaviour of the program? Best regards, Stefan.

Hi, Stefan. I am glad that it works for you. Yes, the program does behave strangely sometimes, but it is still a useful and good one andfree some more. WesternStone wrote: Hi Singa, I already read this advise somewhere else and I didn't try it because it sounds a little bit stupid to me: "Switch the Windows SteadyState Service from automatic start to manual and will be started and will work better!" But it helps! Thank you very much for your help!!! @Microsoft: Can anybody explain this strange behaviour of the program? Best regards, Stefan.

Singa wrote: Hi, WesternStone, you can try setting the Windows steadystate service to manual instead of automatic. Hi, Doing this will break the Windows SteadyState service, and prevent it from performing its most important tasks. When a service is set to "manual," it is not started until it is requested. In the case of SteadyState, this means that the service does not start until after a user logs in (when SCTUINotify queries the service for something). Thus, it won't be able to run updates during the update cycle (and also won't be able to reboot after updates are complete), disable/enable user accounts, or a host of other tasks. Not recommended. Thanks, Rob Elmer Development Lead Windows SteadyState

I'm having the same issue is there 'STILL' no fix for this????I'm receiving this error "Timeout (30000 milliseconds) waiting for a transaction response from the Windows SteadyState service" on my XP SP3 netbooks. It eventually starts and the users can logon but it causes a long pause at logon (can be 1 minute).I'm getting this on more than one netbook (they're brand new) and i've tried reinstalling Steadystate and a clean install of XP. I only downloaded Steadystate the other day so it's the latest version.I've followed the suggestions in the link below but non of them have sorted it. Can anyone else suggest a way to troubleshoot this issue?http://social.technet.microsoft.com/Forums/en-US/windowssteadystate/thread/4275d3f5-6595-4cc4-a26e-0a4899880b7fThanks.

I realize this post has been dormant for over a year, but I read a ton of posts related to this "Timeout (30000 milliseconds) waiting for a transaction response from the Windows SteadyState service" log in my event viewer. I also noticed that my Terminal Service would start after the timeout error message in my event viewer. I realized that SteadyState is not programmed correctly and it is indeed dependent on the Teminal Services service. I found this MS Support article http://support.microsoft.com/kb/193888 that explains how to add dependencies to any service. So I added the Terminal Services service as a dependency to the Windows SteadyState Service and viola....the timeout error disappeared and my account did not hang at login.