kb3003743

kb3003743

Postby Izibia » 09.12.2018, 13:53

I applied WSUSOU Updater to Windows 7 Pro 64bit, without internet connection.

kb3003743 is listed in both ExcludeList-superseded-seconly.txt and ExcludeList-superseded.txt, but ...
Updater reports in the log:
Code: Select all
Warning: Update kb3003743 (id: b73e02b6-7a35-485b-a7ca-8be088fe5294) not found

Why?
Izibia
 
Posts: 15
Joined: 30.08.2014, 22:24

Re: kb3003743

Postby hbuhrmester » 17.12.2018, 21:55

kb3003743 is an old update for Windows 7 from 2014. It is superseded by the last three quality update rollups from October, November and December 2018. It is not superseded by the monthly security-only updates, because they seem to include only new updates.

Therefore, if you select security-only updates, some old updates may be requested again.

This can be corrected by adding the missing updates to the file ExcludeList-superseded-exclude-seconly.txt, but there is no automatism.

You can create a custom file wsusoffline/exclude/custom/ExcludeList-superseded-exclude-seconly.txt with the content:

Code: Select all
windows6.1-kb3003743


Note, that the file must end with an empty line.

Greetings,
hbuhrmester
hbuhrmester
 
Posts: 369
Joined: 11.10.2013, 20:59

Re: kb3003743

Postby Izibia » 20.12.2018, 06:27

Thank you for your answer.

1) Is this right?
ExcludeList-superseded-exclude-seconly.txt represents exclusions from ExcludeList-superseded-seconly.txt

2)
This can be corrected by adding the missing updates to the file ExcludeList-superseded-exclude-seconly.txt, but there is no automatism.

What do you mean by "no automatism"?

3) (it may be answered in point 2 already)
Is there a way how to determine updates that will be missing due to the described process, and do it in advance?
The process
download - run Updater - check missing updates in logfile and create custom\ExcludeList-superseded-exclude-seconly.txt - redownload - rerun Updater
seems to be complicated.
Izibia
 
Posts: 15
Joined: 30.08.2014, 22:24

Re: kb3003743

Postby hbuhrmester » 20.12.2018, 19:56

1) Is this right?
ExcludeList-superseded-exclude-seconly.txt represents exclusions from ExcludeList-superseded-seconly.txt


Yes.

2) What do you mean by "no automatism"?


The original configuration files are maintained manually by WSUSUpdateAdmin, but I don't know, what he uses to search for possibly missing updates. Users can create custom files with the same file name in the custom subdirectory.

3) (it may be answered in point 2 already)
Is there a way how to determine updates that will be missing due to the described process, and do it in advance?
The process
download - run Updater - check missing updates in logfile and create custom\ExcludeList-superseded-exclude-seconly.txt - redownload - rerun Updater
seems to be complicated.


Yes, but it isn't needed all the time. I only know of one similar case: In 2017 the update kb2631813 was reported as missing in Windows 7: viewtopic.php?f=4&t=7085

This kb number was subsequently added to the file ExcludeList-superseded-exclude.txt. The more specific ExcludeList-superseded-exclude-seconly.txt was introduced later.

Actually, I once tested a new method for the calculation of superseded updates: viewtopic.php?f=5&t=6141

It included a correction for superseded updates, if the superseding updates are excluded from download. This method still needed a list of excluded updates to start with, and it wasn't clear at the time, how this list could be created. But it can detect missing updates, if a list of full quality update rollups is used as the initial block list. This list can now be extracted from the file client/exclude/HideList-seconly.txt.

With this method, the following additional updates will be downloaded, if security-only updates are selected:

