Jump to content


Autopatcher.exe won't start


7 replies to this topic

#1 Atom

    Member

  • Members
  • PipPip
  • 16 posts

Posted 30 January 2012 - 04:52 PM

I just installed the apup 1.3 in my Windows 7x64 Home Premium. The updating went smoothly. But when I tried to open autopatcher.exe for the first time I got an error message that said something about it being not compatible. After that when I click on autopatcher.exe again to open it, there was zero response. Nothing happened. Not even an error message like the first time.

I did a search of this forum, but it appears that no one has the same problem.

Could someone please let me know the solution. Thank you.

#2 ViroMan

    Just an awesome guy.

  • Project Manager
  • PipPipPipPipPipPip
  • 1,160 posts
  • Gender:Male
  • Location:California, USA, Earth, SOL, Milkyway
  • Interests:Programming and being a know it all pest.

Posted 30 January 2012 - 08:45 PM

Well that is indeed odd. Try deleting the autopatcher program and then re-download it with apup. Do you have an anti-virus that may stop it?

#3 Atom

    Member

  • Members
  • PipPip
  • 16 posts

Posted 31 January 2012 - 12:30 AM

View PostViroMan, on 30 January 2012 - 08:45 PM, said:

Well that is indeed odd. Try deleting the autopatcher program and then re-download it with apup. Do you have an anti-virus that may stop it?

No, my ESET antivirus is only scan on demand. Not real time. Another odd thing I noticed is that when I click autopatcher a foldr named #AutoPatcher_Temp# is instantly created in my C drive.

Anyway, I'll delete and re-install and see what happens. Thank you.

#4 ViroMan

    Just an awesome guy.

  • Project Manager
  • PipPipPipPipPipPip
  • 1,160 posts
  • Gender:Male
  • Location:California, USA, Earth, SOL, Milkyway
  • Interests:Programming and being a know it all pest.

Posted 31 January 2012 - 03:30 AM

Wait, so you have your real-time detection off? That is rather pointless to have an Anti-virus if its off then isn't it? Anyways... that aside... the creating a directory is standard behavior... I don't remember what it does with it though.

#5 Atom

    Member

  • Members
  • PipPip
  • 16 posts

Posted 31 January 2012 - 02:17 PM

Thanks ViroMan for your concern. I off the antivrus real time because I have comodo firewall running. However, when I was trouble-shooting the autopatcher I turned off comodo too, but unfortunately that didn't help me to fire up the autopatcher.exe file. I'm still trying to figure out the problem.

#6 Atom

    Member

  • Members
  • PipPip
  • 16 posts

Posted 02 February 2012 - 03:13 AM

I managed to trace the error report by my win 7x64 Home Premium about autopatcher.exe not being able to start.

I that this report (appended below) will give you an idea of the problem. Thank you.

