Windows 10: SettingSyncHost (7996) Unable to read the header of logfile C:\WINDOWS

  1.    20 Aug 2015 #1

    SettingSyncHost (7996) Unable to read the header of logfile C:\WINDOWS

    I installed Windows 10 Pro yesterday and I've been checking Event Viewer and was receiving the following errors:
    SettingSyncHost (7740) {B72881E1-82AC-49AD-B8AE-71A0704F3457}: Error -1032 (0xfffffbf8) occurred while opening logfile C:\Users\Christopher\AppData\Local\Microsoft\Windows\SettingSync\metastore\edb.log.
    SettingSyncHost (7740) {B72881E1-82AC-49AD-B8AE-71A0704F3457}: An attempt to open the file "C:\Users\Christopher\AppData\Local\Microsoft\Windows\SettingSync\metastore\edb.log" for read only access failed with system error 32 (0x00000020): "The process cannot access the file because it is being used by another process. ". The open file operation will fail with error -1032 (0xfffffbf8).
    SettingSyncHost (7740) 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.
    So I thought I would manually those files (empty text documents renamed) and now I am receiving the error code: SettingSyncHost (7996) Unable to read the header of logfile C:\WINDOWS\system32\edb.log. Error -4001.
    How can I fix this error?
    Thank you
      My ComputerSystem Spec

  2.    20 Aug 2015 #2

    Yes, this one exists in the 10525 here too.
    I'm afraid only MS will fix this. The file is in use, and then falsely Windows tries to write into System32, which doesn't have the permission (there was a thread about this somewhere). Apparently MS only fixed half of the problem.
    Best report this to Microsoft directly (Feedback) if you are an Insider.
    If the report is that the file is in use, you can check via Process Handler in Process Explorer by which file. It will show you where the handle is open. For me, it was Cortana, which I am not touching. I had my share of problems with Cortana, and ended up repairing windows.
    It doesn't break anything else here though, so I simply ignore it.
      My ComputerSystem Spec

  3.    13 Sep 2015 #3

    Apparently turning off "Sync your settings" will stop the issue for now.
      My ComputerSystem Spec

  4.    14 Sep 2015 #4

    Turning that where off?
      My ComputerSystem Spec

  5.    14 Sep 2015 #5

    kosta said: View Post
    Turning that where off?
    Settings (app) > Accounts > Sync your settings > "Sync settings"
      My ComputerSystem Spec


Related Threads
Hello, I have installed Windows-10, and I'm encountering the problem that I can't read older Windows help files (attempt to read them will result in the display of I had the same problem in Windows...
I have yet to install Windows 10, but I wanted to see if someone could tell me (before I install it) if Windows 10's File Explorer can read ID3 v2.4 tags on MP3. And if it can't read them by default (as I suspect), is there any way to enable File...
Solved Random BSOD when gaming "BAD POOL HEADER" in BSOD Crashes and Debugging
Hello, so I've been experiencing a large amount of BSOD's when I game but I've recently upgraded to windows 10 in hopes of the issue possibly being fixed so the old crash dump files are gone. One bsod occured today, so I'll leave a download for it...
I tried updating to Windows 10 from Windows 7 Pro Sp1. Update went through fine but as soon as I get to the login screen and hit enter I get a BSOD with Bad Pool Header. I couldn't boot into safe mode, do the "reset my PC" option or system...
since installing Windows 10, I can not save updates to word files or anything to a folder. I've read I should change the user settings that default to 'read-only' in the system folder. I've done this 3 times. The fix doesn't work. Help!
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 13:58.
Find Us