Code: Select all
windows6.1-kb2509553-x64_bcfe608b4d9e514ba1dc24a9e9dd6d45016ed3e5.cab
windows6.1-kb2509553-x86_843f5ab59bd04db015980cfc64955237b64526ac.cab
windows6.1-kb2544893-x64_21bb7cf8af8571e12267e165c4687429dc966544.cab
windows6.1-kb2544893-x86_fe24e7c2caae32c3a4b8dca345291fa3e5dbc492.cab
windows6.1-kb2862152-x64_ed45dcf054886800ff4dc5e0028e817c5cc270d3.cab
windows6.1-kb2965788-x64_e7b573d40904d4e65e426dccf3f387300e79bdf4.cab
windows6.1-kb2965788-x86_1733520483c7fa356e9fe33c739d5c4dc9aa701b.cab
windows6.1-kb2973351-x64_69e386b2997576d366447f5f6a4f64cef793dd89.cab
windows6.1-kb2973351-x86_1d98385c302921da0112861f4b335f9e543481ba.cab
windows6.1-kb3003743-x64_7b2bfcbba9ee00e54d485e9661e5a1683bb85561.cab
windows6.1-kb3003743-x86_1e1aca36281ad757a17c33cfc250888574a53a7d.cab
windows6.1-kb3022777-x64_c2c0f0636c921ab25678cbbceb1799eeb139956c.cab
windows6.1-kb3062577-x64_5f0aa3b50babc8ff66d05016b00dceded2a2fc73.cab
windows6.1-kb3067904-x64_e1eaa895232ebec13e92e03cd6cd42c536b5a501.cab
windows6.1-kb3067904-x86_21339712080d852fd1c9620cabd14001c6919fbf.cab
windows6.1-kb3076949-x64_0a58cffb033470caf3115e3719344ec6eb90c62a.cab
windows6.1-kb3076949-x86_04780a3bd2d40a15a1a97b331c61f6017c49c8bf.cab
windows6.1-kb3108381-x64_7a72ad5641ec26c94bfc535739b4603c40a41ccd.cab
windows6.1-kb3108381-x86_5eb32b0285429111fb1b3b43c15b246954b37545.cab
windows6.1-kb3109094-x64_570b08f22988118cfa06a014be2a7b66ab493802.cab
windows6.1-kb3109094-x86_d5582ff8e01aabb11ca0ce174f8106fdace1aecd.cab
windows6.1-kb3126446-x64_4300f47d4856ce306acb5e27d449e9f03a95f098.cab
windows6.1-kb3126446-x86_866aa06ef6867614de101fc367e4bdfb3f3ba6b8.cab
windows6.1-kb3185911-x64_f74ebe94266c2783206c56e4d9afe247ed051b81.cab
windows6.1-kb3185911-x86_8ffad3e4d18531aa0955df7893e892a2404817f0.cab
windows8-rt-kb2790978-x64_20d706ae85e2ab40cff77e5760fccd6ac5f17509.cab
windows8-rt-kb2862330-x64_d5cece56211c20f4abbe976da00979c185a596b0.cab
windows8-rt-kb3126446-x64_460dab794113a943b134ea8b28da80e23ebacc54.cab
windows8.1-kb2992611-x64_083da877dabb7775303a42bc5630be2f3fe15bca.cab
windows8.1-kb2992611-x86_ef583397acb662fb155ddb98344dc78bca512797.cab
windows8.1-kb3030377-x64_87d46acf9b8b0de4e8d2261f05d53e7cf4cc92fa.cab
windows8.1-kb3030377-x86_8d24e84428be8cd9f976c9c6c48ac51e64eee9a8.cab
windows8.1-kb3047234-x64_5c972c072885d258f3bf2af20020e16c6984e9b4.cab
windows8.1-kb3067505-x64_a7c28a6488de340ae72c6789a613e5ecd627cf44.cab
windows8.1-kb3067505-x86_9e09f6fde6cc54b4a175a4b120f808d6ab990dde.cab
windows8.1-kb3075220-x64_53cc5afdd13f15ba5144e56dedc22b372fcef63f.cab
windows8.1-kb3075220-x86_5a2f9ff414b12d74668b555efa2109fee27771db.cab
windows8.1-kb3088195-x64_56e84f191e0d49a22216e8b0115fbe2b92b5bee3.cab
windows8.1-kb3109094-x64_f3565d8f6b53c5a85c654ab441b4696be918fe49.cab
windows8.1-kb3109094-x86_6ef6791ea79ca15ace90ea318d66fccb2c31c071.cab
windows8.1-kb3121461-x64_37f61d9afa6898c2861bb854abcb3a22d97fee9e.cab
windows8.1-kb3121461-x86_6f79849cd93561fbc19a8ab03f3fcdee4ce7d6cf.cab


These updates would also be candidates for the file ExcludeList-superseded-exclude-seconly.txt.

Most of these updates are old updates, which were created before the introduction of update rollups. But it seems, that the full quality update rollups included some of these older updates at some time, while the security-only updates only include new updates for the current month. This is, of course, only guessing.

Greetings,
hbuhrmester
hbuhrmester
 
Posts: 369
Joined: 11.10.2013, 20:59

Re: kb3003743

Postby WSUSUpdateAdmin » 21.12.2018, 14:52

Hi.

hbuhrmester wrote:[...]You can create a custom file wsusoffline/exclude/custom/ExcludeList-superseded-exclude-seconly.txt [...]

Sorry, there hasn't been support for a custom addition to this file yet.
Added by r1002.

hbuhrmester wrote:The original configuration files are maintained manually by WSUSUpdateAdmin, but I don't know, what he uses to search for possibly missing updates.

Just a blank reference VM...
Last regression run was in September, where kb3003743 was installed.
As I just saw in the download log, kb3003743 was deleted by the wsusscn2.cab catalog in October.

By today's regression run, kb3003743 is not reported as missing, but anyway:
Added by r1002.

Greets,
Torsten
WSUSUpdateAdmin
Administrator
 
Posts: 2194
Joined: 07.07.2009, 14:38

Re: kb3003743

Postby Izibia » 21.12.2018, 15:57

WSUSUpdateAdmin wrote:By today's regression run, kb3003743 is not reported as missing, but anyway:
Added by r1002.

I checked in which situations kb3003743 was reported as "not found" during the update process of WSUSOU 11.5:

I applied UpdateInstaller to a fresh Windows 7 SP1, without internet connection; NDP472-KB4054530 was not installed due to missing certificate: kb3003743 was not reported in the log
Then I manually installed NDP472-KB4054530; I reran UpdateInstaller without internet connection: kb3003743 was reported as not found

Then I returned to a fresh Windows 7 SP1 and I tried to run UpdateInstaller with internet connection: kb3003743 was not reported in the log

--------------------------------
( what is r1002? )
Izibia
 
Posts: 15
Joined: 30.08.2014, 22:24

Re: kb3003743

Postby Dalai » 21.12.2018, 16:55

Izibia wrote:( what is r1002? )

It's a reference to the WSUS Offline Update trunk (http://trac.wsusoffline.net/browser/trunk), and a specific change set in the source. WSUS Offline Update's releases are built from the trunk eventually.

Regards
Dalai
Dalai
 
Posts: 839
Joined: 12.07.2016, 21:00

Re: kb3003743

Postby Izibia » 23.12.2018, 03:07

Continuation of ...
I checked in which situations kb3003743 was reported as "not found"


4th try:

First I manually added a certificate accordingly to this post, in order to solve the problem with an offline installation of .NET 4.6.2
Then I ran UpdateInstaller without internet connection: .NET 4.6.2 was installed and kb3003743 was not reported in the log
Izibia
 
Posts: 15
Joined: 30.08.2014, 22:24


Return to Verschiedenes / Miscellaneous

Who is online

Users browsing this forum: No registered users and 2 guests