AutoPatcher Stalling!

[PictorieN]

Heya guys been using autopatcher for a few years now and never had a problem till now really.

Ive installed the May Core with July Updates. When i have run auto patcher serveral times it gets stuck at the end of a module and usualy says 99% or 98% and it wont continue until i kill the cmd.exe process. Its happened to me on about 5-6 computers now. Most of them have Kaspersky AV or IS installed, i thought it was that causing it but today i did a fresh install of XP and went to do autopatcher and again still does it on about 7-10 modules. Could be more. Kinda annoying not being automated exactly what auto patcher is meant to help out in doing. BTW this is over a network install.

I might just reextract all the files again and start over.

Be great if u guys can help me out. Thanks again for the time and effort put forth month in month out.

[patipata]

If Autopatcher stops when installing Powermenu, see this post.

[PsiMoon314]

Hi,

If you run AP from a .CMD file from the AP Folder / Share using code something similar to:

@echo off
setlocal enableextensions enabledelayedexpansion
pushd %~dp0
autopatcher.exe /nolicense /verbose /log
popd

then this will map a drive letter for you automatically and run Autopatcher. Adjust the command line options for Autopatcher as you need them.

In addition the current directory is correctly set so you might have less issues with installing some of the modules which currently fail via a Network install.

BTW There are at least two other threads discussing installations via Network Shares or via LAN's. You might want to READ them as they could just contain useful information! ;)

Kind Regards

Simon

[PictorieN]

@patipata: yeah im not installing PowerMenu, i did read that thread.

@PsiMoon314: Thanks for the info i did read threads on this, maybe my problem seeing i use to run the old autopatcher from command prompt. At the moment all im doing is maping a drive and running autopatcher.exe.

Just reextracted all releases and started fresh. Still same problem. Ill try the pushd method.

Anyways here is some screen caps of the modules in question, seems all MS Ones.

http://www.liquidite.com/ap01.jpg

http://www.liquidite.com/ap02.jpg

http://www.liquidite.com/ap03.jpg

http://www.liquidite.com/ap04.jpg

Thanks again guys.

[Guest adaman02]

@patipata: yeah im not installing PowerMenu, i did read that thread.

@PsiMoon314: Thanks for the info i did read threads on this, maybe my problem seeing i use to run the old autopatcher from command prompt. At the moment all im doing is maping a drive and running autopatcher.exe.

Just reextracted all releases and started fresh. Still same problem. Ill try the pushd method.

Anyways here is some screen caps of the modules in question, seems all MS Ones.

http://www.liquidite.com/ap01.jpg

http://www.liquidite.com/ap02.jpg

http://www.liquidite.com/ap03.jpg

http://www.liquidite.com/ap04.jpg

Thanks again guys.

I have also had this problem and I just re-installed Autopatcher and then it worked fine. Hope it helps.

[PictorieN]

tried pushd method, same problem.

@adaman02: yeah i did that too but still same problem. Might try downloading the full August Core, Maybe i have one of the updates messed up or something.

Thanks again guys, will get it soon i hope.

[PictorieN]

Ok tried using August Core, installed with July Addon Pack and August DirectX Pack.

Still does it, on a brand new machine with only xp being activated.

I have noticed though its the same updates i said above in the screen shots the 1st one is Windows Defender.

I have gone to the AutoPatcher Temp Directory where is has the batch file to run the said msi or exe file.

If i run the batch file the computer does give me a Windows Secruity Warning which is normal but im wondering if this cause be causing the issue within autopatcher as you dont ever see the command prompt with autopatcher which is causing it to hang on certain modules.

After i kill the cmd.exe process the module isn't installed, and the new batch file is written for the next module in the autopatcher temp directory, but it hangs again cause its one of these modules. once ive killed about 5-6 of them it carries on and installs the rest.

Modules i know that cause the it to hang are:

Windows Defender

Windows Live Messenger

Removal of MSN Messenger 4.6

There are more.

[+theblazingangel MVC]

install the august update. try again to see if it still happens. if so, run the new autopatcher.exe with the /log /report /verbose switches, and post C:\WINDOWS\autopatcher.log

[PictorieN]

