Session "PerfDiag Logger" failed to start error: 0xC0000035 Event ID 2

If I try Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Diagnostics\Performance\ShutdownCKCLSet tings and modify to 128 I get Error Editing File Cannot edit MaxFileSize: Error writing the value's new contents.

I tried the test again by modifying the "Maximum Size" to both 64 and 200 MB and when I restart the computer this checkbox mark remains greyed out and shows 200 MB again.

Also when I try to apply any number whether 64 or 200 MB the Performance Monitor after clicking Apply crashes. After restarting computer even though I still get the Session "PerfDiag Logger" failed to start with the following error: 0xC0000035 PerfDiag Logger still appears to be running in the Performance Monitor Events Trace.

I have wasted many hours last year trying to fix it. Personally I don't think it is worth trying any more. This first started emerging since I started using Windows Update Blocker tool and even after I did windows system restore or reverted back to before, this error would no longer go away since. Do you use Windows Update Blocker tool by any chance?

I know that if I do reinstall windows this perfdiag logger error will probably disappear temporarily but it will probably return again after some time.

Otherwise there isn't really any computer issue afterall. This is a superficial error that I really couldn't care less as long as it is not affecting the use of the computer or performance, big deal.

Try running Regedit as an Administrator, that should allow you to change the "MaxFileSize" option.

I didn't use Windows Update Blocker tool. This problem started as soon as I upgraded from Windows 7.

For me this issue did cause some kind of a nuisance, because the computer is running much more smoothly than it was before I performed the fix. Programs, (especially browser windows) close and open more quickly. The whole system seems to perform better and is more stable. The whole computer just seems more snappy now.

No, I do not see any performance difference in terms of snappiness regardless of when the error log shows up or not.

Given the fact that this error shows up only on restart. If you shut down computer normally and turn it back on normally the error doesn't show up. Also it is completely random, and I have made experiments in both cases when the error doesn't show up and when the error does. There is absolutely no difference in computer performance or snappiness. No difference in game frames per second either. This is a placebo effect.

It is a similar error like Why Certain DCOM 10016 Events Don't Matter

Even EdTittel mentions that this doesn't affect computer performance in any shape or form. Ultimately the PerfDiag Logger will run and do its duties at some point. Most of performance issues are related to disk defragmentation. Superficial errors that happen randomly is psychological, because we don't want to see the errors piling up, not that it really has a negative impact on the computer performance.

I know for a fact that if I see ShutdownPerfDiagLogger.etl and if I see ‎22 ‎July ‎2020, ‏‎01:25:53 which is the time on my last restart, error won't show up.

But if I restart the computer now and I see still ‎22 ‎July ‎2020, ‏‎01:25:53 for example then I know the error will get logged for sure. But there is absolutely no difference in my experience when it comes to the computer performance with the error showing up or not.

Anyway, I tried running Regedit as Administrator and tried to modify "MaxFileSize" error is still showing up. It is only with this.

As far as my solution is concerned with Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\WMI\Autologger\EventLog-System\{b675ec37-bdb6-4648-bc92-f3fdc74d3ca2} at least modifying Enabled and EnableProperty value to a 0 will mean this error will not show up any more even when it is random and that's all that matters. The purpose of this is to hide the error so it is not logged.

Until I can find a proper solution that guarantees that the error won't show up on reboot only then I will try to change the value back to 1. As I see the error is not fixed with your method I decided to return the value to 0 again.

After much testing I can confirm that this error is indeed caused by the MaxFileSize parameter being too low to write the contents of the log file. Once I had changed the value to 250 (decimal) the Event 4 error went away. Very rarely now will I sometimes see the Event 2 error when shutting down, but I think that's because the logger is trying to start when the computer is shutting down. It's seems to be a timing issue that sometimes prevents the log from being written. The log successfully gets written now, and I can navigate to it's location and see that it has been successfully written. It's file size is usually always under 10MB.

To get around the problem of changing the key in the registry, simply follow these directions to gain full permission of the keys:
How to Gain Full Permissions to Edit Protected Registry Keys

Simply change the setting to 250.

As for performance now that the logger is running correctly.. Many strange issues have gone away. Most importantly for me the stuttering playback of streaming videos (YouTube especially) is now gone. I thought it was a misbehaving tab in my browser, or a browser setting (like hardware performance). Nope.. When I changed the MaxFileSize to 250 the problems went away, and now the computer is running more smoothly. I'm not 'seeing things'.

I'm very pleased now that my error log is empty (without disabling logging)!

I'm happy to say the Perfdiag logger is working just fine now. No more errors of any kind in my Event Viewer!

I have made the experiment last night after a long time. This time I managed to change MaxFileSize to 250 after gaining permission by changing Ownership to Administrators.

On one hand it seems that this method did improve the situation on shutdown the PerfDiag Logger error no longer shows up.

However, on restarts this error does show up but less than 10 minutes up time. I don't know if you have conducted this experiment but if you restart your PC after 10+ minutes then PerfDiag error will not show up!

