[EX-100 - v1.9.2.] [RS3 Build 16299.15] Windows Updates not installed?

I removed Windows Update because I want to install updates with WSUS offline update (<- this is a link). It seems, the offline installer installs several updates successfully, because it shows succsess-messages. BUT they are not shown. Does anyone has an idea why?

When I use WSUS Offline Update on an unreduced RS3 it installs the cumulative update KB4043961 successfully an it's also displayed. On my reduced installation it fails with a DISM error (anyway it says "success" at the end), regardless of having wuauserv.exe included or not.

But in a reduced version with wuauserv included, windows Update doesn't find KB4043961 but the windows malicious software removing tool from october.

That leads me to the question: Does Windows Update realise that the cumulativ update affects components that are not there so that it is not offered?

And I have an other question: What is the best way to get important security updates but nothing else, especially no feature updates?

Maybe my problem has to do with the following:

When I make a doubleklick on a MSU-update file in my reduced Windows, this error massage appears:



It says: "Windows can't open this file type (.msu)"

Question: Which component is needed to open MSU-files? What do I have to keep? (It's not Windows Update, I tested that already.)

My wccf: Link

Hello,

The *.msu files support is removed if you remove "Services - Windows Update" ... and it seems you removed it.

Could you please try without removing it, and let me know the result.

Thanks

I did this already with v1.9.2 without success. It wasn't possible to open an msu-file. But I will test it again with v1.9.3 now.

But even if it would work: Isn't it better to keep everything you need for a manual update even if you remove "Windows Update"? Or as a comprimise, to have an option to keep manual update?

Yes, I think I will propose such option ("keep a manual update support") in the future.

There are maybe also more components involved to keep this working, such as :
- "Services - Background Intelligent Transfer Service"
- "Services - COM+ Event System Service"
- "Services - COM+ System Application Service"
- "Services - System Event Notification Service"
- "Services - Update Orchestrator Service"
- "Services - Windows Updates Service"

My former test with v1.9.2 kept all the services you mentioned. I'm not sure if I also activated "Protect Windows Update" but I think so.

In my Windows with removed Windows Update WUSA.EXE is missing. But even if I copy it from an unchanged Windows into the reduced Windows it's not possible to open an msu-file. Could it be a wrong registry entry?

Hmm, with v1.9.3 it's possible to open a msu-file. The ony change I made to my above wccf is to keep windows update service. But wusa.exe crashes when I try to install KB4043961 (it just stops without installation progress and it's not possible to close it withoiut taskmanager):






And the programm "WSUS offline update" (link in the first post) has still the same DISM error:

This is what sfc /scannow gives me: Link

Summary:
Operation: Detect only 
Operation result: 0x0
Last Successful Step: CSI store detection completes.
Total Detected Corruption: 28
CBS Manifest Corruption: 0
CBS Metadata Corruption: 28
CSI Manifest Corruption: 0
CSI Metadata Corruption: 0
CSI Payload Corruption: 0
Total Repaired Corruption: 0
CBS Manifest Repaired: 0
CSI Manifest Repaired: 0
CSI Payload Repaired: 0
CSI Store Metadata refreshed: True

Total Operation Time: 53 seconds.

