Windows 10 Mobile Build 14955 has been pushed by Microsoft yesterday. But many were again either not able to see the update at all or were facing error 80242006. The trick to get the Build 14955 is not different from what was used for Build 14951. So just follow these easy steps.

Steps:

  1. Go to Settings–>Update & security–>Windows Insider Program and choose Slow Ring
  2. Go to Settings–>Time & Language and manually set a date of 7 days from now. For example set 28th October manually.
  3. Go to Settings–>Update & security–>Phone update and you will see device checking for updates and will throw some kind of error (check the screenshot below) build-14951-install-trick-2
  4. Now Go to Settings–>Update & security–>Windows Insider Program and choose Fast Ring
  5. Go to Settings–>Time & Language and set it to update automatically and it will show today’s date and time
  6. Go to Settings–>Update & security–>Phone update and you should be able to get the update (Check the screenshot below)build-14951-install-trick-1

Microsoft has today shared four tricks to get Windows 10 Mobile Build 14951 installed on devices stuck at 0% download. But while the users are getting limited success with these official four tricks that you can read below, here is one trick (above) that worked beautifully on two of our devices. (Thanks to Nate for sending it).

Error 80242006 fix while trying to download Build 14951:

As part of our recent Mobile flight, some users have reported seeing error 80242006 while trying to take the update.

This error arises as part of a update information collision.  There is however a workaround, please see the steps below:

  1. Switch your device to the Slow ring

  2. Change device date to 7 days in the future

  3. Check for updates (should say “no updates available”)

  4. Change device date back to current date

  5. Change device back to Fast ring

  6. Check for updates

Microsoft recommended Tricks:

  • FASTEST  – You can force the update session to time out by:
    • Plug your device into a charger
    • Open Settings > Update & Security > Windows Insider Program –  Change your device to “Slow” and then back to “Fast”
    • Turn on airplane mode Settings > Network & wireless > Airplane Mode
    • Navigate to Settings > Time & Language > Date & Time –  If On, turn “Set date and time automatically” to the Off position
      1. Change the date on the device to 7 days in the future
    • Return to the home screen & Reboot the device
    • After the reboot, turn off airplane mode – Settings > Network & wireless > Airplane Mode
    • Check for updates – Settings > Update & Security > Phone update > Check for updates
    • This process will fail with an error code.  This is expected!
    • Change the device date back to the current date – Settings > Time & Language > Date & Time
    • Check for updates –  Settings > Update & Security > Phone update > Check for updates
    • This check may fail again, this is ok.
    • Reboot the device
    • After the reboot, check for updates – Settings > Update & Security > Phone update > Check for updates
    • The check for updates should succeed and begin downloading 14951*Note*  We have seen several instances of users reporting getting error code 80242006 after this last check for updates.  We will be doing some additional testing on our side for this, but in the mean time, Insiders are awesome and have noted these additional steps seem to bypass this final error message:
    • Switch Insider setting to Slow ring
    • Check for updates (will say you are up-to-date for the Slow ring)
    • Change back to Fast ring
    • Check for updates again and it should update
  • EASIEST-LONGEST – If your device is already in this state, it will timeout after 5 days. Once the update times out, your device will get the updated metadata and should move forward as normal with download Build 14951.
  • MEDIUM WORK – If your factory reset your device on Build 14946 – Settings->System->About->Reset your phone – you will be able to download 14951 without issue now.
  • MOST WORK – Less optimal, but if you have already rolled back to an older build such as Windows 10 Version 1511 or Windows 10 Anniversary Update using WDRT, you can easily move forward avoiding this issue.