Windows 10: Event Log "beta site mode settings 0x800000" on Win10, 1709 and 1803

Discus and support Event Log "beta site mode settings 0x800000" on Win10, 1709 and 1803 in Windows 10 Support to solve the problem; Soon after I installed a new computer that came with Windows 10, I exported the Application Event Log to examine some messages that a program on which... Discussion in 'Windows 10 Support' started by TXWizard, May 10, 2018.

  1. TXWizard Win User

    Event Log "beta site mode settings 0x800000" on Win10, 1709 and 1803


    Soon after I installed a new computer that came with Windows 10, I exported the Application Event Log to examine some messages that a program on which I was working sent there. I almost didn't find them because they were overwhelmed by hundreds of "beta site mode settings 0x800000" messages.

    Following the recommendation of a trusted colleague, I upgraded from 1709 to 1803 (Redstone 4) the day it arrived, and have seen few of the legions of reported problems.

    This morning, I decided to have a look at the event logs to see whether the many "beta site mode settings 0x800000" messages have been shut off. No; they're still there, at least as numerous as before, maybe more so.

    While most refer to svchost, I noticed a couple that refer instead to MicrosoftEdge. They appear in the Application Event Log, which is in the active tab of Windows_Event_Logs_20180510_135835.xlsx (copy attached).

    Both worksheets in this book contain predefined imports that accept files generated by the SysInternals psloglist.exe utility, using the following command.

    Code: psloglist.exe -accepteula -d %3 -s -t \t %1 > "%~2"[/quote] In the above command line, a shell script (a .CMD file) makes the following substitutions.
    • %1 = EVTLOG: Registered name of event log, e. g., System, Application
    • %2 = PIPEFILE: Name of file into which to pipe the output
    • %3 = NDAYS: Number of days to dump, or "ALL" to dump all event records

    I created this shell script so long ago that I've forgotten what the switches mean; what matters most to me is that it just works.

    I would love to know how these messages can be shut off, so that they no longer clutter my event logs.

    :)
     
    TXWizard, May 10, 2018
    #1
  2. Magnazure Win User

    After the fall creators update, i am getting a new information event in my event viewer, event id 916, and would just like to know what it is

    I am receiving the event once to three times an hour, and the event description reads "The beta feature EseDiskFlushConsistency is enabled in ESENT due to the beta site mode settings 0x800000." What is this, and is it supposed to be happening a few times
    an hour?
     
    Magnazure, May 11, 2018
    #2
  3. Blue Screen of Death after upgrade to Fall creator update 1709

    After upgrade windows 10 to Fall creators update build 1709. My computer is constantly experiencing blue screen errors. I found the cause in the event log is due to ESENT (svchost (3924,G,0) The beta feature EseDiskFlushConsistency is enabled in ESENT
    due to the beta site mode settings 0x800000.). Please give me the solution
    Event Log "beta site mode settings 0x800000" on Win10, 1709 and 1803 [​IMG]
     
    SouthVietnam, May 11, 2018
    #3
Thema:

Event Log "beta site mode settings 0x800000" on Win10, 1709 and 1803

