BatchPatch Forums Home › Forums › BatchPatch Support Forum › Win 7 Extended User Agreement
Tagged: Win 7 EUA error 198 offline mode
- This topic has 4 replies, 2 voices, and was last updated 3 years, 1 month ago by doug.
-
AuthorPosts
-
September 28, 2020 at 6:02 am #12518Richard KnightParticipant
Morning,
I was wondering if there were any additional considerations to make for the use of BatchPatch on Win 7 machines now that support has ceased?
I have 3 stand alone systems, 2 running Win 7 and one on Win 10. I have successfully deployed BP on the Win 10 device but am suffering Error 198 – Failed to add scan package service. on both Win 7 devices. (HRESULT 2146762487)
I have read through the various threads on this forum dedicated to that and have had no luck employing any of the suggestions. I have attempted to update the WUA, I’ve added the digital certificate to the trusted store, I did wonder however if the extended support package available from Microsoft was required to update Win 7 machines? Given the wsusscn2 file would contain all patches since Jan 2020, would it just fail to install any patches released after this point?
Any help would be appreciated.
September 28, 2020 at 4:18 pm #12519dougModeratorI wouldn’t be surprised if certificates is one of the methods that Microsoft uses to prevent people who didn’t pay for ESU. I found a wsusscn2.cab from July 2019, and I was able to use it successfully to search for updates on a Windows 7 target. However, when I use the current wsusscn2.cab from Sept 2020, I get the same certificate error that you got.
0x800B0109 -2146762487 CERT_E_UNTRUSTEDROOT A certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider
I think there is a pretty good chance that if/when you pay for ESU, the first thing they do is give you an update that updates your certificate store so that you’re able to continue updating the OS. This is just an educated guess. I can’t say for sure.
September 29, 2020 at 3:29 am #12520Richard KnightParticipantMorning Doug,
Thank you for your response, interesting that you suffered the same issue when attempting to use the current wsusscn2 file. I’m in discussions with our system accreditor regarding the extended support.
Will reply to the thread if I make progress.
Kind regards,
Rich
September 29, 2020 at 4:48 pm #12523dougModeratorThanks, Rich. Please do reply to this thread if/when you have more info. I’m very curious to know if purchasing ESU does the trick.
-Doug
November 9, 2021 at 12:30 pm #13158dougModeratorMore recently we’ve learned of two possible causes for this error. 1: If you are trying to apply updates to an operating system that Microsoft is no longer supporting and delivering updates for. If you have not purchased an Extended Security Update (ESU) package from Microsoft, you might need to do this. 2: You have not installed the most recent servicing stack update (SSU). Try manually applying the most recent SSU for the OS in question, and it’s likely this error will go away.
-
AuthorPosts
- You must be logged in to reply to this topic.