BatchPatch Forums Home › Forums › BatchPatch Support Forum › Batpatch -102: Failed to execute the search. HRESULT: -2145124297
- This topic has 3 replies, 2 voices, and was last updated 5 years, 2 months ago by doug.
-
AuthorPosts
-
November 1, 2018 at 5:28 am #8769P UruParticipant
Hello,
hey everyone. I need some help with batchpatch. I’m getting this -102: Failed to execute the search. HRESULT: -2145124297 while patching workstation. We use windows server 2012 R2 to patch all the workstation. If anyone can help me please. I can provide more info if needed.
Thank you
November 1, 2018 at 10:13 am #9990P UruParticipantSo I fixed my own issue if anyone ever had this error fix is https://github.com/zeffy/wufuc/releases wufuc install it and reboot the target it machine. It should start scanning.
November 1, 2018 at 4:07 pm #9992dougModeratorMicrosoft’s error text for that HRESULT is:
0x80240037 -2145124297 WU_E_NOT_SUPPORTED The invoked functionality is not supported.
This is not a BatchPatch error per se. It is a Windows Update error. While it might be possible for other circumstances to trigger the same error as above, in your case based on the fact that you resolved it by installing the program at the linked github page, it sounds like you are running a version of Windows OS on hardware that is not supported by Microsoft for the OS version that you are running.
Excerpt from the github project that you linked to:
“The release notes for Windows updates KB4012218 and KB4012219 included the following:
‘Enabled detection of processor generation and hardware support when PC tries to scan or download updates through Windows Update.’
These updates marked the implementation of a policy change they announced some time ago, where Microsoft stated that they would not be supporting Windows 7 or 8.1 on next-gen Intel, AMD and Qualcomm processors.
This is essentially a big middle finger to anyone who decides to not “upgrade” to Windows 10, and it is especially unfortunate considering the extended support periods for Windows 7 and 8.1 won’t be ending until January 4, 2020 and January 10, 2023 respectively.
Some people with older Intel and AMD processors are also affected! I’ve received user reports of the following CPUs all being blocked from receiving updates:”
Intel Atom Z530
Intel Atom D525
Intel Core i5-M 560
Intel Core i5-4300M
Intel Core i7-4930K
Intel Pentium B940
AMD FX-6300
AMD FX-8350
AMD Turion 64 Mobile Technology ML-34
The github project that you linked to attempts to enable Windows Update on older versions of Windows running on computers with newer/unsupported processors. The project author may or may not be accurate in his/her assessment that “This is essentially a big middle finger to anyone who decides to not “upgrade” to Windows 10, and it is especially unfortunate considering the extended support periods for Windows 7 and 8.1 won’t be ending until January 4, 2020 and January 10, 2023 respectively.” However, regardless of your opinion about Microsoft’s motives for the change, if you are running a version of Windows on hardware that is not supported for that version, you’re asking for problems. We do not recommend doing this. Additionally, if you are already doing this, we also do not recommend installing such a program as the one in this github project on your computers. It may resolve the issue temporarily or perhaps indefinitely, but installing such a program would of course be done at your own risk, as it may break the OS in some way or cause instability etc.
Microsoft blogged about the changes to hardware support here: https://blogs.windows.com/windowsexperience/2016/01/15/windows-10-embracing-silicon-innovation/
September 19, 2019 at 12:05 am #11942dougModeratorFor all other -102 HRESULT values, please see batchpatch-error-102-failed-to-execute-the-search-hresult-xxxxxxxxxx
-
AuthorPosts
- You must be logged in to reply to this topic.