Main Forum > Tweaking.com Support & Help
Windows 7 and WMI
Willy2:
- Some (final ??) additional thoughts:
- "Security Center" and "IPhelper" are stopped by repair #5 & #18 but not (re-)started. The PRO version of Windows Repair allows the user to automatically run the *.bat script (see one of my previous replies in this thread) that will start those 2 Services.
- But the start-up states of these 2 Services are not changed. So, when the user restartes one's system then these 2 Services will be (automatically) started again.
- If the user wants to then he/she can modify the startup states of one or more Services. Instructions on how to do that are provided in the "Repair Info" of repair #26.
- This question/problem makes it clear that I need to do some additional research. (I know what to look for).
Still_Game:
--- Quote from: Boggin on September 15, 2017, 05:47:05 am ---Others have also commented on the actual restore point not being created in Win 10 even though it says it has with a date and time stamp.
There's no such problem in Win 7.
Initially from Win 8 a new restore point wouldn't be created within 24hrs of the last one but Shane has told me that WR changes that frequency, although it hasn't resolved it for me and the restriction has never applied because of the time difference of days since the last one was created.
It is the same on both of my upgraded Win 10 laptops.
It's better to rely on the Registry Backup than on any restore point WR has said it has created, but unless you know about the lack of physical restore points and you try to restore from within the program then you could have problems.
I'll raise this again to see if it can be resolved.
--- End quote ---
Actually, Boggin, I've found that System Restore points are not reliably created on my laptop under Windows 7 Home Premium 64 bit from within WRAIO but work OK when created and restored using the inbuilt Windows 7 procedures. I've reported this before.
Boggin:
Sorry, I'd assumed all reports related to Win 10 - bad memory.
Still_Game:
No problems - though it's something that needs fixing (not your memory😀).
win7user:
Same issue here on Windows 7 SP1 Home Premium 32-bit...
Using Tweaking.com v4.0.7, and after running Windows Repair, a number of services wouldn't start or work. Spent a considerable amount of time trying to troubleshoot the issue, but fortunately had done a Registry Backup.
Restoring the registry seems to have fixed the affected services, but continuing to have other residual problems. Overall the system is functioning worse than before running Windows Repair. Currently leaning toward reformatting the drive and reinstalling the O/S.
It appears that at a minimum Windows Repair causes bad/corrupted image paths for the services... very disappointing.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version