Some .exe don't start

[cere88]

Hello.
I recently installed Windows 7 Professional on my laptop. All worked great until I found that some applications I used without any problem (For example Show Desktop.exe, a small utility wich minimizes all open windows or TeaksLogon.exe, another small utility wich let me change the background image when I log on with Windows 7) now doesn't work. When you double click on the exe you just don't see anything except the loading blue circle of my pointer for a few seconds. Opening the Windows Task Manager I can see in the active processes that the application starts and ends quickly.
I don't know what I could have done for make these applications don't work and I have no restore point. I tried to live with it but now it's becoming annoying and I wish there is a way to fix this issue. I wish I could solve it without formatting.

Well thanks for the help and sorry about my english, I'm not a native englishe speaker.

Edit: I may forgot to say: this is not a compatibility problem since all these applications worked well with windows 7 and I tried to run them in Xp, Vista and Windows 2000 mode.
This is the "Show Desktop" application I was talking about: http://ceiiular.deviantart.com/art/Show-Desktop-133022210

 

[Jonathan_King]

Welcome to the Forums!
What anti-virus do you have? Try using Microsoft Security Essentials or Malwarebytes to scan for viruses.

Did these programs work in Windows 7 before, or another OS?

 

[cere88]

Welcome to the Forums!
What anti-virus do you have? Try using Microsoft Security Essentials or Malwarebytes to scan for viruses.

Did these programs work in Windows 7 before, or another OS?

Hello and thanks.
I'm using Avast as antivirus and Ad-Aware.
These programs worked in Windows 7 before. It happened something like this
- I first installed Windows 7
- I had no problem with these programs
- After 2 weeks they stopped to work

 

[Jonathan_King]

Sounds like a virus. Try MSE or Malwarebytes to scan for viruses. You can also try a system restore if the problem happened recently.

 

[fseal]

If you look in your admin tools, event viewer, probanly under applications, there may be more information about why the program failed to start.

It's quite likely it's dependent on a library that got uninstalled or moved or something. Sometimes you'll get a very confusing "The programs configuration is not correct" dialog box which means specifically that a CRT or other basic library version is not installed that the program needs, or sometimes you get nothing at all, the program just fails to load due to a missing resource.

 

[cere88]

If you look in your admin tools, event viewer, probanly under applications, there may be more information about why the program failed to start.

It's quite likely it's dependent on a library that got uninstalled or moved or something. Sometimes you'll get a very confusing "The programs configuration is not correct" dialog box which means specifically that a CRT or other basic library version is not installed that the program needs, or sometimes you get nothing at all, the program just fails to load due to a missing resource.

Well I'm looking in the event viewer but I don't see any "event" or any log here.

 

[cere88]

And when I try to load the events log I get a "Snap-In" error.

 

[seekermeister]

Try the Reliability Monitor.

 

[cere88]

Oh alright, now I can see the logs!

Here's the logs for 3 different programs:

Firma del problema
Nome evento problema: APPCRASH
Nome applicazione: Show Desktop.exe
Versione applicazione: 1.0.20.17
Timestamp applicazione: 4a902ecb
Nome modulo con errori: StackHash_3250
Versione modulo con errori: 0.0.0.0
Timestamp modulo con errori: 00000000
Codice eccezione: c0000005
Offset eccezione: 0001102e
Versione SO: 6.1.7600.2.0.0.256.1
ID impostazioni locali: 1040
Informazioni aggiuntive 1: 3250
Ulteriori informazioni 2: 325055436168101a578479ab72a66d1a
Ulteriori informazioni 3: c8b0
Ulteriori informazioni 4: c8b0deb27397de66dbbb0cb7ca788765

Ulteriori informazioni sul problema:
ID bucket: 1586779069

Firma del problema
Nome evento problema: APPCRASH
Nome applicazione: ChanThreadWatch.exe
Versione applicazione: 1.2.0.2
Timestamp applicazione: 4a903246
Nome modulo con errori: StackHash_3250
Versione modulo con errori: 0.0.0.0
Timestamp modulo con errori: 00000000
Codice eccezione: c0000005
Offset eccezione: 0001102e
Versione SO: 6.1.7600.2.0.0.256.1
ID impostazioni locali: 1040
Informazioni aggiuntive 1: 3250
Ulteriori informazioni 2: 325055436168101a578479ab72a66d1a
Ulteriori informazioni 3: c8b0
Ulteriori informazioni 4: c8b0deb27397de66dbbb0cb7ca788765

Ulteriori informazioni sul problema
ID bucket: 1597491618

Firma del problema
Nome evento problema: APPCRASH
Nome applicazione: TweaksLogon.exe
Versione applicazione: 1.1.3371.36752
Timestamp applicazione: 49caea35
Nome modulo con errori: StackHash_3250
Versione modulo con errori: 0.0.0.0
Timestamp modulo con errori: 00000000
Codice eccezione: c0000005
Offset eccezione: 0001102e
Versione SO: 6.1.7600.2.0.0.256.1
ID impostazioni locali: 1040
Informazioni aggiuntive 1: 3250
Ulteriori informazioni 2: 325055436168101a578479ab72a66d1a
Ulteriori informazioni 3: c8b0
Ulteriori informazioni 4: c8b0deb27397de66dbbb0cb7ca788765

Ulteriori informazioni sul problema
ID bucket: 1586071755

 

[cere88]

With the Reliability Monitor I can see that these programs started to crash on 24/11/09. The fact is that it seems I didn't install anything before it they started to crash.

Here's anyway the first log of the ShowDesktop crash:

Descrizione
Faulting application name: Show Desktop.exe, version: 1.0.20.17, time stamp: 0x4a902ecb
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x00011017
Faulting process id: 0x1100
Faulting application start time: 0x01ca6ca11f664c70
Faulting application path: C:\Data\Downloads\Show_Desktop_by_CeIIular\Show Desktop.exe
Faulting module path: unknown
Report Id: 5e4acacd-d894-11de-8b92-d163af6a93df

 

[Tews]

As you can see, those programs ( Show Desktop.exe, ChanThreadWatch.exe, Show Desktop.exe, and TweaksLogon.exe) are not compatible when run as native windows 7 programs... Try running them in Vista/XP compatibility mode... no guarantee that they will, but its worth a try...

 

[seekermeister]

As far as Show Desktop, what is wrong with the built in function for that?

 

[cere88]

As you can see, those programs ( Show Desktop.exe, ChanThreadWatch.exe, Show Desktop.exe, and TweaksLogon.exe) are not compatible when run as native windows 7 programs... Try running them in Vista/XP compatibility mode... no guarantee that they will, but its worth a try...

No, they are compatible. As I said before they all worked without problems before 24/11/09 on Windows 7 (On the same laptop that now doesn't make them work). And yes, I've tried to run them in Vista/XP compatibility but nothing changes.

So the point is: what could have changed that made these programs doesn't work? How can I know/repair it?

As far as Show Desktop, what is wrong with the built in function for that?

Sorry I didn't understand, what do you mean?

 

[Tews]

Possibly an update through WU??

 

[fseal]

Hmm, actually crashing on launch then... (Rather than "Crashing" these days, most programs get caught doing something that might crash or /would/ crash and the OS throws an "exception" which a LOT of programmers don't bother to "catch" and the result is the program is closed without any warning.)

But anyway, my next move would be to catch the crash with a debugger and investigate if you have "teh koding skilz" Short of that, I'd say that those programs were probably not /really/ W7 complient even though they appeared to work and suddeny your finding that out. I wouldn't JUST expect them to suddenly stop working but a Windows Update, program install or uninstall might cause it.

As for solution, yes W7 has a couple of "show desktop" features built in, and the others I'd stop using till a W7 version of them is created.

Though you could always try to reinstall the applications if they came with an installer...

[Edit] BTW Exception code 0xC0000005 is a memory acess violation. The most common exception. Cause by either forcing a call to a library that has changed version/api on the program or by simply poor programming practice. I.e. allocating a 100 byte char array to hold say a a file path, and that works for a long time then one day the OS returns a 101 character path and suddenly POW...

 

[zigzag3143]

As you can see, those programs ( Show Desktop.exe, ChanThreadWatch.exe, Show Desktop.exe, and TweaksLogon.exe) are not compatible when run as native windows 7 programs... Try running them in Vista/XP compatibility mode... no guarantee that they will, but its worth a try...

No, they are compatible. As I said before they all worked without problems before 24/11/09 on Windows 7 (On the same laptop that now doesn't make them work). And yes, I've tried to run them in Vista/XP compatibility but nothing changes.

So the point is: what could have changed that made these programs doesn't work? How can I know/repair it?

As far as Show Desktop, what is wrong with the built in function for that?

Sorry I didn't understand, what do you mean?

\

Cere

There is something that can cause this. go to control panel>system control panel>advanced settings>performance>DEP. What is it set to?

Ken J+

 

[SpYke]

reinstall it

 

[cere88]

Hmm, actually crashing on launch then... (Rather than "Crashing" these days, most programs get caught doing something that might crash or /would/ crash and the OS throws an "exception" which a LOT of programmers don't bother to "catch" and the result is the program is closed without any warning.)

But anyway, my next move would be to catch the crash with a debugger and investigate if you have "teh koding skilz" Short of that, I'd say that those programs were probably not /really/ W7 complient even though they appeared to work and suddeny your finding that out. I wouldn't JUST expect them to suddenly stop working but a Windows Update, program install or uninstall might cause it.

As for solution, yes W7 has a couple of "show desktop" features built in, and the others I'd stop using till a W7 version of them is created.

Though you could always try to reinstall the applications if they came with an installer...

[Edit] BTW Exception code 0xC0000005 is a memory acess violation. The most common exception. Cause by either forcing a call to a library that has changed version/api on the program or by simply poor programming practice. I.e. allocating a 100 byte char array to hold say a a file path, and that works for a long time then one day the OS returns a 101 character path and suddenly POW...

Thanks for the help Well I have no coding skills so I can't debug them, and no, they don't came with an installer.

As you can see, those programs ( Show Desktop.exe, ChanThreadWatch.exe, Show Desktop.exe, and TweaksLogon.exe) are not compatible when run as native windows 7 programs... Try running them in Vista/XP compatibility mode... no guarantee that they will, but its worth a try...

No, they are compatible. As I said before they all worked without problems before 24/11/09 on Windows 7 (On the same laptop that now doesn't make them work). And yes, I've tried to run them in Vista/XP compatibility but nothing changes.

So the point is: what could have changed that made these programs doesn't work? How can I know/repair it?

As far as Show Desktop, what is wrong with the built in function for that?

Sorry I didn't understand, what do you mean?

\

Cere

There is something that can cause this. go to control panel>system control panel>advanced settings>performance>DEP. What is it set to?

Ken J+

It is set on "Turn on DEP for essential windows programs and devices only"

 

[Frostmourne]

These functions are built in, as has been mentioned - use Aero Peek and keyboard shortcuts instead.

 

[cere88]

These functions are built in, as has been mentioned - use Aero Peek and keyboard shortcuts instead.

Well with that ShowDesktop I could minimize my windows without hiding Rocketdock, wich is a dock I'm using. And again, this is a problem with my OS, not these programs' problem. I can have this problem with other programs I will use, that's why I'm trying to fix it.