Version=1
EventType=APPCRASH
EventTime=129724447898475933
ReportType=2
Consent=1
UploadTime=129724447898875939
ReportIdentifier=f150efe9-4ba5-11e1-b210-b4749fd140d1
IntegratorReportIdentifier=f150efe8-4ba5-11e1-b210-b4749fd140d1
WOW64=1
Response.BucketId=1986372980
Response.BucketTable=1
Response.type=4
Sig[0].Name=Application Name
Sig[0].Value=autopatcher.exe
Sig[1].Name=Application Version
Sig[1].Value=5.6.0.100
Sig[2].Name=Application Timestamp
Sig[2].Value=4b964772
Sig[3].Name=Fault Module Name
Sig[3].Value=StackHash_16ed
Sig[4].Name=Fault Module Version
Sig[4].Value=0.0.0.0
Sig[5].Name=Fault Module Timestamp
Sig[5].Value=00000000
Sig[6].Name=Exception Code
Sig[6].Value=c000041d
Sig[7].Name=Exception Offset
Sig[7].Value=73674f0d
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=6.1.7601.2.1.0.768.3
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=18441
DynamicSig[22].Name=Additional Information 1
DynamicSig[22].Value=16ed
DynamicSig[23].Name=Additional Information 2
DynamicSig[23].Value=16ed1adffde04af53107426435404b46
DynamicSig[24].Name=Additional Information 3
DynamicSig[24].Value=1896
DynamicSig[25].Name=Additional Information 4
DynamicSig[25].Value=1896c4791f154a8b8d8f5cabd27d539c
UI[2]=C:\apup\autopatcher.exe
UI[3]=AutoPatcher main module has stopped working
UI[4]=Windows can check online for a solution to the problem.
UI[5]=Check online for a solution and close the program
UI[6]=Check online for a solution later and close the program
UI[7]=Close the program
LoadedModule[0]=C:\apup\autopatcher.exe
LoadedModule[1]=C:\windows\SysWOW64\ntdll.dll
LoadedModule[2]=C:\windows\syswow64\kernel32.dll
LoadedModule[3]=C:\windows\syswow64\KERNELBASE.dll
LoadedModule[4]=C:\windows\system32\MSVBVM60.DLL
LoadedModule[5]=C:\windows\syswow64\USER32.dll
LoadedModule[6]=C:\windows\syswow64\GDI32.dll
LoadedModule[7]=C:\windows\syswow64\LPK.dll
LoadedModule[8]=C:\windows\syswow64\USP10.dll
LoadedModule[9]=C:\windows\syswow64\msvcrt.dll
LoadedModule[10]=C:\windows\syswow64\ADVAPI32.dll
LoadedModule[11]=C:\windows\SysWOW64\sechost.dll
LoadedModule[12]=C:\windows\syswow64\RPCRT4.dll
LoadedModule[13]=C:\windows\syswow64\SspiCli.dll
LoadedModule[14]=C:\windows\syswow64\CRYPTBASE.dll
LoadedModule[15]=C:\windows\syswow64\ole32.dll
LoadedModule[16]=C:\windows\syswow64\OLEAUT32.dll
LoadedModule[17]=C:\windows\system32\apphelp.dll
LoadedModule[18]=C:\windows\AppPatch\AcGenral.DLL
LoadedModule[19]=C:\windows\syswow64\SHLWAPI.dll
LoadedModule[20]=C:\windows\system32\UxTheme.dll
LoadedModule[21]=C:\windows\system32\WINMM.dll
LoadedModule[22]=C:\windows\system32\samcli.dll
LoadedModule[23]=C:\windows\system32\MSACM32.dll
LoadedModule[24]=C:\windows\system32\VERSION.dll
LoadedModule[25]=C:\windows\syswow64\SHELL32.dll
LoadedModule[26]=C:\windows\system32\sfc.dll
LoadedModule[27]=C:\windows\system32\sfc_os.DLL
LoadedModule[28]=C:\windows\system32\USERENV.dll
LoadedModule[29]=C:\windows\system32\profapi.dll
LoadedModule[30]=C:\windows\system32\dwmapi.dll
LoadedModule[31]=C:\windows\syswow64\SETUPAPI.dll
LoadedModule[32]=C:\windows\syswow64\CFGMGR32.dll
LoadedModule[33]=C:\windows\syswow64\DEVOBJ.dll
LoadedModule[34]=C:\windows\syswow64\urlmon.dll
LoadedModule[35]=C:\windows\syswow64\WININET.dll
LoadedModule[36]=C:\windows\syswow64\iertutil.dll
LoadedModule[37]=C:\windows\syswow64\CRYPT32.dll
LoadedModule[38]=C:\windows\syswow64\MSASN1.dll
LoadedModule[39]=C:\windows\system32\MPR.dll
LoadedModule[40]=C:\windows\system32\IMM32.DLL
LoadedModule[41]=C:\windows\syswow64\MSCTF.dll
LoadedModule[42]=c:\windows\syswow64\nvinit.dll
LoadedModule[43]=C:\windows\SysWOW64\guard32.dll
LoadedModule[44]=C:\windows\system32\fltlib.dll
LoadedModule[45]=C:\Program Files (x86)\Samsung\Movie Color Enhancer\WinCRT.dll
LoadedModule[46]=C:\windows\system32\WINSPOOL.DRV
LoadedModule[47]=C:\windows\system32\SXS.DLL
LoadedModule[48]=C:\windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_5.82.7601.17514_none_ec83dffa859149af\comctl32.dll
LoadedModule[49]=C:\windows\syswow64\CLBCatQ.DLL
LoadedModule[50]=C:\Windows\SysWOW64\scrrun.dll
LoadedModule[51]=C:\windows\system32\CRYPTSP.dll
LoadedModule[52]=C:\windows\system32\rsaenh.dll
LoadedModule[53]=C:\windows\SysWow64\FM20.DLL
LoadedModule[54]=C:\windows\system32\RICHED20.DLL
LoadedModule[55]=C:\windows\SysWow64\fm20ENU.DLL
LoadedModule[56]=C:\windows\system32\RpcRtRemote.dll
LoadedModule[57]=C:\windows\SysWow64\MSCOMCTL.OCX
LoadedModule[58]=C:\windows\syswow64\comdlg32.dll
LoadedModule[59]=C:\windows\SysWow64\COMCTL32.OCX
LoadedModule[60]=C:\windows\SysWow64\COMDLG32.OCX
LoadedModule[61]=C:\windows\system32\asycfilt.dll
LoadedModule[62]=C:\windows\SysWow64\RICHTX32.OCX
LoadedModule[63]=C:\windows\SysWow64\oledlg.dll
LoadedModule[64]=C:\windows\system32\RichEd32.DLL
LoadedModule[65]=C:\windows\WinSxS\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.17514_none_41e6975e2bd6f2b2\comctl32.DLL
LoadedModule[66]=C:\Program Files\WIDCOMM\Bluetooth Software\SysWOW64\BtMmHook.dll
LoadedModule[67]=C:\windows\syswow64\PSAPI.DLL
LoadedModule[68]=C:\windows\SysWOW64\SSUBTMR6.DLL
State[0].Key=Transport.DoneStage1
State[0].Value=1
FriendlyEventName=Stopped working
ConsentKey=APPCRASH
AppName=AutoPatcher main module
AppPath=C:\apup\autopatcher.exe

