Main Forum > Tweaking.com Support & Help
Help line never replies to email Cannot back up Registry
Hugh Pratt:
Tom
many thanks
Hugh
Hugh Pratt:
Tom
Sorry to say that both discs had same error "... incompatible version..."
The issue is that the computer worked and "tweaking" Registry back up worked. No hardware changes - only new software.Then "tweaking" Registry back up stopped.
Looking at internet such as:
https://forum.acronis.com/forum/acronis-true-image-home-forum-older-versions/windows-7-repair-your-computer-f8-boot-option-not-working-solved#comment-96395
is this helpful as well above my pay grade? Seems to be for those who have non standard installations?
Hugh
Boggin:
No, I don't think that applies.
I've been wondering if it's confusing Win 7 with Win 10 and causing this error as all of the disks I've sent you work perfectly on my solo Win 7 laptop.
I'm unable to replicate your set up.
I think the best bet would be to perform a repair install on your Win 7 which won't affect your personal stuff or installed programs.
Boot into Win 7 - click on Computer - insert one of the Pro disks I've sent you and double click on its drive.
This will start the process and use the product key you got with the bought disk when prompted.
This can take 2hrs or so, so you will have to pick a time when you don't need to use your machine.
Hugh Pratt:
This is a complete re-install?
sfc /scannow is still unhappy!
1) I downloaded regback.exe - a free software. This appeared to operate in normal and safe mode. This backed up Registry including troublesome ntusers.bak
2) Tweaking only operates in normal and NOT in safe mode. This backed up Registry excluding troublesome ntusers.dat
sfc /scannow is still unhappy!
Is the free software then incorrect???
Boggin:
I don't know why the repair program won't work in Safe Mode as that is the recommended mode to run it in.
It could be because of the file corruption.
I'm not familiar with that regback.exe software, so I can't comment.
I'd go for the repair install as I've described and then perform another sfc /scannow which should then report no integrity violations.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version