Stardock Central Mess Up Windows
Bad bug!
Monday, July 4, 2005 by lilstarfish | Discussion: Stardock Support General
Bad idea =\
I had payed online and started up my Stardock Central to let it update
to the newest version. Just as it updated the central I noted that
the "hidden when inactive" icons in the systray suddenly all popped
out in full view.
But guess what, the Stardock Central update removed the "hidden when inactive"
feature in Windows

I tried for 3 hours to find some way to get it to work again
but got so irritated I uninstalled Stardock Central and made
a System Restore back to yesterday

That returned the feature.
Then I read that other people are getting their systems
destroyed from different Stardock products

What's up with this crap!?
Reply #2 Monday, July 4, 2005 10:57 PM
How come then that after 3 hours the System Restore was
the only thing that could get it working again?
Even uninstalling all OD applications, the Central and rebooting
didn't return it

Reply #3 Monday, July 4, 2005 11:04 PM
If you adopted a more reasonable approach....and determined that the non-hiding of inactive icons was not a threat to the sanctity of your computing environment you would have waited....to determine whether there was a SIMPLE solution available before you dived in with a System-Restore.
It's much like the [old] situation with Litestep...where Windows would pop up a message saying 'you must re-install windows' so people did....and they did NOT need to. It was a simple thing to fix but they still jumped in and claimed the sky was falling...
Reply #4 Monday, July 4, 2005 11:14 PM
I'm sorry but can't you read?
I sat for three(3!) bloody hours!! trying every single little thing
I could think of that could solve it.
Since SDC has no business messing with my systray unless I
give it permission to I intended to figure out what was causing
the shit.
Even downloading the whole SDC install and doing a fresh install
created exactly the same problem.
I was just lucky to have a System Restore point created yesterday
that corrected the mess.
Reply #5 Monday, July 4, 2005 11:34 PM
| I'm sorry but can't you read? |
Yes, quite well, thanks...
If it were me I would have probably looked at effort vs. return ... as one does with most problem-solving and just waited and/or sought assistance online.
There was/is no real 'need' to waste 3 hours attempting to solve something that, as I already said, is hardly drastic or disasterous.....and certainly not a system-restore, which might or might not cause other issues worse than the one you are dealing with.
Usually when something goes gaga on my machine I search via Google for similar issues...and solutions....and failing that, I ask.
With a Stardock Proggy....a great place to go to FIRST is here, #stardock [IRC] and/or email the Company for support.
IF all that fails....and one simply MUST hide them icons, THEN [maybe] resort to a Restore....
But not before....
Reply #6 Monday, July 4, 2005 11:45 PM

Reply #7 Tuesday, July 5, 2005 12:03 AM
Fondest Regards From Atlantic Canada
Reply #8 Tuesday, July 5, 2005 12:03 AM
I unload all programs and return to default Windows theme including all icons, as well as deselecting any option to "run at start-up", before installing anything - even updates.
I know it is old fashioned, and often not necessary, but using the Windows 9x methods (reboot after installing anything, etc.) - has always been good to me.
Though I have seen some issues, they have - for the most part - been workable, and the Google is a good thing.
I am thinking that the Stardock MCP may be involved here, though not certain.
My SDC install is done by disconnecting from the internet during initial install, then running offline and selecting/deselecting the options I want in "Tools>Settings", then connecting to the server and installing what I want.
For a stability issue, I would recommend not installing any Beta versions of either SDC, or other applications - as well as requiring confirmation before installing. At least this way, if something goes wrong, one knows exactly what one allowed and can search out an answer much easier.
Hope things go better for you in the future.

Reply #9 Tuesday, July 5, 2005 11:54 AM
refuses to be deleted even after uninstalling Stardock Central.
For some unknown reason it is running silently in the background

How do I remove it?
Reply #10 Tuesday, July 5, 2005 12:42 PM
| MCPCore.dll in the folder C:\Program Files\Common Files\Stardock refuses to be deleted even after uninstalling Stardock Central. For some unknown reason it is running silently in the background |
You will need to end the process before deleting - either via Task Manager (preferred method), or perhaps unregistering it via command prompt.
It is usually: regsvr32 /u FILENAME.dll
If you are not sure on unregistering a service, I would contact Tech Support.
Note - if you are running other Stardock programs - especially ObjectDock or DesktopX - removing the service may cause problems.
I hope this helps.

