none
error 0x80070002 and/or 0x80070020 on several Server 2008 R2 with update KB4467107 failing and preventing newer updates to succeed RRS feed

  • Question

  • On almost all our Servers running WIndows Server 2008 R2 we have an issue with updating since kb4467107

    https://support.microsoft.com/en-gb/help/4467107/windows-7-update-kb4467107

    This failing update is preventing a lot of newer updates to fail.

    Tried the following options but nothing solves it;

    - clean boot install
    - manual install (also unpacked manual dism install)
    - wuagent cleanup

    - sfc scan

    - chkdsk scan

    - dism cleanup
    - system readiness installation
    - installing latest service stack (kb4516655)

    If there is anyone who has more ideas to help. It is a wsus environment and there are a few servers that do not have the issue but also not having that patch installed but others do.

    Another typical thing is that the few servers that do not have these issues have a windows update agent version 7.6.7601.24436 (2019/04) while the failing servers have version 7.6.7601.24085 (2018/03).

    Checking the servers online gets other updates but then those also fail again. Below some of the errors from several logfiles.

    2019-10-01 09:54:14, Error                 CBS    Failed to pre- stage package: Package_for_RollupFix~31bf3856ad364e35~amd64~~7601.24241.1.6 [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
    2019-10-01 09:54:14, Info                  CBS    Perf: Stage chain complete.
    2019-10-01 09:54:14, Info                  CBS    Failed to stage execution chain. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
    2019-10-01 09:54:14, Error                 CBS    Failed to process single phase execution. [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]


    2019-10-01 11:30:14:594
    4052 1148
    Handler FATAL: CBS called Error with 0x80070002, 
    2019-10-01 11:35:22:516
    976 3dc
    Agent WARNING: WU client fails CClientCallRecorder::RemoveService with error 0x80248014
    2019-10-01 11:35:22:518
    1164 16a8
    COMAPI WARNING: ISusInternal::RemoveService failed, hr=80248014

    2019-10-02 10:12:54:573
    976 3c0
    Report REPORT EVENT: {D62AD5E5-1420-4F1B-8FF4-721F8F4314D7}
    2019-10-02 10:07:43:067+0200 1
    182 101
    {1F74C5CC-0F12-40E5-A947-81516A1CCE12}  200 80070002  AutomaticUpdates Failure
    Content Install Installation Failure: Windows failed to install the following update with error 0x80070002: 2018-11 Security Monthly Quality Rollup for Windows Server 2008 R2 for x64-based Systems (KB4467107).

    2019-10-02 13:26:35:268
    976 10c
    Report REPORT EVENT: {1D8D980C-EFB2-4046-A314-4232F6B256BE}
    2019-10-02 13:23:52:032+0200 1
    182 101
    {82BF6959-36FF-4D3E-A909-B1CF9FFC9880}  201 80070002  AutomaticUpdates Failure
    Content Install Installation Failure: Windows failed to install the following update with error 0x80070002: 2019-08 Security Monthly Quality Rollup for Windows Server 2008 R2 for x64-based Systems (KB4512506).

    2019-10-02 19:40:46:024
    968 11c4
    PT WARNING: Exceeded max server round trips: 0x80244010

    2019-10-02 19:40:46:024
    968 11c4
    Agent WARNING: WU client failed Searching for update with error 0x80244010

    2019-10-03 04:05:19:515
    976 1a70
    Misc Validating signature for C:\Windows\SoftwareDistribution\ScanFile\bd8fb065-c575-451c-86a0-7fc7f2c0f0bc\Source.cab with dwProvFlags 0x00000080:
    2019-10-03 04:09:22:766
    976 11f0
    Agent WARNING: Failed to evaluate Installable rule, updateId = {C646D973-56DD-480C-83CD-4CFE066B2FEA}.201, hr = 80070663
    2019-10-03 04:09:38:876
    976 11f0
    PT +++++++++++  PT: Synchronizing extended update info  +++++++++++
    2019-10-03 04:09:38:876
    976 11f0
    PT   + Offline serviceId = {BD8FB065-C575-451C-86A0-7FC7F2C0F0BC}
    2019-10-03 04:10:18:048
    976 11f0
    OfflSnc WARNING: Failed to add file to the FileLocationList with 0x80240013
    2019-10-03 04:10:18:517
    976 11f0
    Agent Bundle contains no deployed children and thus is invalid.
    2019-10-03 04:10:18:517
    976 11f0
    Agent Update {7E7049E7-B870-4C87-AF60-BC5A0BACE002}.201 is not a valid bundle. Not returning it.
    2019-10-03 04:10:18:517
    976 11f0
    Agent Bundle contains no deployed children and thus is invalid.
    2019-10-03 04:10:18:517
    976 11f0
    Agent Update {393D97F5-B447-43C5-9E0C-B6707C8D29CE}.201 is not a valid bundle. Not returning it.


    2019-10-03 09:36:21, Error                 DISM   DISM Package Manager: PID=5888 Failed finalizing changes. - CDISMPackageManager::Internal_Finalize(hr:0x80070002)
    2019-10-03 09:36:21, Error                 DISM   DISM Package Manager: PID=5888 Failed processing package changes - CDISMPackageManager::ProcessChanges(hr:0x80070002)
    2019-10-03 09:36:21, Info                  DISM   DISM Package Manager: PID=5888 Loaded servicing stack for online use only. - CDISMPackageManager::RefreshInstanceAndLock
    2019-10-03 09:36:21, Error                 DISM   DISM Package Manager: PID=5888 Failed while processing command add-package. - CPackageManagerCLIHandler::ExecuteCmdLine(hr:0x80070002)
    2019-10-03 09:36:21, Info                  DISM   DISM Package Manager: PID=5888 Further logs for online package and feature related operations can be found at %WINDIR%\logs\CBS\cbs.log - CPackageManagerCLIHandler::ExecuteCmdLine
    2019-10-03 09:36:21, Error                 DISM   DISM.EXE: DISM Package Manager processed the command line but failed. HRESULT=80070002


    2019-10-03 09:44:48, Error                 DISM   DISM Package Manager: PID=6220 Failed finalizing changes. - CDISMPackageManager::Internal_Finalize(hr:0x80070002)
    2019-10-03 09:44:48, Error                 DISM   DISM Package Manager: PID=6220 Failed processing package changes - CDISMPackageManager::ProcessChanges(hr:0x80070002)
    2019-10-03 09:44:48, Info                  DISM   DISM Package Manager: PID=6220 Loaded servicing stack for online use only. - CDISMPackageManager::RefreshInstanceAndLock
    2019-10-03 09:44:48, Error                 DISM   DISM Package Manager: PID=6220 Failed while processing command add-package. - CPackageManagerCLIHandler::ExecuteCmdLine(hr:0x80070002)
    2019-10-03 09:44:48, Info                  DISM   DISM Package Manager: PID=6220 Further logs for online package and feature related operations can be found at %WINDIR%\logs\CBS\cbs.log - CPackageManagerCLIHandler::ExecuteCmdLine
    2019-10-03 09:44:48, Error                 DISM   DISM.EXE: DISM Package Manager processed the command line but failed. HRESULT=80070002

    2019-10-03 09:44:48, Error                 CBS    Failed to perform operation.  [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]


    • Edited by Erwin_Jong Thursday, October 3, 2019 8:51 AM extra info
    Thursday, October 3, 2019 8:41 AM

All replies

  • Hi Erwin,
      

    Does the latest SSU (kb4516655) be successfully installed on these WUA clients in the version 2018/03?
    If it does not install successfully, I suggest you consider installing the following updates first:
      

    After completing the installation of the above update, please try to install the monthly cumulative update for the client in question.
    Reply back with the results would be happy to help.
       

    Regards,
    Yic

    Please remember to mark as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Friday, October 4, 2019 1:40 AM
  • Hi,
     

    Any update is welcome here.
    If the issue is resolved, share your solution or find the helpful response "Mark as Answer" to help other community members find the answer.
     

    Thank you for your cooperation, as always.
     

    Regards,
    Yic

    Please remember to mark as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Monday, October 7, 2019 2:11 AM
  • Hello,

    kb4516655 was installed succesfully but didn't fix anything. I will install both updates (KB4490628 and KB4474419) and will report back the status.

    Thanks

    Monday, October 7, 2019 10:01 AM
  • both updates mentioned were already installed for the KB4474419 version 3 (latest one)

    I queried the server with all updates installed;

    KB2386667
    KB2425227
    KB2484033
    KB2488113
    KB2492386
    KB2503665
    KB2505438
    KB2506014
    KB2506212
    KB2506928
    KB2507618
    KB2508272
    KB2509553
    KB2510531
    KB2511250
    KB2511455
    KB2515325
    KB2518869
    KB2522422
    KB2529073
    KB2533552
    KB2536275
    KB2536276
    KB2539635
    KB2541014
    KB2544893
    KB2545698
    KB2547666
    KB2552343
    KB2556532
    KB2560656
    KB2562937
    KB2563227
    KB2563894
    KB2564958
    KB2567053
    KB2567680
    KB2570791
    KB2570947
    KB2572077
    KB2574819
    KB2584146
    KB2585542
    KB2586448
    KB2588516
    KB2592687
    KB2603229
    KB2604115
    KB2607047
    KB2607576
    KB2608658
    KB2616676
    KB2617657
    KB2618444
    KB2618451
    KB2620704
    KB2620712
    KB2621440
    KB2631813
    KB2633873
    KB2633952
    KB2636573
    KB2639308
    KB2639417
    KB2640148
    KB2641653
    KB2641690
    KB2643719
    KB2644615
    KB2645640
    KB2647516
    KB2647518
    KB2647753
    KB2653956
    KB2654428
    KB2655992
    KB2656356
    KB2656373
    KB2658846
    KB2659262
    KB2660075
    KB2660465
    KB2661254
    KB2665364
    KB2667402
    KB2670838
    KB2675157
    KB2675625
    KB2676562
    KB2677070
    KB2679255
    KB2685811
    KB2685813
    KB2685939
    KB2686831
    KB2688338
    KB2690533
    KB2691442
    KB2695962
    KB2698365
    KB2699779
    KB2699988
    KB2705219
    KB2706045
    KB2709630
    KB2709715
    KB2709981
    KB2712808
    KB2718523
    KB2718704
    KB2719033
    KB2719857
    KB2719985
    KB2722913
    KB2724197
    KB2726535
    KB2729094
    KB2729452
    KB2731771
    KB2731847
    KB2732059
    KB2735855
    KB2736233
    KB2736422
    KB2739159
    KB2741355
    KB2742599
    KB2743555
    KB2744842
    KB2749655
    KB2750841
    KB2753842
    KB2756822
    KB2757638
    KB2758857
    KB2761217
    KB2761226
    KB2761465
    KB2762895
    KB2763523
    KB2765809
    KB2769369
    KB2770660
    KB2778344
    KB2778930
    KB2779030
    KB2779562
    KB2785220
    KB2786081
    KB2786400
    KB2789645
    KB2790113
    KB2790655
    KB2790978
    KB2791765
    KB2798162
    KB2799494
    KB2800095
    KB2804579
    KB2807986
    KB2808679
    KB2809289
    KB2813170
    KB2813347
    KB2813430
    KB2820197
    KB2820331
    KB2829361
    KB2829530
    KB2830290
    KB2830477
    KB2832414
    KB2833946
    KB2834140
    KB2834886
    KB2835361
    KB2836942
    KB2836943
    KB2838727
    KB2839894
    KB2840149
    KB2840631
    KB2841134
    KB2843630
    KB2844286
    KB2845690
    KB2846071
    KB2847311
    KB2849470
    KB2849696
    KB2849697
    KB2850851
    KB2852386
    KB2853952
    KB2855844
    KB2857650
    KB2861191
    KB2861698
    KB2861855
    KB2862152
    KB2862330
    KB2862335
    KB2862772
    KB2862966
    KB2862973
    KB2863058
    KB2863240
    KB2864058
    KB2864202
    KB2868038
    KB2868116
    KB2868623
    KB2868626
    KB2868725
    KB2871997
    KB2872339
    KB2875783
    KB2876284
    KB2876331
    KB2882822
    KB2884256
    KB2887069
    KB2888049
    KB2891804
    KB2892074
    KB2893294
    KB2893519
    KB2893984
    KB2894844
    KB2898785
    KB2898857
    KB2900986
    KB2901112
    KB2904266
    KB2908783
    KB2909210
    KB2909921
    KB2911501
    KB2912390
    KB2913152
    KB2913431
    KB2913602
    KB2913751
    KB2916036
    KB2918614
    KB2919469
    KB2922229
    KB2923545
    KB2925418
    KB2926765
    KB2928562
    KB2929733
    KB2929755
    KB2930275
    KB2931356
    KB2936068
    KB2937610
    KB2939576
    KB2943357
    KB2957189
    KB2957503
    KB2957509
    KB2957689
    KB2961072
    KB2962872
    KB2966583
    KB2968294
    KB2970228
    KB2972100
    KB2972211
    KB2973112
    KB2973201
    KB2973337
    KB2973351
    KB2976897
    KB2977292
    KB2977629
    KB2977728
    KB2978092
    KB2978120
    KB2978668
    KB2979570
    KB2980245
    KB2982378
    KB2984972
    KB2984981
    KB2985461
    KB2987107
    KB2991963
    KB2992611
    KB2993651
    KB2993958
    KB2994023
    KB2998527
    KB2999226
    KB3000061
    KB3000483
    KB3000869
    KB3000988
    KB3002885
    KB3003057
    KB3003743
    KB3004361
    KB3004375
    KB3004394
    KB3005607
    KB3006137
    KB3006226
    KB3006625
    KB3008627
    KB3008923
    KB3010788
    KB3011780
    KB3012176
    KB3013126
    KB3013410
    KB3014029
    KB3014406
    KB3018238
    KB3020338
    KB3020369
    KB3020370
    KB3020388
    KB3021674
    KB3022777
    KB3023215
    KB3023266
    KB3030377
    KB3031432
    KB3032655
    KB3033889
    KB3033929
    KB3035126
    KB3035132
    KB3037574
    KB3040272
    KB3042058
    KB3042553
    KB3045685
    KB3046017
    KB3046269
    KB3054205
    KB3054476
    KB3055642
    KB3059317
    KB3060716
    KB3061518
    KB3068457
    KB3068708
    KB3069392
    KB3071756
    KB3072305
    KB3072595
    KB3072630
    KB3072633
    KB3074543
    KB3075226
    KB3075249
    KB3076895
    KB3077715
    KB3078601
    KB3078667
    KB3080079
    KB3080149
    KB3080446
    KB3081320
    KB3084135
    KB3086255
    KB3087039
    KB3092601
    KB3092627
    KB3097877
    KB3097966
    KB3097989
    KB3100773
    KB3101246
    KB3101722
    KB3101746
    KB3102429
    KB3102810
    KB3104002
    KB3107998
    KB3108371
    KB3108381
    KB3108664
    KB3108670
    KB3109094
    KB3109103
    KB3109560
    KB3110329
    KB3112343
    KB3115858
    KB3118401
    KB3121255
    KB3122648
    KB3123479
    KB3124275
    KB3126587
    KB3127220
    KB3133043
    KB3133977
    KB3135983
    KB3137061
    KB3138378
    KB3138612
    KB3138901
    KB3139398
    KB3139914
    KB3139940
    KB3140245
    KB3142024
    KB3142042
    KB3145739
    KB3146706
    KB3146963
    KB3147071
    KB3149090
    KB3156016
    KB3156017
    KB3156019
    KB3159398
    KB3161561
    KB3161949
    KB3161958
    KB3163245
    KB3164033
    KB3164035
    KB3168965
    KB3170455
    KB3172605
    KB3175024
    KB3177186
    KB3177467
    KB3177723
    KB3178034
    KB3179573
    KB3181988
    KB3184122
    KB3185911
    KB3188730
    KB3188740
    KB3192321
    KB3192391
    KB3197867
    KB3205394
    KB3210131
    KB3212642
    KB4012212
    KB4014504
    KB4014573
    KB4014579
    KB4015546
    KB4019990
    KB4020322
    KB4025337
    KB4034679
    KB4038779
    KB4040966
    KB4040980
    KB4041678
    KB4048960
    KB4049068
    KB4051956
    KB4054176
    KB4054521
    KB4054998
    KB4056897
    KB4092946
    KB4095874
    KB4099950
    KB4130978
    KB4284826
    KB4339284
    KB4343205
    KB4343899
    KB4344152
    KB4344177
    KB4457044
    KB4457055
    KB4457145
    KB4457426
    KB4459934
    KB4462915
    KB4466536
    KB4467106
    KB4468323
    KB4470600
    KB4471328
    KB4474419
    KB4480063
    KB4480085
    KB4480960
    KB4480965
    KB4483187
    KB4483458
    KB4483483
    KB4486459
    KB4486474
    KB4486564
    KB4488662
    KB4489873
    KB4489885
    KB4490128
    KB4490628
    KB4493435
    KB4493448
    KB4495606
    KB4495612
    KB4498206
    KB4499175
    KB4501226
    KB4503259
    KB4503269
    KB4506976
    KB4507004
    KB4507434
    KB4507456
    KB4507704
    KB4511872
    KB4512486
    KB4516655
    KB958488
    KB976902
    KB977236
    KB977238
    KB977239
    KB981111
    KB981390
    KB981391
    KB981392
    KB982018

    Monday, October 7, 2019 10:22 AM
  • i added the windowsupdate.log that was recreated after restoring to an old snapshot but after the System Update Readiness Tool for Windows Server 2008 x64 Edition (KB947821) [October 2014]

    Error Code 80070002 is reported which kept coming back in previous attempts.

    That error should mean that some file would not be found which is also

    0x80070002 ERROR_FILE_NOT_FOUND The system cannot find the file specified.

    CBS called Error with 0x80070002

    appareantly it has something to do with CBS but the system readiness does not report this in the checksur.log

    i only see some errors in CBS.log of some packages not found.  log file is quite big (211 MB) but also rapidly recreated and filled again after trying an update.

    This one was the lastest but i have seen more in older CBS logging.

    target: Installed, status: 0x80070002, failure source: Stage, failure details: "(null)", client id: WindowsUpdateAgent, initiated offline: False, execution sequence: 1284, first merged sequence: 1284
    2019-10-07 21:49:22, Info                  CBS    SQM: stage time performance datapoint is invalid. [HRESULT = 0x80070490 - ERROR_NOT_FOUND]
    2019-10-07 21:49:22, Info                  CBS    SQM: execute time performance datapoint is invalid. [HRESULT = 0x80070490 - ERROR_NOT_FOUND]
    2019-10-07 21:49:22, Info                  CBS    SQM: Failed to initialize Win SAT assessment. [HRESULT = 0x80040154 - Unknown Error]
    2019-10-07 21:49:22, Info                  CBS    SQM: average disk throughput datapoint is invalid [HRESULT = 0x80040154 - Unknown Error]
    2019-10-07 21:49:22, Info                  CBS    SQM: Upload requested for report: PackageChangeEnd_Package_for_RollupFix~31bf3856ad364e35~amd64~~7601.24289.1.11, session id: 142862, sample type: Standard
    2019-10-07 21:49:22, Info                  CBS    SQM: Ignoring upload request because the sample type is not enabled: Standard
    2019-10-07 21:49:22, Info                  CBS    Enabling LKG boot option
    2019-10-07 21:49:22, Info                  CBS    Restored system sleep block state: 0x80000000
    2019-10-07 21:49:22, Info                  CBS    Exec: Processing complete.  Session: 30768456_399530705, Package: Package_for_RollupFix~31bf3856ad364e35~amd64~~7601.24289.1.11 [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]

    2019-10-07 21:49:22, Info                  CBS    Exec: Processing complete.  Session: 30768456_399530705, Package: Package_for_RollupFix~31bf3856ad364e35~amd64~~7601.24289.1.11 [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]

    2019-10-07 21:49:34, Info                  CBS    Failed to get session package state for package: Package_126_for_KB3000483~31bf3856ad364e35~amd64~~6.1.1.5 [HRESULT = 0x80070490 - ERROR_NOT_FOUND]


    Monday, October 7, 2019 7:55 PM
  • Hi,
      

    Please consider downloading the standalone installation package for KB4467107 and checking if the installation can be completed on these problematic clients.
      

    If you are unable to complete the installation, consider the method mentioned in this article to download the latest version of the Windows Update Agent: "How to update the Windows Update Agent to the latest version".
      

    Regards,
    Yic

    Please remember to mark as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Tuesday, October 8, 2019 2:56 AM
  • Both were already tried. KB4467107 is a problem update (error 80070002) on all our 2008 R2 servers and installing the Windows Update agent works but does not bring the version of the agent higher then it already is (7.6.7601.24085 , 14-03-2018)

    we have a few 2008R2 servers that have no issue and do have a newer version then this so that might be a cause but how to get the newer version ?

    Any more idea's ?

    What i still haven't figured it out why i get other updates if i don't use Wsus but Microsoft Online but then i end up with the same kind of failures so it might be all related to the wu agent but where to find the newer wu agent 7.6.7601.24436 (2019/04) then ?

    Tuesday, October 8, 2019 7:41 AM
  • Hi Erwin,
      

    Provide some of my current findings:
       

    1. I tried to test on a 2008 R2 client with a WUA version of 7.6.7600.23806. With KB4490628 and KB4474419 installed, KB4467107 was successfully installed, and the WUA version was changed to 7.6.7600.24085.
    2. Continue to install KB4493472 (2019-04 Monthly Rollup). After successful installation, the version of WUA has not changed, it is still 7.6.7600.24085.
    3. Continue to install KB4519976 (2019-10 Monthly Rollup). After successful installation, the WUA version is changed to 7.6.7601.24436.
        

    In summary, I think the older WUA will not affect the installation of KB4467107. And after installing the monthly rollup, the WUA will also be updated.
      

    Going back to our thread, I am currently experiencing 0x80070002. I think it is very likely to be an operating system problem. Since you have already mentioned trying to use dism to fix it, is this process smooth?
       

    Regards,
    Yic

    Please remember to mark as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Wednesday, October 9, 2019 6:24 AM
  • Ok, thanks you for checking that. Yes, all checks seem fine, there are a few things in DISM.log that might mean something.

    I will see if i can find something about that. since the error is something that cannot be found maybe this servicingstack not found has something to do with it.

    2019-10-09 08:37:51, Warning               DISM   DISM Provider Store: PID=4788 Failed to Load the provider: C:\Users\Admin-Account\AppData\Local\Temp\6\7140D20E-FD9A-4CEB-BABA-F7BBD2653EF2\PEProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)

    2019-10-09 08:37:51, Info                  CSI    00000001 Shim considered [l:256{128}]"\??\C:\Windows\Servicing\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.24516_none_6810bdd8f70626d9\pkgmgr.exe" : got STATUS_OBJECT_PATH_NOT_FOUND

    2019-10-09 08:37:51, Info                  CSI    00000002 Shim considered [l:250{125}]"\??\C:\Windows\WinSxS\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.24516_none_6810bdd8f70626d9\pkgmgr.exe" : got STATUS_SUCCESS

    Wednesday, October 9, 2019 7:15 AM
  • Hi Erwin,
      

    Thank you for your reply and look forward to your more progress.
    At the same time, I am continuing to research, and any progress will be made immediately.
       

    Regards,
    Yic

    Please remember to mark as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Friday, October 11, 2019 6:24 AM
  • Hello Yic,

    thanks for helping , so far i have not gotten any further and all default options i have tried already.

    i am almost done trying since i have no lead where to look next. if someone has idea's i would appreciate all the help.

    it will take a bit too long before we can replace all our Server 2008 R2 servers so it would be great to get this fixed.

    Regards, Erwin

    Friday, October 11, 2019 8:08 PM
  • Hi Everyone,
       

    In order to facilitate understanding, the following is the current progress, for your reference:
       

    • Issue Symptom
      Some Windows Server 2008 R2 client installation update kb4467107 (November 13, 2018 - Monthly Rollup) failed with installation error code 0x80070002.
          
    • Possible CauseThe operating system is down, the update component is missing, or the file is missing.
         
    • Troubleshooting Steps so far
      The troubleshooting steps that have been taken:
      (1) OS: Clean boot / SFC scan / chkdsk scan / DISM cleanup / system readiness installation
      (2) Update installation: KB4516655 / KB4490628 / KB4474419(v3)
      (3) An attempt was made to install independently using an update package but was unsuccessful.
      (4) It has been tested to rule out the possible impact of the WUA version on this.
      (5)During the DISM check, the following error was obtained: 0x8007007e / got STATUS_OBJECT_PATH_NOT_FOUND
         
    Hope this helps everyone continue to analyze this thread.
    thank you very much!   


    Regards,
    Yic

    Please remember to mark as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Monday, October 14, 2019 6:16 AM
  • Yes, this sums it up quite fine. Issue symptom is perhaps more then some. From about 30 2008R2 servers there are more then 20 which have update problems.

    Since we have a server that had issues with updates in the past and that server now does not have issues i have the feeling there is some update that has made made the old one (kb4467107) obsolete, only question is how to find out who.

    Monday, October 14, 2019 6:38 AM
  • Dears,

    I was fighting with the same issue since several months... today, I was able to install the update with another attempt: I booted the computer in Diagnostic Mode and selected multiple services. For sure, these were needed:

    Background Intelligent Transfer Service
    COM+ Event System
    DCOM Server Process Launcher
    Remote Procedure Call (RPC)
    RPC Endpoint Mapper

    Maybe there are some else services required, as I enabled according to my best assumption (leaving disabled all the services not really needed like Remote Management). After that, the Update was able to install... as I made no Snapshot of the VM, I can't exactly determine, which service causes the fail... hope this helps further!

    Best regards

    Friday, November 15, 2019 10:48 AM
  • Hello,

    Thank you for sharing this !!

    i will see to test this also and report back the outcome. Enjoy your weekend !

    Best Regards

    Friday, November 15, 2019 1:52 PM
  • unfortunately this didn't help for me. Installing the update in diagnostic mode gives me an "The update is not applicable to your computer" .

    It does indicate my feeling about that the system might not need this update (2018-11 Security Monthly Quality Rollup for Windows Server 2008 R2 for x64-based Systems (KB4467107)) since we have some servers without issues that do not have this update pending.

    I did get temporary new updates (see last picture) but then afterwards i got the three updates i had when i began.

    Tuesday, November 19, 2019 11:26 AM
  • I now also see that another server with the same kind of issues (this one gives the error

    0x80070020        STIERR_SHARING_VIOLATION)

    but this one has the update 2018-10 Security Monthly Quality Rollup for Windows Server 2008 R2 for x64-base systems (KB4462923)

    Strangely it installed succesfully (starting with 13 updates) and after reboot there were 12 2019 updates which failed to instal and then there were 13 available updates again.

    It seems somehow as if this points a bit more to the wsus environment where it does not get registered on the client or the server that an update is done or not needed but how to find out which next step to take ?

    Friday, November 22, 2019 9:56 AM