SessionLauncher

[Kaj]

Does anyone get the following message in the error log of WinXP SP2: The service SessionLauncher could not be started. Could not find the file or path. It looks it something to do with Easy Media Creator 10

[TBeaulieu]

Yes. I get the same error. If you look in at the target exe of the service, you'll see why. It's pointint to an exe that *was* in a temp folder created during the install. BIZZARRE!

 

C:\DOCUME~1\TODDBE~1\LOCALS~1\Temp\DX9\SessionLauncher.exe

 

I, too need a fix. I'm going to contact support.

[Kaj]

I have mailed to Roxio Customer Care and get the following answer:

SessionLauncher appears to be a installation component related to the DirectX installation process that does not always correctly remove itself after installation. To resolve this issue, we will manually remove it:

 

a. Click on the 'Start' button and select 'Run'.

(Windows Vista users will have to hold down the Start button and press the letter R)

b. Type 'msconfig' and click on the 'OK' button or press the 'Enter' key.

c. Select the 'Services' tab over on the right side.

d. Click on the 'Hide All Microsoft Services' checkbox.

e. Find and uncheck the box for 'SessionLauncher' and hit OK.

f. Click 'YES' to restart the computer.

 

 

If the information provided does not resolve your issue simply update your webticket with a detailed explanation with the steps you have tried and any error messages you receive.

 

Regards,

 

Roxio Technical Support

http://www.roxio.com/enu/support

 

I am not quite sure it is the right way to fix this problem. It would be good if anyone more would contact Roxio for a better fix of this problem. Using the Roxio proposal causes only selective start but not a normal start of Windows. According to my opinion Roxio should create a fix that remove SessionLauncher in a correct way.

 

Kaj

[gi7omy]

Once you uncheck the box and reboot, you can tell the nag screen "Yes, I do KNOW I disabled a startup item - now go away and don't ask again"

[grandpabruce]

Are you using some EMC 10 program when you get that notification?

[wowexec]

The log entry is noting that a call was made to sessionlauncher, but sessionlauncher was not found.

 

I can't see what use blocking the execution of sessionlauncher with msconfig can be to anyone, when the log entry is complaining that sessionlauncher is not there!!. It seems the service droid has misunderstood the problem.

 

If you locate the registry entry which calls sessionlauncher and remove that entry, the error should not show in the log in future.

 

Regards,

Brendon

 

Hi Brendon,

the service reference in registry is located in:

 

Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SessionLauncher

 

and in some configuration in this keys too:

 

Computer\HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\SessionLauncher

 

Computer\HKEY_LOCAL_MACHINE\SYSTEM\ControlSet002\Services\SessionLauncher

 

--------------------------------------------

 

The service is from Sonic.

I don't know what does it do specifically so i try to reinstall it from an extracted packages before to remove it.

 

 

Update: I've decided to delete the registry entries and the error in the event viewer are gone.

 

Update2: A more convenient and clean way to remove the service is to open a "command prompt" in Vista is needed to right click on the "Command prompt" and choose "Run as administrator".

In the command prompt simply type: sc delete SessionLauncher

Vista will delete all related keys in the registry for you and prevent a sort of restore mechanism that try to "re-install" the service at the first roboot if the registry keys are manually deleted.

[Brendon]

Thanks Wowexec. That's very useful.

 

Regards,

Brendon

[BFB]

I'm seeing the same error so I'll be checking back here to see if anyone confirms that it is a Roxio problem and hopefully has a fix. That said, the error doesn't appear to affect anything so far.

 

BFB

[Kaj]

Hello!

My SessionLauncher problems seems to be over. I have tested it for a long time now. I removed all Roxio components, incl. EMC 10. Downloaded the EMC 10 exe-file to the Hard disc. Disconnect McAfee Security Center and start the installation of EMC 10. Connect McAfee Security Center again and the problem was over. It seems to be a classical mistake from my side. Before the SessionLauncher problem arosed I downloaded and opened the EMC 10 exe-file directly from the Roxio download site with McAfee Security Center in action. It caused problems with both EMC 10 and McAfee Security Center.

 

So, the problem fix was rather simple!

[Kaj]

[johnata]

I'm seeing the same error so I'll be checking back here to see if anyone confirms that it is a Roxio problem and hopefully has a fix. That said, the error doesn't appear to affect anything so far.

 

BFB

 

I see the same error in my logs, I'm using EMC 10 but have upgraded from previous versions.

 

-- John

[Brendon]

The log entry is noting that a call was made to sessionlauncher, but sessionlauncher was not found.

 

I can't see what use blocking the execution of sessionlauncher with msconfig can be to anyone, when the log entry is complaining that sessionlauncher is not there!!. It seems the service droid has misunderstood the problem.

 

If you locate the registry entry which calls sessionlauncher and remove that entry, the error should not show in the log in future.

 

Regards,

Brendon

[johnata]

The log entry is noting that a call was made to sessionlauncher, but sessionlauncher was not found.

 

I can't see what use blocking the execution of sessionlauncher with msconfig can be to anyone, when the log entry is complaining that sessionlauncher is not there!!. It seems the service droid has misunderstood the problem.

 

If you locate the registry entry which calls sessionlauncher and remove that entry, the error should not show in the log in future.

 

Regards,

Brendon

 

For whatever it's worth, I disabled the service in the "administrative tools/services" applet. Not as clean as removing it from the registry but it works for now.

 

-- John

[Brendon]

So everything is working okay, and you're not being given an error message by some failing Roxio application, but you're finding an error in some XP log buried deep in your system area?

 

It looks to me as if that is a call which runs a process during the installation of DirectX 9. The program which was called has been deleted after running because it wasn't needed again after the install was finished, but the call to run it hasn't been deleted.

 

It looks untidy if you're given to reading logs during your spare time, but it isn't a sign that your Roxio software has broken. I'd ignore it myself, or delete the call from the registry if it was making me obsessive.

 

Regards,

Brendon

[Brendon]

Thanks Kaj,

 

That might save others from a similar problem.