-102: Failed to execute the search. HRESULT: -2145103860

Note, HRESULT -2145103860 converts to 8024500C.

If you are encountering the aforementioned error then please review this link: Dual Scan Difficulties with Windows 10 and Windows 2016

If after reading through the previous link you are still stuck, you might take a look at the following reddit link, which has an alternate possible solution:

From https://www.reddit.com/r/sysadmin/comments/6k8ayw/possible_fix_for_error_8024500c_on_server_2016/ :

I set up a Server 2016 WSUS server and I’d been running into an issue where, despite everything I’d do (WSUS cleanup, reset, switching to SSL), Server 2016 or Windows 10 v1607 clients would never pull updates from the WSUS machine, always showing error 8024500c. Server 2012 R2 machines worked perfectly fine.

“You’re getting errors because you’re using conflicting policies.

I see this stuff almost every time someone complains about WSUS clients having errors, when you use WSUS, do not configure any Microsoft Update policies. You literally control what devices get using WSUS, that’s the point of the service…

Defer features, do not include drivers etc, are all policies that should not be used when your clients speak to a WSUS server.

If you actually want to prevent your users from clicking the ‘Check online at Microsoft for updates’ then configure the ‘Turn off access to all Windows Update features’ policy found in ‘Administrative Templates > System > Internet Communication Management > Internet Communication Settings’. Windows Store updates still work using that policy.”