I think this is a misunderstanding. I specifically said "All Microsoft certificates are up-to-date/same". That means 2011 CA cert is there in the store. When I said "signatures are different" I am talking about signatures on "wsus3setup.cab" on problem 2008 SP2 machine vs "wsus3setup.cab" on a working 2008 R2 machine. I did not mean that the CA certificates are somehow different between the machines - only the signatures of the file that gives the error. But thank you for your time & attention on my insignificant issue!
Sorry for being a nonsesnse but I feel a little rusty...So I ran v12 without uninstalling v11 and I only have choices 2,4,7,9 and what about the wim integration ? Any help is welcome.
@abbodi1406 I found an issue where immediately after installing WU ESU Patcher and setting option [1] Embedded 7 (and rebooting) it won't find Embedded 7 updates. But then changing category to option [2] 2008 R2 it does find those 2008 R2 updates, and then changing back to option [1] Embedded 7 it will then finally find Embedded 7 updates. Seen it a few times now in testing. Note: on W7 clients that find Embedded 7 updates right after installing WU ESU Patcher, the "Check for updates" always fails a few times with error, then eventually completes the check after repeated attempts and finds all Embedded updates. On W7 clients that do not find the updates, "Check for updates" always completes the first time very quickly, does not fail, but doesn't find updates, so maybe Windows Update is not re-scanning correctly after installing WU ESU Patcher and setting category option for the first time?
Clean/Reset DataStore.edb will probably solve the conflict Code: net stop wuauserv 2>nul net stop TrustedInstaller 2>nul del /f /q %SystemRoot%\SoftwareDistribution\DataStore\DataStore.edb 1>nul 2>nul pushd %SystemRoot%\SoftwareDistribution\DataStore\Logs rmdir /s /q . 1>nul 2>nul popd
If you clean/reset DataStore.edb, will it also remove the installed updates info in "View Update History"?
@nicolaasjan see the reply by @abbodi1406 to this post: https://forums.mydigitallife.net/th...dates-eligibility.80606/page-359#post-1779913 And also my reply further down: https://forums.mydigitallife.net/th...dates-eligibility.80606/page-360#post-1780274
Thanks. I don't have this Convenience rollup update KB3125574 installed here. So I can install all Server 2008 R2 updates, including the optional ones (without the "Best Practises Analyser" updates)?
Everything is working fantastic so far. However, I have a question. I noticed this from the most recent post that it doesn't work for Windows Embedded. Is this a technical issue which makes it impossible or a workaround hasn't been created yet? Windows embedded POSReady 7 gets updates until October of 2024 and is based upon Windows 7 SP1 code base. Thanks
You need to do some reading friend! https://forums.mydigitallife.net/th...-extended-security-updates-eligibility.80606/
I'm well read. My problem was in articulating my question. What I was actually asking is it possible to apply POSReady 7 updates on Windows 7 similar to what was previously done for XP. I am presently using V12 which has allowed me to apply 2008 R2 updates on my Win 7 machine. So now with that out of the way, is there a technical problem with creating a version of BypassESU which prevents POSReady 7 updates on Win 7?
oldsh_t was being a bit sarcastic since the last 4 or 5 pages (or more) of posts are about how ESU Bypass has now been modified to install POS updates to Windows 7. EDIT: I need to read more carefully too before posting.