Windows 10 Home Update Errors After SSD Disk Swap and EaseUS Todo Backup Clone

Hello,

I switched to a ssd disk in my laptop - a clone made with EaseUS Todo Backup. After replacing the disks, I made Windows Update (Windows 10 Home). Error 0x80080005 appeared. Trying again does nothing.
After links etc. I got to the command line where I did such steps
1.Dism / Online / Cleanup-Image / ScanHealth -> The operation completed successfully.
2.Dism / Online / Cleanup-Image / CheckHealth -> The component store is repairable. The operation completed successfully.
3.Dism / Online / Cleanup-Image / RestoreHealth / Source: F: \ sources \ sxs / LimitAccess -> appears Error: 0x800f081f Use the "Source" option to specify the location of the files that are required to restore the feature
4.Dism / Online / Cleanup-Image / RestoreHealth / Source: F: \ sources \ sxs -> Error: 0x800f0906 The source files could not be downloaded.
Use the "source" option to specify the location of the files that are required to restore the feature.

I also tried to get to Local group policy editor (gpeditor.msc), but it did not find startup after typing in the search engine. I tried to move 2 folders from syswow64 to system32 regarding group policy. It turned out that they were empty, and gpeditora.msc was different in this location.
MMC cannot open the file: /

Does anyone have an idea how to solve this problem effectively?

This is not always successful.
At least how is the difference in disk capacity.
it's best to reinstall everything.

If you still have an old HDD drive and the untouched data on it that you want to transfer to a new SSD, the best solution would be to make a post-sectoral copy, which will reflect all the 1: 1 data.
The condition is that the target disk must be equal (or larger) capacity from the disk from which the data will be ripped.
https://www.elektroda.pl/rtvforum/topic1330869.html

Dawiidos wrote:

using EaseUS Todo Backup.

Unfortunately, such programs effectively damage the structure of new "untouchable" systems above W7 (especially by doing the unimaginable - cloning from the level of OS, which is cloned).
Check clonezilla. The condition has already been given - the destination disk is the same or larger than the source disk.
ps. Recently I was rolling out a topic where the system did not fire with SSD even after successful cloning 1: 1 with HDD. Before we were blamed for bio-current and magic, there was a hypothesis for OS access to the HDD service zone; ?.