Main Forum > Tweaking.com Support & Help

Sys Restore & other problems after running Windows Repair Tool v3.9.23 on Vista.

<< < (2/8) > >>

Boggin:
Julian was wanting to see the result of the pre-scan from Step 2: Optional

When you click on Step 2 - click on Open Pre-Scan in the right pane then on Start Scan.

Pepo:
I can't see any saved results there or anywhere else?  So I'm running the scan again.
As it's 4.30am here I need to get some sleep, so I'll get the results to you when I re-surface again.

Thanks again.

Boggin:
When the pre-scan has completed, expand the window - right click and select Select all  - right click again and select Copy.

You can then right click in the reply box and select Paste.

Pepo:
These are the results.

┌────────────────────────────────────────────────────────────────────────────────┐
│ Tweaking.com - Windows Repair v3.9.24 - Pre-Scan
│ Computer: PETES-DV5-1222T (Windows Vista (TM) Home Premium 6.0.6002 Service Pack 2) (32-bit)
│ [Started Scan - 27/01/2017 11:34:58 AM]
└────────────────────────────────────────────────────────────────────────────────┘
┌────────────────────────────────────────────────────────────────────────────────┐
│ Scanning Windows Packages Files.
│ Started at (27/01/2017 11:34:58 AM)
│
│ No problems were found with the Packages Files.
│
│ Files Checked & Verified: 7,646
│
│ Done Scanning Windows Packages Files.(27/01/2017 11:44:26 AM)
└────────────────────────────────────────────────────────────────────────────────┘
┌────────────────────────────────────────────────────────────────────────────────┐
│ Scanning Reparse Points.
│ Started at (27/01/2017 11:44:26 AM)
│
│ Reparse Points are OK!.
│
│ Files & Folders Searched: 350,001
│ Reparse Points Found: 63
│
│ Done Scanning Reparse Points.(27/01/2017 11:50:24 AM)
└────────────────────────────────────────────────────────────────────────────────┘
┌────────────────────────────────────────────────────────────────────────────────┐
│ Checking Environment Variables.
│ Started at (27/01/2017 11:50:24 AM)
│
│ No problems were found with the Environment Variables.
│
│ Done Checking Environment Variables. (27/01/2017 11:50:24 AM)
└────────────────────────────────────────────────────────────────────────────────┘
┌────────────────────────────────────────────────────────────────────────────────┐
│ [Finished Scan - 27/01/2017 11:50:24 AM]
│
│ [x] Scan Complete - No Problems Found!
└────────────────────────────────────────────────────────────────────────────────┘

Boggin:
That looks fine and while your chkdsk in read-only mode looks fine, I'm not sure how Julian wants to proceed with this.

I think I would be going for a repair install as your update problems more than pre-date running WR and whatever else is wrong could have been compounded by WR, but that is an unknown factor.

There could be a problem with activating the repair install on an OEM machine, but if your COA sticker key is still legible then you can go Start - type Slui 3 and enter your COA sticker key to change your product key from an otherwise OEM key.

If you don't have a Vista x86 install disk that includes SP2 you can download the ISO from https://docs.google.com/uc?id=0B1bjzCHZkpy9ejgzMllaMlM4T2M&export=download

I've downloaded the ISO and it has passed the security checks.

You Save the download and then can use Windows USB/DVD Burner Tool to create a bootable disk.

http://wudt.codeplex.com/

This is how to do a Vista repair install - https://www.vistax64.com/tutorials/88236-repair-install-vista.html

You can back up your drivers folders onto something like an USB stick and drop them back in after if required and can be found in C:\Windows\System32

An alternative to a repair install can be an offboot sfc /scannow where you would need to change the boot order to boot up with the install disk to navigate to the Recovery Environment and select Command Prompt.

At the prompt enter bcdedit |find "osdevice" then use that partition letter in the next command as Windows doesn't always see the volume in C:

Enter where X=your partition letter -

sfc /scannow /offbootdir=X:\ /offwindir=X:\Windows

For clarity that is a Pipe symbol before find in the bcdedit cmd which is the uppercase of \ and there's a space before each /

This will check and repair any files against the incorrupt source of the ISO.

Navigation

[0] Message Index

[#] Next page

[*] Previous page