←  AutoPatcher for Windows Vista

AutoPatcher Forum

»

Error while using APUP

Tech's Photo Tech 06 Jun 2008

I've downloaded and installed Autopatcher Vista July 2007.
I've done the same with APUP. I've unzipped the files but when I try to run apup.exe, after the UAC answer, I get this error message:
http://www.wikiforti...reenShot-32.png

What is Run-time error 372?

What am I doing wrong?
I have a HP Compaq nx6320 notebook running Vista Business 32bits.
Vista firewall and avast! Professional version as antivirus.
Also running ThreatFire.

Thanks for any help.
Edited by Tech, 06 June 2008 - 02:26 AM.
Quote

Tech's Photo Tech 07 Jun 2008

Can I bump? Any answer from the users/moderators?
Hmmm... doesn't anybody have an answer to this?
Edited by Tech, 07 June 2008 - 05:23 PM.
Quote

Tech's Photo Tech 11 Jun 2008

Lack of support?
Why forums then?
I'm used to live forums, sorry, 131 views and not a help word :(
Quote

Erik Ramey's Photo Erik Ramey 11 Jun 2008

Sorry about that. Lately MS has been pumping up the updates which I've been busy working on modules and away from the forums.

I'm currenlty behind a corporate firewall and cannot view the image. What does the error indicate?
Quote

Tech's Photo Tech 11 Jun 2008

First, many thanks for the answer.
The error message is:

Run-time error '372':
Failed to load control 'ctlwinsockdownloader' from . Your version of may be outdated. Make sure you are using the version of the control that was provided with your application.

After from and version of there aren't any particular info. The message is as is above.
Quote

Erik Ramey's Photo Erik Ramey 11 Jun 2008

This one is actually past my expertise. I think I know what is up but I would like to talk to Antonis first.

BTW - You will need to run APUP without the old July pack. All if not most of these updates have been superseded.
Quote

Tech's Photo Tech 12 Jun 2008

Quote

BTW - You will need to run APUP without the old July pack. All if not most of these updates have been superseded.
I've tried first, but I get nothing, nothing was updated, not a package downloaded, autopatcher was not installed so it couldn't, indeed, update. Right now, I have no other thing to do besides wait for your input... or Antonis'.
Quote

Erik Ramey's Photo Erik Ramey 17 Jun 2008

I still haven't heard from Antonis as of yet. I'm not sure which DLL is causing this but go ahead and try the following:

- Re-Register winsock.dll by going to run an typing in: regsvr32 /s winsock.dll "this is an educated guess by looking at the error"

- From the APUP folder, copy MSWINSCK.OCX to your System32 folder and try again
Quote

Tech's Photo Tech 21 Jun 2008

None of these two actions worked...
Strange... can I log the application or dump it in anyway?
Quote

Erik Ramey's Photo Erik Ramey 21 Jun 2008

I'm not sure what you mean when you say "dump it in"

I'm go ahead and dump the other OCX and the aamd532.dll from the apup_bin into your system32 folder. Afterwards, register them with the regsvr32 /s command and see what happens. Since these are the only libraries apup uses, this might do the trick.
Quote

BlueScreenOfDeath's Photo BlueScreenOfDeath 22 Jun 2008

Im also getting this same error in Windows Vista SP1 x64. I have put the 2 files from Server 2008 and it seems the actual Autopatcher app works but as far as trying to get apup.exe to function properly it gives me that error.
Quote

Erik Ramey's Photo Erik Ramey 22 Jun 2008

If you have tried everything up to now, I only have one last suggestion. APUP is basically vb6, try running vbrun60sp6.exe from the win9xnt folder.

Also after some reading on the net, make sure to run regsvr32 /s mswinsck.ocx after copying it to your system32 folder.
Quote

BlueScreenOfDeath's Photo BlueScreenOfDeath 22 Jun 2008

running the vb6 package didnt work either. Also did the regsvr32 stuff and didn't get any popup confirming it registered at all.
Quote

Erik Ramey's Photo Erik Ramey 22 Jun 2008

Last thing I can think of - There's a newer version of MSCOMCTL.OCX out there. Here's a link

Download and place it in your apup_bin folder
Quote

BlueScreenOfDeath's Photo BlueScreenOfDeath 22 Jun 2008

Wont believe this...deleted both of those files out of my system32 directory and apup.exe started right up :P
Quote

Erik Ramey's Photo Erik Ramey 22 Jun 2008

All I have to say is :wacko: :blink: :unsure:

I'll keep this in mind if this happens again with anybody else. Thanks for the resolution!
Quote

Tech's Photo Tech 22 Jun 2008

View PostBlueScreenOfDeath, on Jun 22 2008, 01:40 AM, said:

Also did the regsvr32 stuff and didn't get any popup confirming it registered at all.
This is due to /s parameter. Take it out and you'll see the confirmation window.

I think the problem is on the dll registration.
The error translation is something like: "The module "aamd532.dll" was loaded, but the entry point DllRegisterServer was not found". "Be sure that "aamd32.dll" is a DLL or OCX valid file and try again".
Seems it's not a 'valid' dll file for my Vista.

I've also downloaded the latest MSCOMCTL.OCX file but it does not work.

When I've said "dump" is to get a memory dump as it could be something bad processed in memory.

I really can't imagine a way to troubleshoot this :angry:
Quote

Guest_RoelofB_* 07 Aug 2008

I found this subject while doing a search for "ThreatFire" on this forum (this word was mentioned by Tech in his first writing). ThreatFire is a free but good rootkit (& more) scanner. On my PC (Windows XP) it found "Trojan.Dropper.VB.bag" in ..\AutoPatcher\apup_bin\uz.exe . Could this be of any help to you all ?
Quote

James's Photo James 07 Aug 2008

Hi RoelofB

Thanks for the post, but Trojan.Dropper.VB.bag is a false alarm and is old news.

See This Topic where the subject has just about been thrashed to death.

I'm amazed at how slow and/or how sloppy some AV vendors are in updating their definitions.

--



Edit: corrected typo.
Edited by James, 07 August 2008 - 11:53 AM.
Quote

James's Photo James 07 Aug 2008

Just to put this back On Topic:

"Run-time error '372'" and "Failed to load control 'ctlwinsockdownloader'..."
mean that you have a problem with MSWINSCK.OCX.

AutoPatcher's APUP comes with a copy of MSWINSCK.OCX, but there may be a copy in the Windows SYSTEM32 folder which conflicts with it.

See This Topic

--
Quote