OTC updater problem

Anonymous
2020-09-20T16:26:13+00:00

when i try to update the windows 10 for Lumia 532  using  OtcUpdater 8.2.1.0 after few minutes getting the error as follows " An error occurred while making the HTTP request to https://fe2.update.microsoft.com/v6/ClientWebService/client.asmx. T "

please help me to recertify the my problem

Windows for home | Other | Devices and drivers

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

64 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2020-11-08T15:16:25+00:00

    Just this

    \HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft.NETFramework\v4.0.30319

    Add 

    SchUseStrongCrypto --> DWord --> Value 1

    Was this answer helpful?

    7 people found this answer helpful.
    0 comments
  2. RedSpook-9082 4,765 Reputation points Volunteer Moderator
    2020-11-03T09:51:37+00:00

    Try the solution given in this post:

    https://answers.microsoft.com/en-us/mobiledevices/forum/all/otc-tool-server-issues-fix-here/03cc2165-71b5-4fd6-8e64-5065d2000838

    Solution in the post doesn't work (isn't it incomplete or something?). OTC Updater still can't establish a secure connection.

    There was a second post in that thread with more detailed instructions which the author has decided to delete, I have no idea why. This is now posted as a new thread:

    https://answers.microsoft.com/en-us/mobiledevices/forum/all/otc-updater/b2fb7107-7e1f-4d30-b441-7313524ceed4

    Try also this MS resource, the relevant information is at the bottom of the page:

    https://docs.microsoft.com/en-us/mem/configmgr/core/plan-design/security/enable-tls-1-2-client

    In short, MS have updated the properties of the servers which the OTC updater tool is programmed to look for, however they have not updated the OTC itself since W10M reached end of support in January this year and is no longer maintained. The only way to get it to work is by using the suggested workaround involving the registry edit.

    Was this answer helpful?

    5 people found this answer helpful.
    0 comments
  3. Anonymous
    2021-09-18T23:05:02+00:00

    I updated this registry (based on the link), and it worked.

    For 32-bit applications that are running on 64-bit OSs, update the following subkey values:

    [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft.NETFramework\v2.0.50727]

          "SystemDefaultTlsVersions" = dword:00000001

          "SchUseStrongCrypto" = dword:00000001

    [HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft.NETFramework\v4.0.30319]

          "SystemDefaultTlsVersions" = dword:00000001

          "SchUseStrongCrypto" = dword:00000001

    Was this answer helpful?

    3 people found this answer helpful.
    0 comments
  4. Anonymous
    2020-11-02T18:37:15+00:00

    Try the solution given in this post:

    https://answers.microsoft.com/en-us/mobiledevices/forum/all/otc-tool-server-issues-fix-here/03cc2165-71b5-4fd6-8e64-5065d2000838

    Solution in the post doesn't work (isn't it incomplete or something?). OTC Updater still can't establish a secure connection.

    Was this answer helpful?

    3 people found this answer helpful.
    0 comments
  5. Anonymous
    2020-09-23T02:37:02+00:00

    A readme file came with the OTC updater download.

    Read this file and comply with the requirements for running the updater.

    Was this answer helpful?

    3 people found this answer helpful.
    0 comments