• Still running Windows 7 or earlier? Support for Windows 7 ended on January 14th 2020. Please review the thread here for more details.

[SOLVED] No Restore Points in Vista

as mentioned, I am unable to resize the windows repair window, although it has that little triangle in the lower right corner. when I click that triangle I can move dotted lines as if resizing the window. the moment I let the triangle go, the lines snap back to the same size as before, as per the earlier screenshot. I suspect because of this issue I cannot see beta button nor cpu indicator etc in normal mode.
 
Let's check system volume information owners and permissions.
Upload both files, you'll find on your desktop after the following commands, here.

From an elevated command prompt:
Read More:
You should get SystRestOwners.txt on your desktop and it should be opened automatically.
I get (currently I have system restore disabled):
Read More:
Then, from the same command prompt:
Read More:
You should get SystRestInfo.txt on your desktop and it should be opened automatically.
I get (currently I have system restore disabled):
Read More:
 
@Xilolee & @Humble:
- "Tweaking's Windows Repair" has "a problem" when used on a Vista system. Then running repair #4 ("Register System Files") is known to break the "Volume Shadow Copy" subsystem. The solution is to always run repair #4 & #19 together.
- I hope this bug will be fixed soon. The author of the program has received a report on this bug. I hope it will get fixed ASAP.
 
Willy2: We did it at posts 78 to 80...

01 - Reset Registry Permissions
02 - Reset File Permissions
03 - Reset Service Permissions
04 - Register System Files
05 - Repair WMI
06 - Repair Windows Firewall
10 - Remove Policies Set By Infection
14 - Remove Temp Files
15 - Repair Proxy Settings
17 - Repair Windows Updates
19 - volume shadow copy service
21 - Repair MSI (Windows Installer)
26 - important windows services
27 - windows services default startup
Click to expand...
Or do you mean (intend?) only those two?

Humble: run this command from an elevated command prompt then post the result here (it will create whoami.txt on your desktop and the file will be opened):

((net user %username% & whoami) > "%userprofile%\desktop\Whoami.txt") & notepad "%userprofile%\desktop\whoami.txt"
Click to expand...
 
Last edited:
Willy2: thank you for sharing this valuable piece of information
Xilolee:

thanks for suggesting to execute whoami command. may I know why?

wondering what do we hope to gain from whoami in the context of RP fixing?
 
- @Xilolee: I checked that and you're right. You indeed did that in post #78.
- In repair #4 a large number of files are registered (think: REGSVR32) including a number of files that are needed for VSS. But these VSS related files are not registered in the right order and that (sometimes ??) "breaks" VSS. But the right order of registering (with the right switches) is done repair #19. So, #19 repairs what #4 breaks.
- The content of repair #19 is (for a 32 bit system):

cd /d c:\windows\system32

regsvr32.exe /s ole32.dll
regsvr32.exe /s oleaut32.dll
regsvr32.exe /s vss_ps.dll
vssvc /register
regsvr32.exe /s swprv.dll
regsvr32.exe /s /i swprv.dll
regsvr32.exe /s eventcls.dll
regsvr32.exe /s /i eventcls.dll
regsvr32.exe /s es.dll
regsvr32.exe /s wbem\stdprov.dll
regsvr32.exe /s wbem\vsswmi.dll
regsvr32.exe /s vssui.dll
regsvr32.exe /s msxml.dll
regsvr32.exe /s msxml2.dll
regsvr32.exe /s msxml3.dll
regsvr32.exe /s msxml4.dll
regsvr32.exe /s comsvcs.dll
vssvc /register

- I am starting to think that "Humble" could have a HD that's in the 1st stages of failing, with some "weak spots". Just a thought. But I see that Xilolee has much more experience.
 
Hey, Willy2, much appreciate your thoughtful input.

failing HD? well, hope not. then again, who knows, right?

I checked, shows good health in all HD diagnostics programs I tried.

any other ideas/suggestions you wish to share are certainly welcome
 
@willy2 & @xilolee

we did it !

after running repairs 4 & 19 together and rebooting, system created restore point
and I was able to manually create one as well.

thank you both very very much for sharing your expertise, your persistence...
your contributions to solving this issue.

keep up the good work!
 
p.s.: I should also mention that -- contrary to developer recommendation -- I ran this repair
( only 4 & 19 checked ) in normal, not in safe mode.

remember, earlier, 4 & 19 together with other items checked as per xilolee recommendations and running in safe mode twice had been unsuccessful.
 
- Perhaps more things were (a bit) "broken" on your Vista system and then running this program then helped to fix those other things as well.
- And then running #4 & #19 (only & together) helped the system to get (finally) back on its feet.
- Anyway, good to hear it was something (comparatively) simple.
- The VSS sub-system on a Vista machine actually is much more "vulnerable" than on e.g. a Win 7 system. See this thread:

Windows Repair task 04 (Register System Files) clobbering Vista VSS??

This issue simply must be solved in (one of) the next versions of "Tweaking's Repair"

Computers are complicated things, right ?
 
- @Xilolee: Do you mean that Piriform's Defraggler "breaks" VSS ? OMG !!!!! Is this limited to Vista ? I have used that program on a XP and Win 7 OS, and there it didn't cause any problems. But I don't have too much experience with Vista.
- I know that "Tweaking's Windows Repair" has more "tricks up its sleeves" for repair #19 but I am not going to "spill those beans" here.
 
@willy2: interesting question! I do not have an answer.

I had defraggler installed, used it and at one point it was set to boot defrag every time.

Could be interesting to study that topic further.
 
- Ah, starting (too much) programs upon start up could be the problem. Because then the OS is VERY busy doing multiple things. Then things can get messed up (comparatively) easy. Your Vista system seems to create/creates a System Restore Point upon start up. But Piriform's Defraggler also somehow triggers the VSS sub-system. Well, then there're, upon start up, two pieces of software that are competing to use VSS. Yes, that indeed could "break" VSS. (Xilolee ???)
- I have a number of programs that also start when I start my system. Using Task Scheduler to run those programs with a 3, 4 or 5 minute or any other time delay after start up makes that those programs no longer show "irregular"/unwanted behaviour (e.g. VERY high CPU).
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top