Due to a state the local profile gets into for many users Of Microsoft 365, when editing a file from a WebDav server and Track Changes and There Are a Number of Edits, The Application Come to a Crawl

Dear Kyle_Carter,

Good day! Thank you for posting to Microsoft Community. We are happy to help you

Based on your description, we understand that when you read a Word document from a WebDav server, the reading speed is abnormally slow

I want to confirm if this behavior is related to the WebDAV server first, I noticed that you mentioned file interaction, and I was wondering if you would still get the same behavior if you upload the file to SharePoint for editing along with document change tracking. If you are separated from the WebDAV server, this phenomenon will not occur, and I think this phenomenon should be related to WebDAV. 

If this is the case, in order to further deal with the issue,  regarding your query on WebDAV . Please understand that this query is outside of our support boundaries. For you to be assisted properly, please reach out to Microsoft supported products on Q&A | Microsoft Learn; I am sure that our experts from that team can address your query effectively and accurately.  

Thank you for your cooperation and understanding. Please do not hesitate to post your queries in Microsoft Community and we will always do our best to assist you!  

Sincerely,

Tin | Microsoft Community Moderator

There is one possibility that can be checked easily. Go to File > Options > Advanced and, under the "Save" heading, turn on the option "Copy remotely stored files onto your computer, and update the remote file when saving" if it doesn't already have a check mark.

As you probably know, WebDAV is a protocol for transferring files over an HTTP connection. Word is designed to use temporary files, some of which are required to be stored in the same folder as the original document. For a large document, moving the data back and forth to the server could be slowing the program, so storing it locally during editing may improve the speed.

Thank you for your reply. Unfortunately checking this box has no affect on the responsiveness.

We are experiencing the same issue with our clients. This has started a month or two ago. Not all users of the same office are affected, even though they seem to share the same configuration.

One thing that seemed to help was removing the pc from the AD-domain.

We are also looking for a better solution which we can spread to all our clients.

Things we tried

Situation: windows 10 with office build 2304.

• Clear recent file cache of office 365: did not work

• Reinstall office 365: did not work

• Have a new user part of the same domain use the same computer: DID WORK

• Have the user which was experiencing the problem use a different computer for the first time: DID WORK

• Downgrade the version of office 365 by switching to the semi-anual channel and roll back office to version 2208: did not work

• Clear registry for word: remove HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Word: did not work

• Disable all COM-plugins: did not work

• Disable virus-scanner: did not work

• Remove the userprofile of the user on his computer and have him sign in again, recreating the profile: DID WORK

This made us conclude the problem lies somewhere within the local profile of the user. We were unable to locate where exactly. We'll now wait and see if the problem comes back or not.
We removed the profile for two seperate users (on two seperate computers), one with version 2208, one with version 2304, so perhaps it will show a difference at some point.

It's good to hear that we are not alone with this issue. I also appreciate you sharing your steps and what has worked for you and what hasn't worked for you. Trying what you explained worked to get our users out of the problematic state even if they were on what we thought were problematic versions of Office. Maybe those that said they had reverted back to the monthly patch channel and that fixed it for them actually were accidentally clearing out their profile as well.

We, as well, tried digging in deeper to see if there was anything surgically we could fix about the profile rather than just wiping it out entirely but were unsuccessful.

We are experiencing the same issue with our clients. This has started a month or two ago. Not all users of the same office are affected, even though they seem to share the same configuration.

One thing that seemed to help was removing the pc from the AD-domain.

We are also looking for a better solution which we can spread to all our clients.

Things we tried

Situation: windows 10 with office build 2304.

• Clear recent file cache of office 365: did not work

• Reinstall office 365: did not work

• Have a new user part of the same domain use the same computer: DID WORK

• Have the user which was experiencing the problem use a different computer for the first time: DID WORK

• Downgrade the version of office 365 by switching to the semi-anual channel and roll back office to version 2208: did not work

• Clear registry for word: remove HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Word: did not work

• Disable all COM-plugins: did not work

• Disable virus-scanner: did not work

• Remove the userprofile of the user on his computer and have him sign in again, recreating the profile: DID WORK

This made us conclude the problem lies somewhere within the local profile of the user. We were unable to locate where exactly. We'll now wait and see if the problem comes back or not.
We removed the profile for two seperate users (on two seperate computers), one with version 2208, one with version 2304, so perhaps it will show a difference at some point.

Firstly great reply by : Pieter Nys : rebuilding user profile worked for us, along with testing with other 'new' users profile on a different machine.

However this is not a great solution. Removing user profiles for 100+ users is not feasible. Is Microsoft able to pin point root cause of this issue?

It seems now our WebDav and Word experience when in Review mode is very slow. At a business level it impacts some of our regulatory processes.

also noticed something similar here: https://answers.microsoft.com/en-us/msoffice/forum/all/2307-2306-breaks-webdav-interactions-in-office/a83262b1-7bc9-4dc9-8497-31656f1d4583

Hi there,

This has plagued our staff as well and the only workaround we were able to find was the following:

Close all office applications (Outlook, OneNote, Excel, Word, etc)

Rename or delete "Computer\HKEY_CURRENT_USER\SOFTWARE\Microsoft\Office" reg key  (Will cause Outlook to lose profiles, must reconfigure after)

Rename or delete %localappdata%\Microsoft\Word (Or Excel, etc., depending on the circumstance)

Open Word (should display a box stating Office 365 was updated)

Open the problematic document. 

It's far from perfect but it's better than rebuilding the user profile for each one of our employees. This could ultimately be baked in to a logon script MECM deployment or maybe even as a GPO.

Hope it helps,

M

We are also facing the same issue, when end user editing document with track changes on and with webdav.

If user try to edit the same document with his own system word (not webdav) it's working fine, if tracking is off then also with webdav it is working

we are using 2305 version.

Any suggestion on this?

Any help would be appreciated

Thanks !!

Try this.

Rename or delete these two registry hives.

HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Common\ExperimentConfigs\Ecs\word\ConfigContextData

HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Common\ExperimentConfigs\FirstSession\word\ConfigContextData

It has been reported to fix the issue. Please let me know if it works.

Please note the name of the hives "ExperimentConfigs" I think they are experimental updates that Microsoft is pushing on some people. Which potentially explains why it only impacts some users and not all.

Thanks for this Office 42, can you also share the link of where else it was 'reported to fix the issue' ?

Kind regards,