Windows 10 Creators Update: Error 0xc000000e on Restart

When I download and install the Creator Update (Feature update 1703), and then restart my computer, I get this screen:

I can bypass this recovery screen by going into 'UEFI Firmware Settings' (and sometimes 'Startup Settings') and using the 'boot override' option on my bootable partition. My system then boots normally from then on. (Even on further restarts.)

However, the update says it failed to install.

This is just using windows update from settings. I've also tried using the windows update assistant, and it produces the same issue (though I get the recovery screen for two boots with it continuing it's update progress in between).

Using a bootable USB and trying to repair my startup system failed:

Root cause found:

Unspecified changes to system configuration might have caused the problem.

Repair action: Result: Failed. Error code = 0x32 Time taken = 78 ms

Repair action: System files integrity check and repair Result: Failed. Error code = 0x490 Time taken = 321188 ms

Additionally, using bootrec /scanos from the command line in the bootable USB said it couldn't find any windows installations...

I am booting on an SSD with a HDD as my data disk.

Looking here (last post) suggests it might be a USB firmware problem. I do have a gaming mouse, could this really be causing it? (I'll try it again with my mouse unplugged when I have the time.)

Any ideas on how to push through the update without breaking my currently working system?

I tried updating using the windows update assistant again, this time with my mouse unplugged.

I got the same recovery screen and error, again bypassed it with the 'boot override' option, and this time I didn't get the screen a second time and upon booting into my account, I found the creators update was successfully installed.

Honestly I'm not sure if this was due to my mouse or not, since the same error occurred, but this time didn't seem to affect the update's progress.

It still gives the error screen every time I hard reboot or install updates (but I can bypass it as before), so if anyone has a real fix, it would still be appreciated.