@theblazingangel: Heya thanks for the help, ok what ive done is reinstalled just August Core, Shared the Directory, Map Networked the Folder, Run Autopatcher with following switches /log /report /verbose, in the list i have only selected Windows Defender cause i know this module causes the same problem as about 5-6 others. It goes through and stop at 99% of progress. I end the cmd.exe process and autopatcher comes up finished but has not installed windows defender. Also used the pushd method that was mentioned previously and in other threads, doesn't seem to work everytime though, eitherway i don't see the pushd method being any different then just mapping a drive, unless it caches it or something.

How ever if i copy the autopatcher directory from the network to desktop on the workstation computer it goes through and completely finishes. I think this the issue lies with windows blocking autopatcher to run the module batch file which autopatcher creates, but if that is the case why does it only do it with 5-6 modules and not every single one?

If this is being cause by Windows Security is it possible to make a registry entry as 1st module installed to disable windows network scripting blocking the modules?

This time i tested it on a brand new hard drive in my laptop with fresh install of Windows XP Home SP2 OEM, Have tested it with Pro does the same thing.

Here is the log file you requested, ive gone through it but seems pretty useless doesn't say anything but me selecting windows defender to be installed, of course u may notice something missing from log file that might be helpful.

AutoPatcher 5.6 loaded the filesystem.

AutoPatcher was run with the following commandline arguments: /nolicense /log /report /verbose
Detected English (1033) Windows XP Home Service Pack 2

System Components:
	Internet Explorer: 7.0.6000.20641
	Windows Media Player: 11.0.5721.5230
	.NET Framework: 1.1.4322|1.1SP1|2.0.50727.42|2.0SP0|3.0.04506.30|3.0SP0
	Windows Installer: 3.1.4000.1823
	DirectX: 4.09.00.0904
	MSN/Live Messenger: 8.1.178.0

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: 

