How to make the Windows Event Log system service work in Windows 10?

Question

Windows

Attention, long and meticulous description of the problem!!!
I must say right away that I reviewed everything that is possible, in Google and Yandex. The situation is this: the Windows Event Log service in Windows 10 (Corporate version) does not want to start at all. When you start it manually through "Control Panel" -> "Administrative Tools" -> "Services", we see the following:

The fact is that in "Computer Management" there is an "Event Viewer", which, as I understand it, uses the "Windows Event Log" service . The following is displayed when accessing the event viewer:

This is logical, the service does not start. I started digging deeper, found different information. Below I will write what I did:

1. Unlocked the built-in admin account via the command line using the net user administrator /active:yes command. After that, everything that remained was created in her, because her powers are needed.
   
2. I checked the dependencies of the "Windows Event Log" service, everything this service depends on or who it depends on - works from automatic start. These services are:
   
   And in principle, all services that are set to start automatically - they all start, except for the log service!
   
3. I opened the C:\Windows\System32\winevt folder, which is written about in many instructions for solving my problem, added both for this folder and for the Logs subfolder in the rights of the LOCAL SERVICE user, who supposedly works with the log service, here is the confirmation:
   
   Here I added the "Everyone" user group for both winevt and the Logs subfolder, and gave it full access, just in case. Even for C:\Windows\Logs and C:\Windows\System32\LogFiles, I added LOCAL SERVICE to full control, as well as the "Everyone" group if possible.
   
4. Checked for the existence of the file C:\Windows\System 32\services.exe, it is in place. I don't think that's the problem, because then, I'm sure, other critical services did not start.
   
5. I also met crazy, it seems to me, advice to reset the routing tables via the command line using the route -f and net winsock reset commands . After restarted the computer.
   
6. Updated drivers via Iobit Driver Booster and DriverPack Solution Online (downloading the latest drivers).
   
7. I climbed into the Windows update, there was nothing sensible there, because I update periodically anyway, and I checked everything in advance so that everything that could be downloaded:
   
   
8. I changed the owner of all the above folders from "System" to the "Administrators" group on the advice of Vasily - it did not work.
   

The result of my torment is a sleepless night and no result! The problem is still the same!
PS: All this was started due to the installation of Microsoft Office 2007 on the computer, which clearly indicated the problem of write permissions along the path HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\EventLog, and there are also almost all subfolders that do not open with the same verdict:

After I I tried Microsoft Office 2016, it also does not want to be installed. I even went so far as to download the portable version of office in desperation, so he told me that services.exe gives an error 0x0000007e (a fairly common error, but considering that I previously learned about starting the log service using it, I think that portable office also climbs to the Windows log.
Phew, did you read it? :) Well, please help, suggest, maybe I did something wrong?? I don’t know what else to do, even though it’s really possible to take and demolish the top ten, install Windows 7 ...
UPD: Separately, I thought about whether it is possible to restore / reset the registry branch HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\EventLog by default? Like, the state of the service settings as in a freshly installed operating system. Are there any emergency methods?

Answer 1

access to the administrator can be denied for one reason (excluding "viral"), the owner of SYSTEM and the access rights to the administrator forgot to dump, appoint yourself as the owner and try further (although sometimes it is easier to demolish the system), for example, the recovery service fell off for me similarly.

Answer 2

The following helped me (I found it somewhere on Microsoft TechNet):

There was a similar problem. It arose as a result of disabling self-cleaning of logs (there was an overflow when the audit of the file system was enabled). As soon as I cleared the C:\Windows\System32\winevt\Logs folder, everything worked

Although the folder size was small, but after cleaning everything started up fine.