Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - Willy2

Pages: [1] 2 3 ... 71
- I don't think this is limited to WR only. Because when I use a different program (e.g. Restore Point Creator) then sometimes that new SRP isn't  the usual size (think:  GBs). In that regard the way Windows (in my case Win 7 SP1 Pro) creates these SRPs is very confusing and "opaque". It seems to have its own (opaque) logic when it comes to making those SRPs.

- Run Antibody's WizTree. It will show you the size of those SRPs which are placed in the folder "System Volume Information". When I look at what's happening over there then I can't "make hay" of it, from time to time it's VERY confusing. E.g. the size of that one folder can be say 80 GB with say 10 SRPs but when I remove 9 SRPs then the size of that one folder will shrink only (very) modestly. I then have to switch off and switch off the SRPs feature in Windows to free up all that occupied diskspace.

- Shane wrote it because the previous program he was using for Windows Repair was more than "a bit  buggy". I DO know it can be run from the commandline with A LOT OF options. (No, I won't provide more info). But don't ask me all the specifics of the program. That's something Shane knows.

- In a subfolder in which Windows Repair is installed there's a program called "ManageACl.exe". With that program you can set the permissions for files & folders. Ask Shane for all the options that are available for that program. It has been written specifically for Tweaking's Windows repair to manage/set permissions for Windows.
- I think Shane should make it more accessible for advanced users and make a GUI for the program. But I know he's Always very busy.

Program & Site Requests / Re: Improvements for Windows Repair
« on: November 10, 2017, 08:30:19 AM »
When WR runs this repair then the following happens:
1) the process called "Explorer.exe" is killed/closed
2) the thumbcaches are deleted/removed.
3) then WR searches all logical drives for the file called "thumbs.db" (these are generated by Win XP and Vista (????)) and those files are then deleted.
4) The process "Explorer.exe" is re-started.

Suggestion to improve the program code:
- first determine which OS the user has and based on that let WR search only for the files called "thumbs.db" when the user has a XP or a Vista system. In all other cases let WR delete the thumbcaches only.

(this is based on the assumption that only Win 7 and newer use those thumbnailcaches and that the file "thumbs.db" is used only in XP and Vista.)

Another suggestion (independent from the previous one):
- Restart the process "Explorer.exe" before WR starts to remove the "thumbs.db" files.

- I also think that the programcode for the removal of the "thumbs.db" files needs to be improved. I think the code needs a few small but IMPORTANT code changes. Including 2 extra spaces at 2 particular spots. Because I am NOT convinced the current code is able "to do the job".

(@Boggin: Please pass this onto Shane)

5 Programs & Site Help & Support / Re: Resource Monitor
« on: November 05, 2017, 02:15:24 PM »
- Try if running this command (in the MSDOS window) helps:

for /f %s in ('dir /b *.dll') do regsvr32 /s %s, C:\Windows\system32

6 Programs & Site Help & Support / Re: Resource Monitor
« on: November 05, 2017, 12:56:56 PM »
- Windows Repair has a number of repairs that each fixes one part of Windows. Just run the program and see if your problem has been fixed. Windows is a complicated set of software. So, I am not sure if & what repair will/could fix this problem.
- My best guess is that you - at least - should run repair #4 ("Register systemfiles").
- You also can try the commands "CHKDSK" and "SFC /Scannow". Also included in Windows Repair.

7 Programs & Site Help & Support / Re: Resource Monitor
« on: November 05, 2017, 12:07:26 PM »
- Is the "Superfetch" Service running ?
- What do you mean by "Not populating" ?

Program & Site Requests / Re: Improvements for Windows Repair
« on: October 10, 2017, 11:00:30 PM »
- When Windows Repair starts then it runs (a stripped down version of ??) CLEANMEM. Suggestion: Add a weblink to the appropriate PcWinTech webpage in the logfile of Windows Repair.Then hopefully more people will start using CLEANMEM.

