[SOLVED] WU/Store/TSL/Reset connection errors (0x80240437)

Please open Powershell and try the following commands:

PowerShell -ExecutionPolicy Unrestricted $manifest = (Get-AppxPackage Microsoft.WindowsStore).InstallLocation + ‘\AppxManifest.xml’ ; Add-AppxPackage -DisableDevelopmentMode -Register $manifest

and

PowerShell -ExecutionPolicy Unrestricted -Command “& {$manifest = (Get-AppxPackage Microsoft.WindowsStore).InstallLocation + ‘\AppxManifest.xml‘ ; Add-AppxPackage -DisableDevelopmentMode -Register $manifest}”

There may be a few errors, but you can ignore them.
 
Yeah, I found those online, too. :)

I don't think either of those commands is parsed right. They both just get syntax errors. Probably worked with an older version of PowerShell but they don't work now. "=" apparently isn't a valid element in the expression the way it's parsed here. Unfortunately, I don't know enough about PowerShell to know how to correct them, but I could tell they were doing nothing.
 
Step#1 - Capture Process Monitor Trace
1. Download and run Process Monitor. Leave this running while you perform the next steps.
2. Try updating the system just like you have in the past.
3. Stop Process Monitor as soon as it fails. You can simply do this by clicking the magnifying glass on the toolbar as shown below.
i3yiUac.png


4. Select the File menu...Save... and save the file to your desktop. This is likely the default location. The name (unless changed) will be LogFile.PML. This is fine.
5. Zip up and provide the link to the LogFile.PML file as well as your CBS.log Examples of services to upload to are Dropbox or OneDrive or SendSpace.
 
I think you may have found the problem. There are manual proxy settings enabled, and when I clear them, they just come right back.

In Control Panel settings, the Connections page states that some settings are being managed by the System Administrator. I don't know of any System Administrator. Now, this IS an Enterprise edition of Windows. I assume because that's what was loaded when it was purchased. Maybe that's why it's talking about a System Administrator.

You wouldn't happen to know how to remove those proxy settings, would you?
 
The thing is I thought I did.

Let's check:

Step#1 - FRST Scan

1. Please download Farbar Recovery Scan Tool and save it to your Desktop.
Note: You need to run the 64-bit Version so please ensure you download that one.
2. Right-click FRST64.exe and click Run as Administrator to run it as administrator. When the tool opens, click Yes to disclaimer.
3. Please ensure you place a check mark in the Addition.txt check box at the bottom of the form before running (if not already checked).
4. Press Scan button.
5. It will produce a log called FRST.txt in the same directory the tool is run from (which should now be the desktop)
6. Please attach the log back here.
7. Another log (Addition.txt - also located in the same directory as FRST64.exe) will be generated Please also attach that along with the FRST.txt in your reply.
 
I figured it out!!

My thought immediately was, could there be a process that has taken over the proxy?

There was a process running called Inno Uninstaller or something like that. I couldn't even find it in the App list, so it must be some kind of Malware. Heaven knows how it got there, but when I stopped the process, the proxy went away and everything started working again.

Now I just have to figure out how to clean this crap off the system.

Thank you for your patience. I will add another update if I have more info on what it was and how I got rid of it.

So, you probably DID remove the proxy stuff, but that process (whatever crap it was) put it right back in.
 
You must log in or register to reply here.

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top