OTC Tool Server Issues?! -> FIX HERE

If you're having trouble with the OTC Tool not pulling the update down from the servers, this will more than likely be the fix. This is the info given to me from MS with some accompanying information as to why. I can confirm that updating this doesn't have any adverse effects on the registry and worked flawlessly for my updates. Hopefully this helps the people affected that I've seen around here for the past few weeks.

Windows Update service migrated to TLS 1.2 but OTC tool is built against .NET 4.0 that does not support TLS 1.2.

Support for Windows Phone 8.1 and Windows 10 Mobile has ended and that’s why also OTC is out of support and Microsoft is not making updates to that.

However, users can still get the existing OTC tool to work by adding the following values to the registry of the PC on which OTC tool is used.

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

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

      "SystemDefaultTlsVersions" = dword:00000001

      "SchUseStrongCrypto" = dword:00000001

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

      "SystemDefaultTlsVersions" = dword:00000001

      "SchUseStrongCrypto" = dword:00000001


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 discussion helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this discussion?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this discussion?

Thanks for your feedback.

* Please try a lower page number.

* Please enter only numbers.

* Please try a lower page number.

* Please enter only numbers.

hi , sorry to ask this but could you let me know how to do this in a bit more detail please ? i've tried my best but it still does not work and to be honest i dont really know to use the registry and there's not a lot of information online about this particular change to allow the phones to be updated to win 10. im running windows 10 home 64 bit on my PC

many thanks :)

44 people found this reply helpful

·

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

It seams that author copy-pasted with error from here: 

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

You need to update such values:

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

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

      "SystemDefaultTlsVersions" = dword:00000001

      "SchUseStrongCrypto" = dword:00000001

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

      "SystemDefaultTlsVersions" = dword:00000001

      "SchUseStrongCrypto" = dword:00000001


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

12 people found this reply helpful

·

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Still does not work.

Tried exactly as suggested.

Same after that:

An error occurred while making the HTTP request to https://fe2.update.microsoft.com/v6/ClientWebService/client.asmx. T

6 people found this reply helpful

·

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

It does not work and cannot work as it was not a full copy and paste from the original solution. See original solution below, but unfortunately that does not work either. Still says

An error occurred while making the HTTP request to https://fe2.update.microsoft.com/v6/ClientWebService/client.asmx. T

2 people found this reply helpful

·

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

These are the only instructions that worked to overcome the error:

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

One of the key pieces that many people miss: RESTART PC.

Unfortunately even though it got rid of this error:

"An error occurred while making the HTTP request to https://fe2.update.microsoft.com/v6/ClientWebService/client.asmx. T"

It failed to update my phone. Even though it is on the list of compatible phones, it is an old (I used it only for travel) Nokia Lumia 635. And Microsoft does include it in the list of compatible deceives.

But OtcUpdater 8.2.1.0 says:

58e309609037794754d2c3d31d585e19: Lumia 635(RM-975_1005) 8.10.12397.895

No updates are available for this device.  Please disconnect the device.


3 people found this reply helpful

·

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Internet Settings\WinHttp\DefaultSecureP

Name         Type          Data

DWORD    Reg_Sz      800

Is this correct??

2 people found this reply helpful

·

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

This worked for me ,but in the v2 and v4 there were no dwords so i had to create by right clicking then new dword 32 Rename the dword with the exact names SystemDefaultTlsVersions without spaces and SchUseStrongCrypto also without space  in both v2 and v4

Enter the hex value 00000001 in each created Dwords as you click okay ,close and restart the OTC tool , i never restarted the my pc but it still worked. 

  Thanks everyone anyway. 

That was lumia 640 LTE 

7 people found this reply helpful

·

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Nokia Lumia 635 with 1GB of Ram

1 person found this reply helpful

·

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Hi, Natalile!

Good catch. I updated the original post with the additional details. Funnily, I originally used the ones you posted and mine worked fine. Then the Microsoft rep said I only needed to do what I posted. So, I copy/pasted the info they had. That's my fault for not double checking. Apologies for the delay in responding here. Been a busy month.

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

There's a chance that the version of your device that it's detecting isn't available for upgrade. For instance, my Lumia 640s didn't work because they were "T-Mobile" versions of the 640. But ones that were flashed with universal firmware worked just fine. Sometimes, the carrier matters is what I've scene.

3 people found this reply helpful

·

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

* Please try a lower page number.

* Please enter only numbers.

* Please try a lower page number.

* Please enter only numbers.

 
 

Discussion Info


Last updated May 11, 2021 Views 7,227 Applies to: