SOLVED
Home

Windows 7 and Release 19.222.1110.0006

%3CLINGO-SUB%20id%3D%22lingo-sub-1112769%22%20slang%3D%22en-US%22%3EWindows%207%20and%20Release%2019.222.1110.0006%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1112769%22%20slang%3D%22en-US%22%3E%3CP%3EAfter%20having%20OD%2C%20release%2019.222.1110.0006%2C%20deployed%20in%20our%20environment%2C%20we%20cannot%20authenticate%26nbsp%3Bwith%20the%20OD%20client.%20OD%20is%20available%20via%20the%20web%20and%20other%20desktop%20clients%2C%20such%20as%20Outlook%2C%20continue%20to%20work.%20After%20authentication%20fails%2C%20the%20error%20message%20returned%20is%200x8004de40.%20We%20have%20opened%20a%20ticket.%20Is%20any%20else%20experiencing%20this%20outage%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1112769%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EOffice%20365%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EOneDrive%20for%20Business%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1113834%22%20slang%3D%22en-US%22%3ERe%3A%20Windows%207%20and%20Release%2019.222.1110.0006%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1113834%22%20slang%3D%22en-US%22%3E%3CP%3EIn%20our%20case%2C%20Microsoft%20had%20removed%20support%20for%20TLS%201.0%20and%20TLS%201.1%20earlier%20than%20had%20been%20communicated.%20While%20they%20re-enabled%20it%20later%20in%20the%20day%2C%20the%20fix%20below%20will%20work%20for%20Windows%207%20and%20applications%20that%20require%20TLS%201.2%20support%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20title%3D%22Update%20to%20enable%20TLS%201.1%20and%20TLS%201.2%20as%20default%20secure%20protocols%20in%20WinHTTP%20in%20Windows%22%20href%3D%22https%3A%2F%2Fsupport.microsoft.com%2Fen-us%2Fhelp%2F3140245%2Fupdate-to-enable-tls-1-1-and-tls-1-2-as-default-secure-protocols-in-wi%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%22%3EUpdate%20to%20enable%20TLS%201.1%20and%20TLS%201.2%20as%20default%20secure%20protocols%20in%20WinHTTP%20in%20Windows%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
New Contributor

After having OD, release 19.222.1110.0006, deployed in our environment, we cannot authenticate with the OD client. OD is available via the web and other desktop clients, such as Outlook, continue to work. After authentication fails, the error message returned is 0x8004de40. We have opened a ticket. Is any else experiencing this outage?

 

1 Reply
Highlighted
Solution

In our case, Microsoft had removed support for TLS 1.0 and TLS 1.1 earlier than had been communicated. While they re-enabled it later in the day, the fix below will work for Windows 7 and applications that require TLS 1.2 support:

 

Update to enable TLS 1.1 and TLS 1.2 as default secure protocols in WinHTTP in Windows