2017-11-08 20:37:59, Info                  CBS    CheckSur: hrStatus: 0x0 [S_OK], download Result: 0x0 [S_OK]
2017-11-08 20:37:59, Info                  CBS    Count of times corruption detected: 0
2017-11-08 20:37:59, Info                  CBS    Seconds between initial corruption detections: -1
2017-11-08 20:37:59, Info                  CBS    Seconds between corruption and repair: -1
2017-11-08 20:37:59, Info                  CBS    Reboot mark cleared
2017-11-08 20:37:59, Info                  CBS    Winlogon: Simplifying Winlogon CreateSession notifications
2017-11-08 20:37:59, Info                  CBS    Winlogon: Deregistering for CreateSession notifications
2017-11-08 20:37:59, Info                  CBS    Exec: Processing complete, session(Corruption Detecting): 30628040_4114484751 [HRESULT = 0x00000000 - S_OK]
2017-11-08 20:37:59, Info                  CBS    Session: 30628040_4114484751 finalized. Reboot required: no [HRESULT = 0x00000000 - S_OK]
2017-11-08 20:38:00, Info                  CBS    Session: 30628041_365146881 initialized by client DISM Package Manager Provider, external staging directory: (null), external registry directory: (null
2017-11-08 20:38:41, Info                  CBS    TiWorker: Client requests SFP repair object.
2017-11-08 20:38:41, Info                  CSI    0000000b@2017/11/8:19:38:41.444 WcpInitialize (wcp.dll version 0.0.0.6) called (stack @0x649081ed @0x6fe97c49 @0x6fe97d4f @0x12cb974 @0x12cd122 @0x778305e4)
2017-11-08 20:38:42, Info                  CSI    0000000c [SR] Verifying 100 components
2017-11-08 20:38:42, Info                  CSI    0000000d [SR] Beginning Verify and Repair transaction
2017-11-08 20:38:43, Info                  CSI    0000000e [SR] Cannot repair member file [l:12]'msdtckrm.dll' of Microsoft-Windows-COM-DTC-Runtime, version 10.0.16299.15, arch x86, nonSxS, pkt {l:8 b:31bf3856ad364e35} in the store, file is missing
2017-11-08 20:38:43, Error                 CSI    0000000f (F) STATUS_OBJECT_NAME_NOT_FOUND #205135# from Windows::Rtl::SystemImplementation::DirectFileSystemProvider::SysCreateFile(flags = 0, handle = {provider=NULL, handle=0, name= ("null")}, da = (SYNCHRONIZE|FILE_READ_ATTRIBUTES), oa = @0xabd82c->OBJECT_ATTRIBUTES {s:24; rd:NULL; on:[104]'\SystemRoot\WinSxS\x86_microsoft-windows-deployment_31bf3856ad364e35_10.0.16299.15_none_c2bc8739a6150417'; a:(OBJ_CASE_INSENSITIVE)}, iosb = @0xabd924, as = (null), fa = 0, sa = (FILE_SHARE_READ|FILE_SHARE_WRITE|FILE_SHARE_DELETE), cd = FILE_OPEN, co = (FILE_DIRECTORY_FILE|FILE_SYNCHRONOUS_IO_NONALERT|0x00004000), eab = NULL, eal = 0, disp = Invalid)
[gle=0xd0000034]
2017-11-08 20:38:43, Error                 CSI    00000010@2017/11/8:19:38:43.147 (F) onecore\base\wcp\sil\merged\ntu\ntsystem.cpp(2938): Error STATUS_OBJECT_NAME_NOT_FOUND originated in function Windows::Rtl::SystemImplementation::DirectFileSystemProvider::SysCreateFile expression: (null)
[gle=0x80004005]
2017-11-08 20:38:43, Info                  CBS    Added C:\Windows\Logs\CBS\CBS.log to WER report.
2017-11-08 20:38:43, Info                  CBS    Could not get active session for current session file logging [HRESULT = 0x80004003 - E_POINTER]
2017-11-08 20:38:43, Info                  CBS    Not able to add pending.xml to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2017-11-08 20:38:43, Info                  CBS    Not able to add pending.xml.bad to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2017-11-08 20:38:43, Info                  CBS    Not able to add poqexec.log to Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2017-11-08 20:38:43, Info                  CBS    Failed to submit the Windows Error Report. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2017-11-08 20:38:43, Error                 CSI    00000011 (F) STATUS_OBJECT_NAME_NOT_FOUND #205134# from Windows::Rtl::SystemImplementation::CDirectory::OpenExistingDirectory(...)[gle=0xd0000034]
2017-11-08 20:38:43, Error                 CSI    00000012 (F) STATUS_OBJECT_NAME_NOT_FOUND #205133# from Windows::Rtl::SystemImplementation::CDirectory_IRtlDirectoryTearoff::OpenExistingDirectory(flags = 0, da = (SYNCHRONIZE), oa = @0xabdad4->SIL_OBJECT_ATTRIBUTES {s:20; on:"x86_microsoft-windows-deployment_31bf3856ad364e35_10.0.16299.15_none_c2bc8739a6150417"; a:(OBJ_CASE_INSENSITIVE)}, sa = (FILE_SHARE_READ|FILE_SHARE_WRITE|FILE_SHARE_DELETE), oo = (FILE_DIRECTORY_FILE|FILE_SYNCHRONOUS_IO_NONALERT|FILE_OPEN_FOR_BACKUP_INTENT), dir = NULL, disp = Invalid)
[gle=0xd0000034]

"Update Orchestrator Service" is needed to prevent WUSA.EXE from crashing. I think you can't call it a bug but it might be a useful information for a preset "Protect manual update".

But still KB4043961 won't be installed (in an unchanged RS3 Pro it works). Is it possible that this happens because KB4043961 is a cumulative update? Some parts may affect removed components.

Yes, interesting information, which confirms my thoughts .... thank you very much for this.

The fact that the update is not installed should be linked to the fact that some components are removed ... but I'm also working on this point to bypass these troubles