Main Forum > Tweaking.com Support & Help

Serious problem with Windows Repair 4.3.0

<< < (4/4)

Boggin:
As you will have seen by jpm's post that this is under investigation, but you may be able to revert the condition by using the Registry Restore option in the program's Backup Tools.

Open the repair program and click on Backup Tools then Restore under Registry Backup.

Click on the Restore Registry tab and use the dropdown to select the auto created back up then hit Restore Now which will hopefully restore your system.

While I had a different problem caused by the repair program when I test ran it in 1809, it fully rebooted to normal mode.

I have since restored to 1803 to await MS's rerelease of the 1809 feature update, but I always create a Macrium system image before I test run the repair program.

WAWood8:
This sounds interesting -- when I have a chance, I will try it and report back

UPDATE: OK -- tried this and got mixed results.

When I rebooted back from safe mode, like before, witn WR 4.3.1, the display was out and the search box was unresponsive.

When I looked at restoring the Registry from backup, there were two listed: (1) the one I had made manually before running RW, and (2) one that WR made.

I restored using the second -- just to see what would happen -- and nothing changed.

So, I restored using the first, and the good news is that the display returned. But the bad news is that the search box problem was still there. And this time, unlike with WR 4.3.0, running the cftmon command did not "fix" it.

So, I restored from my MR image backup.

Boggin:
My 1809 froze after the reboot after test running 4.3.1

WAWood8:

--- Quote from: Boggin on November 09, 2018, 01:42:33 pm ---My 1809 froze after the reboot after test running 4.3.1

--- End quote ---
That's certainly not good!

Looks like WR has a problem with Win10 1809 -- and unless MS comes out with a re-release of Win10 1809 this week, I'm going to restore my PC back to Win10 1803 next week.

Boggin:
I created a Macrium image before and after the update to 1809 so I was able to take it straight back to 1803 but both 4.3.1 and 4.3.0 were causing a problem on two Win 10 laptops on 1803 and that was after the reboot, I was unable to access Services with an error message that Admin had blocked mmc.exe

However, when running 4.3.1 again on 1803 and it produced that error, I ran the program again which resolved that error.

Navigation

[0] Message Index

[*] Previous page