Page 1 of 2

newbie

Posted: Tue Apr 25, 2017 12:00 am
by gkarasik
Hi,

I'm new to autopatcher. I ran it for the first time today on my Win7 Ent/SP1 machine. Running Windows Update shows my machine as fully patched, but autochecker shows a boatload of available updates. What accounts for the discrepancy?

GaryK

Re: newbie

Posted: Tue Apr 25, 2017 1:21 am
by TheAPGuy
Ok.. first things first... Hello!
on to the next thing... are the updates in AP you are looking at blue? If they are blue they are already installed.

Re: newbie

Posted: Tue Apr 25, 2017 1:32 am
by gkarasik
No, they are black.

Re: newbie

Posted: Tue Apr 25, 2017 1:37 am
by TheAPGuy
If the Autopatcher.log file is not to big... can you copy it into here please.

Re: newbie

Posted: Tue Apr 25, 2017 1:41 am
by gkarasik
Autopatcher v6.2.22 ! ADMIN ! Has Started at 4/24/2017 6:40:40 PM

Starting Autopatcher From C:\Temp

Checking if OCX Files are registered.


Checking if an update is already running.
Detected (arguments) file. Reading...
Arguments file was empty. Shame on you!
Detected OS: English (1033) Microsoft Windows 7 Enterprise X86 Service Pack 1
Current Locale: English / Non-Unicode Default: English

checking for obsolete files...
Deleting File C:\Temp\temp_bin\apengine.rti
Deleting File C:\Temp\temp_bin\common.rti
Deleting File C:\Temp\temp_bin\seven_x86_sp1.rti
UNOFFICIAL: File 'C:\Temp\modules\windows_common.apm' (mentioned by RTI 'common.rti') does not exist!

UNOFFICIAL: File 'C:\Temp\modules\Common\KB890830_x64_glb.apm' (mentioned by RTI 'common.rti') does not exist!

UNOFFICIAL: File 'C:\Temp\modules\Common\KB890830_x86_glb.apm' (mentioned by RTI 'common.rti') does not exist!

Exit Button Pushed From Selection Window.

Autopatcher Is Terminating At 4/24/2017 6:41:12 PM

Re: newbie

Posted: Tue Apr 25, 2017 1:48 am
by TheAPGuy
first off...
Arguments file was empty. Shame on you!
for shame!
hmm log shows you are missing some files. Might want to re-download the Common script. <-- not a deal breaker but, if your missing the "windows_common.apm" you will not see any of the updates that are children of that apm.
OK says your using windows 7 SP1 x86... you downloaded the script for it... Check.

Next can you give an example KB update you see that Autopatcher says is NOT installed?

Re: newbie

Posted: Tue Apr 25, 2017 3:01 am
by gkarasik
Sorry--not sure what the arguments file is or how to use it.

Autopatcher says that KB2503665 needs to be installed. Registry shows it's there.

Re: newbie

Posted: Tue Apr 25, 2017 4:04 am
by TheAPGuy
ok... just to test this...
go to your windows directory.
find
system32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\Package_for_KB2503665~31bf3856ad364e35~x86~~6.1.1.0.cat

That file should be there.

You can also run cmd prompt hit start button and type in cmd and hit enter. Now.. type in

Code: Select all

wmic qfe | find “2503665”
you should see only one line with that update if it is installed.

also... the arguments file is there to throw switches in that you normally use. /verbose for example. If you don't have anything in there it is useless. It doesn't harm anything to have an empty file there though.

Re: newbie

Posted: Tue Apr 25, 2017 2:56 pm
by gkarasik
Typing wmic qfe | find “2503665” in CMD results in no response; also that file is absent in Catroot\{F75....

Autopatcher is doubtless correct that(those) update(s) is(are) absent. What's confusing is that autopatcher is telling me I'm missing 25 updates that Windows Update says I don't need.

Given that I'm running autopatcher on an older, already-updated system, might it be that these 25 updates are earlier versions of updates that have been superseded?

GaryK

Re: newbie

Posted: Wed Apr 26, 2017 2:36 am
by TheAPGuy
It is possible since that update is part of MS11-046... which was put out in Jun of 2011.
God I hate trying to figure out superseded updates because it is so convoluted when your looking that far back

KB2592799 supersedes KB2503665(but only for XP and server 2003) This is all I could figure out since there are a TON of security bulletins to go though since 2011. Care to look yourself? https://technet.microsoft.com/en-us/lib ... 32604.aspx
WhatACrock might know more about this sort of thing.

edit:
ohh here we go... Found an easier way to search... https://support.microsoft.com/en-us/hel ... t-for-2017 Go to bottom of page and start searching for the KB of the updates listed... you can see what update superseded what update...

For you: KB3092601 -> KB2961072 -> KB2875783 -> KB2645640 -> KB2503665 (win7)
So KB3092601 should be in the list not KB2503665.


Please list the KB files you see and we will get them removed and or updated with superseded updates.