Reply #11 Tuesday, July 5, 2005 12:58 PM
Yeah, the problem is that it's not visible in the Task Manager.
And undegistering it through command prompt doesn't work either.
The feedback says *LoadLibrary("MCPCore.dll") failed - The specified module could not be found.*
Reply #12 Tuesday, July 5, 2005 1:55 PM
| *LoadLibrary("MCPCore.dll") failed - The specified module could not be found.* |
This would indicate that something else is holding on to the "MCPCore.dll" file, which is not actually running.
If you are running Windows XP, my last thoughts would be:
1 - Go here Link and perform a clean boot (paying special attention to the text regarding "Load System Services" - which if disabled will remove System Restore points).
After a successful clean boot, try to delete the file manually.
2 - If this fails, then the only option I know of - other than Tech Support - is to reinstall SDC without being connected to internet, then running it offline and going to "Tools > Settings" and deselecting the two options for the MCP and selecting "Check for Stardock Central Release updates on startup" and "Prompt before updating Stardock Central" - close program and reboot.
Reconnect to internet > start SDC > update SDC to the officially release update if offered, then close SDC and reboot computer.
Uninstall SDC, reboot computer, delete the "SDCentral" folder in the "\Program Files\Stardock" folder.
3 - Since I do not write programs, I must defer to Tech Support.
Hopefully, one of these will help.

Reply #13 Tuesday, July 5, 2005 2:07 PM
I am thinking, if there is a cache written there which uses that ".dll", it may be creating an issue.
Just a thought.

Reply #14 Tuesday, July 5, 2005 3:11 PM
You can use the command prompt and type tasklist /m
Hit Enter
This will show a list of all processes, modules, etc. that are running.
If you find the "MCPCore.dll" in the tasklist.exe section, you can use tskill MCPCore command to kill process.

Reply #15 Tuesday, July 5, 2005 4:09 PM
The oddest thing...it wouldn't be deleted but I could rename it(!) so I rebooted and was able to finally delete it.
These are the oddest happenings I've been through for a very long time.
I reinstalled SDC and WB, IP etc but the systray is still messed up.
My Steam games also refused to start so I uninstalled Icon Packager 3.00.090
and removed iprepair.dll in the registry and was able to get the games running
again.
https://www.wincustomize.com/Forums.aspx?ForumID=166&AID=80214#613209
Reply #16 Tuesday, July 5, 2005 6:00 PM
Good to hear you found a reasonable solution.
It does indeed seem that IconPackager 3.00.090 has some bugs that are creating some significant issues.
Perhaps the additional shell functions and the needed ".dll" files to provide the functionality is at the root cause of problems.
Hopefully, they will design a fix soon.
Note - I had an issue with the system tray icons not showing up consistently, and after disabling the Stardock MCP option, I have not seen the issue (it was especially problematic with Norton Internet Security tray icons) - though I was able to use this solution because I do not use ObjectDock's system tray functions or DesktopX.
I have also seen fixes for system tray problems by copying the "sdmcp.exe" file to the "Startup" folder in the users Documents and Settings directory - go figure).
Again, glad to help in any way I can.

Reply #17 Wednesday, July 6, 2005 9:26 AM
With me the XP COM+ service failed to startup .This had the result of loads of applications failing to register .I tried re-installing COM-catalog in its entirety by following the procedure described here :
Link
But to no avail . I ended up re-installing Windows XP and SP 2 ( apparently system restore doesn't work with COM+ service failing )and after that re-installed SDC . I installed Windowblinds ONLY after this and everything seems to be working fine . This is indicative the problem is with another OD - compnent , maybe Iconpackager - I did upgrade to the new version just before the problems started occuring - but certainly not windowblinds or SDC itself .
Is this problem a known issue at Stardock or is it dependent on computer-configuration ( i.e. : not a bug as such ) ??
Reply #18 Thursday, July 7, 2005 4:07 PM
Today I got mail from the support:
"Hi,
You may want to Disable the MCP notification area and see if that helps.
Open Stardock Central and go to Tools > Settings. Uncheck the options "Enable MCP Notification Area" and reboot.
Thanks."
I started up Stardock Central and it updated to a new version. I then unchecked both "Enable MCP SmartStartup" and "Enable MCP notification area support". Finally I downloaded the latest version of IconPackager with it's fixed iprepair.dll.
My systray finally works again!
It seems that SDC was the culprit but the problem has been resolved =D
Again, many thanks Corky for your valuable insights and kindness

Reply #20 Thursday, July 7, 2005 10:50 PM
| With a Stardock Proggy....a great place to go to FIRST is here, #stardock [IRC] and/or email the Company for support. IF all that fails....and one simply MUST hide them icons, THEN [maybe] resort to a Restore.... But not before.... |
From post #5
Not so silly afterall...
Please login to comment and/or vote for this skin.
Welcome Guest! Please take the time to register with us.
There are many great features available to you once you register, including:
- Richer content, access to many features that are disabled for guests like commenting on the forums and downloading skins.
- Access to a great community, with a massive database of many, many areas of interest.
- Access to contests & subscription offers like exclusive emails.
- It's simple, and FREE!







Reply #1 Monday, July 4, 2005 10:48 PM
"If" it's a glitch it's hardly earth-shatteringly disasterous....and not something warranting a system restore, etc.
Just post your problem details at [email protected] for assistance....