Autopatcher v6.2
Re: Autopatcher v6.1 beta
OK... so this version has
- new detection compares KO'd and returned to the previous revision.
- Executables and MSU' seems to work now thanks to Pendragon's bread crumbs. Will now scan for " '.exe' and '.com' " in the execution string and start it as an app if this is the case, otherwise treat it as a console command.
I think I forgot to do something for this release... leme think about it a bit.
Well I am tired so, the latest release on the first page. V.39
- new detection compares KO'd and returned to the previous revision.
- Executables and MSU' seems to work now thanks to Pendragon's bread crumbs. Will now scan for " '.exe' and '.com' " in the execution string and start it as an app if this is the case, otherwise treat it as a console command.
I think I forgot to do something for this release... leme think about it a bit.
Well I am tired so, the latest release on the first page. V.39
- Whatacrock
- Release Maintainer
- Posts: 1967
- Joined: Mon Oct 28, 2013 10:47 am
- Location: Australia
- Contact:
Re: Autopatcher v6.1 beta
Tested the newest autopatcher 6.1.39, it appears something has broken. Each time I tried to download a release in which contains deletes I receive a YIKES error.
Message in YIKES box GeneralFunctions.RunCommand() at line 104
Error Code: 0 x 35: File Not Found
Tested on the Following releases and received the same error: Adobe Acrobat Reader, Adobe AIR; Java x64 and x86 and list goes on..
For the time being reverting back to 6.1.32
Message in YIKES box GeneralFunctions.RunCommand() at line 104
Error Code: 0 x 35: File Not Found
Tested on the Following releases and received the same error: Adobe Acrobat Reader, Adobe AIR; Java x64 and x86 and list goes on..
For the time being reverting back to 6.1.32
"Now if you Sons of B*@ches got anything else to say, NOW'S THE F@#%ING TIME!!"
-
- Posts: 97
- Joined: Mon Oct 19, 2015 5:52 am
Re: Autopatcher v6.1 beta
Yay! It's not just me then lol. I only tried with Win 7 x86 but got the same error when trying AP 6.1.39.
Here's the last part of the log:
I even downloaded TheOne_Seven_x86_20151020.7z, put it in the temp_bin folder, & renamed it TheOne_Seven_x86.7z, but still got the "File not found" error.
Here's the last part of the log:
Code: Select all
Error Detected: File not found in RunCommand At Line 104
Attempted Commandline: call "C:\AutoPatcher-v6_1_39\apup_bin\curl.exe" -o "C:\AutoPatcher-v6_1_39\temp_bin\TheONE_Seven_x86.7z" http://www.autopatcher.net/releases/seven/TheOne_Seven_x86_20151020.7z
-
- Posts: 97
- Joined: Mon Oct 19, 2015 5:52 am
Re: Autopatcher v6.1 beta
Update: I skipped the Download section and went straight to Install. The Critical & Non-Critical updates seemed to install without any issues. (I copied the Modules folder that I had downloaded using 6.1.38)
So the crashes when installing .msu files in 6.1.38 seems fixed in 6.1.39, but introduced a new bug that the prior version did not have. Hm, can we have version 6.1.38.5?
So the crashes when installing .msu files in 6.1.38 seems fixed in 6.1.39, but introduced a new bug that the prior version did not have. Hm, can we have version 6.1.38.5?
Re: Autopatcher v6.1 beta
Ok try this. This is just a work around it there is a fix. When you get a YIKES error just keep clicking on the red x close button and you will be able to go on the the next step. Works for me. Just give it a try.
-
- Posts: 97
- Joined: Mon Oct 19, 2015 5:52 am
Re: Autopatcher v6.1 beta
That was a good idea, thanks! I had to hit the X close button twice, then AP proceeded as normal.
Here is the log from that part:
OK I think I see the problem, kinda. The folder is just bin not apup_bin. So I made a copy of bin and named it apup_bin, ran AP again - and got the exact same error! Sooo maybe I don't see the problem, after all.
Here is the log from that part:
Code: Select all
The Following Releases have been Picked:
seven/autopatcher_seven_x86_sp1_20151021.script
***Running Any Pre-Cleanup Routines***
Calculating Download Average
Download queue processed. Proceeding to next phase.
Executing shell command: ren "C:\AutoPatcher-v6_1_39\modules\Windows_Seven_x86\Critical\Critical_files\E11-Windows6.1-KB3003057-x86.msu" IE11-Windows6.1-KB3003057-x86.msu
trying to execute an external command or program.
Executing shell command: call "C:\AutoPatcher-v6_1_39\apup_bin\curl.exe" -o "C:\AutoPatcher-v6_1_39\temp_bin\TheONE_Seven_x86.7z" http://www.autopatcher.net/releases/seven/TheOne_Seven_x86_20151020.7z
trying to execute an external command or program.
Error Detected: File not found in RunCommand At Line 104
Attempted Commandline: call "C:\AutoPatcher-v6_1_39\apup_bin\curl.exe" -o "C:\AutoPatcher-v6_1_39\temp_bin\TheONE_Seven_x86.7z" http://www.autopatcher.net/releases/seven/TheOne_Seven_x86_20151020.7z
Executing shell command: call "C:\AutoPatcher-v6_1_39\apup_bin\7za.exe" x -y -o"C:\AutoPatcher-v6_1_39\temp_bin\" "C:\AutoPatcher-v6_1_39\temp_bin\TheONE_Seven_x86.7z"
trying to execute an external command or program.
Error Detected: File not found in RunCommand At Line 104
Attempted Commandline: call "C:\AutoPatcher-v6_1_39\apup_bin\7za.exe" x -y -o"C:\AutoPatcher-v6_1_39\temp_bin\" "C:\AutoPatcher-v6_1_39\temp_bin\TheONE_Seven_x86.7z"
Executing shell command: call "C:\AutoPatcher-v6_1_39\temp_bin\TheOneW7x86.bat"
trying to execute an external command or program.
***Starting Detection Routine Phase***
Missing file C:\AutoPatcher-v6_1_39\seven_x86_sp1.rtiz
--Adding http://www.autopatcher.net/releases/seven/seven_x86_sp1_20151021.rtiz--
-
- Posts: 97
- Joined: Mon Oct 19, 2015 5:52 am
Re: Autopatcher v6.1 beta
I ran both those commands from a command prompt, and they worked fine - but not when AP calls them. What gives?
(I had to create the temp_bin folder first, as this goes away when AP is closed.)
(I had to create the temp_bin folder first, as this goes away when AP is closed.)
Re: Autopatcher v6.1 beta
That is impossible! A code search gives no results for apup_bin. Yet I see it in your post!?
Got it...
This is found in the script itself.
WAC: This means the delete commands are not being issued. That is why I had extra files that one time I posted about them. I need to create a preaction command for you to download things in preaction that is safer. So for example when I get around to cutting out curl or it changes directories (not going to happen) you don't have to change things.
AP was silent error'ing out on these, but the new way will throw errors.
Got it...
Code: Select all
PreAction=call "autopatcher:\apup_bin\7za.exe" x -y -o"autopatcher:\temp_bin\" "autopatcher:\temp_bin\TheONE_Seven_x86.7z"
WAC: This means the delete commands are not being issued. That is why I had extra files that one time I posted about them. I need to create a preaction command for you to download things in preaction that is safer. So for example when I get around to cutting out curl or it changes directories (not going to happen) you don't have to change things.
AP was silent error'ing out on these, but the new way will throw errors.
- Whatacrock
- Release Maintainer
- Posts: 1967
- Joined: Mon Oct 28, 2013 10:47 am
- Location: Australia
- Contact:
Re: Autopatcher v6.1 beta
Ah OK, was wondering why I also ended up with stray files even though they were listed in the control txt file.
This occurred in my backup copy as was testing in the VM's but left my main Autopatcher on version 6.1.32
This occurred in my backup copy as was testing in the VM's but left my main Autopatcher on version 6.1.32
"Now if you Sons of B*@ches got anything else to say, NOW'S THE F@#%ING TIME!!"
-
- Posts: 97
- Joined: Mon Oct 19, 2015 5:52 am
Re: Autopatcher v6.1 beta
I have some more fun to add about AP 6.1.39.
In addition to the YIKES error on the Download screen (which we discussed above), after "Loading modules... done", I got another YIKES error:
tyrying??
From the Show Log screen:
As per parkd1's suggestion with the previous error, I hit the X button to close the error, and AP continued.
AP showed Official Release.
I proceeded to install the updates, clicked FINISH, then got another YIKES error message:
From the Show Log screen:
I have tried this several times, with reboots in between, but keep getting these errors. I even ran autopatcher.exe as Admin (via right-click) instead of from a .bat file, and got the same errors.
In addition to the YIKES error on the Download screen (which we discussed above), after "Loading modules... done", I got another YIKES error:
Code: Select all
What AutoPatcher was trying to do
It appears that the error occured while AutoPatcher was tyrying to start index process.
Where: mdlReleaseIntegrity.indexRTIFiles() At Line 132
Error Code: 0x35: File not found
From the Show Log screen:
► Show Spoiler
AP showed Official Release.
I proceeded to install the updates, clicked FINISH, then got another YIKES error message:
Code: Select all
What AutoPatcher was trying to do
It appears that the error occured while AutoPatcher was trying to clean up the temporary folders.
Where: frmMain.Form_Unload() At Line 104
Error Code: 0x46: Permission denied
► Show Spoiler