9 Programs & Site Help & Support / Re: Windows 7 and WMI
« on: October 09, 2017, 10:08:12 AM »
- Then I would check the SMART condition of the HD first. Run GSmartControl and see if any pink lines show up in the "Attributes" tab of that program (assuming you have HD and not a SSD). If the HD is (in the 1st stages of) failing then a re-install won't help either.
- Windows Repair sometimes puts a lot of strain on your HD.

(And I Always keep the last say 10 versions of WR)

- What OS are you running ?
- Does this happen in each version of Windows Repair or only the one (e.g. the last) version ?
- Running the Regsvr32 command for all *.dll files is not to be recommended. It's possible that you "break" more things in Windows than you "fix".

11 Programs & Site Help & Support / Re: Windows 7 and WMI
« on: October 08, 2017, 05:32:34 PM »
- I just re-installed Win 7 Pro 64 bit and the switche(s) for svchost.exe is -k netsvcs. A new fresh re-install is a good way to get rid of A LOT OF "pollution" of the registry (think: permissions, obsolete registry entries, etc.)
- Perhaps the users that have problems have installed some software that changes those/that switch(es) for WMI ??

- It's more complicated than this. Some repairs require a restart to get the changes taken into account (e.g. repair #26 and repairs that repair a bunch of Services) and others don't (e.g. #5).
- It also could mean that the software that's being used to restart Windows is corrupted. That software is build-in in Windows. In that case check the HD for errors (CHKDSK in Windows Repair) and/or run the command SFC /scannow (also in Windows Repair).

Program & Site Requests / Re: Improvements for Windows Repair
« on: September 18, 2017, 12:55:46 PM »
- There's another thing that can be improved in Windows Repair (WR) and it has to do with the process called "Explorer.exe". This is NOT something that causes Windows to (completely) "crash". It simply makes one program behave differently.

-I have a program installed called "Classic Shell".

When WR cleans the thumbs cache ("Repair Icons") on my Win 7 system then WR:
1) first "kills" the process called "Explorer.exe" with the MSDOS command "taskkill ........... ".
2) removes the thumb nail caches
3) and then re-starts "Explorer.exe" (MSDOS: "Start Explore.exe")

The problem is that then Classic Shell doesn't properly work anymore. I can use Classic Shell but then the behaviour has changed. The normal behaviour of Classic Shell is restored after I re-start my win 7 system.

- This problem doesn't occur when I use Task Manager to 1) kill "Explorer.exe" and 2) re-start Explorer.exe  again afterwards.
It seems that Task Manager executes some additional commands/tasks that allows Classic Shell to close itself without causing problems. I know that Windows issues socalled "Events" when it is about to do something that's could have/has a major impact on programs running. I know that one of those events is issued when Windows restarts the process called "Explorer.exe". I could imagine that WR should issue/send out such a "warning"/event as well when WR is about to "kill" Explorer.exe as well. Then programs, like Classic Shell" can prepare themselves better for "Explorer.exe" to be killed.

- I would appreciate when Tweaking - at least - would have a look at this problem. Perhaps there's a simple fix/solution for this problem ? Perhaps adding a (small) delay already would help to solve this ?

- Do readers of this post have other programs that don't function as they should when "Explorer.exe" is killed and re-started (in "Repair Icons") ?

14 Programs & Site Help & Support / Re: Windows 7 and WMI
« on: September 16, 2017, 05:59:21 AM »
- 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).

15 Programs & Site Help & Support / Re: Windows 7 and WMI
« on: September 14, 2017, 03:41:17 PM »
- Odd, very odd. I assume you ran all repairs ???
- I know how Windows Repair fixes/repairs the info for the WMI Service in repair #25. (No, no details). It seems that the info Windows Repair uses needs to be reviewed.
- WMI is used to pull up A LOT OF info from one's system. That's why it puzzles me so much that the switch "-netsvc" works on my Win 7 system (see above) and not on the systems reported above.

Pages: [1] 2 3 ... 71