Now there is a confusion here regarding the MaxFileSize when changing to Decimal value 0x000000fa (250) this number changes to fa. Fa signals that this is actually a false value!

Changing the value to 250 Hexadecimal 0x00000250 (592) will change the value to this. Which, when I look at google search from another poster https://h30434.www3.hp.com/t5/Notebook-Software-and-How-To-Questions/OS-Windows-10/td-p/7805784

This users screenshot shows as as 0x00000250 (592) for MaxFileSize. Anyway, I have conducted the experiment both ways and it makes no difference whatsoever!

If I restart the computer after 10 minutes following the boot then this error does not reflect regardless of whether MaxFileSize is modified or not. So in essence this is probably a waste of time and does little to get rid of the error.

Maybe this is solving the shutdown errors, but the restarts less than 10 minutes following PC boot will still show the PerfDiag Logger error. Now I believe you have not made this experiment, because frankly most people don't see the need to restart their computers less than 10 minutes following a boot. But the issue still remains even after Windows update!

Anyway SFC/ Scannow reports no integrity violations. This is a superficial error, although the user on the HP forum only made this change because he experiences freezing in videos that this change seems to rectify that. So I'll leave the change made. But the error as far as I am concerned will show up if restarts are made less than 10 or 11 minutes following boot. After 11-12 minutes error won't show on restart.

Thanks for the reply.

I performed the test and the error doesn't show up when I restart before 10 minutes. In my log I see the error was logged about 3 or 4 times this month (October).

I get this related Event 2 error more now:

Session "Microsoft.Windows.Remediation" failed to start with the following error: 0xC0000035

Same error code. From what I can gather this is because I have windows update paused. But I'm really not sure. I'm hoping all of this 'failed to start' task scheduler nonsense will be fixed in the next Windows version Updates, but I'm not holding my breath.

raedotted said:

Thanks for the reply.

I performed the test and the error doesn't show up when I restart before 10 minutes. In my log I see the error was logged about 3 or 4 times this month (October).

I get this related Event 2 error more now:

Session "Microsoft.Windows.Remediation" failed to start with the following error: 0xC0000035

Same error code. From what I can gather this is because I have windows update paused. But I'm really not sure. I'm hoping all of this 'failed to start' task scheduler nonsense will be fixed in the next Windows version Updates, but I'm not holding my breath.

Sorry for the late response. I can indeed confirm that I no longer get this error as long as there are no restarts or shutdowns before the 10 minute mark.

What I have identified is that PerfDiag is performing its task for 10 minutes or so if you look at the Performance Monitor by opening perfmon.exe you will see that in the Event Trace sessions this task runs for 10 minutes or so before the task and the service name disappears. Once this task disappears then restarts and shutdowns no longer produce the error as the task is completed.

But when this runs and the task isn't yet completed, restarts and shut downs disrupt the session from being completed, hence triggering this error.

Somehow this appears to be a bug at least for me on Windows 10 Version 1903 (OS Build 18362.720). Now I do not receive the
Session "Microsoft.Windows.Remediation" failed to start with the following error: 0xC0000035. I have never encountered this error at all.

But perhaps it is possible because I use Windows 10 blocker tool. You can have a try on this Windows Update Blocker v1.6
This will block Windows 10 updates from scanning as well as the service task schedule. Hopefully this should get rid of your error as this is probably related to the Windows 10 update. If it does not then this error is probably related to the latest version.

This is why I hate updating Windows 10 automatically because it often introduces new problems. I like to manually update when I want and not have it automatically do force updates until those updates are proven that they are not problematic.

Thank you for taking the time to reply. I haven't had the Perfdiag error anymore after the latest set of patches. I'm still on version 1909. The Windows.Remediation error only happens when I pause updates for as long as it lets me.

The Windows Update Blocker tool is brilliant so thank you for sharing that. I'll forward that on to the askwoody.com lounge where they are continuously monitoring the Windows updates for bugs. I'm sure they will also find it helpful.

The only other weird annoying Windows bug native to 1909 is the VSS error during shut down.

Event 13:
Volume Shadow Copy Service information: The COM Server with CLSID {4e14fba2-2e22-11d1-9964-00c04fbbb345} and name CEventSystem cannot be started. [0x8007045b, A system shutdown is in progress.

Followed by 8193:
Volume Shadow Copy Service error: Unexpected error calling routine CoCreateInstance. hr = 0x8007045b, A system shutdown is in progress.

I'm told there is a workaround where you can run a batch file to stop CryptSvc
https://answers.microsoft.com/en-us/...f-dd308487229e

I haven't bothered with it since I hear it's fixed in Windows ver. 2004, which I'm waiting to hear from Woody at askwoody.com that he feels is ready for prime time on his machine.

Onward!!

Does Perfdiag Logger run all the time. I see it at start up but later on I don't see it under events trace setting? Is this normal seeing it run and then not to see it? I sometimes get a error message in event viewer.