I was wondering why the discrepancy? is it to do with security updates becoming redundant as new ones are rolled out? if that's the case it would be better not to have them on the list surely, because perhaps they shouldn't be installed?
updates shown as not installed in autopatcher, but not in windows update
#1
Posted 19 January 2013 - 03:55 PM
I was wondering why the discrepancy? is it to do with security updates becoming redundant as new ones are rolled out? if that's the case it would be better not to have them on the list surely, because perhaps they shouldn't be installed?
#2
Posted 19 January 2013 - 07:56 PM
I'm confused exactly what you're asking here.
The ap pic shows lots of BLUE updates - this means installed according to AutoPatcher, BLACK means not installed, a check means the update is viewed as Critical and will be selected for install, a BLACK update unchecked means the update is viewed as optional - just some FYI. The pic only has 5 updates selected for install, killbits is the only one visible. You have 5 updates to install, what updates are missing?
The Windows Update pic lists one, a Windows Defender definition update. I believe the AutoPatcher script that downloads Defender is Microsoft Security ENU Addon Pack.
If you're asking why ANY updates are BLACK (uninstalled) in AutoPatcher, in other words, your system is fully updated so everything should be BLUE (installed), that makes sense.
The Windows Seven (7) script is a bit behind, the maintainer is pretty busy as of late, there will be more discrepencies as time rolls on.
It's probably best to be specific to nail down the exact updates that need attention...
... I have update (kb123456) installed via WU yet AutoPatcher shows it BLACK (uninstalled) - why?
... Windows Update list update (KB654321) is available for install yet AutoPatcher doesn't even list it - can we add it?
What I would do Helly,
...if you use Defender update the definition via WU, and, if you want to, download the script I mentioned that contains Defender - But Don't Install Defender using AutoPatcher - just see after you've updated the definitions via WU if Defender is BLUE or BLACK in AutoPatcher.
...If you've updated killbits it should be BLUE as well and not selected for install unless there's a detection issue or the script has an outdated killbits version.
These 2 issues are a starting point but overall Helly your system appears to be very up-to-date, good job.
#3
Posted 19 January 2013 - 09:17 PM
I take your point about being specific but you can appreciate with my confusion it would have been a big list to send! will do that in future though
I really like autopatcher, used to use it years ago and am trying to sort out an easy "restore system" for my computer and was fighting with windows backup, when I remembered this brilliant program and found it's been brought up to date for W7 64bit. yaah
anyhow I also take your point about maintainers being busy, if you could do with help let me know, I have some programming experience (mostly in C++ and Java)
1 other teeny little suggestion. I don't know if it's just me but I think if the items that are already installed were indicated in a light-grey or even light-blue, and even possibly disabled so they couldn't be installed it would be more obvious (to those simpletons like me) that they are already installed. They actually look kind of highlighted like they need installing in the current setup, IMHO
#4
Posted 19 January 2013 - 09:57 PM
the activex killbits update (I think that may be because I don't really use IE much and poss. that's an IE related update?)
KB2647753 and KB2496290 - these are marked as recommended (and presumably are optional as WU isn't indicating them as due) however on going to the MS info on them they look fairly important. BTW LOVE that I can click on "more info" from the dialog, such a nice touch. I guess that's not the fault of autopatcher, but MS
I'm surprised the WU agent needs updating as according to MS I WU should do that... tut tut
and that the JRE needs an update...but then again my java version (in control panel) indicates it's v7 update 2 , on the cmd line the version is "1.7.xxx" and on the java download site apparently update 11 is available. gawd Java versioning is craazee so I'm not too bothered about that
#5
Posted 19 January 2013 - 10:58 PM
helly, on 19 January 2013 - 09:17 PM, said:
No worries.
In AutoPatcher terms:
BLUE=Installed, BLACK=Uninstalled.
All Critical Uninstalled updates should be BLACK & Checked by default.
All NonCritical Uninstalled updates should be BLACK & UnChecked by default.
I wouldn't use the term up-to-date, the script might have an update but Microsoft might have a newer version, I'm guessing that's the issue with killbits, why it's BLACK in AutoPatcher and not suggested at WU. So don't install killbits in AutoPatcher until you determine it's the latest version, I think you have the latest and AutoPatcher is behind, I'm not positive until the version numbers are compared.
helly, on 19 January 2013 - 09:17 PM, said:
Not a problem.
helly, on 19 January 2013 - 09:17 PM, said:
You may want to ask ViroMan, He's the project manager.
helly, on 19 January 2013 - 09:17 PM, said:
Post your suggestions here - http://www.autopatch...ature-requests/
#6
Posted 20 January 2013 - 12:08 AM
helly, on 19 January 2013 - 09:57 PM, said:
If by missing do you mean absent from AutoPatcher, or do you mean shown as not installed (BLACK) when it should be BLUE? Missing in AutoPatcher speak means there is no such update in the script. I wonder if you're talking about a detection issue and using the term missing - this can get confusing.
helly, on 19 January 2013 - 09:57 PM, said:
See my previous post about killbits, this might be a case of either a bad detection or AutoPatcher has an older version whereas WU installed a newer version!!! Did you install the latest Cumulative Security Update for ActiveX Killbits available from Microsoft on your system? If you did ignore the listing (UnCheck) in AutoPatcher for now, the script needs to update the exe or apm.
helly, on 19 January 2013 - 09:57 PM, said:
Both updates are considered Optional, you need to decide if you want to install them. If you do install them using AutoPatcher, after a reboot of your system they should be BLUE, if not, please report it, no need to try to install a second time.
If you think they've been installed by WU yet still BLACK in AutoPatcher, please report the issue.
Remember, an update not needed on your system wont be shown to you at WU/MU - it doesn't apply to your system. AutoPatcher can't always determine this until after an attempt to install an update. The log file should say somewhere - "Doesn't apply...", keep this in mind.
helly, on 19 January 2013 - 09:57 PM, said:
If you use WUA make sure you have the latest, regardless if you update via AutoPatcher WU/MU.
helly, on 19 January 2013 - 09:57 PM, said:
BEWARE - JAVA(JRE) HAS SECURITY ISSUES
You need to either update to 7u11 which you already know about or simply delete 7u2 outright. Java has had security issues for a long time. Use Java(JRE) with much caution!!! If you're going to keep it on your system always have the latest (stable) version installed, I'm not talking about Beta versions, and be ready to disable Java in your browser should the latest version become exploitable - very likely!!!
#7
Posted 20 January 2013 - 02:25 AM
Quote
If you want to help, I would love help. If you know how to create DLL files, we could collaborate on getting a start on Autopatcher 2 which will combine both AP and APUP together and use a completely new APM format.
#8
Posted 20 January 2013 - 06:15 PM
@NunYa thing about the JRE is that sometimes you need several old versions as backward compatibility is not always, well compatible for existing programs written in java. when you say disable java in your browser do you mean javascript. I generally have that disabled anyway by default
@viroman I've sent you a message...perhaps we can continue there off this thread...
#9
Posted 20 January 2013 - 08:11 PM
helly, on 20 January 2013 - 06:15 PM, said:
I'm referring to Java(JRE), the runtime. In Mozilla Firefox you can find Java by clicking Tools - Add-ons - Plugins
Notice the warning from Mozilla about Java!!! Here's the page linked to for More Information - https://addons.mozil...ox/blocked/p182
As long as you're aware, as they say, the rest is up to you, your decision
#10
Posted 20 January 2013 - 09:07 PM
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users












