WSC4 Posted November 10, 2023 Posted November 10, 2023 Thank you AstroSkipper. Those "Could Not Find C:\WINDOWS\System32\Dllcache\wuaueng.dll" errors could be a bug in the script if the agent was already installed. I have looked at system32 and the 7.6.7600.256. Windows Update Agent,. wuaueng.dll, was updated mid 2021. I cannot remember doing this manually. http://download.windowsupdate.com/windowsupdate/redist/standalone/7.6.7600.320/windowsupdateagent-7.6-x64.exe I will try again and with the above link being for 64-bit.. Actually, It did go through your steps last week but only the Manually reset Windows Update components (KB971058). I have not done these yet: 5. Before installing updates, apply "PosReady.reg" if not already done. 6. Install these four updates KB4467770, KB4019276, KB4493435, KB942288-V3. Credits to @maile3241. 7. Apply "Tls 1.2.reg". Credits to @maile3241. 8. Execute "rootsupd.exe". 9. Install the latest Windows Update Agent 7.6. It's version 7.6.7600.256.
ItCoder Posted November 10, 2023 Posted November 10, 2023 Check if wuaueng.dll has a digital signature into properties. If it hasn't, it's already the patched version. If it has, it must be dated 2012. Check also if you have the same copy in C:\Windows\System32\dllcache. If not, install windowsupdateagent (but version 7.6.7600.256, 320 is not for XP) with /WUForce option. After that, patch wuaueng.dll both in System32 and dllcache.
AstroSkipper Posted November 10, 2023 Posted November 10, 2023 @WSC4 Compare the hash values of wuaueng.dll to be sure you have the patched one in both folders, System32 and Dllcache! 2
WSC4 Posted November 10, 2023 Posted November 10, 2023 (edited) I checked wuaueng.dll and it did not have the digital signature. Also, wuaueng.dll was not in the dllcache directory. I did not know about the WUForce option. Running it Without it, the Update Agent said the agent was up to date and did nothing. I just ran it with the the force option and it installed OK this time. wuaueng.dll now has the digital signature in system32 and the dllcache directory. Rebooted the machine, Launched the ProxHTTPSProxyMII v1.3a by maile3241 and then into Windows Update. Unfortunately, the Express or Custom button still went to error. I think those KB updates need to be installed. I will go through your numbers 5 to 8 and see if that helps. Edited November 11, 2023 by WSC4
AstroSkipper Posted November 10, 2023 Posted November 10, 2023 3 minutes ago, WSC4 said: wuaueng.dll now has the digital signature in system32 and the dllcache directory. The patched wuaueng.dll does not have a digital signature. Therefore, your system has the original, unpatched files meaning the wrong files. Insert the patched one in both folders from outside (boot gor example from an external medium such as Linux or Windows PE)! 3
WSC4 Posted November 11, 2023 Posted November 11, 2023 (edited) OK. I have run maile3241's install.com this time again and checked the system32 and the dllcache. Booted an external drive of an XP install I have and pasted those files The wuaueng.dll files do not have a digital signature and are the correct versions from his install. No luck. Still getting the error. I did note that maile3241 was using Internet Explorer 6 back then. I am using IE 8. Could that be a possible reason for the error? Before I Install these four updates KB4467770, KB4019276, KB4493435, KB942288-V3, I looked at them via the Microsoft Update Catalog. POSReady 2009 (KB4467770) update Architecture: is X86. I don't thing that is going to install on XP 64-bit. I thought so. I had to have a go anyway. Edited November 11, 2023 by WSC4
ItCoder Posted November 11, 2023 Posted November 11, 2023 Can you access https://fe2.update.microsoft.com/windowsupdate/v6/default.aspx?g_sconsumersite=1 with ProxHTTPSProxy?
AstroSkipper Posted November 11, 2023 Posted November 11, 2023 4 hours ago, WSC4 said: I did note that maile3241 was using Internet Explorer 6 back then. I am using IE 8. Could that be a possible reason for the error? As far as I can remember, @maile3241 had problems using IE 8 for accessing MU/WU and used IE 6 instead. He wrote about that in the past. Therefore, it could be a possible reason for the error. 3
ItCoder Posted November 11, 2023 Posted November 11, 2023 Check if your patched wuaueng.dll is 1,xx MB or 2,xx MB. If it's 1,xx MB it's the 32bit version which won't work on 64bit systems. You can try putting it in SysWow64, but I don't know if it works. 2
WSC4 Posted November 11, 2023 Posted November 11, 2023 (edited) 13 hours ago, ItCoder said: Can you access https://fe2.update.microsoft.com/windowsupdate/v6/default.aspx?g_sconsumersite=1 with ProxHTTPSProxy? It does open, but pressing the the buttons has the same Error number: 0x800706B5 11 hours ago, ItCoder said: Check if your patched wuaueng.dll is 1,xx MB or 2,xx MB. If it's 1,xx MB it's the 32bit version which won't work on 64bit systems. You can try putting it in SysWow64, but I don't know if it works. Yes, they are the correct size. Just over 2 MB. 13 hours ago, AstroSkipper said: As far as I can remember, @maile3241 had problems using IE 8 for accessing MU/WU and used IE 6 instead. He wrote about that in the past. Therefore, it could be a possible reason for the error. I am actually reading the January 2022 page. I think the poster was using Windows 7 64-bit and IE 8. I will go through those KB updates one-by-one and check for x64 versions and install those and the reg files and pray. :-) Edited November 11, 2023 by WSC4
WSC4 Posted November 13, 2023 Posted November 13, 2023 (edited) Using XP 64-bit and Internet Explorer 8, and I have made some progress and have now arrived at this page: I am too scared to click Start Now. 5. Before installing updates, apply "PosReady.reg" if not already done. <== I did this anyway, but because of the failed updates, it may have no effect. 6. Install these four updates KB4467770, KB4019276, KB4493435, KB942288-V3. <== All these updates are x86 and will not install on XP 64-bit. I did find KB942288-V4 which is x64 and installed OK. 7. Apply "Tls 1.2.reg". <== I did run this for what it's worth. 8. Execute "rootsupd.exe". <== applied this. 9. Install the latest Windows Update Agent 7.6. It's version 7.6.7600.256. <== This is maile3241's install.com and not the incorrect Microsoft Update Agent. Why is ProxHTTPSProxMII showing https://outlook.live.com and https://login.live.com in the window? Edited November 13, 2023 by WSC4
AstroSkipper Posted November 13, 2023 Posted November 13, 2023 42 minutes ago, WSC4 said: Why is ProxHTTPSProxMII showing https://outlook.live.com and https://login.live.com in the window? Both links are Microsoft related. And the manufacturer of Internet Explorer 8 is Microsoft, too. I don't need to say any more, do I? 2
ItCoder Posted November 13, 2023 Posted November 13, 2023 4 hours ago, WSC4 said: Using XP 64-bit and Internet Explorer 8, I have made some progress and have now arrived at this page: I am too scared to click Start Now. You can try clicking Start now and continue in the following page, if it works it will enable access to MU (without losing access to WU). If it doesn't, nothing will happen. But it might help because it will download authcabs (they are related to checking for updates at least in MU).
WSC4 Posted November 13, 2023 Posted November 13, 2023 (edited) The old saying: don't count your chickens... On 11/11/2023 at 9:18 PM, AstroSkipper said: As far as I can remember, @maile3241 had problems using IE 8 for accessing MU/WU and used IE 6 instead. He wrote about that in the past. Therefore, it could be a possible reason for the error. You are correct about this. There are 2 or 3 page about the discussion about this way back in March last year on page 103: He mentions: "I got the error 0x80072F78 (with IE8) when checking for updates, Under Win Xp x64, unfortunately you cannot access the WU website because you cannot install the necessary PosReady updates." The 3 PosReady updates I could not install on XP 64-bit made it impossible to get IE 8 working. Even KB942288-V4 was not enough. All his screen shots are of IE 6. I wish I had read those pages in more detail last week. I will uninstall IE 8 back to IE 6 and try again. I wonder if IE7 would work also? Edited November 16, 2023 by WSC4
K4sum1 Posted January 27, 2024 Posted January 27, 2024 On 7/9/2022 at 8:01 PM, AstroSkipper said: You can find it on fileeagle. Link: https://www.fileeagle.com/software/470/Process-Explorer/16.26/ Does anyone have a copy of 16.26? Can't seem to find it anywhere. The link is dead, archive.org doesn't have it either.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now