Had a similar install failure with this update and worked on it for a few days. I found there's a conflict if you have an old install that goes back to Windows 8 where registry keys left behind by the old Windows Store bugs up the event logs for the new Microsoft Store and causes this update to fail.
The best place to start troubleshooting is in the "C:\Windows\Logs\CBS\CBS.log" and search for errors. If you look for the string "A rollback will be initiated" is a good place to look because right before that should be the problem that caused the update to fail.
And if you find any errors such as:
00000a04 (F) Error HRESULT_FROM_WIN32(15010) in eventsXml: <events><provider guid="{9c2a37f3-e5fd-5cae-bcd1-43dafeee1ff0}" message="$(string.eventProviderName)" messageFileName="%SystemRoot%\System32\LicenseManager.dll" name="Microsoft-Windows-Store" resourceFileName="%SystemRoot%\System32\LicenseManager.dll" symbol="Microsoft_Windows_Store">
Accompanied by:
00000a07 (F) Failed execution of queue item Installer: Events ({3bb9fd2b-351e-4b9c-b1fc-ed0758805998}) with HRESULT HRESULT_FROM_WIN32(15010). Failure will not be ignored: A rollback will be initiated after all the operations in the installer queue are completed; installer is reliable[gle=0x80004005]
Then you may also see above it:
00000a03 wevtconfig warning #77: Channel Microsoft-Windows-Store/Operational is declared by an existing provider Microsoft-Windows-Store-Client-UI{{53e3d721-2aa0-4743-b2db-299d872b8e3d}}.
And the fix is to just delete the following registry key, reboot and retry:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WINEVT\Publishers{53e3d721-2aa0-4743-b2db-299d872b8e3d}]
And otherwise, start with the logs and you should find the answer, but it might take some searching.