9 replies to this topic

[recluce]

I have been using Autopatcher for a long time on Windows 2000 and Windows XP. I use an USB stick which has had Autopatcher on it for ages and I use it on many PCs to update Windows. Now APUP offered the Windows 7 files for the first time, which I checked, along with new version of APUP and Autopatcher itself. The updates downloaded fine, but autopatcher just crashes on Windows 7. Could this be a problem with an older installation of autopatcher - or is there a known bug for AP on Windows 7? I am happy to provide additional information if the developpers let me know what they need.

BTW: THANKS for Autopatcher - it has saved me a lot of time and nerves over the last couple of years!

[DesertJerry]

I've been running AutoPatcher and APUP on Win7 32- and 64-bit with no problems similar to what you mentioned. It is not on a USB device though.

I was involved in testing it for Win7 and I would recommend you start from scratch for Win7 - download the latest APUP, create a folder on your hard drive and for the install of APUP then AutoPatcher and try again.

For your info - I have ONE AutoPatcher folder for all my operating systems: XP Pro w/SP3, XP Pro x64 w/SP2, Win7 32-bit, and Win7 64-bit. When I run APUP I just select everything appropriate for all four and go from there. It's been working that way for at least a month if not longer.

[recluce]

DesertJerry, on 15 April 2010 - 10:28 PM, said:

I've been running AutoPatcher and APUP on Win7 32- and 64-bit with no problems similar to what you mentioned. It is not on a USB device though.

I was involved in testing it for Win7 and I would recommend you start from scratch for Win7 - download the latest APUP, create a folder on your hard drive and for the install of APUP then AutoPatcher and try again.

I tried to copy the AP folder to the local harddrive to test the USB stick theory, but that didn't change anything. Next thing I will reinstall from scratch und Win 7, as suggested. I have a nagging suspicion that the very old installation might not have updated correctly.

Quote

For your info - I have ONE AutoPatcher folder for all my operating systems: XP Pro w/SP3, XP Pro x64 w/SP2, Win7 32-bit, and Win7 64-bit. When I run APUP I just select everything appropriate for all four and go from there. It's been working that way for at least a month if not longer.

Yep, that is the way I do it as well, for at least a couple of years now. Add to that the USB stick install and it becomes a "swiss army knife" for all the Windows systems I have to deal with: Windows 2000 (the final machine due to be replaced next month), Windows XP SP3 (SP2 has been retired in our environment) and now Windows 7 (we skipped Vista completely). All are 32-bit only.

[_def_x_]

Windows 7 x86 - what version - Pro, Ultimate? Is it on one of your PCs with 7 or all of them that the crash occurs?

What security software are you running, if any, when this happens? If you could elaborate on the environment that AutoPatcher
is being run from, it is easier for you to tell us than for us to try and guess or do the 20 questions thing.

Does AutoPatcher offer an error message dialog box or simply close without notice?

Can you see if there is any information in the AutoPatcher log file regarding the crash? The log file should be in \Windows, I'm
not sure on 7. Do a search for 'autopatcher.log'. If the information in the log seems old, clear the log file or delete it, and run
AutoPatcher again - recheck the log. I don't know if it will add more details but try running autopatcher.exe /verbose, check
the log again - any more detail? If you are unsure of which log to post, if either offer any help, post both using spoiler code.

This is the code (wide brackets) -> [spoiler ] log == file == here [ /spoiler]

Bringing the brackets together produces...

Spoiler

log == file == here

[recluce]

gUiTaR_mIkE, on 16 April 2010 - 02:36 AM, said:

Windows 7 x86 - what version - Pro, Ultimate? Is it on one of your PCs with 7 or all of them that the crash occurs?

So far, I have only one PC with Windows 7 (not rolled out yet, just experimenting). I could try to install on another machine, though.

Windows 7 Ultimate (clean install from Microsoft Technet DVD source) 32 bit.

Quote

What security software are you running, if any, when this happens? If you could elaborate on the environment that AutoPatcher
is being run from, it is easier for you to tell us than for us to try and guess or do the 20 questions thing.

I have Kaspsersky Internet Security 2010, but disabling it (complety exiting the software suite) does not make a difference.

System is a Dell Latitude D830 notebook (docked) with 2.2 GHz Core 2 Duo CPU, 4 GB RAM and NVidia Quadro NVS140 graphics. Not much installed yet besides hardware drivers and web browsers, "Aero" theme is active.

