Произошла неожиданная ошибка фильтра восстановления системы 0xc0000035

По правде говоря, ошибку 0xC0000035 может увидеть у себя в средстве просмотра событий любой пользователь. Она означает, что системе не удалось запустить определенную службу. Бывает довольно много ее разновидностей, в том числе связанных с Circular Kernel Context Logger, Kernel EventTracing, STATUS_OBJECT_NAME_COLLISION и другими. Однако самая распространенная ошибка выглядит так:

Не удалось начать сеанс «Microsoft.Windows.Remediation» из-за следующей ошибки: 0xC0000035!

Нужно ли что-то делать при ошибке 0xC0000035?

На самом деле вам ничего не нужно делать в большинстве случаев. Как говорят в одной из веток технической поддержки Microsoft, это одна из банальных ошибок, которая обычно не нуждается в дополнительном исправлении. Если ошибка не приводит к каким-нибудь реальным проблемам, можно ее просто игнорировать либо просто отключить отображение данного кода. Она появляется по той причине, что система просто не успела запустить какую-то службу или ее вызов был произведен слишком рано (до того, как успела запуститься). Обычная реакция Windows на подобный код – повторная попытка, которая в следующий раз заканчивается успешно.

Если вас не устраивает игнорирование данного кода ошибки, можете отключить его появление с помощью редактора реестра. Вот, как это можно сделать:

1. Клавишами Win + R запускаем строку «Выполнить».
2. Вводим в пустую строку команду rededit и нажимаем Enter.
3. Последовательно открываем Компьютер \ HKEY_LOCAL_MACHINE \ SYSTEM \ CurrentControlSet \ Control \ WMI \ Autologger \ EventLog-System \ {b675ec37-bdb6-4648-bc92-f3fdc74d3ca2}.
4. В правой рабочей области дважды кликаем по EnableProperly и устанавливаем значение для параметра – Hexadecimal, вместо стандартного Base. Если есть параметр Enable, ему тоже устанавливаем такое же значение.
5. Для параметра Value устанавливаем 0.

Если вы не можете мириться с данной ошибкой, то можете попробовать несколько способов. Несколько людей написали, что у них это сработало.

Что можно предпринять?

Вот все, что кто-то советовал и эффективность чего была подтверждена другими пользователями:

• Отключить протокол IPv6. Похоже, он в старых версиях Windows работает не очень стабильно. Для этого нужно перейти в «Центр управления сетями и общим доступом», выбрать «Изменение параметров адаптеров» и перейти в свойства того подключения, которое активно используется. Просто снимаем галочку с «IP версии 6», сохраняем изменения и выходим.

• Восстановить ассоциации. Некачественные установщики могут нарушить ассоциации системных файлов, из-за чего Windows не удается запустить службы. Самый простой способ – скачать с интернета reg-файл для восстановления ассоциации под конкретную версию Windows и запустить его.
• Обновить циклический регистратор контекста ядра. Служба создает снимки системы размером 100 Мб и в них могут быть проблемы. Нужно вставить в строку Выполнить %windir%\panther\ и найти setup.etl, а затем переименовать данный файл в setup.old. Система автоматически сгенерирует новый файл и, возможно, ошибка исчезнет.

В качестве итога можно отметить, что сама по себе ошибка с кодом 0xC0000035 не является чем-то экстравагантным, что требует исправления. Она появляется практически во всех операционных системах, когда Windows не удается запустить службу. В конечном итоге ОС повторяет запрос и выполняет поставленную задачу. Если каких-то дополнительных проблем ошибка не создает, ее лучше игнорировать. В остальных случаях можно попробовать те несколько решений, которые описаны выше.

Если у вы знаете что-нибудь еще, пожалуйста, напишите нам об этом в комментариях. Возможно, это поможет другим читателям в поиске ответа или нам в целях создания максимально полезного материала.

If you’re using the Event Viewer in Windows 11/10, then maybe in recent times, you’ve come across an error code 0xC0000035 that points directly towards a Kernel Event Tracing Error. This is not a new error, of course, but for many, this is the first time they’ve come face-to-face with it.

What is error 0xC0000035?

The 0xC0000035 error code come back as ‘STATUS_OBJECT_NAME_COLLISION’. This error code has been linked with an identical domain security identifier (SID) being detected. Furthermore, because ‘the event logger is full’ with Session, the “Circular Kernel Context Logger” did not start successfully.

What is the cause behind error 0xC0000035 in Windows 11?

