Author Topic: folder C:\Tweaking.com_Windows_Repair_Logs is empty. (Read 18949 times)

ftr · « **on:** August 19, 2013, 02:08:01 pm »

Hi,

the folder C:\Tweaking.com_Windows_Repair_Logs is empty.
Is there any other way to know what tweaking did ?

and:
I thought to have seen that tweaking created a system repair point. But there is none. How that's possible ?

Thanks in advance,
ftr

Shane · « **Reply #1 on:** August 19, 2013, 03:51:44 pm »

The repair tool use bat files to run all the commands, and the bat files only output to the log files if there was any errors.

There is info on each repair in the program and what they do

As for the system restore point, the program, if you had it, will make one and also do a reg backup with my registry backup tool.

90% of the repairs all have to do with the registry, so as long as you got a reg backup you should be fine

Shane

ftr · « **Reply #2 on:** August 21, 2013, 01:51:00 pm »

Shane,

Thanks for your optimistic answer.

One major error which made me use tweaking was the MS installer service which did not work. So I tried again, after the repair run, but got the same error as before :
Impossible to access Windows Installer. This may occur if the installation program of windows has not been installed.
This is not the only error that has not been corrected: the VSS service does not work either.

So, I guess a second repair run would be helpful but one that produces an output. How can I force an output ?
TIA
ftr

Shane · « **Reply #3 on:** August 22, 2013, 02:31:51 pm »

What repairs did you run? Did you trying running them all?

The first 2 are almost always a must. The reg and file permissions. Because if permissions have been changed or corrupted the other repairs wont do much good since they cant have access and a lot of errors can be permissions related.

Shane

ftr · « **Reply #4 on:** August 23, 2013, 10:24:06 am »

Hi Shane,

I currently try to repair a vista and a xp installation, both resulting in errors. This thread is about the vista repair attempt.

Answering your question : I ran all of the procedures, but I wasn't able to create a system backup (which is one of the resasons why I want to repair the vista installation), but I got a registry backup.

Searching the pc again to my surprise I found a folder named Tweaking.com_Windows_Repair_Logs - which is empty and caused me to open that thread - AND I found now a log file in the good log folder of the installation. This is why I thought there was no log file first. Now, here it comes, but the results are different, but not better.

Among others:

Repair MSI (Windows Installer)
Start (19/08/2013 22:31:58)
Running Repair Under Current User Account
Running Repair Under System Account
Done (19/08/2013 22:32:09)

When I tried to install a program with a MSI installer - just to control the result - the same error as before appeared:
Impossible to access the windows installer. this may happened if the service has not been well installed.

ftr

Willy2 · « **Reply #5 on:** August 23, 2013, 03:34:14 pm »

- Seems you got the same systemvariable (%systemroot%) corrupted/changed, resulting in the same errors popping up as in XP. When I look in the registry on my win 7 system then the services (e.g. MSI) also needs the systemvariables %systemroot% & %windir% to be set to the default value (for me it's "c:\windows").

- The folder "c:\Tweaking.com_windows................" is the location where older WR versions used to store the logs.

- If you want to see which & how many system restore points you've created then use a program called Ccleaner. Windows (tries to) hide(s) that info as much as possible.

Shane · « **Reply #6 on:** August 23, 2013, 11:54:42 pm »

Open a cmd.exe window and put in %systemroot% and hit enter.

What does it say after that?

Shane

Willy2 · « **Reply #7 on:** August 24, 2013, 03:46:30 pm »

@FTR: Seems your Vista system is also a 32 bits system. This errors simply show up on every 32 bits system. It has nothing to do with the %systemroot% system variable.

ftr · « **Reply #8 on:** August 25, 2013, 12:50:16 am »

Hi,

Open a cmd.exe window and put in %systemroot% and hit enter.
What does it say after that?

It opens a C:\Windows window.

ftr

Willy2 · « **Reply #9 on:** August 25, 2013, 02:52:42 am »

@FTR:
- The error "Le chemin d'accès spécifié est introuvable" is not automatically a sign the repairs failed. It's a sign WR (v1.9.15) tries to find a (sub-)folder (e.g. "syswow64" in "Repair Internet Explorer") that, for whatever reason, doesn't exist on your computer system. If you have a 32 bit computer (e.g. XP or Vista) that folder "syswow64" never existed in the first place. WR tries to find the "syswow64" folder 128 times on your PC and fails 128 times and therefore generates 128 times an error that shows up in the log file.

In this case the value of %systemroot% doesn't matter. But I see it has proper default value.

ftr · « **Reply #10 on:** August 25, 2013, 06:39:20 am »

Hi,
I just tried your advice on my windows 32 bit vista home pc. To no avail !

1/ I created a restoration point (according to the message shown) and a registry backup with the fallback method (due to slow backup answer time)
2/ I ran a repair of the VSS shadow copy and the MS Installer only.

Log-vss.txt provides the following explanation :
VSHADOW.EXE 3.0 - Volume Shadow Copy sample client.
Copyright (C) 2005 Microsoft Corporation. All rights reserved.

(Option: Generate SETVAR script 'C:\Windows\temp\vss-setvar.bat')
(Option: Execute binary/script after shadow creation 'C:\Windows\temp\vss.bat')
(Option: Create shadow copy set)
(Gathering writer metadata...)
(Waiting for the asynchronous operation to finish...)

Error during the last asynchronous operation.
- Returned HRESULT = 0x8000ffff
- Error text: E_UNEXPECTED
- Please re-run VSHADOW.EXE with the /tracing option to get more details

So, I guess who have some good advice

ftr

Willy2 · « **Reply #11 on:** August 25, 2013, 08:34:02 am »

In "Repair VSS" the two services that are needed for VSS (VSS, swprv), are switched off and not switched back on. (Your log confirms that) Being switched off is an extra hurdle for a program that wants to to use VSS. And Windows System Restore (SR) needs VSS & SWPRV too.

Start VSS & SWPRV using the Windows' "Services". (Don't run WR !!!) But try to make a SR point. Perhaps now Windows SR will work.

Perhaps someone else has more suggestions ?

Shane · « **Reply #12 on:** August 26, 2013, 06:55:22 pm »

Have you tried any of these yet?
http://www.tweaking.com/articles/pages/tweaking_com_registry_backup_online_help,2.html

Shane

Willy2 · « **Reply #13 on:** August 26, 2013, 11:46:03 pm »

@FTR: Delete the old WR log file, download the file in the attachment, unzip it in the folder where the main WR program is located, and run it with admin rights. Perhaps after that VSS will work on your XP and/or Vista system.

(the file contains a slightly modified version of "Repair VSS")