EXE problems

Hey, when i try to run certain EXE's i get this message

Application has generated an exception that could not be handled.

Process id=0x848 (2120), Thread id=0xebc (3772).

I click cancel to debug it and this message comes up

Registered JIT debugger is not avaliable. An attempt to launch a JIT debugger with the following command resulted in an error code of 0x2 (2) Please check computer settings.

cordbg.exe !a 0x848

This only happens on my vista upgrade advisor that i know if so far and i could run it before so i dont know whats happened.

Any help is apprecaited :happy:

Broken file? Fucked up registry settings?

Ive only jsut downloaded, reinstalled it about 5 times and i havent messed with my registry…im not too good with all that stuff :(

Maybe something else messed with your registry, like a virus.

Run a full scan with whatever anti virus you have installed.

Ya my anti virus runs a full scan every other day @ 17:00 and no problems were detected

Download HijackThis, and post the log file it generates here.

Then we can see if there is anything running that could affect it.

I couldnt notice anthing abnormal there but here ya go just in case :happy:

Scan saved at 20:31:26, on 27/02/2007
Platform: Windows XP SP2 (WinNT 5.01.2600)
MSIE: Internet Explorer v7.00 (7.00.6000.16414)

Running processes:
C:\WINDOWS\System32\smss.exe
C:\WINDOWS\system32\winlogon.exe
C:\WINDOWS\system32\services.exe
C:\WINDOWS\system32\lsass.exe
C:\WINDOWS\system32\Ati2evxx.exe
C:\WINDOWS\system32\svchost.exe
C:\Program Files\Windows Defender\MsMpEng.exe
C:\WINDOWS\System32\svchost.exe
C:\WINDOWS\system32\Ati2evxx.exe
C:\WINDOWS\system32\spoolsv.exe
C:\Program Files\Common Files\AOL\ACS\AOLAcsd.exe
C:\WINDOWS\eHome\ehRecvr.exe
C:\WINDOWS\eHome\ehSched.exe
C:\Program Files\Firebird\Firebird_1_5\bin\fbguard.exe
c:\program files\mcafee.com\agent\mcdetect.exe
c:\PROGRA~1\mcafee.com\vso\mcshield.exe
c:\PROGRA~1\mcafee.com\agent\mctskshd.exe
C:\PROGRA~1\McAfee.com\PERSON~1\MpfService.exe
C:\Program Files\Dell\QuickSet\NICCONFIGSVC.exe
C:\WINDOWS\system32\svchost.exe
C:\WINDOWS\System32\WLTRYSVC.EXE
C:\WINDOWS\System32\bcmwltry.exe
C:\WINDOWS\Explorer.EXE
C:\Program Files\Firebird\Firebird_1_5\bin\fbserver.exe
C:\WINDOWS\ehome\ehtray.exe
C:\Program Files\Java\jre1.5.0_11\bin\jusched.exe
C:\Program Files\ATI Technologies\ATI.ACE\CLI.EXE
C:\Program Files\Synaptics\SynTP\SynTPEnh.exe
C:\Program Files\Dell\QuickSet\quickset.exe
C:\WINDOWS\system32\WLTRAY.exe
C:\WINDOWS\eHome\ehmsas.exe
C:\Program Files\McAfee.com\VSO\oasclnt.exe
C:\PROGRA~1\mcafee.com\agent\mcagent.exe
C:\WINDOWS\System32\DLA\DLACTRLW.EXE
C:\Program Files\Common Files\InstallShield\UpdateService\issch.exe
C:\Program Files\McAfee.com\VSO\mcvsshld.exe
C:\PROGRA~1\McAfee.com\PERSON~1\MpfTray.exe
C:\WINDOWS\system32\rundll32.exe
C:\Program Files\Windows Defender\MSASCui.exe
C:\Program Files\Synaptics\SynTP\SynTPLpr.exe
c:\progra~1\mcafee.com\vso\mcvsescn.exe
C:\Program Files\Common Files\AOL\1167616743\ee\AOLSoftware.exe
C:\WINDOWS\stsystra.exe
C:\Program Files\Microsoft Office\Office12\GrooveMonitor.exe
C:\Program Files\MSN Messenger\MsnMsgr.Exe
C:\WINDOWS\system32\ctfmon.exe
C:\PROGRA~1\McAfee.com\PERSON~1\MpfAgent.exe
c:\progra~1\mcafee.com\vso\mcvsftsn.exe
C:\Program Files\Messenger\msmsgs.exe
C:\Program Files\AOL 9.0\waol.exe
C:\Program Files\AOL 9.0\shellmon.exe
C:\Program Files\Common Files\AOL\aoltpspd.exe
C:\Program Files\MSN Messenger\usnsvc.exe
C:\Program Files\Mozilla Firefox\firefox.exe
C:\Program Files\Trillian\trillian.exe
C:\Program Files\MSN Messenger\livecall.exe
C:\Documents and Settings\josh smile\Desktop\VistaUpgradeAdvisor.exe
C:\Documents and Settings\josh smile\Desktop\HijackThis.exe```

Nothing out of the ordinary with that log file, hmm.

What are the "certain EXE's" that don't work? Maybe they're all trying to use a broken .NET Framework installation or something.

Know assembly? simply follow back the cause of the exception, and look at the conditions which generated it. Then you know you problem.

Check the 32Bit/64Bit compatability for the file. If needed Force it to run as a Win 9x file in the properties.

That is one of many windows Xp/Vista fixes for old executable files not being able to run…they may be programmed to run in 16-Bit mode ONLY.

Thanks, but i doubt that its for 16bit only coz its the windows vista upgrade advisor :p [edit] also @ ReDucTor no i dont know assembly, and @ mastergamer its only for this program