KB4474419 will not install

Okay,  I finally fixed it through a series of two actions.  I know just doing the first action by MS didn't solve the update, but it did solve the issue I was having with Windows Fax and Scan installing the fax driver.

1.  Grant access to the log folder as described by MS: 

https://support.microsoft.com/en-us/help/971256/error-message-when-attempting-to-start-the-windows-event-log-service-a

2.  Download and ran a free third party app called tweaking.com_windows_repair_aio that did the trick with repairing Windows Installer,  run it in Safe Mode:

https://www.tweaking.com/content/page/windows\_repair\_all\_in\_one.html

Great. I have the old install version with 100MB.

This little tutorial solved the problem!

Thank you.

It looks like many have tried different methods, but nothing works. The update clearly has bugs and needs to be fixed by Microsoft.

That is also my opinion. There are dual boot and single boot systems and both fail so I will for sure not change anything with the

boot drives.

This is clearly a Microsoft bug and they have to fix it.

So when can we expect Microsoft to fix this?

Please name a time frame or date.

My machine is always rebooting 2 times before I can access Win 7 Ult and this is absolutely senseless (I am using Windows only

for gaming because this is the last and only reason to use Windows at all).

Okay,  I finally fixed it through a series of two actions.  I know just doing the first action by MS didn't solve the update, but it did solve the issue I was having with Windows Fax and Scan installing the fax driver.

1.  Grant access to the log folder as described by MS: 

https://support.microsoft.com/en-us/help/971256/error-message-when-attempting-to-start-the-windows-event-log-service-a

2.  Download and ran a free third party app called tweaking.com_windows_repair_aio that did the trick with repairing Windows Installer,  run it in Safe Mode:

https://www.tweaking.com/content/page/windows\_repair\_all\_in\_one.html

It is completely senseless to run a third party tool that is not endorsed by Microsoft.

It may damage more than it can repair, also: who can guarantee no security issues?

This is still a Microsoft bug and it has to be fixed by Microsoft!

So when can you deliver, Microsoft?

Can we get a quote from some Microsoft official here, when this bug will be solved and with which KB?

It is very annoying.