1703 clean install immediately gives 0x80070057 error

Page 1 of 3 123 LastLast

  1. Posts : 60
    Win10 Pro x64

    1703 clean install immediately gives 0x80070057 error

    1703 upgrade install had some hiccups for me, so I bit the bullet and did full disk clean install. Deleted all partitions and let Windows installer create them as it wished. Everything goes smoothly, and as soon as its done I check Windows Update:
    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 - (0x80070057).

    Next I check Activation Status, which should be activated via digital entitlement. Not activated.
    Something interrupted our troubleshooting. Make sure you're connected to the internet, wait a few minutes, and try again. Error code: 0x80070057

    I gave it a few hours but the errors never resolved. Tried the recommendation to rename the SoftwareDistribution folder etc. (even though how could a brand new 100% fresh-from-MS installation be corrupted before even used?) and no joy. Tried installing x86 and x64 versions, same result with each.

    I had saved a full disk image of my previous 1511 installation and have gone back to that, so I can't try any solutions for the 0x80070057 error right now ... but I will try again to reinstall 1703 as soon as I have some ideas for what to do.
    Last edited by mc510; 30 Apr 2017 at 22:01.
      My Computer

  2. Posts : 39,972
    windows 10 professional version 1607 build 14393.969 64 bit

    In administrative command prompt run sfc /scannow.
    Let us know if you had no integrity violations, whether it found errors and fixed them, whether it found errors and was unable to fix them, or whether it was unable to complete.

    Then run dism /online /cleanup-image /restorehealth

    Then if there are any problems please post your CBS and DISM logs.

    When you attempted your prior update had you placed your computer in clean boot before the upgrade?
    Did you generate panther logs when the update failed?

    In administrative command prompt use control c then control v and paste this command if another update fails: C:\$Windows.~BT\Sources\Panther

    Then search for these logs:

    It will be easier to upgrade with an already made a USB flash drive with a bootable windows 10 iso.
    You will need to the know the computer manufactures F key to choose the boot device and will choose the USB port.

    Download Windows 10

    Some of these links allow you run through the troubleshooting menus.

    Let us know what you were able /not able to do successfully.
    Last edited by zbook; 01 May 2017 at 03:17.
      My Computer

  3. Posts : 60
    Win10 Pro x64
    Thread Starter

    Thanks zbook ... I'm back on my previous 1511 installation, and I'm going to have to wait until I've got a free weekend to devote some time to troubleshooting 1703. Will post back here when I've done that.

    No, I didn't do a clean boot before trying the upgrade-in-place installation of 1703, but it did complete the installation normally and throwing any errors. Except that it gave me the 0x80070057 error in Windows Update, and problems with sleep, which was what prompted me to do the full disk clean install.
      My Computer

  4. Posts : 575
    Windows 10 Home


    A different option for you to consider:

    If you are already using a Windows 10 operating system version, try upgrading to Windows 10 Creators Update using Windows 10 Update Assistant:

    Update to Latest Version of Windows 10 using Update Assistant - Windows 10 Installation Upgrade Tutorials

    No guarantees, but, might be worth a shot.
      My Computer

  5. Posts : 6
    Win 10 Pro 1607

    I just spent my whole weekend with Microsoft Support on this matter. Here are the things I tried - spoiler alert - nothing worked.

    1. Fresh install on a newly formatted disk using Windows 10 1703 aka Creators Update - like the original post I got a 0x80070057 error on Activation, Windows Update and installing app from the Windows Store. Naturally, Microsoft was keen to help.
    2. Tried applying Cumulative Patch (sorry didnt note the KB no) for Win 10 1703 - still no joy
    3. Tried to gpupdate /force after checking Administrative Templates-Windows Component - Windows Update - Configure Automatic Updates = Not Configured (also didn't work)
    4. Tried to regedit IsConvergedUpdateStackEnabled=dword:0000000 - (Regedit will not allow it to be edited, value remains as 1)

    Finally we (me and MS Support) gave up. I wiped my disk clean and reinstalled Windows 10 1607 aka Anniversary Edition. It went smoothly, the activation was automatic as described - I got a digital entitlement license. I applied cumulative patch etc - no more issues.

    In "Update and Security" settings, however, there's an announcement
    - Good News! The Windows 10 Creators Update is on its way. Want to be one of the first to get it?"
    Then I clicked on "Yes, show me how" - it verified my hardware for compliance and it did. Long story short it updated my Win 10 1607 to 1703. Then bam! I got the 0x80070057 once again. But this time I just had to roll back to 1607. I plan to stay there until perhaps I see something worth pursuing.
    Last edited by artipax; 08 May 2017 at 07:46.
      My Computer

  6. Posts : 39,972
    windows 10 professional version 1607 build 14393.969 64 bit

    It's frustrating to have so many problems and no guarantee of success.
    Can you clarify what you did for the clean install. Sometimes that term is used for in place upgrades. Did you make the drive unallocated?
    If not then you may be able to delete the partitions and format the drive and then use a bootable windows 10 iso for installation.
    If you perform an installation after making an unallocated drive please post these logs: CBS, DISM, setupact, and setuperr. We can look at those logs an possibly find a fix.
    Also you can get 1703 by recontacting Microsoft. It will take patience. They have three levels of support with level three the engineers. Update, or upgrade problems are serviced free.
      My Computer

  7. Posts : 6
    Win 10 Pro 1607

    When I installed 1703, I deleted all partitions and let the installer generate all the partitions it requires. I'm afraid I can no longer post those logs because in the end I needed a working system and once again blew all partitions installing 1607.

    Both Win 10 1703 and 1607 are downloadable from https://www.microsoft.com/en-au/soft...d/windows10ISO - anyone can download because you'd need a key if you don't have a digital license to activate anyway.
    Last edited by artipax; 08 May 2017 at 08:19.
      My Computer

  8. Posts : 1,366
    Windows 10 Pro x64

    I saw something similar to this on a Dell laptop. I had to install newer network drives for the wired connection (since it was using that) and after a reboot, the laptop was able to get online and activate properly.
      My Computer

  9. Posts : 39,972
    windows 10 professional version 1607 build 14393.969 64 bit

    When you run winver what is your current version and build?
    When you boot now what are you able and not able to do?
    When you run sfc /scannow does it complete and display no integrity violations?
    If you are currently running version 1607 run dism /online /cleanup-image /restorehealth. Did it complete successfully?
    Does chkdsk complete without bad sectors?
    If you are currently running version 1607 do you want to try again to upgrade to 1703?
    Or do you want to delete the partitions, format the drive, make it unallocated, and install a new copy of version 1703 with a bootable windows 10 iso?
    The second method is preferable.
    If you do that please generate logs to troubleshoot the upgrade or installation problems.
      My Computer

  10. Posts : 60
    Win10 Pro x64
    Thread Starter

    Hey Artipax, sorry you've got this problem too, but at least we can troubleshoot together. I probably won't try again for a month, but when I can again do a full disk clean install of 1703, I'll make sure to run the sfc and dism scans and post the logs that zbook mentions. I'll also try removing the wifi card, which is the only hardware that I can think of that might be causing a problem (it's not the original mfg-provided one).

    I forgot to mention that I also tried the regedit thing, and was also unable to change b/c the values are "owned" by TrustedInstaller and I lack permissions to edit. I found some info about how to change registry ownership and permissions; didn't entirely understand what it said and am a little skittish but will probably try this next time as well.

    Artipax, what hardware are you dealing with? Mine is a very old HP/Compaq laptop -- 945GM chipset and Core2duo T5600 cpu with 2G of ram and 120G Sandisk Plus SSD.
      My Computer


  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 12:08.
Find Us

Windows 10 Forums