OK, I got it!
How much space do I need to select for the restore point?
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Hello,
My PC crashed frequently due to a faulty memory stick. When I used a new memory stick, the problem didn't occurred anymore. Unfortunately, the crash also occurred during the windows update after the in-place upgrade. Until now, I have been unable to download and install two important updates -- the latest cumulative update and the update from August. (Two error codes (0x80070643 and 0x800f0805) appeared alternately)
I just tried Windows update troubleshooter and get a diagnosis --
WaaSMedicService
Issue found by :WinRETargetingPlugin
Problem with BITS service : The requested service has already been started. More help is available by typing NET HELPMSG 2182
Also, I've tried to perform the second in-place upgrade but ended in failure, an error occurred during the process(More details at https://answers.microsoft.com/en-us/windows/forum/windows_10-update/error-in-downloading-windows-10-cumulative/6ec330e1-c849-4b83-97db-286974f4290a?messageId=84f7d351-326d-49d5-8c7a-d154d5a69c89)
I hope all problems can be fixed without losing any data, please help me with a targeted solution as much as possible! Thanks!
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
OK, I got it!
How much space do I need to select for the restore point?
You may allocate 5% of the disk space for System Restore. There is 37 GB of free space.
I am trying to create a restore point, but I notice that ''turn on system protection'' is greyed out and the default setting is ''disable system protection''.
Should I create a restore point in this case?
In that case, you may skip creating the restore point.
Post the output log (fixlog.txt).
Sorry to keep you waiting, my browser's upload function got some issues, and now it return to normal. Here is the log --