W10 email app crash, create file "C:\WINDOWS\system32\edbtmp.log" failed

[OppfinnarJocke]

Day before yesterday I installed the W10 "cumulative update for x64 systems" on my Surface Pro 3. YesterdayI did a cold restart. Since then the email app constantly crashes, it comes up and then just freezes until it eventually closes itself (or gets closed). The event viewer contains two events for each such attermpt.

First comes:
SettingSyncHost (4916) An attempt to create the file "C:\WINDOWS\system32\edbtmp.log" failed with system error 5 (0x00000005): "Access is denied. ". The create file operation will fail with error -1032 (0xfffffbf8).

And then:
SettingSyncHost (4916) Unable to create a new logfile because the database cannot write to the log drive. The drive may be read-only, out of disk space, misconfigured, or corrupted. Error -1032.

These are both generated by source ESENT.

I am a member of Administrators (and Home Users) and from File Explorer I could manually create a folder (did not get the option to create a file) in C::\Windows\System32. From an elevated command prompt I could create a file in the System32 directory. I have 425 GB free space on the SSD. So the problem doesn't seem to be "read-only, out of disk space, misconfigured, or corrupted."

Does anyone have any ideas?

 

[Tmagic650]

No luck fixing this? Maybe a future Windows 10 update will fix this... What version of Windows 10 are you using?

 

[OppfinnarJocke]

No fix for this one yet, no... This is W10x64 Pro

 

[Tmagic650]

Okay, I'm using Windows 10 Pro 64 bit with a trial version of Office 2016 and Outlook as my email client

 

[DelJo63]

"These are both generated by source ESENT." Isn't that MS Essentials? if so, just disable it and try again.

 

[Tmagic650]

Jobeard, esent.dll, the embeddable database engine native to Windows. Not MS Essentials

 

[Nikarax]

Had the same issue in the error log, the log file doesn't exist in the System32 directory, so I did the following:
1. created the edbtmp.log file in the System32 directory using an elevated notepad (Save as "edbtmp.log" with the quotes so .txt doesn't get added.
2. I then gave modify/write permissions on that specific file to the Everyone group.

Error messages seems to have stopped, but they were coming up intermittently so they may show up again. Will keep an eye on it.