Frequently Asked Questions
Frequently Asked Questions
M-Files and Windows 10 1709 Fall Creators Update: "Access is denied" error
Posted by Sakari Heinonen (M-Files) on 27 October 2017 03:49 PM

Background

Starting October 17th, Microsoft's has started gradually rolling out the latest update to the Windows 10 operating system worldwide. It is called Windows 10 version 1709, the Fall Creators Update and it is continuation of the 1703 Creators update last spring.

M-Files and Windows 10 1709 Fall Creators Update

We have received reports of "Access is denied" errors after installing the Fall Creators Update update on systems that use RPC over HTTPS document vault connection. This renders the vault unusable.

The root cause for this behavior has been identified and we have a functioning workaround, see below.

Root Cause

This is a misfunction in Microsoft's Windows 10 Fall Creators Update. A brief summary of the cause: In Windows 10 version 1709, processes that run under "Local System identity" (like M-Files Client service) ask for HTTP/2 communication from the server. The server accepts this request at first, but then later refuses it with an error stating that HTTP 1.1 is required. This results to the "Access is denied" error on the client workstation. HTTP/2 support was first introduced in Windows Server 2016 (IIS 10.0), so the error is encountered with a combination of Windows Server 2016, RPC over HTTPS connection and Windows 10 Fall Creators Update.

M-Files has now concluded a process with Microsoft to find a fix to this error that affected many developers. Microsoft has given a statement that HTTP/2 is not currently compatible with RPC over HTTPS, and they will disable it in a future Feature Update of Windows 10. This will most likely happen in the RS5 Fall update around September. More information about Windows 10 releases here https://www.microsoft.com/en-us/itpro/windows-10/release-information.

The Workaround

M-Files Server

A functioning workaround to the issue is to set a registry key to disable HTTP/2 communication on a server that is running RPC over HTTP (RPC Proxy). Please note that this setting will affect all web sites on the server. 
Full server reboot is required after applying the setting.

Registry key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\HTTP\Parameters

Value name: EnableHttp2Tls

Value type: DWORD (32 bit)

Value data: 00000000

M-Files Client

If setting the above key on the server is not feasible, HTTP/2 communication can alternatively be disabled on the client computer running M-Files Desktop with the following registry setting. You need to restart the M-Files Client service for the new setting to take effect.

Registry key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Internet Settings\WinHttp

Value name: EnableDefaultHttp2

Value type: DWORD (32 bit)

Value data: 00000000

*IMPORTANT* You need to use only one of the settings: either the server or the client setting, not both. We recommend using the server-side setting because it ensures that the issue is solved for all client computers.


If you are not able to set either registry setting, the only other workaround to this issue is to roll back to the earlier version of Windows 10:

Open the Start Menu. Next, click on the Settings link.

Having opened the Settings panel, click on "Update and security" and here select Recovery settings.

Next click on the Get started button under Go back to an earlier build section.

The process will start, and you will be asked some questions for information purposes, as to why you are going back to the previous build of Windows 10.

The reason for the rollback would be:

  • My apps or devices don’t work on this build

M-Files Web Access, Mobile apps and M-Files Admin were not affected by this issue. M-Files internal tracker ID for this issue is 143722.

 

Last edited: May 30th, 2018

M-Files Customer Support Team, http://support.m-files.com

(29 vote(s))
This article was helpful
This article was not helpful

Help Desk Software by Kayako case