Loading...
  1. Event Log "beta site mode settings 0x800000" on Win10, 1709 and 1803 - Similar Threads - Event Log beta

  2. Update 1709 to 1803

    in Windows 10 Installation and Upgrade
    Update 1709 to 1803: Hello, I know, I know - countless problems with that update everywhere. In short: since the inception of the 1803 update in October 2018 my computer tries to bring that update to a good end - in vain. And this several times a week, with a considerable slowing down of the...
  3. Upgrade 1709 to 1803

    in Windows 10 Installation and Upgrade
    Upgrade 1709 to 1803: Hello Forum, Thinking about upgrading from 1709 to 1803 version, and I am doing some preparations not to be dependant on being online to upgrade. What I did so far: 1. Downloaded the Win 10 1803 (pro, English) installation file from this site:...
  4. Kernal Trap Mode - Win10 - 1803

    in Windows 10 BSOD Crashes and Debugging
    Kernal Trap Mode - Win10 - 1803: I've been getting this error and the only fix i have is to factory reset my computer. Ive did the MS verifier but and disable to drive. Still having the same issue. Uninstall all of my drivers and still unable to get pass Kernal Trap Mode. Startup Repair diagnosis and...
  5. Version 1803 or 1709?

    in Windows 10 Installation and Upgrade
    Version 1803 or 1709?: I have a Dell Inspiron 660S, 64-bit, running Windows Home Edition 10. After some recent Windows updates, I noticed I have version 1709 & OS Build 16299.666. In viewing my recent updates, I saw there had been a feature update to Windows 10, version 1803. It keeps showing that...
  6. Windows 1709 to 1803 confusion

    in Windows 10 Installation and Upgrade
    Windows 1709 to 1803 confusion: I'm running Win 10 1709.16299.492 on this desktop. I've got a download (automatic) which won't install for • Feature update to Windows 10, version 1803. I'd like to upgrade to 1803 but none of the downloads will install: KB4284848 or KB4338819. I can't get rid of...
  7. 1709 & 1803 MediaCreationTool cannot Download Win10 Home China

    in Windows 10 Installation and Upgrade
    1709 & 1803 MediaCreationTool cannot Download Win10 Home China: [ATTACH] then wait 5min USB bootable device OK. reboot computer. [ATTACH] my choise Win10 Home China ??????? where????? It has been posted on the Chinese language community many times and the staff there doesn't even acknowledge this is an issue....
  8. 1709 or 1803

    in Windows 10 Installation and Upgrade
    1709 or 1803: With all of the posts about troubles with the 1803 version, is it even worth it to install the new version? I have 1709 and am enjoying it. I have read about the add ons and deletion of the different things in 1803 and none of the new add ons I would even use. What is the...
  9. XPS Viewer was in 1709 not in 1803

    in Windows 10 Software and Apps
    XPS Viewer was in 1709 not in 1803: The XPS Viewer was in 1709 before the upgrade to 1803 and it is not in Apps and Features. How do I use Features on Demand with DISM to install the XPS Viewer? This does not work: dism /online /add-capability /capabilityname:XPS.Viewer~~~~0.0.1.0 See logfile 109643
  10. Beta map sites

    in Browsers and Email
    Beta map sites: I have been able to use a beta map site successfully until today. Despite numerous restarts, reboots and troubleshooting with Microsoft, I am suddenly unable to access the site that I've been using before. Other computers in my home can access the site so my suspicion is that...

Users found this page by searching for:

  1. The beta feature EseDiskFlushConsistency is enabled in ESENT 2019

    ,
  2. windows event log policy 0x800000

    ,
  3. svchost the beta feature esediskflushconsistency

    ,
  4. windows beta site mode,
  5. psloglist.exe /accepteula,
  6. svchost (3476 g 0) the beta feature esediskflushconsistency is enabled in esent due to the beta site mode settings 0x800000.,
  7. event 1202 win10 1803,
  8. MicrosoftEdge (2852 G 98) The beta feature EseDiskFlushConsistency is enabled in ESENT due to the beta site mode settings 0x800000.,
  9. svchost (11024 g 98) the beta feature esediskflushconsistency is enabled in esent due to the beta site mode settings 0x800000.,
  10. esediskflushconsistency logoff,
  11. svchost (4780 G 98) The beta feature EseDiskFlushConsistency is enabled in ESENT due to the beta site mode settings 0x800000.,
  12. svchost (4288 G 98) The beta feature EseDiskFlushConsistency is enabled in ESENT due to the beta site mode settings 0x800000.,
  13. The beta feature EseDiskFlushConsistency is enabled in ESENT due to the beta site mode settings 0x800000 Windows 10 1803