17 replies to this topic

[Atom]

Real mystery. I'm running Windows 7x64 SP1 Home Premium.

Several weeks ago, I mentioned that autopatcher wouldn't run. After that I just gave up as no one offered any solution. Today, I saw a new file named apup131NEW and so I thought I would try it out and so I installed it. The downloading of the updates went without a hitch. But autopatcher.exe would not run. When I click on it the first time, there was an error saying that it didn't run properly. Subsequent clicks on autopatcher.exe produced nothing. Not an even error message.

Am I the only one facing this problem? Has anyone running on the same windows platform as mine successfully use autopatcher.exe? I'm really curious.

The other thing is that unwittingly ran the WindowsUpdateAgent30-x64.exe that I found in one of the folders installed by apup. Is it okay? Do I have to uninstall that? If yes, what do I need to do?

Thank you for your help.

[ViroMan]

no running anything in the folders downloaded is fine. They are from Microsoft so it won't hurt you. I know for you problem from last time. Im sorry but, I still have no clue what the problem could be. Did you try what I suggested in the last topic? Does autopatcher.exe have admin rights? Are you logged in as admin or a restricted account?

Can you find a log file in the windows directory called autopatcher.log and post it here?

Edited by ViroMan, 04 April 2012 - 08:59 PM.

[Atom]

Sorry, didn't attach log file properly. See my next post. Thanks.

Edited by Atom, 05 April 2012 - 12:10 AM.

[Atom]

ViroMan, on 04 April 2012 - 08:57 PM, said:

Can you find a log file in the windows directory called autopatcher.log and post it here?

While installing and running apup I have disabled comodo firewall, ESET NOD32. Yes, I was running as administrator. I also tried right clicking on autopatcher.exe and run it as administrator. Didn't help at all.

Attached is the apup.log file. Hope is attached properly.

Attached Files

•  apuplog.7z   4.4K   1 downloads

[ViroMan]

err.. um no, that is apup's log file. I need autopatcher.log file.. Its in the windows directory... go here

c:\windows\autopatcher.log (or what ever your windows directory was named during install)

[Atom]

ViroMan, on 05 April 2012 - 02:36 AM, said:

err.. um no, that is apup's log file. I need autopatcher.log file.. Its in the windows directory... go here
c:\windows\autopatcher.log (or what ever your windows directory was named during install)

Sorry. Here's the correct file...

Attached Files

•  autopatcher.zip   542bytes   2 downloads

[ViroMan]

Well it looks like it gets far enough into loading the program to generate a log and there doesn't seem to be anything wrong at that point. It just dies generating a usable GUI it seems.

[ViroMan]

hmm... well.. IF you have your original windows install CD and you have some time to babysit your computer... an hour or so. You can open up a dos window by going into START -> RUN and type in cmd. Hit enter and you will see a dos emulator window pop up. Put in your windows install CD into the CD tray and close any windows that pop up from it. Type in this in the dos window...

sfc /scannow

This will tell windows to scan itself for any weird things and replace files if they got screwed up. Like I said it can take a while depending on how fast your hard drive is.

Here is a LINK to describe SFC in more detail.

Edited by ViroMan, 05 April 2012 - 08:20 AM.

[Atom]

ViroMan, on 05 April 2012 - 08:18 AM, said:

This will tell windows to scan itself for any weird things and replace files if they got screwed up.

I did SFC scan as advised by you. When the process was completed, there was a message which said something like, "windows found corrupt files but were not able to recover for some of them."

I then exited cmd and rebooted, and then clicked on autopatcher.exe. Still no luck. The autopatcher.log is the same as the one I gave you earlier. Is it possible that some of the corrupt files not replaced are the ones affecting autopatcher.exe? The next question is what else can I do apart from re-installing windows itself?

I'm attaching the cbs.log in case you can make some sense of it. It's all Greek to me.

Thank you so much for your help.

Edited by Atom, 05 April 2012 - 09:56 AM.

[Atom]

Atom, on 05 April 2012 - 09:52 AM, said:

I'm attaching the cbs.log in case you can make some sense of it. It's all Greek to me.

Attached cbs.log

Edited by ViroMan, 06 April 2012 - 01:01 AM.

[ViroMan]

Well its quite large. Looks like there were a number of files it repaired. I also noted an abundance of errors about

SQM: Failed to start upload with file pattern: C:\windows\servicing\sqm\*_std.sqm, flags: 0x2 [HRESULT = 0x80004005 - E_FAIL]

What ever that may be. Perhaps a service that is not working. Looking it up gives me Micosoft Software Quality Manager, which could be it. Although I can't say if this is your problem.

I didn't notice anything else wrong other then LOTS of that kind of error, and tons of files replaced.

Have you tried to run Windows Disk Check yet? THIS is something to start before going to bed.. it will take 2-3+ hours to check your HD for bad sectors as well as checking all the files on your HD for being bad but, in a different way. Its significantly different way of checking files. I won't go into tech details but, ya its good to do this a 1-2 times a year or right away if your computer starts doing unexpected things. Basically files go bad once in a while... SFC only checks DLL and exe files based on a signature. This will check all files many different ways.

edit: ohh forgot to mention when you do as that link says... it may say that a checkup has been scheduled for the next start. Just reboot the computer and don't touch it. You can wait and see if the scan starts up before going into window.

Edited by ViroMan, 05 April 2012 - 11:56 AM.

[Atom]

I'm attaching a file named fix.zip which contains three files which I found after doing a search for "autopatcher".

1. Report.wer
2. autopatcher.exe.6992.dmp
3.AUTOPATCHER.EXE-3575D941.pf

Please take a look if you're not already tired and fed up looking at this problem. :-)

I'll be doing the scans which you recommended later tonight. Once again, thank you.

[ViroMan]

um.. still waiting for the attachments...

[Atom]

Sorry. I thought it was attached. Here it is.....fix.zip.

Edited by Atom, 05 April 2012 - 01:44 PM.

[Atom]

Atom, on 05 April 2012 - 01:44 PM, said:

Sorry. I thought it was attached. Here it is.....fix.zip.

For some reason the attachement is not working. I'll try again later.

Edited by Atom, 05 April 2012 - 01:55 PM.

[Atom]

ViroMan, on 05 April 2012 - 01:00 PM, said:

um.. still waiting for the attachments...

Apparently, I've exceeded my quota of 500kb of upload. So, I'm using higher compression to zip the three files. Hope that it works.

Attached Files

•  files.7z   207.35K   5 downloads

Edited by Atom, 05 April 2012 - 07:37 PM.

[ViroMan]

OK so I saw the same error report as before and decided to do some internet surfing on it. All I found is that the "Sig[3].Value=StackHash_16ed" means that windows has no idea why it crashed but, the reason is generally due to bad management of the memory stack. It basically crashed while inside of itself not due to a loaded object. So somewhere in the code is a bug.

Are you using any language besides English? I seen some reports that say Greek and a few other languages can cause this type of crash due to an application not being able to display multi-byte characters.

[Atom]

ViroMan, on 06 April 2012 - 02:26 AM, said:

Are you using any language besides English? I seen some reports that say Greek and a few other languages can cause this type of crash due to an application not being able to display multi-byte characters.

.

No, only English.