#7 ViroMan

    Just an awesome guy.

  • Project Manager
  • PipPipPipPipPipPip
  • 1,160 posts
  • Gender:Male
  • Location:California, USA, Earth, SOL, Milkyway
  • Interests:Programming and being a know it all pest.

Posted 02 February 2012 - 04:30 AM

nope sorry that doesn't help. :(

Try this though...
Right click on the autopatcher.exe file... then hit properties.
Click on the compatability tab.
Put a check in the check-box that says run this program in compatibility mode.
Change the windows version in the box to windows xp. Then try to run the program.

#8 timerrington@hotmail.com

    Newbie

  • Members
  • Pip
  • 1 posts

Posted 02 February 2012 - 10:17 AM

I have a similar problem (using x64 version)

Where: frmMain.Form_Load()
Error Code: 0xB: Division by zero

Log follows:

Attempting to initialize common controls.
Accessing filesystem...
AutoPatcher 5.6 loaded the filesystem.

Detected
English (1033) Windows 7 Ultimate 64-bit
System Components:
Internet Explorer: 9.0.8112.16440
Windows Media Player:
.NET Framework: 2.0.50727.5420|2.0SP2|3.0.30729.5420.5420|3.0SP2|3.5|3.5SP1|4|4SP0|4.0|4.0SP0
Windows Installer: 5.0.7601.17514
DirectX: 4.09.00.0904
MSN/Live Messenger:

Office Components:
Microsoft Word:
Microsoft Excel:
Microsoft PowerPoint:
Microsoft Outlook:
Microsoft Access:
Microsoft Project:
Microsoft Publisher:
Microsoft OneNote:
Microsoft FrontPage:
Microsoft InfoPath:
Microsoft Visio:
Microsoft SharePoint Designer:
Microsoft Groove:





1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users