Dexpot won't load

[jdj]

Hi everyone.

I have installed dexpot on a windows 7 ultimate machine. The very first time, directly after installation, the program ran on its own fine. After a reboot, however, it no longer loads. Prior to the reboot I configured the settings for it to boot with windows on startup, but now it will not load automatically, nor will it load by clicking the desktop or menu icon.

I have tried launching the 64 bit exe as well to no avail. Any idea why I am not getting the icon on the system tray similar to after I installed it? Seems like an awesome program from what I saw and I'd really like to use it.

Thanks.

[Sebastian]

,

have you checked the task manager for a dexpot.exe?

[Saidas]

I just installed your program and having the same problem. I installed on two machines, one W7U 32 and one W7P 64 and the program won't open at all on either. I checked Task Manager on both and it shows as running and Dexpot is in Program Files. Neither double clicking or rt. clicking/Open works.

Please advise.

Merged from different thread:
Having the same problem. I went into Settings/Start Start with Windows and checked the box but nothing. Desktop icon doesn't open anything either.

[intregrisist]

I'm having the same exact issue with Win 7 64bit.

[Sebastian]

,

starting Dexpot with admin privileges?

[irvinm]

I'm having the exact same problem. (W7 x64 Ultimate) It ran fine after I installed it and after I rebooted I can not get the program to launch successfully. The program is in the task manager, but appears to get stuck at the splash screen but visually goes away if I click on the splash screen. (While the program is still in the task manager with no icon in the tray) If I try launching the program again, I get multiple instances of the EXE in task manager.

I've tried reinstalling (w\admin rights) and rerunning (w\admin rights) ... no luck.

[Patrick]

Try this: [FAQ] Splash screen remains until I click on it

[irvinm]

I'm having the exact same problem. (W7 x64 Ultimate) It ran fine after I installed it and after I rebooted I can not get the program to launch successfully. The program is in the task manager, but appears to get stuck at the splash screen but visually goes away if I click on the splash screen. (While the program is still in the task manager with no icon in the tray) If I try launching the program again, I get multiple instances of the EXE in task manager.

I've tried reinstalling (w\admin rights) and rerunning (w\admin rights) ... no luck.

This worked for me:

http://dexpot.de/forum/viewtopic.php?f=12&t=2581

[Patrick]

Great. Exactly which part of that thread solved the problem? (So we can add it to the FAQ.)

[irvinm]

Great. Exactly which part of that thread solved the problem? (So we can add it to the FAQ.)

For me, I ended up changing 2 things and am not 100% sure which solved the problem. Let me explain. When I found the other thread, I turned on the /debug option and noticed I had the same log file results as someone else. I first registered the OCX as prescribed in the thread as I felt both were 64-bit related: regsvr32 %windir%\SysWOW64\mscomctl.ocx

That in an of itself did not fix the issue but I had not yet reboot. I looked earlier in the thread and saw how they recommended downloading the VB6 common controls. As I went to download these controls from the MS site, IE 9 complained about not having access to my environment defined TEMP directory to save the file.

As I looked into this problem, I found that my RAMDISK (which is used for both TEMP and TMP environment variables) had changed drive letters and was the reason why IE was not able to download the file. I updated the environment variables to point to correct drive letter and decided to reboot my machine. [I still need to see why my RAMDISK drive letter was changed ... hmm]

After my reboot, everything was back to normal for both IE and dexpot! (So, not having access to the TEMP folder or the OCX could have been my problem) I guess I could go back and point my TEMP\TMP folders to invalid drives to isolate what really fixed it ...