Quote

Does AutoPatcher offer an error message dialog box or simply close without notice?

Can you see if there is any information in the AutoPatcher log file regarding the crash? The log file should be in \Windows, I'm
not sure on 7. Do a search for 'autopatcher.log'. If the information in the log seems old, clear the log file or delete it, and run
AutoPatcher again - recheck the log. I don't know if it will add more details but try running autopatcher.exe /verbose, check
the log again - any more detail? If you are unsure of which log to post, if either offer any help, post both using spoiler code.

Windows gives me the following exception report:

Problem signature:
Problem Event Name: BEX
Application Name: autopatcher.exe
Application Version: 5.6.0.100
Application Timestamp: 4b964772
Fault Module Name: StackHash_81b7
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 00000000
Exception Offset: 003d9098
Exception Code: c0000005
Exception Data: 00000008
OS Version: 6.1.7600.2.0.0.256.1
Locale ID: 4105
Additional Information 1: 81b7
Additional Information 2: 81b74d3b4c52baf9e3845bd462773448
Additional Information 3: aaa2
Additional Information 4: aaa2ff6fb354be2d41f4697d6746ed55


This is the content of autopatcher.log:

AutoPatcher 5.6 loaded the filesystem.

Detected
English (1033) Windows 7 Ultimate 32-bit
System Components:
Internet Explorer: 8.0.7600.16535
Windows Media Player: 12.0.7600.16415
.NET Framework: 2.0.50727.4927|2.0SP2|3.0.30729.4926.4926|3.0SP2|3.5|3.5SP1
Windows Installer: 5.0.7600.16385
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:

Output running autopatcher.exe /verbose from the shell is identical.

Hope this helps...

[Cristiano]

thanks. our developers was informed about this topic. but i had an hint: Fault Module Name: StackHash_81b7

Quote

The StackHash error occurs any time DEP is invoked and has an issue with whatever application you’re trying to run (and there are several hundred out there that seem to give it fits). The error is related to Data Execution Prevention. Here’s how 99 percent of Vista users can fix a StackHash failure:

1. Open the Start menu and click Control Panel
2. Browse to System Maintenance then System
3. In the left panel, select Advanced System Settings from the available links
4. You should now see the System Properties Window, which will have three sections. The top section is labeled Performance and has a Settings button. Click this button.
5. Select the Data Execution Prevention tab.
6. Select the option which reads Turn on DEP for all programs and services except those I select.
7. Use the Browse button to locate the executable file for the application you were trying to start (oiwsetup.exe) when you received the StackHash error, and click Open to add it to your exceptions list.
8. Click Apply or OK to commit your changes.

the solution is for vista, but also applies to seven. so, can you please try that?

thanks

[]s

[recluce]

Cristiano, on 17 April 2010 - 02:19 AM, said:

thanks. our developers was informed about this topic. but i had an hint: Fault Module Name: StackHash_81b7


the solution is for vista, but also applies to seven. so, can you please try that?

thanks

I actually have DEP enabled ("Turn on DEP for all programs and services") by default on all XP SP3 machines and I did configure Win 7 the same way. Adding "autopatcher.exe" to the list of exclusions for DEP solves the problem (or is a viable workaround). So autopatcher works for now! Still would be good if it could do without this workaround, but I don't complain

Thanks for the help, especially to Christiano for this workaround!

[Cristiano]

> if it could do without this workaround
it's possible do that, if we sign the app, but there's a couple of issues involved. also is possible replace vb6 and it shall solve the issue too. we are talking about .net, but then it could make autopatcher incompatible with an clean install of 2k/winxp. but we are thinking about it

glad to help

[]s

[recluce]

Cristiano, on 17 April 2010 - 02:44 PM, said:

> if it could do without this workaround
it's possible do that, if we sign the app, but there's a couple of issues involved. also is possible replace vb6 and it shall solve the issue too. we are talking about .net, but then it could make autopatcher incompatible with an clean install of 2k/winxp. but we are thinking about it

I believe your concerns are very valid - so if you decide not to change autopatcher for better behaviour with DEP on Win 7, may I suggest that you include some big dialog window on APUP that would instruct users on Win 7 on how to disable DEP for autopatcher? Otherwise, you are going to see more bug reports like mine than you care for...

[Cristiano]

that's an idea

thanks

[]s