Have you tried restarting to see if it resolves itself ?
If you have access to another computer, you can create Win 10 install media to boot up with to try your restore points.
You can create the install media after reading the instructions at
https://www.microsoft.com/en-gb/software-download/windows10It's been found that you need to use Internet Explorer to download the Media Creation Tool (MCT).
Tap F12 as you switch on and use the cursor keys to select the install media - DVD or USB.
Insert the install media and press enter.
If using a DVD you may be prompted to press any key to boot from a CD/DVD.
When using an USB I've found it best to insert the USB before you switch on.
Navigate to the Install screen and select Repair your computer - Troubleshoot - System Restore
Click on Windows 10 - Next then click on a restore point then on Next and wait for it to complete.
If that fails to resolve then there are a number of steps in this article which may resolve -
https://answers.microsoft.com/en-us/windows/forum/windows_10-performance/error-the-user-profile-service-service-failed-the/d07201f9-0746-4cb4-a486-a5d1fb075f03You also get the option to use your restore points when switching on then use the power button to shutdown when the Windows logo comes up.
Do this another twice and on the third switch on it will go into Preparing Automatic Repair then Diagnosing your PC.
Click on Advanced options - Troubleshoot - Advanced options and then on System Restore.
However, in this mode you are given an account name to click on and then enter a password if you use one.
As your profile won't load in normal mode then I'm not sure if you will be able to try your restore points by this method.
If either method resolves the Profile error and you get Windows back up, open either a Command Prompt (Admin) or Powershell (Admin) and enter these cmds exactly as I've typed them.
dism /online /cleanup-image /startcomponentcleanup
dism /online /cleanup-image /restorehealth
sfc /scannow
Enter exit to close the cmd window and try your updates again.
Were you getting an error code when the updates were failing ?