Start10.exe installed in Start11 program folder - along with Start11.exe

Hi

I have Start11 1.41 installed. All working well.

However, a software monitoring package I used indicated I had an out-of-date copy of Start10 installed as well.
Turned out there's a Start10.exe, Start10ThemeEdit.exe and Start10tweak.exe, all in the same path (C:\Program Files (x86)\Stardock\Start11 ) as Start11.exe

Are the Start10 files likely to be residuals from previous upgrades, or are they necessary for Start11?
The file dates would suggest that the Start10 files have been modified more recently that the Start11.exe

Thanks in advance

3,044 views 5 replies
Reply #1 Top

Those all need to be there for Start11 to work properly.  If you look in the Registry, the Start11 entries are all under Start8. I believe this has been done to save programming steps by the developer.

Reply #2 Top

Ignore your software monitoring app.  Unfortunately often these tools have no way to recognise the version installed correctly.

Reply #3 Top

@pelaird : Thanks for this info. I'll leave things as they are.

@Neil Banfield : It's not a problem with the monitoring software. It correctly identifies the Start11 as V1.4.1.1 and confirms it's up to date. It also correctly identifies the Start10 as V1.5.0.0 but suggests there is a V1.9.7.0 out there somewhere. Anyway, everything works at present.

I'm in no rush to change anything but I thought I'd just check here to account for the situation. I can tell the monitoring app to ignore the Start10 executable now as the name doesn't necessarily correspond to what it is or what it does.

Thanks to both of you.

Reply #4 Top

Quoting kenmuir, reply 3

@pelaird : Thanks for this info. I'll leave things as they are.

@Neil Banfield : It's not a problem with the monitoring software. It correctly identifies the Start11 as V1.4.1.1 and confirms it's up to date. It also correctly identifies the Start10 as V1.5.0.0 but suggests there is a V1.9.7.0 out there somewhere. Anyway, everything works at present.

I'm in no rush to change anything but I thought I'd just check here to account for the situation. I can tell the monitoring app to ignore the Start10 executable now as the name doesn't necessarily correspond to what it is or what it does.

Thanks to both of you.
End of kenmuir's quote

Well it is a problem in the monitoring app that would be good to be resolved.  It is incorrectly assuming that was a Start10 exclusive file and it is the correct file to detect version from.

We always use the version on the config exe (Start11config in Start11, Start10config in Start10) not the other files in pretty much every app.

What app is it so we can contact them to get how they detect version fixed?

Reply #5 Top

Hi Neil

I think the issue is more a matter of my natural curiosity than any malfunction or misbehaviour by the software monitoring package. Here's an extract from the most thorough scan I can get it to do -


You can see that it quite correctly - in your view - uses Start11Config.exe as the source of info for the product named "Stardock Start11"
However it has also interrogated the other executables and presented the appropriate information available from them.

I do like Start11 but I must confess, if pushed to say where the confusion starts, I'd have to say that Stardock having elements named Start8, Start10 and Start11, all in the one program folder named Start11, is the main contributor.

I can adjust the level of detail and the specific files scanned by the monitoring software. This issue emerged when I did the most extensive scan - just out of curiosity - and spotted the Start10 entries. I'm quite satisfied now that they are genuine and not orphans from previous installations. 

If you really want to contact the authors/publishers of the monitoring app, it is SUMo from KC Softwares

Regards

Ken