It occurs when some processes fail to start. They could be network-related or other processes. some examples are PerfDiag Logger, NetCfgTrace, Microsoft.Windows.Remediation, sensorframework, etc.

Fix Error Code 0xC0000035 in Event Viewer on Windows 11/10

Because there are several ways to trigger error 0xC0000035 on a Windows machine, this article will focus on explaining how to get the job done via several of these ways.

1. Modify the Autologg registry key
2. Disable or remove your third-party antivirus
3. Update Intel or other Network drivers
4. Run Network Reset
5. Run DISM scan to repair system image

1] We suggest modifying the Autologg registry key

There are times when this error code doesn’t cause any form of problem at all. If you realize this is indeed the case, then the best step to take here is to prevent it from appearing in the first place.

Do this by opening the Run dialog box. Click on the Windows key + R, and from there, type Regedit and hit the Enter key. Right away the Registry Editor will appear

From within the editor, please navigate to the following:

Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\WMI\Autologger\EventLog-System\{b675ec37-bdb6-4648-bc92-f3fdc74d3ca2}

Once you’re within the right section, the next step is to go to the right of the Registry Editor and be sure to double-click on the Enabled key.

Now, from within the Edit DWORD (32-bit) Value, change the Base to Hexadecimal, then edit the Value data from whatever it is now, to 0. Click OK to save the changes.

After you have completed that task, you will want to double-click on EnableProperly and then change the Base to Hexadecimal and set the Value data to 0. Finally, click OK to save the changes.

The next step, then, is to reboot your computer and then check to see if error 0xC0000035 still persists.

2] Disable or remove your third-party antivirus

In some cases, your third-party antivirus could be the reasoning behind the 0xC0000035 error within the Event Viewer. We believe you need to disable your anti-virus program, then restart your computer to end the error, hopefully.

If that doesn’t work, then chances are you may need to remove the utility altogether. To get the job done in Windows 11, you need to fire up the Settings app by clicking on the Windows key + I. From there, select Apps > Apps & Features, then scroll down until you see your anti-virus program on the list.

3] Update Intel or other Network drivers

OK, so there are a few ways you can update Intel or other network drivers on your Windows 11 computer.

To begin, open the Settings by pressing the Windows key + I. From there, select Windows Update from the bottom, then click on the Update button to have the operating system check for new updates.

Should any drivers be available, Windows 11 will download and install them automatically, or request your assistance. This all depends on your particular Windows Update settings.

4] Run Network Reset

Another means to get rid of error code 0xC0000035, is to reset your network. This is a simple task to accomplish. All you have to do here is read How to Reset Network Adapters using Network Reset feature in Windows 11.

5] Run DISM scan to repair system image

Repairing your system image is one of the best ways to solve error code 0xC0000035. To do this, you must run DISM (Deployment Imaging and Servicing Management) right away. To learn how to scan your computer system using DISM, we suggest reading Run DISM to repair Windows System Image and Windows Component Store in Windows 11/10.

How do I fix kernel power critical error?

To fix the Kernel power critical error in Windows 11/10 PC, you need to turn off the Fast startup first. Then, you can run the CHSDSK tool to identify the potential error and fix it accordingly. Apart from that, you can test your PSU and check if there are some issues in the PSU or not.

Hope it helped.

Read: How to find and view BSOD log files in Windows 10 Event Viewer

Some Windows users are discovering that their Event Viewer is always filled with 0XC0000035 errors pointing towards a Kernel Event Tracing Error. This problem is confirmed to occur on every recent Windows version including Windows 7, Windows 8.1, Windows 10, and Windows 11.

After investigating this particular issue, it turns out that there are a few different causes with the potential of triggering this particular error. Here’s a shortlist of culprits that might be responsible for filling your Event Viewer with 0XC0000035 errors:

• Perfdiag is modifying the Event Tracing of Windows session – The ETW session is normally for private use only by the operating system. However, various factors might have it stuck into a retry look due to some async activity. In this case, the system interprets this as an attempt to modify the Event Tracing of Windows which is why the error is thrown. In the vast majority of these cases, the error should be considered completely benign and no action should be taken to resolve it. In this case, you can hide these benign errors by modifying a few registry values using Registry Editor.
• 3rd party AV interference – As it turns out, certain 3rd party AV suites are known to cause this issue due to an overprotective active shield feature. As it turns out, this particular issue can only be resolved by disabling the real-time protection or uninstalling the 3rd party suite and replacing it with a more permissive 3rd party equivalent.
• Outdated Intel Network drivers – If you’re using the network drivers fleet for Windows, chances are this issue is being caused by some kind of interference between the Intel WI-FI driver with a sensitive kernel process. In this case, you should be able to fix the issue by using the Intel Driver & Support Assistant to update your network driver’s feet with the latest driver equivalents.
• A network issue caused by Bad IP Range or DNS Cache – Under certain circumstances, you can expect to see this issue occurring due to a bad DNS cache or in a situation where you’ve been assigned a bad IP range. In this case, you should be able to fix the issue (at least temporarily) by flushing the IP and DNS cache from an elevated Command Prompt.

