Main Forum > Tweaking.com Support & Help

Registry backup

<< < (2/9) > >>

Boggin:
Update -

The repair install had no effect so I phoned MS Support who after showing him my error message proceeded to open a Command Prompt (Admin) and take own of the WindowsApps folder.

He then created a batch file to rename it to .old and then left me while I performed another system restore with a promise to phone me back in 20mins or so.

~40 mins has gone without any call back so far.

This one also failed with the same error message.

I had a look at the batch file he left on my desktop but wondering if he left something off in the final cmd - I'll get him to look at that if/when he gets back.

He wasn't aware of any reports about this and says anything to do with Windows Updates would need to be elevated and I had to persuade him that it was OS specific and not computer specific.

oldgray1938:
Boggin,
If you ever get a call back with a solution please email me so we can both be working with a PC where restore points work.  I have been trying everything for three months when I realized restore points were not working on my Windows 10 Pro PC.  Right now my only solution is to do a full image restore with my Ease US TODO backup program.

Thanks in advance.

Boggin:
That guy didn't call back yesterday so I phoned up this morning but she was working on the premise that it was computer specific and not OS specific.

Anyway, after she'd run a dism /scanhealth, /checkhealth and a /restorehealth - all of which came back clean, she then suggested a repair install.

I told her I'd already done one yesterday but she proceeded to download the ISO.

I then made my point that it wasn't machine specific with others getting the same problem and that it should be elevated and let them try it, as it had been proven to be as a consequence of January's update.

Given all I'd done and she had done without resolution, she chucked the towel in and agreed to elevate it.

Getting a call back tomorrow afternoon.

I asked her to try a restore point on her own Win 10 machine and she'd get the same error as everyone else has.

In the meantime I've restored the machine with an external image - reinstalled Norton Security and now waiting for a new system image to complete - it always takes hours on that machine.

I'm then going to boot up into the advanced boot options to select Command Prompt and enter the cmds as in Fix #5 of this article, substituting UserDomain for the full name of my laptop and UserName for my admin name.

http://borncity.com/win/2017/02/22/windows10-version-1607-system-restore-error-0x80070091/

You can get the full name of the machine by right clicking on This PC and selecting Properties.

I don't know when I'll be able to test them as there's still about a 3rd left to go on the image progress bar.

If you want to give them a go, to find which partition Windows sees your volume in before you enter the cd cmd, enter -

bcdedit |find "osdevice" which will give the partition letter to use in the cd cmd.

Just to clarify, that's a Pipe symbol before find and is the uppercase of \

Boggin:
Update -

The cd C:\Program Files didn't change anything in the WPE Cmd Prompt but worked in a normal Cmd Prompt (Admin).

I was able to do the takeown and icacls cmds but got an Access Denied for the attrib cmd and a file not found for the rename.

I then tried to delete the folder with rd /s WindowsApps as in the article and while it scrolled all the way through the files, each gave an Access Denied.

It's too late here in the UK for me to try the restore operation but will give it another go tomorrow - but not holding out much hope though.

Hope you have better luck with the cmds.

Boggin:
Success !

That restore point failed as I'd expected so I went back into the WPE Command Prompt and entered c: then entered cd Program Files

As I'd already done the cmds to take ownership and grant permissions, I just did the attrib unhide and rename cmds which were successful this time.

Entered exit to close the cmd window, shut down then rebooted and did the restore which came back as successful.

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version