AstroSkipper
Content Type
Profiles
Forums
Events
Posts posted by AstroSkipper
-
-
34 minutes ago, Dave-H said:
OK, I've fixed the launcher problem.
Bothering the read its help file would have helped!
I didn't realise you needed to specify the program you want it to run in its shortcut.
How strange that it runs notepad by default if you don't though!@Dave-H Ok, reading instructions and manuals before using a new program is mandatory. In program folder of HTTPSProxy you have to pull HTTPSProxy.exe on top of launcher.exe using left mouse button to start program in SysTray. And I hope you have installed only one HTTPSProxy CA and cleaned up your Certs folder. Furthermore update cacert.pem by clicking entry in SysTray menu. But I need more answers. I asked you a lot. What about your firewall?. Check out all!. Your screenshot of proxycfg looks as it should be. That's fine. What's going on with your Windows Update Log file? And so on. Inform me completely if you want get rid of these errors! And please upload a readable log file!
0 -
@Dave-H I found a comment to error code 0x801901F6
QuoteI would venture a guess that either your Windows XP machine is not properly configured to use a required proxy server, or the proxy server is not properly configured to handle the requirements of using Windows Update.
The first step will be identifying what device is causing this error.
I think you have connection errors due to proxy misconfiguration or incorrect use.
Try following after command line prompt: proxycfg
If HTTPSProxy is disabled it should look like this:
"Direktzugriff <kein Proxyserver>" means "Direct access <no proxy server>".
If it doesn't look like that then enter proxycfg -u
And check your HOSTS file to make sure you don't have any static IP entries for the Microsoft/Windows Update web site listed in the file.
Here what Germans say if they get in trouble translated for you:
It always gets worse before it gets better.
0 -
@Dave-H Here two screenshots how HTTPSProxy has to look if it is switched on:
Does it look like that?
0 -
56 minutes ago, Dave-H said:
Should I disable SSL 2.0?
Try it! And clear SSL cache and personal information once again! And I can't read your WindowsUpdate.log. Check it and upload it again! There is something misconfigured either in config.ini (do you use my provided config.ini for HTTPSProxy?) or in IE. Why is your WindowsUpdate.log unreadable?
p.s.: Use a taskmanager to check if nothing interferes your connection to MU. I use Process Hacker, in my opinion the best.
2 -
12 hours ago, maile3241 said:
I've tried everything. Up to about 2 days but no result.
Just to clarify Microsoft Update Search doesn't work in your Windows XP system due to never ending process. Is that right?
0 -
4 minutes ago, maile3241 said:
The problem is that you search forever but never get a result.
In the past I had similar problems but thinking the search is forever never getting a result is in most cases wrong. Such searches can last more than an hour. But no one wants to wait for such a long time so they will be abandoned by user. My tip often helps to avoid such long searches.
0 -
5 minutes ago, maile3241 said:
A little tip: I would recommend disabling SSL 2.0, as problems with Tls 1.2 can occur.
Thanks for your tip! In my system no interfering or problems detected. By the way did my tip
QuoteThe old trick to avoid long searches of MU was reinstalling latest cummulative IE update. Resetting of datastore.edb can help too. By the way my search lasts only seconds.
help you?
0 -
On 1/29/2022 at 7:47 PM, Dave-H said:
OK, I'll fire up HTTPSProxy, switch off ProxHTTPSProxyMII, and replicate your settings.
You're absolutely right that we need to be comparing two systems that are as similar as possible!@Dave-H Here are my advanced IE settings. Please check!
https://imgur.com/83qHpbdAnd check if HTTPSProxy and IE are not blocked by Malwarebytes Premium and your firewall. Make exclusions or better disable them temporarily when accessing MU.
By the way which firewall do you use? Built-in or a firewall software? My security combination is Avast Premier and Windows 10 Firewall Control XP. The firewall feature in Avast is not installed. Web protection temporarily disabled. Malwarebytes Premium for Windows 3.5.1.2522 (official last version for XP) didn't work properly in my system (very buggy!) so I went back to Malwarebytes Anti-Malware 2.2.1.1043 for on demand scan which works fine.
0 -
8 minutes ago, abbodi1406 said:
Adding g_sconsumersite manually to fe2.update url (to open MU site) prevent the redirection loop with www.update url
http://fe2.update.microsoft.com/microsoftupdate/v6/default.aspx?ln=en&g_sconsumersite=1
Thanks! Good find. Works flawlessly.
0 -
@Dave-H Although our ProxHTTPSProxy versions are different here are the equivalent lines of my Windows Update Log if ProxHTTPSProxy is doing its job:
2022-01-29 19:24:30:015 1128 b1c Misc =========== Logging initialized (build: 7.6.7600.256, tz: +0100) ===========
2022-01-29 19:24:30:140 1128 b1c Misc = Process: C:\WINDOWS\System32\svchost.exe
2022-01-29 19:24:30:140 1128 b1c Misc = Module: C:\WINDOWS\system32\wuaueng.dll
2022-01-29 19:24:30:015 1128 b1c Service *************
2022-01-29 19:24:30:140 1128 b1c Service ** START ** Service: Service startup
2022-01-29 19:24:30:140 1128 b1c Service *********
2022-01-29 19:24:30:875 1128 b1c Agent * WU client version 7.6.7600.256
2022-01-29 19:24:30:875 1128 b1c Agent * Base directory: C:\WINDOWS\SoftwareDistribution
2022-01-29 19:24:30:890 1128 b1c Agent * Access type: No proxy
2022-01-29 19:24:31:078 1128 b1c Agent * Network state: ConnectedAnd you can see MU recognized No proxy.
0 -
3 hours ago, AstroSkipper said:
So switch to HTTPSProxy and do the same settings. You can do it by clicking Inet_CurUser_ProxySettings.reg Switching on and off by SysTray icon. Important first screenshot. Automatic Configuration both options are unchecked. And check your hosts file if it is clean related to MU. And in background ProxHTTPSProxy may not be loaded. Post your Windows Update Log once again.
I want to compare your system to mine. Without HTTPSProxy I can't do that. AFAIK your connection error is related to synchronizaton and you've got other setting than me. We have to do trial and error. For comparing systems they have to have same structure. And our logs speak a clear language. We have different proxy settings. Beyond that MU is connecting to a https version of fe2.update.microsoft.com although you've loaded http version. You can see this in the log. If you want to solve your problem perform the steps above.
And you know you can have installed both HTTPSProxy and ProxHTTPSProxy. They have different certificates and both are portable. None of them will harm your system. I use both and they are working properly. The only thing you have to take notice of is not runnig both in RAM at once. Due to the fact that I have installed ProxHTTPSProxy Rev 3d we can't compare these versions and my test partition has still to be installed.
0 -
@Dave-H I have compared your log to mine.
In your log you can see:
2022-01-29 12:28:25:312 1860 cc4 Misc =========== Logging initialized (build: 7.6.7600.256, tz: -0000) ===========
2022-01-29 12:28:25:312 1860 cc4 Misc = Process: D:\WIN-NT\System32\svchost.exe
2022-01-29 12:28:25:312 1860 cc4 Misc = Module: D:\WIN-NT\system32\wuaueng.dll
2022-01-29 12:28:25:312 1860 cc4 Service *************
2022-01-29 12:28:25:312 1860 cc4 Service ** START ** Service: Service startup
2022-01-29 12:28:25:312 1860 cc4 Service *********
2022-01-29 12:28:25:343 1860 cc4 Agent * WU client version 7.6.7600.256
2022-01-29 12:28:25:343 1860 cc4 Agent * Base directory: D:\WIN-NT\SoftwareDistribution
2022-01-29 12:28:25:343 1860 cc4 Agent * Access type: Named proxy
2022-01-29 12:28:25:343 1860 cc4 Agent * Default proxy: https=127.0.0.1:8079
2022-01-29 12:28:25:343 1860 cc4 Agent * Default proxy bypass: <local>
2022-01-29 12:28:25:343 1860 cc4 Agent * Network state: ConnectedIn my log you see a difference:
2022-01-29 14:26:34:093 1128 b38 Misc =========== Logging initialized (build: 7.6.7600.256, tz: +0100) ===========
2022-01-29 14:26:34:109 1128 b38 Misc = Process: C:\WINDOWS\System32\svchost.exe
2022-01-29 14:26:34:109 1128 b38 Misc = Module: C:\WINDOWS\system32\wuaueng.dll
2022-01-29 14:26:34:093 1128 b38 Service *************
2022-01-29 14:26:34:109 1128 b38 Service ** START ** Service: Service startup
2022-01-29 14:26:34:109 1128 b38 Service *********
2022-01-29 14:26:35:140 1128 b38 Agent * WU client version 7.6.7600.256
2022-01-29 14:26:35:140 1128 b38 Agent * Base directory: C:\WINDOWS\SoftwareDistribution
2022-01-29 14:26:35:234 1128 b38 Agent * Access type: No proxy
2022-01-29 14:26:35:578 1128 b38 Agent * Network state: ConnectedHere are my IE LAN-Settings:
HTTPSProxy switched off:
https://imgur.com/TRquakL
HTTPSProxy switched on:
https://imgur.com/w19OXo2
https://imgur.com/iuu80ifSo switch to HTTPSProxy and do the same settings. You can do it by clicking Inet_CurUser_ProxySettings.reg Switching on and off by SysTray icon. Important first screenshot. Automatic Configuration both options are unchecked. And check your hosts file if it is clean related to MU. And in background ProxHTTPSProxy may not be loaded. Post your Windows Update Log once again.
0 -
4 hours ago, Dave-H said:
OK, I've disabled NetTime and restored the default Windows system, using your German server, which seems to work fine.
We'll see what happens! It's only set to synchronise once a day.@Dave-H Well, now we are at the same time and your Windows update Agent works as it should be.
Microsoft Update error code 0x80072F8F means ERROR_INTERNET_SECURE_FAILURE ErrorClockWrong.
Maybe this can help you:
Check in your registry if the key HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate doesn't exist otherwise delete it.
Open system panel, click Automatic Updates and check if it is not greyed out. Then select Turn off Automatic Updates.
Open Internet Explorer on the Tools menu, click Internet Options.
Under Advanced check if check for server certificate revocation is unselected.
Then click the Content tab. Under Certificates, click Clear SSL State. Click OK when you receive the message that the SSL cache was successfully cleared.
Under Personal information, click AutoComplete. Under Clear AutoComplete history, click Clear Forms. Click OK when you are prompted to confirm the operation. Click Clear Passwords.
Click OK when you are prompted to clear all previously saved passwords, and then click OK two more times.
Close Internet Explorer.
Start ProxHTTPSProxy and then Internet Explorer.
Try to access Microsoft Update one more time.
Post your Windows Update Log again.
0 -
Yeah, in your posted link there is a second link to a Microsoft site https://docs.microsoft.com/en-us/archive/blogs/win7/windows-update-error-80072f8f and setting "time.windows.com" as time server was the recommendation. Anyway try Windows time service for a next short time and try other time servers. I use "ptbtime2.ptb.de" or use one located in your country. Your log shows you have synchronization errors. The good news your WU Agent works properly we have fixed it. The "WARNING: Unable to establish connection to the service. (hr=80004002)" is blown away.
0 -
10 minutes ago, Dave-H said:
No difference I'm afraid
@Dave-H Damn! Quick view of your Windows Update Log shows your Windows Update Agent is working correctly now. That's fine. Ok, which time server do you use for time synchronization? And is your computer part of a domain?
0 -
Here you can have a look: https://ryanvm.net/forum/viewforum.php?f=25&sid=56abd568c7cb0f44bc3764c209527f9a
0 -
On 1/20/2022 at 3:48 PM, wyf180 said:
I used update check from github on my xp virtual machine,it could found my xp lack some updates.I googled them and could find some of them to download but 6 of them including kb895961 kb954920 kb955417 kb960680 kb2264107 kb971314 I could only find dead links.So could anybody from msfn find these copy of updates,could you share them for me ?
Hi, try looking for old Windows Update Packs for Windows XP and extract them. Maybe some of these updates are included. I have nearly all updates since Service Pack SP3 but only for German version of Windows XP. Some of your requested updates are very old so I don't think they are offered via Microsoft Update but. you can give it a try:
0 -
@Dave-H After performing all steps from post
10 hours ago, AstroSkipper said:Manually reset Windows Update components (KB971058)
do the following steps:
13. Install Restore_WU_XP_2003 again. No reboot at this time.
14. Do following steps of Restore_WU_XP_2003's install.cmd manually: adding registry entries by importing via reg file if necessary and injecting wuaueng.dll in the case you find wrong version in folders system32 or system32\dllcache.
15. Reboot your computer.
16. Switch on ProxHTTPSProxy.
17. Try accessing MU again.
18. Post your Windows Update Log.
Hope it will work at last.
0 -
10 minutes ago, Dave-H said:
Thanks!
I won't be doing all that tonight though, I'll give it a try tomorrow!Of course. Sleep well!
0 -
So here is the official instruction from Microsoft how to reset Windows Update. I've crossed out instructions that aren't referring to Windows XP or 2000. Furthermore I've added steps I found that they are missing. Make a backup if you want to perform this. In any case read carefully!
Manually reset Windows Update components (KB971058)
Important: Follow the steps in this section carefully! Serious problems might occur if you modify the registry incorrectly. Before you modify it, back up the registry for restoration in case problems occur! To reset the Windows Update components, follow these steps:
1. Open a command prompt. To do this, use one of the following methods, depending on your version of Windows:
Windows 8.1 and Windows 8: From the Start screen, swipe in from the right side to display the charms, select Search, and then search for cmd. (Or, if you are using a keyboard and mouse, type cmd at the Start screen.) In the search results, press-and-hold or right-click CommandPrompt, and then select Run as Administrator.
Windows XP and earlier versions: Press the Windows logo key + R, type cmd in the Run box, and then press Enter. Right-click cmd, and then select Run as Administrator.
2. Stop the BITS service, the Windows Update service, and the Cryptographic service. To do this, at a command prompt, type the following commands. Make sure that you press Enter after you type each command.
net stop bits
net stop wuauserv
net stop appidsvc
net stop cryptsvc
3. Delete the qmgr*.dat files. To do this, at a command prompt, type the following command, and then press Enter: Del "%ALLUSERSPROFILE%\Application Data\Microsoft\Network\Downloader\qmgr*.dat"
4a. If this is your first attempt at resolving your Windows Update issues by following the steps in this article, you should skip step 4 and go to step 5. You should follow step 4 at this point in the troubleshooting only if you cannot resolve your Windows Update issues after you follow all steps except step 4. (Step 4 is performed by the "Aggressive" mode of the Fix it Solution that was mentioned earlier.).
Rename the softare distribution folders backup copies. To do this, at a command prompt, type the following commands. Make sure that you press Enter after you type each command.
Ren %systemroot%\SoftwareDistribution SoftwareDistribution.bak
Ren %systemroot%\system32\catroot2 catroot2.bak
4b. Reset the BITS service and the Windows Update service to the default security descriptor. To do this, at a command prompt, type the following commands. Make sure that you press Enter after you type each command.
sc.exe sdset bits D:(A;;CCLCSWRPWPDTLOCRRC;;;SY)(A;;CCDCLCSWRPWPDTLOCRSDRCWDWO;;;BA)(A;;CCLCSWLOCRRC;;;AU)(A;;CCLCSWRPWPDTLOCRRC;;;PU)
sc.exe sdset wuauserv D:(A;;CCLCSWRPWPDTLOCRRC;;;SY)(A;;CCDCLCSWRPWPDTLOCRSDRCWDWO;;;BA)(A;;CCLCSWLOCRRC;;;AU)(A;;CCLCSWRPWPDTLOCRRC;;;PU)
5. At a command prompt, type the following command, and then press Enter: cd /d %windir%\system32
6. Reregister the BITS files and the Windows Update files. To do this, at a command prompt, type the following commands. Make sure that you press Enter after you type each command.
regsvr32.exe atl.dll
regsvr32.exe urlmon.dll
regsvr32.exe mshtml.dll
regsvr32.exe shdocvw.dll
regsvr32.exe browseui.dll
regsvr32.exe jscript.dll
regsvr32.exe vbscript.dll
regsvr32.exe scrrun.dll
regsvr32.exe msxml.dll
regsvr32.exe msxml3.dll
regsvr32.exe msxml6.dll
regsvr32.exe actxprxy.dll
regsvr32.exe softpub.dll
regsvr32.exe wintrust.dll
regsvr32.exe dssenh.dll
regsvr32.exe rsaenh.dll
regsvr32.exe gpkcsp.dll
regsvr32.exe sccbase.dll
regsvr32.exe slbcsp.dll
regsvr32.exe cryptdlg.dll
regsvr32.exe oleaut32.dll
regsvr32.exe ole32.dll
regsvr32.exe shell32.dll
regsvr32.exe initpki.dll
regsvr32.exe wuapi.dll
regsvr32.exe wuaueng.dll
regsvr32.exe wuaueng1.dll
regsvr32.exe wucltui.dll
regsvr32.exe wups.dll
regsvr32.exe wups2.dll
regsvr32.exe wuweb.dll
regsvr32.exe qmgr.dll
regsvr32.exe qmgrprxy.dll
regsvr32.exe wucltux.dll
regsvr32.exe muweb.dll
regsvr32.exe wuwebv.dll
And following added by me (@AstroSkipper):
regsvr32.exe mssip32.dll
7. Reset Winsock. To do this, at a command prompt, type the following command, and then press Enter: netsh winsock reset
8. If you are running Windows XP, you have to configure the proxy settings. To do this, at a command prompt, type the following command, and then press Enter: proxycfg.exe -d
If you are running other versions of Windows, at a command prompt, type the following command, and then press Enter: netsh winhttp reset proxy
9. Restart the BITS service, the Windows Update service, and the Cryptographic service. To do this, at a command prompt, type the following commands. Make sure that you press Enter after you type each command.
net start bits
net start wuauserv
net start appidsvc
net start cryptsvc
10.Windows Vista only: Clear the BITS queue. To do this, at a command prompt, type the following command, and then press Enter: bitsadmin.exe /reset /allusers
11. Install the latest Windows Update Agent.
12. Restart the computer.
Article ID: 971058 - Last Review: 12/08/2015 06:57:00 - Revision: 42.0
Applies to
Microsoft Windows Update
Here is a link of the original document:
https://web.archive.org/web/20160307084624/https://support.microsoft.com/en-us/kb/971058
And here is the the latest Windows Update Agent: http://download.windowsupdate.com/windowsupdate/redist/standalone/7.6.7600.320/WindowsUpdateAgent-7.6-x86.exe. It's version 7.6.7600.256.
Supposedly all these steps should be done by a Microsoft Fixit Tool. No guarantee! Not tested! Here is the link: https://www.mediafire.com/file/r98pvby076rub6j/Mats_Run.WindowsUpdate.exe/file
Although I am not a friend of automatisms, I also offer a another tool here to perform this reset of Microsoft or Windows Update automatically. Anyway, I recommend to backup your system partition completely at first.
This tool called Reset Windows Update Tool (Script) is said to be working properly, but it has not been tested by me, so no guarantee of success and use at your own risk.
The last XP compatible version is 10.5.3.7:
https://www.mediafire.com/file/k48ll6e41eypogy/ResetWUEng10.5.3.7.zip/file
and a less recent version 10.5.3.4 with a help file included:
https://www.mediafire.com/file/wl0yrq98me8dfkj/ResetWUEng10.5.3.4.zip/file
There are many steps in this article that I was going to suggest anyway. Only if previous steps don't help. So have a lot of fun!
PS: This posting will no longer be maintained. It will stay here just for historical purpose. The new, maintained and up-to-date version can be found here:
0 -
32 minutes ago, Dave-H said:
The file version information is no help at all of course, but my archived file says it's 6.2.29.0, the one I've just downloaded says it's 6.3.21.0.
Of course the Windows Update Agent with file version 6.3.21.0 has to be installed. This is the version I have. Install it with command option: WindowsUpdateAgent-7.6-x86 /WUforce.
Then install Restore_WU_XP_2003 again. No reboot at this time.
Then do following steps of Restore_WU_XP_2003's install.cmd manually: adding registry entries by importing via reg file if necessary but injecting wuaueng.dll in any case. Then reboot your computer. Try MU again.
P.S. No more further editing. I swear!
0 -
3 minutes ago, Dave-H said:
Windows Update looks more promising
I agree. You are on the right way.
0 -
1 hour ago, maile3241 said:
Delete the sites and add the 3 back
@Dave-H I agree to @maile3241. Only the three mentioned sites may be listed in your Trusted Zone. Otherwise http://fe2.update.microsoft.com/microsoftupdate/v6/default.aspx?ln=en will be blocked.
"Trusted Zone to high with only these three urls related to MU: http://www.update.microsoft.com, https://www.update.microsoft.com and http://update.microsoft.com. Disable in IE settings "Check for server certificate revocation"."
And once again your problem is most likely caused by a not properly working Windows Update Agent. I will post a more detailed procedure published by Microsoft later.
0 -
On 1/27/2022 at 3:58 PM, Dave-H said:
One thing I don't want is to lose my update history, and I guess resetting will do that.
I do have backups though, so I guess I can always restore it if this does not restore the updates to working.Of course you'll lose your update history. My suggestion was to make an image of your OS partition to revert back at any time you want. I can restore my whole system in less than a half hour (very old computer, very slow). Your Windows Update history is located in "DataStore.edb". So you can backup this file at first. In your Windows Update Log you can see clearly:
2022-01-27 12:28:48:824 1860 1560 Agent *********** Agent: Initializing Windows Update Agent ***********
2022-01-27 12:28:48:824 1860 1504 Report WARNING: Reporter failed to upload events with hr = 80240004.I guess there is a problem with your Windows Update Agent.
I have added a link of "winUpdRestore!v28" right down at the bottom, a more recent version of "winUpdRestore!v23". I used it first.
Then you have to reinstall Windows Update Agent. Resetting of SoftwareDistribution folder is not the same. I suggested you:
On 1/27/2022 at 3:25 PM, AstroSkipper said:...install two versions one after another (the order is important). At first WindowsUpdateAgent30-x86.exe and then WindowsUpdateAgent-7.6-x86.exe using the option /WUforce e.g. WindowsUpdateAgent30-x86 /WUforce and WindowsUpdateAgent-7.6-x86 /WUforce. For resetting Windows Update there is a nice tool I used when I had problems with MU. It's called winUpdRestore!v23. If you don't have it or you can't find it I can upload for you. These steps would have been my next suggestions for you in any case. I did these steps definitely when I fixed my system. You should backup your partition by making an image using Norton Ghost for older computers and Aomei, Macrium or Acronis for newer ones if something is going wrong or you have to revert back. Hope we'll get ahead.
After this procedure you have to reinstall "Restore_WU_XP_2003". Here you have to check if "install.cmd" did its job properly i.e. all commands in "install.cmd" have to be performed properly. Check the correct version of "wuaueng.dll" in both folder system32 and system32\dllcache. Check if all registry entries have been added. If not do it manually by creating a reg file for importing necessary entries from "install.cmd" and copying wuaueng.dll first in folder system32\dllcache and then in folder system32. And what about some posts before where
On 1/27/2022 at 12:27 AM, AstroSkipper said:By the way have you ever tried reregistering following components in the command prompt? Here if not:
regsvr32 Softpub.dll /s
regsvr32 Wintrust.dll /s
regsvr32 Initpki.dll /s
regsvr32 Mssip32.dll /sSo a lot to do!
https://www.mediafire.com/file/xn2a1rlriapkhym/winUpdRestore%21v28.zip/file1
On decommissioning of update servers for 2000, XP, (and Vista?) as of July 2019
in Windows XP
Posted · Edited by AstroSkipper
addition
@Dave-H Ok, thanks for more details! But I don't know your last received error code. You didn't mention. One thing is clear. Your system has become more similar to mine which can be seen in your log:
2022-01-30 18:12:42:328 1864 cd8 Misc = Module: D:\WIN-NT\system32\wuaueng.dll
2022-01-30 18:12:42:328 1864 cd8 Service *************
2022-01-30 18:12:42:328 1864 cd8 Service ** START ** Service: Service startup
2022-01-30 18:12:42:328 1864 cd8 Service *********
2022-01-30 18:12:42:343 1864 cd8 Agent * WU client version 7.6.7600.256
2022-01-30 18:12:42:343 1864 cd8 Agent * Base directory: D:\WIN-NT\SoftwareDistribution
2022-01-30 18:12:42:343 1864 cd8 Agent * Access type: No proxy
2022-01-30 18:12:42:343 1864 cd8 Agent * Network state: Connected
But here is your problem:
2022-01-30 18:14:23:468 576 65c Misc WARNING: DownloadFileInternal failed for https://www.update.microsoft.com/v11/3/legacy/windowsupdate/selfupdate/wuident.cab: error 0x801901f6
So your error code still seems to be 0x801901f6. My guess is that something interferes the download of wuident.cab. Disable Malwarebytes and your internal firewall before accessing MU. Then provide error code and log!
I think we are close to solve it.