Now that you are aware of every scenario that might trigger this error, let’s get over some of the methods that other affected users have used so far to fix this issue completely.

Modify the Autologg Registry key

If the error is benign and you notice that it doesn’t affect the performance or behavior of your system, you can simply prevent the 0XC0000035 error from appearing inside your Event Viewer interface.

You can do this by navigating to the registry key used by the Autologg functionality and modifying the values of Enable and EnablePropertly.

Important: While this is generally harmless and will have no effect on your computer, it might hinder you from discovering a different issue that the Event Viewer might give you clues about. If you go through with this change, remember to undo this modification whenever you need to investigate something using Event Viewer.

If you are ready to apply this fix, follow the instructions below to ensure that your Event Viewer is no longer flooded with benign 0XC0000035 errors:

1. Press Windows key + R to open up a Run dialog box. Inside the Run dialog box, type ‘regedit’ and press Ctrl + Shift + Enter to open up Registry Editor with admin access.
2. When you’re prompted by the User Account Control, click Yes to grant admin access.
3. Once you’re inside the Registry Editor utility, use the menu on the left-hand side to navigate to the following location:

   Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\WMI\Autologger\EventLog-System\{b675ec37-bdb6-4648-bc92-f3fdc74d3ca2}

   Note: You can either get here manually by clicking on each key individually or you can paste the full location path inside the nav bar at the top and press Enter to get there instantly.

4. Once you’re inside the correct location, move over to the right-hand pane and double-click on the Enabled key.
5. Inside the Edit DWORD (32-bit) Value, set the Base to Hexadecimal, then change the Value data to 0.
6. Next, double-click on EnableProperly from the same key. Next, set the Base to Hexadecimal and Value data to 0. Click OK to save the changes.
7. After both registry values have been interfered with, reboot your PC to make the changes permanent, then make sure to return to the same Event Viewer and see if you notice any new instances of the 0XC0000035.

If you followed the steps above and you’re still dealing with the same consistent 0XC0000035 kernel errors, move down to the next potential fix below.

Disable or Uninstall 3rd party antivirus

As it turns out, a lot of affected users are blaming their 3rd party antivirus because of the constant 0XC0000035 kernel errors.

You can test out this theory by temporarily disabling the antivirus shield and seeing if the apparition of the kernel errors stops.

Test out this theory by accessing your antivirus settings and disabling the real-time protection and see if the 0XC0000035 error stops occurring.

Of course, doing this will be different from one AV tool to another, but typically you can disable the real-time virus protection directly by right-clicking ok the taskbar icon.

Unfortunately, if you discover that your 3rd party antivirus is indeed to blame, there is nothing else you can do other than uninstalling it.

Note: After you get rid of the interfering antivirus suite, the Windows Defender will take over automatically (unless you install a different 3rd party equivalent).

Follow the instructions below to get rid of the interfering 3rd party antivirus suite:

1. Press Windows key + R to open up a Run dialog box. Inside the text box, type ‘appwiz.cpl’ and press Enter to open up the Programs and Features menu.

   Note: If you’re prompted by the User Account Control, click Yes to grant admin access.

2. Once you’re inside the Programs and Features menu, scroll down through the list of installed programs and look for the 3rd party antivirus suite that you feel is interfering with your kernel processes.
3. After you locate the problematic antivirus, right-click on it and choose Uninstall from the context menu.
4. Inside the uninstallation screen, follow the on-screen instructions to complete the uninstallation process.
5. After the problematic antivirus is uninstalled, reboot your PC one final time and see if the problem is now fixed.

If this problem is still not resolved as you’re still seeing new instances of the 0XC0000035 error, move down to the next potential fix below.

Update your Intel Drivers

As it turns out, the 0XC0000035 error can also be caused by a severely outdated Intel Wi-Fi driver that’s interfering with a Kernel process. As it turns out, this is typically occurring if you recently upgraded from an older Windows version to Windows 11.

