[SOLVED] SFCfix.exe shows files corrupted

[PeterJ]

Is drive F: still connected ?

 

[Piuma]

In attachment the following screenshots:
1) disk management, Cattura di schermata (195).png
2) this pc (my computer), Cattura di schermata (196).png
3) a view of My Computer with the "hide empty drives" box unticked,Cattura di schermata (197).png
4) Bluetooth not connected , Cattura di schermata (198).png
I don't remember about any drive F, and my scans are always made without any external drive plugged in.

Please, explain me.

 

[PeterJ]

I noticed drive F: in the latest log here:

F:\[7cb0a24f-9b49-46e5-a149-fea26d020941]\
...
F:\[7cb0a24f-9b49-46e5-a149-fea26d020941]\BACK up PC 03_2020\Immagini\

Does that ring a bell ?

 

[Piuma]

Oh yes, I've found it in the log. That's an external HDD which I've plugged in to back up my files when I've started having issues at the end of September 2023.
No, it's not plugged in since that day.
I've found the URL in the regedit.
Shall I delete the whole Key #2 with its subkeys? Cattura di schermata (199).png

 

[PeterJ]

Shall I delete the whole Key #2 with its subkeys? Cattura di schermata (199).png

No. Can you please first connect that external HDD again and create a new backup.
Next, leave the external HDD connected while you perform a new scan with FRST like in message #97.

 

[Piuma]

Followed your instructions, and then performed a new FRST64 scan, but the external HDD has not been scanned from FRST
More than that I've plugged in any other USB that I own, and the pc always calls them "G" drive, never F. Cattura di schermata (200).png
Also plugged in two external units and still no one gets named as "F": Cattura di schermata (202).png
In the FRST.txt results I've noticed that "F" drive: Cattura di schermata (201).png

I'm very confused

 

[Piuma]

that "F" drive: Cattura di schermata (201).png

VZW_Software_upgrade_assistant, is Verizon from the Samsung mobile phone.
I don't need it in my pc, instead I'd rather the pc Bluetooth back to normal, as such findable from other devices

 

[PeterJ]

Followed your instructions, and then performed a new FRST64 scan, but the external HDD has not been scanned from FRST

FRST doesn't need to scan drive F:. I just need the log file Addition.txt when drive F: is connected. That is fine now and you may disconnect it.


Warning: This script was written specifically for this user, for use on that particular machine. Do not run this script on another machine.

1. Download the attachment fixlist.txt and save it to your desktop.
2. Right-click on FRST.exe and select "Run as administrator".
3. Press the Fix button.
4. The tool will now process fixlist.txt.
5. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run.
6. When finished, a log called Fixlog.txt will appear in the same directory the tool is run from.
7. Attach the files Fixlog.txt and <date>_<time>.zip to your next reply.

 

[Piuma]

done

 

[PeterJ]

Warning: This script was written specifically for this user, for use on that particular machine. Do not run this script on another machine.

1. Download the attachment fixlist.txt and save it to your desktop.
2. Right-click on FRST64.exe and select "Run as administrator".
3. Press the Fix button.
4. The tool will now process fixlist.txt.
5. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run.
6. When finished, a log called Fixlog.txt will appear in the same directory the tool is run from.
7. Attach the files Fixlog.txt and <date>_<time>.zip to your next reply.

 

[Piuma]

Here's the fixlog.
Sorry, no zip file was produced

 

[PeterJ]

Step 1:
Warning: This script was written specifically for this user, for use on that particular machine. Do not run this script on another machine.

1. Download the attachment fixlist.txt and save it to your desktop.
2. Right-click on FRST64.exe and select "Run as administrator".
3. Press the Fix button.
4. The tool will now process fixlist.txt.
5. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run.
6. When finished, a log called Fixlog.txt will appear in the same directory the tool is run from.
7. Attach the file Fixlog.txt to your next reply.

Lets see the result of the previous fixes.
Step 2: FRST Scan

1. Right-click on FRST64.exe and select "Run as administrator".
2. Note: Ensure that the Addition.txt check box is checked at the bottom of the form within the Optional Scan area.
3. Press the Scan button.
4. Please wait for the tool to finish. It will produce two logfiles called FRST.txt and Addition.txt in the same directory the tool is run from (which should be the desktop)
5. Post the logfiles FRST.txt and Addition.txt as attachment in your next reply.

 

[Piuma]

log and scans:

 

[PeterJ]

Looking good.
Any remaining issues left ?

 

[Piuma]

I'd rather to have my pc Bluetooth working and findable from other devices

 

[PeterJ]

The program "Qualcomm Atheros Bluetooth Suite" is installed.
Does it provide any message as to why bluetooth is not working ?
Some drivers by this program are running which is good.
Do you see any problems in Device Manager related to bluetooth or other devices ?

 

[Piuma]

ok, I've uninstalled the Bluetooth module from Device Manager , and reinstalled it. It seems to work.
Hence, I made some research about the Asus Bloatware, and reinstated ExpressCache and ATK Package.
In attachment my last FRST scan to your attention, to check if they're ok or in need of a further tuning.

 

[PeterJ]

Step 1:
I would not recommend the use of "Outbyte", "Advanced System Repair" or any so-called cleanup or optimizer tools. They often promise more than they deliver or you have to pay first to remove fake positives.

Warning: This script was written specifically for this user, for use on that particular machine. Do not run this script on another machine.

1. Download the attachment fixlist.txt and save it to your desktop.
2. Right-click on FRST64.exe and select "Run as administrator".
3. Press the Fix button.
4. The tool will now process fixlist.txt.
5. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run.
6. When finished, a log called Fixlog.txt will appear in the same directory the tool is run from.
7. Attach the file Fixlog.txt to your next reply.

Step 2:
Are there other remaining issues we need to look at ?

 

[Piuma]

Thank you for your tips about Outbyte & co., I had already uninstalled it.
Yes, it's tricky to insist on fake positives. I'll stay away
I don't see particular issues right now, thanks to your help;
I wish but I don't feel safe to try and update to Windows 10, because I've seen too many machines getting terribly slow after undertaking this step.
What do you reckon?

 

[PeterJ]

You can keep using Windows 8.1but it is no longer supported by Microsoft to receive (security) updates.
Instead of upgrading this machine you can consider buying a new machine (with Windows 10/11). That way you can move all your data to the new machine when it suits you without losing the current state of this Windows 8.1 machine.


Warning: This script was written specifically for this user, for use on that particular machine. Do not run this script on another machine.

1. Download the attachment fixlist.txt and save it to your desktop.
2. Right-click on FRST64.exe and select "Run as administrator".
3. Press the Fix button.
4. The tool will now process fixlist.txt.
5. If for some reason the tool needs a restart, please make sure you let the system restart normally. After that let the tool complete its run.
6. When finished, a log called Fixlog.txt will appear in the same directory the tool is run from.
7. Attach the file Fixlog.txt to your next reply.