The following items are flagged as critical:
	Microsoft Windows - Critical Updates (WINDOWS_CRITICAL_PARENT)
	Critical Update for Windows XP (KB885626 v2) (KB885626_XP_X86_ENU)
	Security Update for Windows XP (KB873339) (KB873339_XP_X86_ENU)
	Security Update for Windows XP (KB885836) (KB885836_XP_X86_ENU)
	Critical Update for Windows XP (KB886185) (KB886185_XP_X86_ENU)
	Security Update for Windows XP (KB888302) (KB888302_XP_X86_ENU)
	Security Update for Windows XP (KB891781) (KB891781_XP_X86_ENU)
	Security Update for Windows Messenger (KB887472) (KB887472_XPSP2_X86_ENU)
	Security Update for Windows XP (KB890859) (KB890859_XP_X86_ENU)
	Windows Installer 3.1 (v2) (KB893803_X86_ENU)
	Security Update for Windows XP (KB896358) (KB896358_XP_X86_ENU)
	Security Update for Windows XP (KB896428) (KB896428_XP_X86_ENU)
	Security Update for MSXML 2.6 (KB887606) (KB887606_MSXML2_6_ENU)
	Security Update for Windows XP (KB901214) (KB901214_XP_X86_ENU)
	Security Update for Windows XP (KB899591) (KB899591_XP_X86_ENU)
	Security Update for Windows XP (KB899587) (KB899587_XP_X86_ENU)
	Security Update for Windows XP (KB896423) (KB896423_XP_X86_ENU)
	Security Update for Windows XP (KB893756) (KB893756_XP_X86_ENU)
	Security Update for Windows XP (KB902400) (KB902400_XP_X86_ENU)
	Security Update for Windows XP (KB900725) (KB900725_XP_X86_ENU)
	Security Update for Windows XP (KB901017) (KB901017_XP_X86_ENU)
	Security Update for Windows XP (KB905414) (KB905414_XP_X86_ENU)
	Security Update for Windows XP (KB905749) (KB905749_XP_X86_ENU)
	Security Update for Windows XP (KB904706 v2) (KB904706_XP_X86_ENU)
	Windows Update v7 (WU7_X86)
	Security Update for Windows XP (KB908519) (KB908519_XP_X86_ENU)
	Security Update for Windows XP (KB901190) (KB901190_XP_X86_ENU)
	Security Update for Windows XP (KB911927) (KB911927_XP_X86_ENU)
	Security Update for Windows Media Player Plug-in (KB911564) (KB911564_X86_ENU)
	Security Update for Windows XP (KB911562) (KB911562_XP_X86_ENU)
	Security Update for Windows XP (KB908531 v2) (KB908531_XP_X86_ENU)
	Security Update for Windows XP (KB913580) (KB913580_XP_X86_ENU)
	Security Update for Internet Explorer for Windows XP SP2 (KB918439) (KB918439_XPSP2_X86_ENU)
	Security Update for Windows XP (KB914389) (KB914389_XP_X86_ENU)
	Security Update for Windows XP (KB917953) (KB917953_XP_X86_ENU)
	Security Update for Windows XP (KB911280 v2) (KB911280_XP_X86_ENU)
	Security Update for Windows XP (KB914388) (KB914388_XP_X86_ENU)
	Security Update for Windows XP (KB917422) (KB917422_XP_X86_ENU)
	Security Update for Windows XP (KB920670) (KB920670_XP_X86_ENU)
	Security Update for Windows XP (KB920683) (KB920683_XP_X86_ENU)
	Security Update for Windows XP (KB920685) (KB920685_XP_X86_ENU)
	Security Update for Windows XP (KB919007) (KB919007_XP_X86_ENU)
	Update for Windows XP (KB922582) (KB922582_XP_X86_ENU)
	Security Update for Windows XP (KB922819) (KB922819_XP_X86_ENU)
	Security Update for Windows XP (KB923191) (KB923191_XP_X86_ENU)
	Security Update for Windows XP (KB923414) (KB923414_XP_X86_ENU)
	Security Update for Windows XP (KB924270) (KB924270_XP_X86_ENU)
	Security Update for Windows XP (KB920213) (KB920213_XP_X86_ENU)
	Security Update for Windows XP (KB926255) (KB926255_XP_X86_ENU)
	Security Update for Windows XP (KB927779) (KB927779_XP_X86_ENU)
	Security Update for Windows XP (KB926436) (KB926436_XP_X86_ENU)
	Security Update for Windows XP (KB928255) (KB928255_XP_X86_ENU)
	Security Update for Windows XP (KB928843) (KB928843_XP_X86_ENU)
	Security Update for Windows XP (KB924667) (KB924667_XP_X86_ENU)
	Security Update for Windows (KB923723) (KB923723_X86_ENU)
	Security Update for Windows XP (KB927802) (KB927802_XP_X86_ENU)
	Security Update for Windows XP (KB918118) (KB918118_XP_X86_ENU)
	Cumulative Update for Internet Explorer 7 for Windows XP SP2 (KB928090) (KB928090_XP_IE7_X86_ENU)
	Security Update for Windows XP (KB925902) (KB925902_XP_X86_ENU)
	Security Update for Windows XP (KB930178) (KB930178_XP_X86_ENU)
	Security Update for Windows XP (KB932168) (KB932168_XP_X86_ENU)
	Security Update for Windows XP (KB931261) (KB931261_XP_X86_ENU)
	Security Update for Windows XP (KB931784) (KB931784_XP_X86_ENU)
	Security Update for CAPICOM (KB931906) (KB931906_X86_ENU)
	Cumulative Security Update for Outlook Express for Windows XP (KB929123) (KB929123_XP_X86_ENU)
	Security Update for Windows XP (KB935840) (KB935840_XP_X86_ENU)
	Security Update for Windows XP (KB935839) (KB935839_XP_X86_ENU)
	Security Update for .NET Framework 2.0 (KB928365) (KB928365_DN2_X86_ENU)
	Security Update for Windows Media Player 6.4 for Windows (KB925398 v2) (KB925398_X86_ENU)
	Security Update for .NET Framework 1.1 SP1 (KB928366) (KB928366_DN11SP1_X86_ENU)
	Root Certificates Update (1st Aug 2007) (ROOTCERTUP_ENU)
	Windows Script 5.7 for Windows XP (SCRIPT57_XP_X86_ENU)
	Malicious Software Removal Tool - August 2007 (KB890830 v1.32) (KB890830_X86_ENU)
	Cumulative Security Update for IE7 for Windows XP SP2 (KB937143) (KB937143_XP_IE7_X86_ENU)
	MSXML 6.0 SP1 inc. Security Update KB933579 (MSXML6SP1_ENU)
	MSXML 4.0 SP2 inc. Security Update KB936181 (MSXML4SP2_ENU)
	Security Update for IE7 for Windows XP SP2 (KB938127) (KB938127_XP_IE7_X86_ENU)
	Security Update for Windows XP (KB938829) (KB938829_XP_X86_ENU)
	Security Update for WMP 11 for Windows XP (KB936782) (KB936782_XP_WMP11_X86_ENU)
	Security Update for Windows XP (KB921503) (KB921503_XP_X86_ENU)
	Security Update for Windows XP (KB936021) (KB936021_XP_X86_ENU)
