Windows 10: Windows 10 Update Error 0x80240439

I am currently on Windows 10 Build 1703 Version 15063.0 following an in-place upgrade. Every time I try to Check for Updates on Windows 10, I get the error 0x80240439. I have spoken to 5 of the Microsoft team now, and I've done two repair installs, one clean install, and two in-place upgrades. Every time, the issue has persisted. At one point, it let me update, but after a restart and another "Check for Updates" the error started again. I have tried manually installing the windows updates, but an unexpected error doesn't allow me to. I've done sfc /scannow numberous times, reset the Windows Update Components several times and started services via an elevated command prompt until it has driven me insane. The last member of the Microsoft team I spoke to suggested I buy the Assure Plan for £95 to get a higher technician on the case, which I am not doing. Can someone please give me any advice on how to proceed? I have exhausted my options.Original post here: Windows Update Error 0x80240439 - Windows 10 Forums

:)

 

windows update and store problem error (0x80240439)

The syntax of that record suggests something is being mangled

When this happened to someone else last year the syntax was different but the resolution was to do an ISO upgrade repair.

https://superuser.com/questions/1122080/windows-update-error-code-0x80240439-and-web-service-xml-errors

<extract>

2016.09.08 00:08:56.6928651 676 792 Misc Got service 855E8A7C-ECB4-4CA3-B045-1DFA50104289 plugin Client/Server auth token of type 0x00000001

2016.09.08 00:08:56.6932602 676 792 ProtocolTalker PTError: 0x80240439

</extract>

So, if you just had a bad update for your CU that could probably explain a lot of things too.

 

ERROR (0X80240439

I have the very same problem.

I'm on 14393.321 and switched from Release preview to fast ring. Error 0x80240439 in Windows Update.

Regards,

 

Hi llluminati lzzy.

Using DISM in this thread seemed to help a number of people.

https://answers.microsoft.com/en-us/...3-404b346b5509

That said given all the installs, repairs, upgrades I myself would start with a clean install. I would first run a chkdsk against my storage and I would even run memory diagnostics.

Then when I performed the clean install I would delete all partitions from the drive and let Windows create the partitions it needs. Of course you need to get your data off the device. I would also do the install without looking for updates. If you have a lot of storage devices attached just do the installs and subsequent updates with just your "System" drive connected.

My opinion, others will have a different approach.

Ken

 

Thanks for offering your help. I've executed chkdsk /r in an elevated command prompt and I entered "Y" to confirm a chkdsk on reboot. However, upon reboot, the PC boots as normal, and chkdsk does not start. I've checked the "BootExecute" registry path, and the it reads "autocheck autochk /r \??\C:" "autocheck autochk *" (no quotations). I've opened a command prompt in safe mode and tried to run chkdsk /r with a reboot, but it, again, boots as normal. I used the Recovery Command Prompt to run chkdsk C: /r, but I had to change the drive to D: (chkdsk D: /r) for it to scan my storage drive. This confuses me, none of my drives are labelled D:. The command runs straight from the Recovery Command Prompt, without a reboot, and chkdsk /r still won't work on reboot after executing it from an elevated command prompt straight afterwards. The events also aren't uploaded to the event viewer.

I tried to run an extended memory diagnostic with mdsched.exe, but it froze at 21% and the whole PC became awfully slow/delayed. I've never ran a memory diagnostic before, so I'm not sure if this is normal or not.
My last question, does it matter if I do a clean install from a USB or CD/DVD?

Thank you

 

Chkdsk has been fixed with the latest cum. update - which is not gonna help you much, I know - just FYI.

You can run it from booting the windows media (USB or DVD) and selecting the repair link and cmd promt thereafter.

When booting this way your drive letters may become skewed - use diskpart to check for correct one.

Also note the switches: /R recovers info from sectors - to fix them in the first place, use /F

In fact I always use both: chkdsk C: /f /r

 

Let's see what's in your update pipeline. Download and run this tool ....

https://support.microsoft.com/en-us/...-in-windows-10

... and post the results here (like so):





I did not look at all your previous posts in detail but I assume you have already tried to disable WU driver updates entirely; correct?

 

Attachment 136286Attachment 136286

I'm not sure if I've tried to disable WU driver updates... Could you please tell me how I go about that?
Attachment 136286

 

Just did another clean install after chkdsk /f /r... Issue still persists...
Am I doing these clean installs wrong?

 

Control Panel> System> Advanced System Settings> Hardware> Device Installation Settings

 

Disabling didn't fix the error

 

Just ran chkdsk /f /r and it worked on reboot! The clean install must've done something magic *Smile
...Will take some time to finish the chkdsk though

 

I managed to get rid of the error and am currently installing updates. I will say the steps I did in hope that it will help diagnose my error.
"net stop bits/wuauserv/cryptsvc" in an elevated command prompt (not all one command, three separate for each)
Scan for updates - Error
"net start bits/wuauserv/cryptsvc" in an elevated command prompt
Scan for updates - Error
Downloaded Windows Update Troubleshooter for Windows 10 here: https://support.microsoft.com/en-gb/...ate-components
When running the troubleshooter, decided to decline using the more up-to-date version. (It didn't fix anything)
Scan for updates - Downloading/Installing updates.

It seems to me like running the old troubleshooter fixed the error, even though it didn't say it fixed anything. The error will likely return on reboot like it did last time.

 

Well, you did do a few things:

1. You disabled driver updates (did you reboot before testing again?)
2. You got chkdsk to run (w/help from Superfly)
3. You ran the troubleshooter again (and that may have fixed something associated with item #1)

The only way to find out for sure is reboot and see if it still works.

 

I was correct - the error returned after reboot. However, before it returned, it found cumulative update KB4016871 and downloaded it again (didn't install it, possibly because it found it was already installed) checked for updates and gave me error 0x80240439 again

Last time it did this, it tried to install the same cumulative update again, and when it realised it was already installed, it gave me the error.