WR v3.xx issues

[Shane]

There is a bug with the program going pro when a users date and time on the system has words in it, that is fixed.

Added the service to the repair windows updates, Wu.upgrade.ps.dll is already in the repair.

Updated the repair mdac with the two new files as well

Good call on adding the deleting of the thumbs.db

I actually have a bat file I use on my own system that will work with unicode paths as well, I will add this to the repair and have it set to do all fixed drives on the system.

@echo off
chcp 65001
@echo Looking for Thumbs.db files...

set "_dest=C:\"

cd /d %_dest%

for /f "delims=" %%i in ('dir /l /s /b /a:-d thumbs.db') do (
if /i "%%~nxi"=="thumbs.db" (
@echo "Removed - %%i"
ATTRIB -A -R -S -H "%%i"
del /f /q "%%i"
)
)

Shane

[Willy2]

- I now have a list with registered files on a 32 bit Vista system. And came across those 2 MDAC files that weren't registered by WR.

[Willy2]

- I must re-write reply #13.

- In Win XP (and Vista ??) MS used a file called "thumb.db" to store a thumbnail copy of picture files (*.jpg, *.gif, *.bmp, ......... ) in any given folder. And that file could be found in each folder if the user has stored such a picture file in that folder and had opened that folder once in Windows Explorer.

- Starting with Win 7 (or started it with Vista ??) MS used a different system to store these thumbnail copies. Then all those thumbnails were stored in one file called e.g. "thumbcache*.db". But I noticed that on my Win 7 MS seems to have forgotten to extend this system to the folder called "c:\users\<--Username-->\Pictures". There MS still uses the "thumbs.db" system.

- But I don't know if this bug is also present in Win 8 & Win 10. Boggin ???

[Boggin]

I'm not into the finer points of WR but if you have any concerns then I'll pass them onto Shane.

One of the improvements added to 3.9.14 is this repair now checks and removes all thumbs.db files as well.

[Willy2]

- Do you have a Win 10 system ? If so, then open "My pictures" and close it. and then search (e.g. with Voidtool's EVERYTHING) for "thumbs.db". Perhaps MS forgot to strip that code (that generates the file called "thumbs.db") from Win 10 as well.

[Willy2]

- Suggestion: Move repair #10 up the list of repairs and make it repair #05 or repair #04. I think #10 is actually too important to have a such a low ranking.

[Willy2]

- (Small !!) Bug in repair "Repair Icons" ???  In the part where "thumbs.db" are deleted, I saw this

     ">>"

shouldn't that be

      "1>>" ??

[Willy2]

- Shouldn't the "Pre-Repair Commands" be run first as well when the user runs the repair called "Repair System Restore Beta" ?

[Willy2]

- Topic:  "Register Adobe's Flash player".

WR is able to register Adobe's Flash Player related file/files on a Win 8 (and a Win 10 ??) system. But WR isn't able to register the player on a Win 7and a Vista OS. The reason is that on a Win 8 (& Win 10 ?) system with a new update, the name of that Flash Player file always is the same ("flash.ocx"). Whereas on a Win 7 & Vista system that name always changes with every new update. The name includes a reference to the version.

(Does Adobe still support Flash on XP systems ?)

- But in spite of that there's a way to get these Flash files (re-)registered. MSDOS has a command that will do the trick.

   FOR /R "%%systemroot%%\system32\macromed\flash\" %%G in (*.ocx) DO ("%%systemroot%%\system32\regsvr32.exe" /s "%%G")

And a similar command must be used for the "Syswow64" folder.

With this command it doesn't matter what the new name is of the Flash Player file. This command simply registers all *.ocx files in that one folder.

To be added in repair #4 !!!

- But then the program code for this repair #4 must be changed as well. Currently this repair has its own peculiar way of registering files. Then registering files in repair #4 must be changed to how e.g. repairs #7, 8, 27 executes a bunch of commands. Changing the program code for this repair also would allow WR to register system files in the %commonprogramfiles% folders.

[Samson]

(Does Adobe still support Flash on XP systems ?)

Yes, still supported, currently using 23.0.0.205 on FF and Pale Moon.

[Willy2]

- Another bug in repair #4 !!!! And this is a MAJOR one !!! Repair #4 will ALWAYS target the folders C:\Windows\system32 and C:\Windows\syswow64, even if the user has installed the OS on any other (logical) drive (e.g. D: or E:).

Here's an example for this repair. Repair #4 contains - among others - these 2 lines:

    %SystemRoot%\system32\regsvr32.exe "C:\Windows\System32\asctrls.ocx" /s
    %SystemRoot%\sysWOW64\regsvr32.exe "C:\Windows\SysWOW64\asctrls.ocx" /s

It should be:

    %SystemRoot%\system32\regsvr32.exe "%systemroot%\System32\asctrls.ocx" /s
    %SystemRoot%\sysWOW64\regsvr32.exe "%systemroot%\SysWOW64\asctrls.ocx" /s

[Willy2]

@Samson: What's the full path of that *.ocx file on your XP system ? Do you have a 32 bit or 64 bit XP system ?

[Samson]

@Samson: What's the full path of that *.ocx file on your XP system ? Do you have a 32 bit or 64 bit XP system ?

There is no *.ocx file just the numbered flash version.
Path is C:\WINDOWS\system32\Macromed\Flash

XP Pro SP3 32 bit.

[Shane]

I am wondering how much longer flash is going to be around.

[Willy2]

- Another thing I came across: someone who was using a Vista machine made a screenshot of the main WR GUI. What surprised me was that the GUI showed 2 different font sizes. See the 2 different fonts sizes inside the 2 red rectangles. It seems to occur when a repair has two or more sub-repairs.

Weblink for the picture:
https://1drv.ms/i/s!AluvxwylJSzyb7nDxQO8wiMP8yw