EseDiskFlushConsistency is enabled. How do I disable it?

These moderators are as useless as tits on a boar. I swear to God

I can't say that this will eliminate your EseDiskFlushConsistency problem, however my Surface Pro 3 was logging hundreds of the Windows Logs, Application, Information, ESENT 916 events per hour, and I was able to reduce that number to one or two events an hour.  I hope someone more knowledgeable of the system is able to understand why this helps and provide a more complete solution.  To mitigate the problem, I cleaned up a couple of old and invalid index locations and then used the Troubleshooting Search and Index tool to automatically correct errors in the index database.  (Note: The Index is a necessary function and one should consider the maxim "first, do no harm" when contemplating changes).

To access indexing options...

Right-click the Windows Icon to access the pop-up menu

Click [Settings] in the menu which opens Windows Settings

In the [Find a setting] search box, type (without quotes) "control panel" and click [Control Panel] in the results.  

In the Control Panel change the [View By:] from [Category] to either [Icon] option and open the indexing options panel by clicking the [Indexing Options] icon.

To review and modify the index (following the above steps)...

In the Indexing Options panel, click the [Modify] button at the bottom to open the Index Locations panel

Click [Show all locations] to show hidden locations in the upper box.

(Note: On my computer, I had two invalid or incorrect locations, one listed started "CSC:// ... " and I believe I knew it was invalid by hovering the cursor over the location and reading the popup). 

To eliminate an indexed location, uncheck the box next to it.  (Note, that like nested folders, if you uncheck a parent folder, you also uncheck all children folders.  Similarly, checking a parent folder selects the folder and all children folders as well.

After reviewing and possibly modifying the indexed locations, click [OK] to close the dialog box and complete the changes (select [Cancel] to exit without making changes).  This will return you to the parent Indexing Options dialog box.  

To launch the Troubleshoot Search and Index  troubleshooter (following the above steps)...

In the Indexing Options dialog box, click [Advanced] to open the Advanced Options dialog box.

In the Troubleshooting section, click the underlined "Troubleshoot search and indexing" to open the troubleshooter. 

When the troubleshooter form asks "What problems do you notice" appears and prompts you to "Select all that apply," click to select only the one that indicates that search or index is slowing down the computer and then click [Next] to troubleshoot for any problems.  

(Note: the troubleshooter may prompt you to accept repairs or simply indicate that the corrupted index data has been repaired.)

When complete, close the troubleshooter and click the [Rebuild] button to rebuild the index.  This process will take some time, but runs in the background, so you can close the Advanced dialog box and use the computer as normal until the index has been rebuilt.  Once rebuilt, reboot your computer.  

After rebooting my Surface no longer appears to be bogged down, or freeze, and the number of events per hour dropped from approximately 150 to one or two per hour.  Hopefully this will be successful for you too.

Hi,

For more information regarding the issue with EseDiskFlushConsistency, refer to this link and follow the answer provided by the members.

Let us know if you require further assistance.

There was no answer provided.

In fact, the post just gives me a run-around to other posts that also don't have answers.

I provided several links and that link you sent uses one of those links I provided as a source.

Is anyone at Microsoft looking to sort this issue out? It's been 4 months and the issue hasn't been resolved (at least in relation to all of the posts I've seen).

I know you're just trying to help.

I know its not your fault.

I'm just frustrated from how long I've been searching for a solution before posting here.

I know the bug isn't "harmful" but, its beyond invasive with its lack of subtlety as a supposed background task.

Me too, I'm going around and around in circles with no real answers. 

Custom build pc. When it happens, and its random times everything stops for 1 - 2 seconds. 

I leave my pc running 24/7 and the logs show it happens all the time.