I AM your target demographic. Listen up.

How to resolve Error 0x80240fff when installing Windows Insider Builds

·

Recently I was trying to update a Sony Vaio Fit 15E laptop from Windows Insider Slow Ring build 14931 to 14965 via Windows Update. The update would complete downloading and commence installing, but would fail during the multiple reboot process, causing the previous build to be restored.

After ensuring I had no SD cards inserted or USB devices attached, here are the steps I took to resolve it:

Defering Feature Updates

  1. Open Settings.
  2. Click Update & Security.
  3. Click Advanced Options.
  4. Check the Defer feature updates box.
  5. Retry the update process.

That didn’t work, so I tried:

Running the Windows Update Troubleshooter

  1. Open Control Panel.
  2. In the View by: dropdown, select Small icons.
  3. Click Troubleshooting.
  4. Click Fix problems with Windows Update.
  5. Follow the onscreen instructions to fix any problems that are found.
  6. Retry the update process.

That didn’t work either, so I tried:

Deleting the C:\$WINDOWS.~BT folder

  1. Open File Explorer.
  2. Click the View tab.
  3. Check the Hidden items box in the Show/hide ribbon section.
  4. Navigate to the C:\ drive.
  5. Delete the $WINDOWS.~BT folder.
  6. Retry the update process.

That didn’t work either, so I tried deferring feature updates again and rerunning the update process, producing this error:

There were some problems installing updates, but we’ll try again later. If you keep seeing this and want to search the web or contact support for information, this may help: (0x800705b4)

So I tried:

Installing from the ISO instead

  1. Download the latest Slow Ring ISO here. You’ll need to sign in 1st so the page knows you’re a Windows Insider.
  2. Using WinRAR, 7-Zip, or a similar archive extraction tool, extract the ISO file to a folder.
  3. Open the above folder.
  4. Launch the setup file.
  5. Set the installer to keep your apps, files, and settings and let it run.

That didn’t work either, so I tried deleting the C:\$WINDOWS.~BT again and trying to install from ISO as above. This time I got this error:

0x8007042B – 0x4000D The installation failed in the SECOND_BOOT phase with an error during the MIGRATE_DATA operation

Although this error might seem disappointing, it was actually encouraging because it was the 1st one I’d gotten that actually explained what the issue was.

Googling the error produced this excellent post by Andre Da Costa. I had to:

  1. Do a clean boot (see link for instructions. It’s generally a good idea at all times – error or not – to enable clean boot before rebooting from your current build to install the new one. This will prevent existing startup processes from interfering with the installation.)
  2. Disconnect the laptop from the internet (disable Wi-Fi, unplug Ethernet cable.)
  3. Disconnect all non-essential USB peripherals, including mice if you have a working laptop touchpad.
  4. Reboot.
  5. Retry updating from the ISO files.

This finally fixed the issue.

Note that if you have any services or apps you’d prefer to run at startup, you’ll need to manually re-enable them via some combination of Task Manager, System Configuration, and Services.

I hate that the Insider build update process is this unreliable, but issues can be worked around with tenacity and thought.

Thanks to Microsoft employee /u/zac_l for his assistance on this Reddit support thread:

Comment
byu/jdrch from discussion
inwindowsinsiders

¶¶¶¶¶

¶¶¶¶¶

9 responses to “How to resolve Error 0x80240fff when installing Windows Insider Builds”

  1. […] 10 Insider Slow Ring and was experiencing errors during the build update process. As part of the steps to resolve those, I performed a clean boot. After the update process successfully completed, I went through […]

    Like

  2. Hey. I’ve come across this error in build 15002 today and was hoping we could compare our installed programs and perhaps figure out the culprit. A few possibilities: Razer Synapse, MSI Supercharger, Nvidia Drivers, Killer Network Drivers, Samsung Magician. Let me know if any of those ring a bell or if you have any ideas.

    Liked by 1 person

    1. Good idea. Because clean boot resolves the problem, I’m not sure the root cause is installed programs as much as it’s programs or services set to run when the system starts. Since updates are failing before user login, I think we can narrow the culprit down to startup services. The (major 3rd party) ones I (can think of right now that I) have (explicitly enabled) are:
      – Resilio Sync
      – Unified Remote
      – TeamViewer

      Any others on your end?

      Like

      1. I do indeed have Teamviewer installed! We’ll need someone else to test it out and see if it’s truly the culprit.

        Like

        1. The update usually fails just as before it hits 100%, which would be the most likely point at which the TeamViewer service would start prematurely. I’ve noticed TeamViewer PCs pop up as visible during boot, so that might be it indeed.

          Come to think of it, we don’t necessarily need another tester. Run the next update without clean booting. If it fails, disable the TeamViewer service and try again. If it works, we’ll know TeamViewer is the culprit and can file a bug with them.

          Like

          1. The next update came sooner than I expected, so we didn’t need a 3rd person. I just tested it on update 15007 and I can confirm that, everything else the same, disabling the teamviewer service allowed the update to proceed just fine. So, assuming they didn’t patch the update to not have this issue anymore, that seems to be the culprit!

            Liked by 1 person

            1. Nice work, man! Please file this as a bug with TeamViewer so they can fix it.

              Like

  3. […] to previous build”, dumping me back to where I started. After speaking to a blogger named jdrch, we came to the same conclusion: Teamviewer. Disabling the Teamviewer service solved the issue […]

    Like

  4. Hello Jdrch,
    I read this article, you described so deeply. It is right because after Microsoft Windows users while installing the updates often experience error 0x800705b4 – sometimes referred to as Windows update error 0x800705b4.

    I searched and found that error 0x800705b4 appears in Windows system when the system is infected with virus or malware, damaged Windows system files, corrupt Windows updates.
    Whatever may be the reason but the error code 0x800705b4 may cause data loss if updates aren’t installed in the first attempt, I personally faced the situation.
    As per concern data one more point, I would like to share about data recovery software. During research I found that there are software available online that are very helpful if some lost data during this update, they can recover easily. I read reviews and most of them suggested Stellar Data Recovery. I used free demo to check and found better result.
    But, I am wonder to read this blog because of you described numbers of cause and solutions to fix it so well. Very useful article for me I personally believe. Thank you so much

    Like

Comment