If the Event Viewer error references one of the following locations, it’s clear that the problem is surfacing due to an issue produced by an Intel driver issue:

• C:\Program Files\Intel\WiFi\bin\MurocApi.dll
• C:\Program Files\Intel\WiFi\UnifiedLogging\MurocLog.log

In this case, the only solution that is confirmed to fix this issue completely is to use Intel’s driver utility (Intel Driver & Support Assistant) to ensure that you’re using the latest driver version compatible with your Windows version.

Follow the instructions below to use the Intel Driver & Support Assistant utility to update your Intel’s Driver fleet to the latest versions available:

1. First things first, close any non-essential application from running and see that no resource-intensive process is running in the background.
2. Open your default browser and access the home page of the Intel Driver & Support assistant web utility.
3. Once you’re inside the Intel Driver & Support assistant utility, wait until the initial scan is complete, then click on the Download All button at the top to download the updated driver signatures locally.
4. After the download is complete, click on the Install All button (in the same place where the Download All button was previously) and wait until every driver is installed.
5. Depending on the drivers that need to be updated, you might be required to follow an additional set of instructions to get these drivers installed.
6. Once every driver installation is complete, reboot your computer one final time and see if the problem is now fixed.

If your Intel drivers we’re already updated to the latest or this scenario was not applicable in your particular scenario, move down to the next potential fix below.

Flush IP & DNS Cache

As it turns out, this particular issue can also be associated with an underlying network issue coming from a bad IP range or corrupted DNS cache data.

Several affected users going through the same problems and experiencing constant Kernel Event Tracing (0XC0000035) events have managed to get it fixed by using elevated CMD prompts to flush both the temporary data related to the IP and DNS.

For step-by-step instructions on how to do this, follow the guide below:

1. Press Windows key + R to open up a Run dialog box. Next, type ‘cmd’ inside the text box, then press Ctrl + Shift + Enter to open up an elevated Command Prompt.
2. When you’re prompted by the User Account Control, click Yes to grant administrative privileges.
3. Once you’re inside the elevated Command Prompt, type the following command in the same order and press Enter after each one to flush the IP and DNS cache of your PC:

   ipconfig /all
   ipconfig /Flushdns 
   ipconfig /release /all

4. Wait until the operation is complete, then close the elevated CMD prompt and restart your computer.
5. Once your PC boots back up, make sure DCHP is enabled before checking if any instances of the 0XC0000035 error.

Many Windows users reported that their Event Viewer is constantly flooded with 0XC0000035 error, indicating a Kernel Event Tracing Error. Every current Windows version, including Windows 7, Windows 8.1, Windows 10, and Windows 11, has been proven to have this issue

In most circumstances, the system detects a duplicate domain security identification, resulting in the context logger error: 0xc0000035 (SID). As a result, it appears to be more common in computers connected to a local area network.

Luckily the error won’t cause a problem with the functioning of the computer but when it appears the computer starts crashing and running slow. Also in some cases, the output devices fail to function properly.

Here in this article, we have put together the best possible solutions to fix Kernel Event Tracing Error 0XC0000035. But before directly heading towards the fixes it is important for us to understand the common culprit responsible for the error.

After a complete investigation, it was discovered that there are several possible causes for the error.  Here’s a quick rundown of what could be causing your Event Viewer to overflow with 0XC0000035 errors:

1. 3^rd Party Antivirus Program – It turns out that an overprotective active shield function in some third-party AV suites is known to create this problem. So, if you have installed any 3^rd party antivirus program then uninstalling it works for you.
2. Perfdiag is changing the Event Tracing of Windows session – The ETW session is generally reserved for the operating system’s exclusive use only. However, due to some async activity, it may be locked in a retry state due to various circumstances. The system reads this as an effort to change Windows’ Event Tracing, which is why the error is shown. So, in this case, modifying the registry entries works for you.
3. Outdated or corrupted Intel Network drivers – If you’re using the Windows network driver’s fleet, the problem is most likely caused by a conflict between the Intel WI-FI driver and a sensitive kernel process. Updating your network driver’s using the Intel Driver & Support Assistant may work for you.
4. Due to Bad IP Range or DNS Cache – In some rare cases the corrupted DNS cache or a faulty IP range can cause the problem. In this scenario, clearing the IP and DNS caches from an elevated Command Prompt might fix the problem.

Now as you are familiar with the common culprits, try the solutions listed worked for the affected users.

