Why is there no simple workaround for this? Why is it dead in the water and why can't we use another mechanism to verify the update files with SHA1? It's all be

Why is there no simple workaround for this? Why is it dead in the water and why can't we use another mechanism to verify the update files with SHA1? It's all been done before [1]. This would be an improvement, as it enables the project to continue working without any handcuffed relationship to Microsoft. [1] https://github.com/HyperSine/Windows10-CustomKernelSigners https://github.com/HyperSine/Windows10-CustomKernelSigners