Fake Info in Tweaking Tool

[Angelika]

Created = not created (Problem System Restore!)
I've tried some of scripts, commands and other FIX, but System restore hasn't worked for a long time!

https://i.postimg.cc/DzgPKzVP/sshot-2021-02-10-08-36-56.jpg

Pomyślnie utworzono punkt przywracania (Proces = C:\Windows\System32\wbem\WmiPrvSE.exe; Opis = Tweaking.com - Windows Repair 2021).
Successfully created restore point (Process = C: \ Windows \ System32 \ wbem \ WmiPrvSE.exe; Description = Tweaking.com - Windows Repair 2021).

[Boggin]

Yes, I know and I've already passed this onto Shane but as yet, it has remained unaddressed.

It says that it has created a restore point but on checking, it hasn't physically been created.

The registry backup also has a bug in it.

I'll email Shane about this again but my advice is to manually create your own restore point which I've advised in previous queries about this.

[Angelika]

manually create your own restore point which I've advised in previous queries about this.

It doesn't change the form of things.
Shows that a Restore Point has been created, but when reopening and checking, it shows "no restore point was created and it is every time".
System files are not corrupted sfc /scannow - always shows no repair is required! System - healthy!

===
Repair_Volume_Shadow_Copy_Service
C:\Program Files (x86)\Tweaking.com\Windows Repair (All in One)\Logs\10-02-21_12.10.12
===
Usˆuga Kopiowanie wolumin˘w w tle nie zostaˆa uruchomiona.

Dost©pne sĄ dalsze informacje Pomocy; aby je uzyska†, wpisz NET HELPMSG 3521.

Usˆuga Dostawca kopiowania w tle oprogramowania firmy Microsoft nie zostaˆa uruchomiona.

Dost©pne sĄ dalsze informacje Pomocy; aby je uzyska†, wpisz NET HELPMSG 3521.

Usˆuga Kopiowanie wolumin˘w w tle jest wˆa˜nie zatrzymywana.
Usˆuga Kopiowanie wolumin˘w w tle zostaˆa zatrzymana pomy˜lnie.

Usˆuga Dostawca kopiowania w tle oprogramowania firmy Microsoft jest wˆa˜nie zatrzymywana.
Usˆuga Dostawca kopiowania w tle oprogramowania firmy Microsoft zostaˆa zatrzymana pomy˜lnie.
===

[Boggin]

I've already given you my reply to this.

It is known that WR does not physically create restore points and I repeat my advice for you to manually create your own restore point.

I've emailed Shane about this and am awaiting his reply.

Until then I have nothing more to add.

[Angelika]

And I repeat that in the Manual creating a restore point panel shows the same all the time: Created but not actually created. Paradox 

[Boggin]

I've had a reply back from Shane on this and as it works on his machines, he's unable to replicate it but he will be looking into it.

It has something to do with the Windows' WMI files, but I don't think running the WMI repairs would resolve.

I'll check that out later.

Again, all I can suggest is to create your own restore point for the time being.

BTW - Shane has released v4.11.1 because of another bug he had found but unrelated to this.

[Boggin]

I've ran the WMI repairs in Safe Mode with Networking and after the reboot used WR to create a restore point but it still hadn't physically created one.

I even reset WMI with manual cmds from an admin Command Prompt and it still didn't physically create one.