Per Bohlin,
Did you see any DesktopX cache folders during the clearing IconX cache, and did you delete that as well?
If not, I would suggest trying to do so.
The fact that IconX will not start manually after restart suggests that DesktopX is somehow loading, or holding onto something in IconX.
I am not a coder, and do not know why the integration of IconX and DesktopX is set up the way it is.
If you can get IconX to start manually, you might try selecting the run at startup option, and then create and save the theme > reboot to verify functionality.
If none of these work, the only other path that I would suggest trying is the following:
- unload all customization programs
- restore Windows to the default theme including all icons (if you are running Windows XP, use Display Properties > Themes tab > select Windows XP in theme list > click Apply)
- delete all cache folders inside the Stardock cache folder > uninstall both IconX and DesktopX via SDC
- reboot > delete any DesktopX and IconX folders found in "C:\Program Files\Stardock\Object Desktop" folder
- reinstall DesktopX and IconX (non-beta versions)
- test IconX first, before using DesktopX.
Note - you will want to save any files that are not included in the IconX and DesktopX program installations before uninstalling and deleting the sub-directories.
Note #2 - the MCP Smart Startup option in SDC is designed to start Stardock products quickly and efficiently. It is different than the MCP notification area support option which is designed to support Stardock software functions that involve the notification area (A.K.A. - the System Tray). The MCP Smart Startup may or may not have any effect on the IconX program, so you could try running IconX with it disabled to test.
Sorry I don't have anything better to offer at this time.