How Do I Fix Kernel Event Tracing Error: 0XC0000035?

Solution 1 – Identify the Error Location

Locating the error location in the Event ID is important, so first check the location and after that try the fixes given one by one:

• Right-click on the Windows Start button
• From the menu, choose Event Viewer.

• Expand the Custom Views branch on the left side and select Administrative Events.
• Make sure to sort the list as per the by Event ID.
• Examine all errors with an Event ID of 2 until you find the most recent error code 0xc0000035.

Now as you identify the location start following the solutions listed one by one to fix it completely.

Solution 2 – Restart your computer

Very first it is suggested to restart your computer, many times a simple restart fixes various glitches and bugs that cause confliction with the system.

• Click on the Start Menu and from the drop-down menu.
• Press and hold the power button.

• Click Restart your PC option.

Once your system reboots check if the error code is fixed or else head to the next possible solution.

Solution 3 – Try Enabling the SysMain/Superfetch Service

The Superfetch service is now known as SysMain in newer versions of Windows 10. They do almost the same thing. So, here it is suggested to enable the service as this worked for many users to fix the error.

Follow the steps to do so:

• Press the Win+R key to open the Run box, here type services.msc and hit Enter.

• Now sort the values as per their name.
• Locate the service named Superfetch or SysMain.
• And double-click on it for opening the Properties.

• Assure it is running as per the Service status. If not, click the Start button to see if any error messages appear.
• Then set the Startup Type to Automatic.

• And click the OK button.
• Restart your computer.

Solution 4 – Adjust the Startup Event Trace Sessions to Maximum File Size

If the Startup Event Trace Sessions maximum file size is insufficient, then this starts causing the problem and generate the error code 0XC0000035 Windows 10.

So, follow the steps to increase the file size:

• Press Win + R to open the Run box and type perfmon into the open text field > hit Enter
• From the left tree, expand Data Collector Sets.
• Select Startup Even Trace Sessions from the drop-down menu
• Scroll down until you locate the ReadyBoot entry in the main panel, then double-click on it.
• Then select the Stop Condition tab and set the maximum file size to 40 MB (or more).
• Close the Performance Monitor by clicking OK.

Check if this works for you but if not then there is a possibility your antivirus program is causing conflict.

Solution 5 – Turn Off or Uninstall Third-Party Antivirus

Many users confirmed that disabling the 3rd party antivirus works for them to fix the 0XC0000035 Kernel Event Tracing error.

So, temporarily disable the antivirus by clicking on the taskbar and disabling the security program. Check if the kernel stop error is solved. If in your case disabling the antivirus programs works and you stop seeing the error code 0XC0000035 then it is clear that your 3rd party antivirus is the culprit.

In this case, you need to uninstall the antivirus or contact the antivirus support centre and discuss the problem to check if they can offer any help.

Follow the steps to uninstall the antivirus program:

• Press the Win + R key to open the Run box, type appwiz.cpl and hit Enter

• Now in the Programs and Features menu, scroll to locate the antivirus program installed on your system
• Right-click on it and from the menu select Uninstall

• And inside the uninstallation screen, follow on-screen instructions for completing the uninstallation process.
• As the uninstallation process is finished, restart your system.

You can also use the 3rd party uninstaller to remove software or application completely, as manually removing the software won’t remove it completely some of its traces and junk files are left behind that cause conflict when you install the software next time.

Get Revo Uninstaller to Uninstall any Application Completely

Check if you are still seeing the 0XC0000035 error, then head to the next potential fix.

Solution 6 – Disable IPv6

Some of the networks won’t support the latest Internet Protocol Version 6 (IPv6), so there is a possibility your network is not compatible with IPv6 and there showing Kernel Event Tracing error: 0XC0000035.

Despite this Microsoft also suggested disabling the IPv6 to fix further issues and errors.

Follow the steps to do so:

• Press Win + R key to open Run dialog box > type Control Panel > hit Enter

• Click on the Change adapter settings option.
• And right-click on the first connection and select Properties from the drop-down menu.
• Uncheck Internet Protocol Version 6 (TCP/IPV6) under the “This connection uses the following items panel.”

• Click the OK button.
• For the remaining connections on the list, repeat steps 3-5.

If this won’t work for you, then follow the next solution.

Solution 8 – Update PC’s Intel Drivers

If you encounter error code 0XC0000035 on your PC, then it can be due to an outdated or corrupted Intel Wi-Fi driver that interferes with the Kernel process.

It can also appear when you update your Windows operating system to the latest Windows 11 version.

