AutoPatcher Forum

Hello;

Not totally new to autopatcher as I used it exclusively during the Winxp days and am now trying to make it run with Win7 Ultimate. After running apup to DL everything and then running autopatcher I'm getting the confused error box with the mdlinitizalition problem saying that the comctl32.ocx or dependencies is either missing or not registered. In system 32 that ocx file is where it is supposed to be and I re-registered it both manually and automatically with no problems. After rejoining the forum I did some reading and did a search on that particular ocx and got a number of results but when attempting to go to the threads the 404 errors indicated that the threads were no longer there for some reason. The log files are pretty short and sweet. The 'show log' off of the crash handler returns this;


And the log in the windows root returns this;


And help or ideas would be greatly appreciated.

Doing some further research it might be related to the fact that I'm running the 64 bit version of win7 and the comctl32.ocx needs to be in the SysWOW64 folder. I checked and it is in the sysWOW64 folder as well and I re-registered the file and attempted to run auto patcher again and same result. Also the first log is the same as the log in the windows root as I discovered that I didn't scroll down far enough in the crash handler log. LOL
Edited by Arion, 21 January 2011 - 02:20 PM.

No ideas at all from the brains around here? Please??

It's been a whole week with no replies and I would really appreciate some help here. Some of the tech guru's that put autopatcher together must have an idea on this...unless you just don't care to get involved? I'd have to imagine that this isn't the first time that a bug like this has happened.

Hi Arion Things are in flux around here at the moment, nothing intentional, hopefully the dev will see this post and offer deeper insight.

Quote

Can you please provide these links so they can be looked at.

Also, have a look at this post, scroll to post #12, notice the attachment - autopatcherLOG.zip - download and extract the file, autopatcherLOG.exe, to the same folder autopatcher.exe is in.

Run the file, copy the log file, paste in Notepad - what does the log show? What is the status of SSubTmr6.dll (or any of the other files in the \bin directory) on your system? If it helps post the log from the tool (unedited) here. You can delete the file once you've got the info.

Hi Mike;

Thanks for the input. To start off here are some of the links with the 404 html errors...

http://www.autopatch...__fromsearch__1

http://www.autopatch...__fromsearch__1

http://www.autopatch...__fromsearch__1

http://www.autopatch...__fromsearch__1


Looking at it close it seems to be an error in the search feature of the forum. In input the comctl32.ocx into the search box and most of the links returned the 404 error.


Here is a copy of the log generated from the .exe file....


It appears that everything is there but still getting the same mdlinitizalition problem with the comctl32.ocx file apparently.

The links are good, I think you added a few strings that caused the link to give off the 404 error. Btw, one of the links is to the page I already sent you, and another one is simply to the page listing the updated files added a while back.

Here you go

...topic_2010-bug-track-system_post_12586
...topic_2068-verification-failed_post_12542
...topic_1999-confused-autopatcher_post_11994
...topic_1627-new-ocx-dll-files_post_9072

Mike;

I really didn't find anything in those threads that were any help and am still waiting for any of the folks who put this fine program together to give me an idea as to where to go from here? The reason I need to use autopatcher is windows update is broken after an update in November and manual updating is currently the only way make my system current. I would greatly appreciate any of the folks that compiled this program for their assistance.

Hey Arion

To revisit your issue with search, it does look like at times the link is given addition strings (ex: __hl__xxxxxx__fromsearch__1) which gives off an error so it wasn't your doing.

Also, I had mentioned the project seems to be in flux - code for likely winding down, everyone has quit - as far as I can tell. I don't recall which post but it was mentioned that the dev had stopped by in the last few days, it is possible he missed this post but it is also in line with how most folks leave the project - no notice, they just quit communicating and eventually quit logging in. I am not saying this officially, it is not my place, just an opinion based on past experience.

You are an 'admin' right, running both apup and autopatcher locally, not from a remote location? AutoPatcher does work on some 7x64 systems which makes this a system by system issue - we need to know whats different about your 7x64 versus another user who is having no problems???

Will AutoPatcher even load for you, are you getting the 2 EULAs and the main screen or is the app crashing straight away, or when trying to install an update?

Hi Mike;

It is being run with administrator control on a local desktop and not a remote. Autopatcher won't even load and I'm not getting the EULA's at all. As soon as I try to run it the crash handler gives the error and it won't even initialize. The apup updater works fine and downloads the scripts files as it's supposed to do. But it crashes every time I try to start the main application.

A couple of thoughts on the ocx reg...

I believe there are 2 files in the C:\Windows\SysWOW64 folder that AutoPatcher needs - Comctl32.ocx & Comdlg32.ocx - check their version numbers and compare them to the versions in the C:\apup\bin folder. Also, make sure you use the 32-bit version of cmd.exe (should be in the \SysWOW64 folder) running 'elevated' to register and unregister the ocx files.

This is what I would try, make a restore point or zip up the 2 ocx files in the WOW64 folder for safe keeping, try unregistering Comctl32.ocx then start AutoPatcher - what happens? You may try removing Comctl32.ocx (you did zip a copy of both files right?) and replace it with the file in the \bin folder - register using the 32-bit cmd.exe running 'elevated' - right-click cmd.exe, Run As Admin. Make sure UAC and DEP are not getting in the way. If this doesn't work, replace the ocx file with the original from zip and register once again. To be safe I try to get the path and names exact - case and all - if the file is Comctl32.Ocx, that is the case I use, if all lower, I use lower, all upper, I use upper.

I mentioned *dlg32.ocx because this file may give off an error as well and you may need to replace it with the version in the \bin folder - only as a last resort. Zip up the 2 existing files in \SysWOW64 first then see if using the files from the \bin folder fixes things, if not, reinstall the originals.

I'm still hoping Antony will swing by and offer a bit of advice but until then...