Windows 10 Upgrade in WSUS failed (Unable to Find Resource:) ReportingEvent.Client.167;

Question

Windows 10 Upgrade in WSUS failed (Unable to Find Resource:) ReportingEvent.Client.167;

Silent Sea 6

Hi ,
There are a few Windows 10 PCs ( Ver 10.0.17134.1304 , Ver 10.0.18362.1474 ) need to be upgrade to current Windows 10 verstion 21H1 Ver 10.0.19041.1237
The updates was approved in WSUS already.
The last event reports errors.
(Unable to Find Resource:) ReportingEvent.Client.167*;

The earlier event log was shown
"Download succeeded."
"(Unable to Find Resource:) ReportingEvent.Client.181"

It looks there are a few “(Unable to Find Resource:) ” errors happened in the past a few days, not resolved. However it showed download is completed.

I have check with users computer, it will show the installation progress with percentage, but at last it will be failed with unknown reason. Never succeeded.

Thanks

3 answers

Your answer

Answer 1

Limitless Technology 39,926

Hello SilentSea,

This has been a known issue for some version updates. Please try the next:

From the WSUS server, open IIS manager, and select the server name on the left and open the "MIME" type on the right. Select Add, then introduce the next data:

File name extension: .esd
MIME type: application/octet-stream

Now from one of the affected workstations, do a reboot and try to install the update. It should work straight.

Hope this helps with your query.

--If the reply is helpful, please Upvote and Accept as answer--

Robert Bastarache 6 Reputation points

2022-04-06T13:49:30.603+00:00

This resolved my issue.

Answer 2

Rita Hu -MSFT 9,661

@Silent Sea
Thanks for your posting on Q&A.

All the clients failed to get the feature updates and failed to install the feature updates. Am I right?

The ReportingEvent.Client.167/181 error tips are occurred on the WSUS server. Am I right? Could you mind sharing the error screenshots for reference?

Also, I recommended to run the below command to reste the metadata on the WSUS server first:

Navigate to the wsusutil.exe tool and run the wsusutil.exe reset command. Here is reference picture for you:

Then we could check for updates manually on one of the clients to confirm whether this issue will be resolved.

Please keep us in touch if there are any updates of the case. Looking forward for your feedback.

Have a great day.

Regards,
Rita

If the response is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Silent Sea 6 Reputation points

2021-09-27T06:18:39.757+00:00

Currently, I may not to do that wsusutil.exe reset, i could take long time to complete the verification of downloaded files.
Also for my understanding, server side should be ok, because , not all PCs are failed. there are 2-3 PCs were succeeded during ealier test, so now I have put 20 PCs in the upgrade group of WSUS, for the 2nd part of PCs , there are only another 2 PCs succeeded , but other 18 PCs keep showing error.
It proves no issue on the downloaded image.

Last night, I put one user PC in my office to power on any it show installation in progress till 49%, However after this morning, when I checked it report 0xc1900104 error , it is said Windows will try later, then after restart it is doing the loop to installation till 49%.....

I just checked the 0xc1900104 errors, looks it links to System Reserved Partition . not so sure now. Is that the correct direction?
One article https://answers.microsoft.com/en-us/windows/forum/windows_10-update/windows-update-error-0xc1900104/4b661164-ff6b-4a18-a57a-87300781f08a
[4b661164-ff6b-4a18-a57a-87300781f08a][1]
As far as I know, Windows background upgrade should be able to create MS Reserved Parition automatically ......
thanks for checking

Sean
Rita Hu -MSFT 9,661 Reputation points

2021-09-27T07:38:34.007+00:00
Hello Sean,

Thanks for your feedback.

In fact, there are many reasons which could lead the clients failed to install the feature updates. Please try to open the Event Viewer and follow the below steps to get the A result code and An extend code first(please review this link to know more about A result code and An extend code):

Open Event Viewer and navigate to Windows Logs\Application. Click Find, and then search for winsetupdiag02. Double-click the event that is highlighted.

Here is a related link for your reference:
https://learn.microsoft.com/en-us/windows/deployment/upgrade/windows-error-reporting

Also, it is recommended to follow the below link to quick fixes;
https://learn.microsoft.com/en-us/windows/deployment/upgrade/quick-fixes

Hope the above will be helpful.

Regards,
Rita
Silent Sea 6 Reputation points

2021-09-27T09:02:12.357+00:00

II have checked the event log,
the Event name shows WindowsUpdateFailure3

problem signature looks different. is there any pre-patch need to be installed.

I checked your quick fix list, looks no better solutions, I am going to use Windows Update Troubleshooter to try
Rita Hu -MSFT 9,661 Reputation points

2021-09-27T09:24:11.47+00:00

The windows version of the client is windows 10 1803. Right?(we could open the Run and print the winver commend to review the windows version) Please help to confirm whether the client reported the feature updates as Needed on the WSUS console. In fact, it is recommeded to approve the Needed updates.
Here is reference screenshot for you. Please refer to the below picture to confirm whether the client needed the FU:

Regards,
Rita

Answer 3

Silent Sea 6

during a few testing, I found a solution for this, the version 17134 has to been upgrade to Win10 1909 (18362) first, then it will start another round of upgrade to 20H2 or 21H1. Most version 18362 of Win10 upgrading is going well.
It is not impossible to upgrade to 20H2/21H1 from 1803 version.
Thanks all of your help.

Share via

Windows 10 Upgrade in WSUS failed (Unable to Find Resource:) ReportingEvent.Client.167;

3 answers

Your answer