Forum Discussion
One Drive for business stopped working on Windows 7
Same here, in some cases, we are running Windows 7 x86 Pro and have been contacted by these users to say they get the same error message. We tried an uninstall and reinstall, did windows updates and closed teams and managed to get logged in. It was short lived, a few hours later it dropped and now it's not working and the same method fails.
How are you checking the status is forbidden?
KyotoUK MarekCmikiewicz
Hi both,
I managed to fix mine shortly after I made this post. Hopefully it works for you.
Registry location: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.1\Client
DWORD name: DisabledByDefault
DWORD value: 0
Registry location: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.2\Client
DWORD name: DisabledByDefault
DWORD value: 0
- popolouApr 26, 2021Copper Contributor
It seems this page is being cached by Google so am adding to the solution here.
I have just had this same issue and what is described above is part of the process. You also need to consider this page where it explains the steps to control which protocols are permitted within Windows 7: -
https://support.microsoft.com/en-us/topic/update-to-enable-tls-1-1-and-tls-1-2-as-default-secure-protocols-in-winhttp-in-windows-c4bd73d2-31d7-761e-0178-11268bb10392
Once you run the Easy Fix Tool, you would want to go back and change the entry in both paths: -
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Internet Settings\WinHttp\DefaultSecureProtocols
and
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Internet Settings\WinHttp\DefaultSecureProtocols
to
aa0
As is said in the KB: -
By default in Windows, this value is 0x0A0 to enable SSL 3.0 and TLS 1.0 for WinHTTP. The above example keeps these defaults, and also enables TLS 1.1 and TLS 1.2 for WinHTTP. This configuration ensures that the change doesn't break any other application that might still rely on SSL 3.0 or TLS 1.0. You can use the value of 0xA00 to only enable TLS 1.1 and TLS 1.2.
Cheers
Pops
- MarekCmikiewiczApr 19, 2021Copper Contributor
Hi,
I carried out some tests based on what EpicTriffid wrote on Apr 16th.
The outcome is that the only thing which is necessary for One Drive to work again in Windows 7 is to install Easy Fix from this location https://support.microsoft.com/en-us/topic/update-to-enable-tls-1-1-and-tls-1-2-as-default-secure-protocols-in-winhttp-in-windows-c4bd73d2-31d7-761e-0178-11268bb10392#bkmk_easy
It is not necessary to uninstall KB3140245. It is not needed and not safe to change the value in registry under SSL 2.0.
Just Easy Fix which enables TLS 1.1 and TLS 1.2 as default secure protocols in WinHTTP, then reboot and THAT'S IT.
Works like a charm 🙂UPDATE:
I also had machines without KB3140245 initially installed. In those cases it was necessary to install KB and then proceed to Easy Fix.
- doctaeMay 29, 2021Copper Contributor5/29/2021
Had to uninstall update, then install updated update, then apply Easy Fix: everything works! Thank you! - saper_2May 20, 2021Copper Contributor
I had the same error 0x8004de40 only with OneDrive business account (on Win7pro). (I had checked already other things too: running network list service, KB3140245, TLS1.2 checked).
Using just "Easy Fix" did the trick 🙂 , shame that google won't put this topic (& solution) in top results.
Thanks MarekCmikiewicz and EpicTriffid for figuring this out. - KyotoUKApr 21, 2021Copper ContributorQuick update,
The two issues we had with Win7 x86 were new laptops that hadn't fired the auto script off. I edited the registry with the fix it tool linked above and all is working now.
Strangely had similar issues with a few android mobiles but a quick update of the app sorted these out.
- KyotoUKApr 16, 2021Copper Contributor
- alicja900Apr 16, 2021Copper ContributorThe solution doesn't work. I have all TLS (1.0, 1.1, 1.2) enabled and OneDrive still doesn't work. Are you planning to fix this?
- KyotoUKApr 16, 2021Copper Contributorclutching at straws, i'll give it a go.
Our Connectwise has a script that should run to force TLS 1.2 but one of the users had a new machine this week so it might be that the script hasn't run yet.
Only 2% of our Win7 users have reported the issue so far, I'll update once I know more.