Vista SP2 32bit Unsupported
Squall
28 Jun 2010
Hi im currently new to Autopatcher and find it a very convenient product to use especially for friends that are still on the dreaded dialup connection
The problem I have is that I downloaded the Vista SP2 21Jun10 release everything seems to download fine and encounter no erros but upon running the program it says in red Unsupportred/Unofficial I deleted the whole folder and started the download again still same result upon running it
I have attatched my log below using the batch file included when you download the apup zip
Any advice would be greatly appreciated as I like to know everything would be fine before I run it on a few friends pc's
Many Thanks,
Dean
apup.txt (50.75K)
downloads: 4
Edited by Squall, 28 June 2010 - 09:53 PM.
The problem I have is that I downloaded the Vista SP2 21Jun10 release everything seems to download fine and encounter no erros but upon running the program it says in red Unsupportred/Unofficial I deleted the whole folder and started the download again still same result upon running it
I have attatched my log below using the batch file included when you download the apup zip
Any advice would be greatly appreciated as I like to know everything would be fine before I run it on a few friends pc's
Many Thanks,
Dean
apup.txt (50.75K)
downloads: 4
Edited by Squall, 28 June 2010 - 09:53 PM.
_def_x_
29 Jun 2010
Hi Squall
You don't need to download completely a release that has verification errors, usually running APUP again on the same folder will collect any missing files. In some cases a link or file will change and the release will become Unofficial - this is no big deal, simply inform the release maintainer by posting a log file in the proper forum (like you did) and they will correct the issue as soon as they can.
Your issue seems to be that you didn't get a complete release, your log file shows -> Files to be Downloaded: 83 - you surely didn't get the 'Finish' tab indicating the download was complete did you?
I would run APUP again until you get 'Finish' to close APUP, check the log making sure there are no (zero) files to download, if you get errors or an incomplete release still, try again on the same folder, if this doesn't fix the issue post the log file of your last run of APUP. You can put the log file in [spoiler ] log file here [/ spoiler] code which is convenient to read - just bring all the brackets together to create this...
You don't need to download completely a release that has verification errors, usually running APUP again on the same folder will collect any missing files. In some cases a link or file will change and the release will become Unofficial - this is no big deal, simply inform the release maintainer by posting a log file in the proper forum (like you did) and they will correct the issue as soon as they can.
Your issue seems to be that you didn't get a complete release, your log file shows -> Files to be Downloaded: 83 - you surely didn't get the 'Finish' tab indicating the download was complete did you?
I would run APUP again until you get 'Finish' to close APUP, check the log making sure there are no (zero) files to download, if you get errors or an incomplete release still, try again on the same folder, if this doesn't fix the issue post the log file of your last run of APUP. You can put the log file in [spoiler ] log file here [/ spoiler] code which is convenient to read - just bring all the brackets together to create this...
Spoiler
Squall
29 Jun 2010
Thanks for your reply I reran the batch file within the same folder and it got to the finish button where options and exit buttons are greyed out/disabled
After I click finish I run Autopatcher and still presented with the Unofficial/Unsupported Release I clicked on About then Release Info it says the Autopatcher Engine is True and Autopatcher For Windows Vista SP... is False
I have attatched the new autopatcher logs as I renamed the previous one to apup old.txt so I can keep the previous log copy
After I click finish I run Autopatcher and still presented with the Unofficial/Unsupported Release I clicked on About then Release Info it says the Autopatcher Engine is True and Autopatcher For Windows Vista SP... is False
I have attatched the new autopatcher logs as I renamed the previous one to apup old.txt so I can keep the previous log copy
Spoiler
click-click
29 Jun 2010
Squall
Did you by chance look at the autopatcher log file located in c:\windows ?
If it shows any errors usually the beginning messages will indicate what might be wrong. To get the log you need to run autopatcher with the /log /verbose parms.
Edited by click-click, 29 June 2010 - 11:46 AM.
Did you by chance look at the autopatcher log file located in c:\windows ?
If it shows any errors usually the beginning messages will indicate what might be wrong. To get the log you need to run autopatcher with the /log /verbose parms.
Edited by click-click, 29 June 2010 - 11:46 AM.
Squall
29 Jun 2010
Thanks for your reply
No with being new to Autopatcher I was not aware there was a log kept in c:\windows I have attatched the current C:\WINDOWS\autopatcher.log one I have found without using /log /verbose
Then I will post the C:\WINDOWS\autopatcher.log after rerunning the download using /log /verbose to see if theres any change
Edited by Squall, 29 June 2010 - 04:08 PM.
No with being new to Autopatcher I was not aware there was a log kept in c:\windows I have attatched the current C:\WINDOWS\autopatcher.log one I have found without using /log /verbose
Then I will post the C:\WINDOWS\autopatcher.log after rerunning the download using /log /verbose to see if theres any change
Spoiler
Edited by Squall, 29 June 2010 - 04:08 PM.
Squall
29 Jun 2010
Just edit the hit_this_to_generate_a_log_file_for_apup.bat to read the following apup.exe /log /verbose
Reran the batch file afterwards and still displays the Unoffical/Unsupported message the download got to displaying the finish button with the rest all greyed out no errors encountered ill post the new apup.log and c:\windows\autopatcher.log now
New Apup.log
c:\windows\autopatcher.log
Edited by Squall, 29 June 2010 - 04:42 PM.
Reran the batch file afterwards and still displays the Unoffical/Unsupported message the download got to displaying the finish button with the rest all greyed out no errors encountered ill post the new apup.log and c:\windows\autopatcher.log now
New Apup.log
Spoiler
c:\windows\autopatcher.log
Spoiler
Edited by Squall, 29 June 2010 - 04:42 PM.
_def_x_
29 Jun 2010
Nice find Squall, this is an error in the modules (apm files) and needs to be fixed by Domenico.
There are errors in these 4 modules - the details point to the wrong folder and executable - KB980182 instead of KB982381.
There are errors in these 4 modules - the details point to the wrong folder and executable - KB980182 instead of KB982381.
Spoiler
Squall
29 Jun 2010
Which file if any needs editing to get the release to show up as official is it something I could do myself or an I better waiting for the release maintainer
If its something I can edit what do I need to add/change and to which files
Many Thanks
If its something I can edit what do I need to add/change and to which files
Many Thanks
_def_x_
29 Jun 2010
Squall said:
If its something I can edit what do I need to add/change and to which files
If you want to have a look, the files are listed in your AutoPatcher log and in the spoiler from post #7. The .apm files can be opened in any text editor.
Note: Since your release is already Unofficial you can play with the details if you like but don't change the name of any .apm file - KB982381_IE8_vista_x86.apm - the script will replace a file (by the exact name) whose hash doesn't match but if the name changes the script wont know the new name and you will have a stray that will forever cause your release to be Unofficial - unless you start fresh. The details are usually found by extracting the contents of the update (only for the experienced).
Believe it or not there have been a few people who have had one stray file that never got deleted, their release was Unofficial for a long time. Usually they waited too long before updating the release, the scripts were cleaned (thinned out, some detections removed) and so a lone file got left behind. To make it easier to find the strays the use of a recursive .md5 is used (either in the release or provided by the user) to scan an offending release or known good release.
Squall
29 Jun 2010
Thanks all for your help I might have a play sometime and learn a thing or two after making a copy of it first, but for now I think it be best to wait for a fixed update of the script
Many Thanks
Dean
Many Thanks
Dean
Cristiano
29 Jun 2010
i've sent an warning about the topic to domenico, through pm. but there's some time since his last pm reading. so...
[]s
[]s
dkdk_it
30 Jun 2010
Uhm... I've forgotten any details... fixed. Can you check now?
Thanks
P.S.: I must drink less beers...
Thanks
P.S.: I must drink less beers...
alchemist zim
04 Jul 2010
just did it checked the autopatcher log in windows directory this is what i found
Module 'KB981332_IE8_2k8_x86.apm' uses an unknown/unsupported property called '981332'. Please make sure this is not a mis-spelling!
Module 'KB981332_IE8_2k8_x86.apm' uses an unknown/unsupported property called 'Module981332'. Please make sure this is not a mis-spelling!
Module 'Microsoft Network Monitor 3.4' (unique id: 'Microsoft_Network_Monitor_x86') reports 'MICROSOFT_PARSERS_PARENT' as its parent, but such module does not exist or is not loaded in the right order.
Edited by alchemist zim, 04 July 2010 - 01:36 PM.
Module 'KB981332_IE8_2k8_x86.apm' uses an unknown/unsupported property called '981332'. Please make sure this is not a mis-spelling!
Module 'KB981332_IE8_2k8_x86.apm' uses an unknown/unsupported property called 'Module981332'. Please make sure this is not a mis-spelling!
Module 'Microsoft Network Monitor 3.4' (unique id: 'Microsoft_Network_Monitor_x86') reports 'MICROSOFT_PARSERS_PARENT' as its parent, but such module does not exist or is not loaded in the right order.
Edited by alchemist zim, 04 July 2010 - 01:36 PM.
Cristiano
04 Jul 2010
'MICROSOFT_PARSERS_PARENT' issue solved.
about the vista script, domenico will be warned about
thanks
[]s
about the vista script, domenico will be warned about
thanks
[]s
Squall
06 Jul 2010
alchemist zim, on 04 July 2010 - 01:34 PM, said:
just did it checked the autopatcher log in windows directory this is what i found
Module 'KB981332_IE8_2k8_x86.apm' uses an unknown/unsupported property called '981332'. Please make sure this is not a mis-spelling!
Module 'KB981332_IE8_2k8_x86.apm' uses an unknown/unsupported property called 'Module981332'. Please make sure this is not a mis-spelling!
Module 'Microsoft Network Monitor 3.4' (unique id: 'Microsoft_Network_Monitor_x86') reports 'MICROSOFT_PARSERS_PARENT' as its parent, but such module does not exist or is not loaded in the right order.
Module 'KB981332_IE8_2k8_x86.apm' uses an unknown/unsupported property called '981332'. Please make sure this is not a mis-spelling!
Module 'KB981332_IE8_2k8_x86.apm' uses an unknown/unsupported property called 'Module981332'. Please make sure this is not a mis-spelling!
Module 'Microsoft Network Monitor 3.4' (unique id: 'Microsoft_Network_Monitor_x86') reports 'MICROSOFT_PARSERS_PARENT' as its parent, but such module does not exist or is not loaded in the right order.
Tested myself and have the same log as alchemist in autopatcher.log again apup.log shows no errors currently
Cristiano
06 Jul 2010
do you have tried update the extras script? one issue was fixed in that one. the other one was reported to domenico, but he is having an hard time at work at those days. so, an fix for it may take a few days
[]s
[]s
Squall
09 Jul 2010
Cristiano, on 06 July 2010 - 09:23 PM, said:
do you have tried update the extras script? one issue was fixed in that one. the other one was reported to domenico, but he is having an hard time at work at those days. so, an fix for it may take a few days
[]s
[]s
Im not 100% sure what you mean do you mean if I checked the tickbox for extras aswell when I selected Vista SP2 or if I installed/download the extras pack within the same folder then no
As I download each release I put the release on its own in a seperate folder so if i downloaded extras pack i store it at for example c:\autopatcher\extras\ and vista as c:\autopatcher\vistasp2\ etc
Cristiano
09 Jul 2010
well, in alchemist zim log, an issue with MICROSOFT_PARSERS_PARENT was pointed and fixed. after that, you said that your log shows the same. well, if the problem was fixed, then your log couldn't show the same thing, because at least one of the problems pointed was fixed. so please, your log shows the same thing than alchemist zim? if so, are you sure that one script isn't mixed with another one and you have forgot about it or even didn't noticed?
[]s
[]s
Squall
10 Jul 2010
Cristiano, on 09 July 2010 - 10:12 PM, said:
well, in alchemist zim log, an issue with MICROSOFT_PARSERS_PARENT was pointed and fixed. after that, you said that your log shows the same. well, if the problem was fixed, then your log couldn't show the same thing, because at least one of the problems pointed was fixed. so please, your log shows the same thing than alchemist zim? if so, are you sure that one script isn't mixed with another one and you have forgot about it or even didn't noticed?
[]s
[]s
Hi I reran the update and the MICROSOFT_PARSERS_PARENT error has disappeared from the logs now im still showing as unsupported I will attach the new logs
apup.log
Spoiler
autopatcher.log (c:\windows\autopatcher.log)
Spoiler
Cristiano
10 Jul 2010
ok, im more awake today (8h of sleep in 96h... isn't enough, but at least i'm thinking better). looking into the module, i've found this:
981332=Microsoft
Module981332=dkdk_it
and this should be:
Author=Microsoft
ModuleAuthor=dkdk_it
the attached module is the fixed version for this one. domenico is kinda busy right now and i don't have the vista script in here to fix this issue. so please, just extract the attached module into modules\critical, replacing the existing one that that message shall disappear. issue: autopatcher will shows as unofficial until an fix in the script arrive
[]s
981332=Microsoft
Module981332=dkdk_it
and this should be:
Author=Microsoft
ModuleAuthor=dkdk_it
the attached module is the fixed version for this one. domenico is kinda busy right now and i don't have the vista script in here to fix this issue. so please, just extract the attached module into modules\critical, replacing the existing one that that message shall disappear. issue: autopatcher will shows as unofficial until an fix in the script arrive
[]s
