Service Unreliable after latest windows updates (Oct 2021)

After applying October 2021, the Start8 service frequently does not start up after the machine restarts. This results in Start8 not running for anyone (Shared terminal server). Is anyone else experiencing this, or have a fix?

Running Start8 on Server 2012

Thanks

5,343 views 4 replies
Reply #1 Top

Hello,

I have forwarded your report to the Stardock support team for their review and recommendations.

Please keep an eye on this thread for any updates.

We really do appreciate your feedback, thanks.

Reply #2 Top


After applying October 2021, the Start8 service frequently does not start up after the machine restarts. This results in Start8 not running for anyone (Shared terminal server). Is anyone else experiencing this, or have a fix?

Running Start8 on Server 2012

Thanks

Is there anything in the Even Viewer on why the service failed to start?  Does 'Services' think its running but its not (and is it set to Automatic still)?

Sean Drohan
Stardock Support Manager

Reply #3 Top

I'm wondering if setting it to delayed start will help, or setting some options on the Recovery tab.

 

Services does not think it is running when it is having trouble. It is still set to Automatic.

 

System Event log shows these two errors:

Log Name:      System

Source:        Service Control Manager

Event ID:      7009

Level:         Error

Description: A timeout was reached (30000 milliseconds) while waiting for the Stardock Start8 service to connect.

 

Log Name:      System

Source:        Service Control Manager

Event ID:      7000

Level:         Error

Description:

The Stardock Start8 service failed to start due to the following error: 

The service did not respond to the start or control request in a timely fashion.

 

Reply #4 Top

Quoting brianash, reply 3

I'm wondering if setting it to delayed start will help, or setting some options on the Recovery tab. 

Services does not think it is running when it is having trouble. It is still set to Automatic.

Does a manual restart of the service resolve the issue?

Sean Drohan
Stardock Support Manager