Windows Update error 0x80246017 continues to plague users

Martin Brinkmann
May 21, 2015
Updated • May 21, 2015

If you have set up a test system with a preview build of Microsoft's Windows 10 operating system, you may have encountered the update error 0x80246017 before.

I encountered the error yesterday when I tried to to download the newest build on Fast Ring, 10122. Instead of downloading and installing the build, Windows Update would display the error message fbl_impressive Professional 10122 - Error 0x80246017 instead.

While there are lots of suggestions on how to resolve the error, none worked in my case. I did modify Registry keys for instance, used Disk Cleanup to delete old Windows installation files, deleted the Windows Update cache and tried various other options like switching from automatic updates to update notifications.

The Registry solution suggests to delete the keys ThresholdInternal and ThresholdOptedIn under Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsSelfHost\Applicability and make sure that the key ThresholdRiskLevel  is set to low.

It seems to be a wider issue, as it has been confirmed by Gabriel Aul, Microsoft General Manager OSG Data and Fundamentals team, on Twitter.

None worked. To make matters worse, even a refresh or reset of the system did not resolve the update issue

The only thing that did work was to download an ISO image of the latest build and use it to install it on the computer.

Issues like this one may not be uncommon in pre-release software but it could become highly problematic if not resolved before Windows 10 hits RTM.

Microsoft announced some time ago how it plans to deliver updates for the various editions of Windows 10. Updates are likely enforced in some editions which could become a huge issue if errors block systems from receiving those updates especially if Microsoft will make it difficult to obtain those updates elsewhere.

This is for instance the case right now. If Microsoft would have released an ISO image of the Windows 10 Preview build 10122 to the public, it could be used by testers who run into the issue. Since it is not available officially, testers either have to wait for Microsoft to release a patch to fix the update issue, or download the ISO from a third-party source instead to use it to update the system to the latest build.

There is not really a lot you can do right now if you are affected by the update error other than download an ISO image or wait for Microsoft to fix the issue on their end.

Now You: Did you run into updating issues on Windows 10 before?

Windows Update error 0x80246017 continues to plague users
Article Name
Windows Update error 0x80246017 continues to plague users
The Windows 10 update error 0x80246017 blocks recent versions of the operating system from being installed on systems.

Tutorials & Tips

Previous Post: «
Next Post: «


  1. Desplow said on May 25, 2015 at 7:59 pm

    Yes, I made it to a restart but got stuck at 32 % at copying files so I had to abort it and fortunately, eventually returned to the old version.

    1. Desplow said on May 26, 2015 at 6:15 pm

      Never mind, it installed fine on the second attempt. However the Start menu often doesn’t respond making it hard to open certain programs.

  2. GinKo.Wang said on May 25, 2015 at 10:11 am

    you should execute clean install
    step 1.“Win+R”。
    step 2.type input services.msc and enter。
    step 3.find WindowsUpdate Services,and stop it。
    step 4.find C:\Windows\SoftwareDistribution,rename:SoftwareDistribution_Old 。
    step 5.restart Windows UpdateService。
    step control panel , recheck windows update
    good luck 4 u.

  3. CHEF-KOCH said on May 24, 2015 at 5:15 pm

    This always fix all windows update errors for me, it clears the old cache and renew everything.

    net stop wuauserv
    net stop bits
    net stop cryptsvc
    ren %systemroot%\System32\Catroot2 oldcatroot2
    net start cryptsvc
    ren %systemroot%\SoftwareDistribution SoftwareDistribution.old
    regsvr32 wuapi.dll
    regsvr32 wuaueng.dll
    regsvr32 wucltux.dll
    regsvr32 wups2.dll
    regsvr32 wups.dll
    regsvr32 wuwebv.dll
    net start bits
    net start wuauserv

  4. Snuffy said on May 23, 2015 at 5:10 pm

    Yes, seems that the more MS tries to move us from XP, Windows 7, Windows 8/8.1 the more JAMMED Windows 10 is.

  5. Alex said on May 23, 2015 at 9:17 am

    That’s why mandatory autoupdates is a bad idea.

  6. Shawn said on May 21, 2015 at 11:41 pm

    Long live XP the only OS that MS can’t screw up no more xD

  7. PhoneyVirus said on May 21, 2015 at 6:07 pm

    Like me know then they release to RTM witch should be around Q3 September October time frame, the same time Skylake Launches. Oh and the mount of time you spend installing Windows 10 Technical Preview that could basically make up for work done on someone else’s machine for money, so with that no thanks, I have better things to be doing than been a pig for Microsoft.

  8. Å ime Vidas said on May 21, 2015 at 5:11 pm


  9. clas said on May 21, 2015 at 4:15 pm

    hi martin, yeah, forced updates, if true, are not my cup of tea. way too many problems in the past with updates that caused problems. probably most people getting your blog would be able to cope, but the masses of uninformed computer users would just head to the repair shop.

Leave a Reply

Check the box to consent to your data being stored in line with the guidelines set out in our privacy policy

We love comments and welcome thoughtful and civilized discussion. Rudeness and personal attacks will not be tolerated. Please stay on-topic.
Please note that your comment may not appear immediately after you post it.