If Event Viewer error refers to the location below, then it is clear that the issue arises due to an Intel driver:

• C:\Program Files\Intel\WiFi\bin\MurocApi.dll
• C:\Program Files\Intel\WiFi\UnifiedLogging\MurocLog.log

In this situation, you can fix this problem completely by using Intel’s driver utility, but make sure that you are using the latest version of the driver which is compatible with your Windows OS.

Follow the given below instruction to do so:

• First, select non-essential apps that run on your PC and check that no resource-intensive process is running in the background or not.
• Now, open the web browser and visit the official page of the Intel Driver & Support assistant web utility.
• Once you enter the official Intel driver page, wait until the initial scanning process is complete.
• Now, click the Download All button from the top of the screen.
• After completing the download process, now Install All the buttons in the same place where Download All button is stored previously and also wait till the driver is installed properly.
• Now, wait until the driver installs successfully. but make sure to reboot your PC after the installation process is complete.
• Now, check your PC, if your problem is fixed or not.

In case your Intel drivers are up to date and you keep getting the same error message, then proceed to the next solution mentioned below.

Solution 9 – Upgrade the Network Driver

If updating the Wi-Fi driver won’t work for you then there is a possibility that other outdated network drivers are causing the error.

So, check for the outdated drivers and update them:

• Press the Win + R key and in the Run box that appears type devmgmt.msc and click OK

• And in the Device Manager window right click on the LAN device from the drop-down menu, choose Update driver
• Now click on Search automatically for updated driver software.

• Confirm if any confirmation window prompts and close the window.
• Restart your computer.

Manually updating the driver is very time-consuming and sometimes won’t update it, so you can also update the drivers easily with the Driver Updater, this is an advanced tool, that update the entire system drivers automatically.

Get Driver Updater, to Update Device Drivers Automatically

It is estimated the given solution work for you to get past the 0XC0000035 error inside the Event Viewer interface. But if still facing the error then the only option left is to modify the registry keys.

Solution 10 – Change the Autologg Registry key

If none of the above-listed solutions works for you then modifying the registry entries works for you. This is can be easily done by heading to the registry key utilized by the Autologg functionality and changing the Enable and EnablePropertly values.

Please Note: These steps are usually won’t cause any harm to your system functioning, but this may stop you from finding the different problems which Event Viewer may give you signs about. So, if you find any change the undo the modification at the time you require to investigate something using Event Viewer.

So, make sure to follow the steps given carefully:

• Hit Windows + R Key for opening the Run box and type regedit, hit the Enter key

• And as prompted by the User Account Control then click Yes.
• As you are inside the Registry Editor utility, on the left-hand side use the menu for heading to the location:

Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\WMI\Autologger\EventLog-System\{b675ec37-bdb6-4648-bc92-f3fdc74d3ca2}

Please Note: You can get here by manually clicking on each key particularly or else you can simply paste the full location inside the Navbar and hit Enter

• As you are inside the location, in the right-hand double key on the Enabled key
• Then inside the Edit DWORD (32-bit) Value, make sure to set the Base to Hexadecimal, and modify the Value data to 0.

• Now, from the same key double-click on the EnableProperly option. And, set Base to Hexadecimal and the Value data to 0 after that click OK for saving changes.
• As both the registry values are interfered with, restart your computer to let the changes take effect.
• And return to the same Event Viewer and check if you see any new cases of the error 0XC0000035.

So, now the Kernel Event Tracing error code 0XC0000035 is fixed, but if you are not lucky enough and still see the error on your Windows system then the only option left is to reinstall your Windows 10 system

Recommended Solution To Fix Windows Errors & Optimize its Performance

Windows system tends to slow down after a certain period of time or start showing various stubborn errors, so it is very important to clean Windows PC/laptop at regular intervals.

Running the PC Repair Tool works for you to fix various internal PC errors, remove junk files, clear registry entries, prevent malware or viruses, repair system files and much more.

This is an advanced and multifunctional tool, that just by scanning once detect and fix various errors and optimize the Windows PC performance.

Get PC Repair Tool, to Optimize Windows PC Performance

Conclusion

So, this is all about the error code 0XC0000035, here I tried my best to list down the best possible solutions to get past the error.

It is estimated that one of our solutions listed managed to fix the error 0XC0000035 Windows 10.

Try the solutions given one by one carefully till you find the one that works for you.

If there is anything that I missed out on, or you have any queries then feel free to share with us on our Facebook page.

Good Luck..!