Announcing Windows 10 Insider Preview Build 16215 PC + 15222 Mobile Insider

What Tweaking.com Windows Repair does is firstly check that the Windows system repair tools are in place and not corrupted.

It repeatedly warns the user to back up the registry, to run the tools in safe mode and only run the tools that may help your problem.

It will restart your system in safe mode.

If for instance you have messed up your services by stopping some, and starting others inadvisedly, it can return your system services to default settings.

It performs corrective functions like restoring the Windows environment variables, and resetting reparse points to defaults, some of which are often missing in Windows 10 Insider builds, which are repairs difficult to find in other utilities.

It will run SFC /scannow. and DISM restorehealth etc., and reset Windows update.

It will save logs and has a fairly open system of readable scripts to indicate what it is capable of doing during the repair process.

I have never had any problems with it, and use it when, for instance, I find Insider preview upgrades of one build persistently failing, it has cleaned up the Windows installation so that the upgrade then progresses as it should.

I would not advise it is for everyone - certainly those that are impatient are likely to cut corners are more likely to get poor results from it.

If used as directed, it certainly seems that it can help.

Quoting myself from this morning:

Kari said:

I think I found a solution which resolves "The installation failed in the first boot phase..." and other issues that cause a failed upgrade. As I had made a Macrium Image before starting the upgrade process when upgrade was already downloaded and initialized, I have been able to replicate the failing upgrade and then fix it.

I want to be absolutely sure this works before posting the solution, I will replicate the failing upgrade scenario couple more times and if everything works post the solution. If it fails even once in my tests I'll post the words I use most often: "I was wrong" instead , but I really think this works.

Almost 17 hours testing, an hour and a half to write a post and make screenshots for it. Started at 9 AM my time, it's now 4:35 AM but finally here's a solution, at least a workaround to get upgrade done when everything else fails: When Insider build upgrade fails - A Workaround - Windows 10 Forums

Kari

I agree. Tweaking.com is an excellent tool. I bought the Pro version which comes with a bunch of optimization.

Good luck Kari. I hope your fix works. From what you are saying the problem isn't directly due to a multiboot environment so I'll be interested in the root cause. I figure you'll demur but if you do solve this I MS owes you a check.

martyfelker said:

Good luck Kari. I hope your fix works. From what you are saying the problem isn't directly due to a multiboot environment so I'll be interested in the root cause. I figure you'll demur but if you do solve this I MS owes you a check.

I found various culprits, and more interestingly different culprit on same machine in two tries in a row.

Hardware device drivers, user profile settings, existing boot menu (dual / multiboot) seem to be most common culprits. The solution as I found out was to run upgrade using a system profile instead of being signed in with a normal user account, and run upgrade before Windows loads all hardware drivers.

This works, I dare to say: When Insider build upgrade fails - A Workaround - Windows 10 Forums

Fisher Mann said:

Thank you Kari for your time and tireless determined effort. I will try it first thing in the morning.
That is some work around but it looks like you made it all quite clear.

Please post in that thread about how it went for you. I can hardly call it extensive testing when I only had two devices to test, plus some VM tests. Would be nice to know if it works for other users, too, or at least to know it didn't work (I'm fully prepared to post "I was wrong" once again ).

Thanks, Kari.

I don't need it at the moment, but I feel sure I'll need it pretty soon.

Brink said:

File History will eventually be replaced by the new Timeline feature.

Microsoft is introducing a new feature called Timeline - Windows 10 Forums

I am aware of timeline but my point was not only is fhb being retired, MS look like they are trying to drop the image backup again by making it very obscure again (like they tried in Windows 8 where tool was buried in a link at bottom of a screen).

One thing looks fairly certain - timeline is not an image backup tool. I really do not see what MS's problem is with imaging - I guess they want to promote their new sexy tool.

Personally I will stick with Macrium Reflect.