WSUS Offline vs MSFT Built-In Windows Update (Conflicts?)

WSUS Offline vs MSFT Built-In Windows Update (Conflicts?)

Postby wsuuid » 30.04.2017, 17:22

Am I correct in assuming that after using WSUS Offline Update that the internal Windows Update app *recognizes* all the updates done by WSUS Offline Update and will then only recommend newer updates from MS servers that Windows doesn't see after "calling home" to MS?

Or, is there a potential for *conflict* which would suggest that one either use on WSUS Offline Update for all updating OR stay revert to Windows Update exclusively.

(I would be appalled to find that WSUS Offline Updates were not recognized by MS servers! This might cause attempts to double-update and create corruptions!)

Thx!
wsuuid
 
Posts: 7
Joined: 23.04.2017, 12:26

Re: WSUS Offline vs MSFT Built-In Windows Update (Conflicts?

Postby boco » 30.04.2017, 21:25

WOU installs updates (by DISM.exe or WUSA.exe) correctly, they are recognized by WU as being installed (as the packages are registered in the Component Store). However, there are a few quirks:
1. The majority of updates installed by WOU do not appear in Update History. This is probably done by MS so integration of updates does not clutter up the Update History (as integrated updates aren't uninstallable). Could also be a bug. Those updates will correctly show in "Installed Updates"!
2. Occasionally, WU will re-offer a seemingly old update with a small download size. That is perfectly normal, as updates can consist of multiple packages. So, if MS updates/re-issues one package of the whole KB, that KB is offered again.
3. If you run WOU in security-only mode, WU is pretty useless for normal updating (as it does not offer security-only packages at all).
Microsoft update catalog: http://catalog.update.microsoft.com/v7/site/
Windows Install media creator: https://support.microsoft.com/en-us/help/15088/windows-create-installation-media
boco
 
Posts: 1846
Joined: 24.11.2009, 17:00
Location: Germany

Re: WSUS Offline vs MSFT Built-In Windows Update (Conflicts?

Postby wsuuid » 01.05.2017, 01:33

Boco, thank you.

My principal objective is determining if I can simply disable/ignore MS WU completely and just rely on WOU for all OS and related security updates.

The answer seems yes. And if correct, that is good and it would move me to disable any and all RAM eating WU processes that WOU would render needless.

IF, however, there is any reason you may advise *against* disabling any "system-resource eating" WU background processes that I would want to disable, let me know. If no issues, I would happily rely on WOU for all my Win "x" update tasks.

I am using Windows Defender in Win 8.1 and still am trying to determine if this is a negative (in favor of an alternate anti-virus) or if I can just disable and rely on "Malwarebytes" already running.

I wish to run an updated, secure, patched machine and I appreciate your good work with WOU as I have often found WU to hang or just be an overall headache in the various Win 7, 8, 8..1 and 10 machines I use.

END###
wsuuid
 
Posts: 7
Joined: 23.04.2017, 12:26

Re: WSUS Offline vs MSFT Built-In Windows Update (Conflicts?

Postby boco » 01.05.2017, 11:13

First note: The Windows Update service must be left enabled. WOU uses it exactly as WU does.

Disabling WU completely? I wouldn't do that. WOU does not contain all available updates, only the security-critical ones. There will always be the odd update that is available on WU but not in WOU. WOU's purpose is to make a system safe, not completely patched.
The long search problem was patched by a new WU Client update (that WOU installs).

Unfortunately, completely doing away with Wu is not possible.
Microsoft update catalog: http://catalog.update.microsoft.com/v7/site/
Windows Install media creator: https://support.microsoft.com/en-us/help/15088/windows-create-installation-media
boco
 
Posts: 1846
Joined: 24.11.2009, 17:00
Location: Germany

Re: WSUS Offline vs MSFT Built-In Windows Update (Conflicts?

Postby wsuuid » 04.05.2017, 05:57

Guess I am trying to get correct picture of using WOU vs WU.

In a new or re-install of Win "x", WOU provides fast updates of key components. (Great work!)

What I am unclear about is if and when WOU should be used (vs the necessarily enabled) MS WU.

Is the correct usage, install new Win, do massive update for all currently missing updates via WOU and then leave WU to do the rest (per user "nag" prefs) EXCEPT in the case of say a new, heavy version of .net or other major "Service Packs"?

What is your recommended sequence and protocol for usage? (Pls forgive if you answered this before.)

Best,
-B
wsuuid
 
Posts: 7
Joined: 23.04.2017, 12:26

Re: WSUS Offline vs MSFT Built-In Windows Update (Conflicts?

Postby boco » 04.05.2017, 16:32

WOU is meant for updating a newly installed (or heavily out-of-date) system to a safe state before it gets online for the first (or next) time. It is also very useful as a method for installing the security-only update packs (and skip the full update rollups) on Windows 7 or 8.1.

Nothing stops you from running it on live systems. You can use WOU, WU, or both. Almost everything WOU offers is also on WU (security-only packs are not on WU). WU has additional updates that are not security-critical.

Note: For an online Windows 10, it is of limited use only (unless you manage to stop the 'unstoppable' Windows Automatic Update).
Microsoft update catalog: http://catalog.update.microsoft.com/v7/site/
Windows Install media creator: https://support.microsoft.com/en-us/help/15088/windows-create-installation-media
boco
 
Posts: 1846
Joined: 24.11.2009, 17:00
Location: Germany


Return to Installation / Updating

Who is online

Users browsing this forum: No registered users and 12 guests

cron