The following is a list of items that were marked for removal:
The following is a list of items that were marked for installation:
	Windows Defender v1.1.1593.21 (WD_X86_ENU)

[PictorieN]

Ive found out a way to fix my problem, It is a Windows Security Issue.

Im not sure if this can be intergrated into Autopatcher it self, I will however make my own module to run before any other modules to make the rest install. Its weird that no one else has had this issue.

What ive done is to allow file extensions to be automaticaly aloud instead of Windows Halting on a File Type.

[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Policies\Associations]
"LowRiskFileTypes"=".cmd;.bat;.exe;.msi"

Im pretty sure you would only have to allow .bat or .cmd files but added the others just to test.

I do see this as a bit of a security risk letting windows automatically run a cmd or bat file without asking.

I may make another module to delete the registry key after all the other modules are installed. Seems like an akward way of doing it but spose it will work for me in the mean time.

Thanks for all the support, was happy to finally find out what the hell was going after multiple days of trying to install autopatcher and multiple installs of windows.

Thanks again to everyone that has helped get AutoPatcher to where it is today.

[PictorieN]

Just a side note from retesting the entire install process of autopatcher, ive had to add a few more file extensions.

Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Policies\Associations]
"LowRiskFileTypes"=".cmd;.bat;.exe;.msi;.vbs;.msp"

Ive also attached a reg file for ease. Once ive made the modules ill post them up. Not Sure if this will help anyone else but id rather give back to the community.

Sorry for the Multiple Posts thought it would be easier seeing them seperate to see progression.

Disable___LowRiskFileTypes___AutoPatcher.zip

[major4579]

Just a side note from retesting the entire install process of autopatcher, ive had to add a few more file extensions.

Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Policies\Associations]
"LowRiskFileTypes"=".cmd;.bat;.exe;.msi;.vbs;.msp"

Ive also attached a reg file for ease. Once ive made the modules ill post them up. Not Sure if this will help anyone else but id rather give back to the community.

Sorry for the Multiple Posts thought it would be easier seeing them seperate to see progression.

PictorieN,

As I understand it you may want to use The Medium Risk category instead of Low Risk, as Low Risk files can be opened from any Security Zone with a warning, while Medium risk files types will open from the Trusted and Intranet Zones without a problem but will give a warning when opened from the Internet or Restricted zones. (I think I have this right).

In order to run .cmd or .bat files from the server I had to add those extensions to the Medium Zone on any computer running WXP-SP2 + IE7.

The registry key is:

[HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Policies\Associations]

"ModRiskFileTypes"=...

This is a standard change to my workstations so they can run any file from the server.

Hope this helps,

John

[PictorieN]

@major4579:

Thanks for the input, that sounds a bit more secure then i had it. Ill be making a module at the start and end of autopatcher's queue to enable those extensions and then remove them at the end. Thanks for the info im just glad i can run autopatcher on my machines now, having it stall 6 times or so was getting old fast. I did see another way to do it is to add the server to trusted zones but haven't tested that.

[PictorieN]

Here is the Modules for Auto Patcher. What it will do is add the file extensions to the registry before any other modules are installed and after everything is installed remove it making it back to normal. If you have the same problem and test this out be great to have some feed back, ive tested it on my end and just want to know if it help you out also. Ive used major4579's method instead of the orginal way i implented it.

Just Extract into the Modules Directory.

WindowsSecuritySettings.zip

[major4579]

Here is the Modules for Auto Patcher. What it will do is add the file extensions to the registry before any other modules are installed and after everything is installed remove it making it back to normal. If you have the same problem and test this out be great to have some feed back, ive tested it on my end and just want to know if it help you out also. Ive used major4579's method instead of the orginal way i implented it.

Just Extract into the Modules Directory.

I've installed your files to my Autopatcher - haven't had a chance to try it yet - one minor change:

windows_security.apm contains the following line

"[OperatingSystem]

WindowsVersion=2K,XP_X86,2K3_X86"

While the Enable/Disable apms contain:

"[OperatingSystem]

WindowsVersion=XP_X86"

This makes the "Windows Security Settings" section display without the Enable/Disable options in 2K and 2003. I know they are not needed in 2K so the section heading shouldn't show at all, but they may be needed in 2003.

Just a minor thing.

John