Error 80073712: Havent been able to install most updates for almost 2 years

Greetings,

Thank you for going through that verification step.

Now please do this.

===================================================

Obtaining Windows Update History Log Using Farbar Recovery Scan Tool (FRST)

--------------------
  • If necessary, download FRST for either 64 bit or 32 bit computers. If unsure, download both and only the correct one will run.
  • Right click on the FRST icon and select Run as administrator
  • Highlight the below information then hit the Ctrl + C keys at the same time
  • The information will be copied invisibly and will be "pasted" into FRST automatically when you click Fix as instructed below
Code:
Start::
CloseProcesses:
StartPowershell:
$Session = New-Object -ComObject "Microsoft.Update.Session" 
 
$Searcher = $Session.CreateUpdateSearcher() 
 
$historyCount = $Searcher.GetTotalHistoryCount() 
 
$Searcher.QueryHistory(0, $historyCount) | Select-Object Date, 
 
   @{name="Operation"; expression={switch($_.operation){ 
 
       1 {"Installation"}; 2 {"Uninstallation"}; 3 {"Other"}}}}, 
 
   @{name="Status"; expression={switch($_.resultcode){ 
 
       1 {"In Progress"}; 2 {"Succeeded"}; 3 {"Succeeded With Errors"}; 
 
       4 {"Failed"}; 5 {"Aborted"} 
 
}}}, Title | Export-Csv -NoType "$Env:userprofile\Desktop\WindowsUpdates.csv"
EndPowershell:
End::
  • Click Fix
  • When completed he tool will create a log on the desktop called Fixlog.txt. Copy and paste the report in your reply.
  • In addition, a Windows Update file will be placed on your desktop. Please attach that file to your reply.
===================================================

Things I would like to see in your next reply. Please be sure to copy and paste any requested log information unless you are asked to attach it.

  • Fixlog
  • Attached Windows Update file
Hello again,

Before I do this, I just want to confirm:
Should I delete FRST.txt, addition.txt, and (obviously) fixlog.txt from the first run?
 
Thanks for being cautious.

No need to remove anything. We will not get either FRST.txt or Addition.txt and the new run of Fixlist will overwrite the previous Fixlog which is perfectly fine.

:thumbsup2:
 
Ok, we might have a problem (Not sure):
The windows update file only has a a few number of entries. The reason behind this, as I said in my first post, is that one of the "fixes" I tried applying before posting this topic, was renaming the software distribution folder and catroot2 folder. After I did that, windows update started off with a clean "history".

Do I need to revert back for you to see the entire log from the previous years?

In any case, the following 2 replies will be the fixlog, and whatever is currently on the windows update file
 
Fix result of Farbar Recovery Scan Tool (x64) Version: 24.10.2018
Ran by Ahmed Al-Jefairi (25-10-2018 02:44:03) Run:3
Running from E:\
Loaded Profiles: Ahmed Al-Jefairi (Available Profiles: Ahmed Al-Jefairi)
Boot Mode: Normal
==============================================


fixlist content:
*****************
CloseProcesses:
StartPowershell:
$Session = New-Object -ComObject "Microsoft.Update.Session"

$Searcher = $Session.CreateUpdateSearcher()

$historyCount = $Searcher.GetTotalHistoryCount()

$Searcher.QueryHistory(0, $historyCount) | Select-Object Date,

@{name="Operation"; expression={switch($_.operation){

1 {"Installation"}; 2 {"Uninstallation"}; 3 {"Other"}}}},

@{name="Status"; expression={switch($_.resultcode){

1 {"In Progress"}; 2 {"Succeeded"}; 3 {"Succeeded With Errors"};

4 {"Failed"}; 5 {"Aborted"}

}}}, Title | Export-Csv -NoType "$Env:userprofile\Desktop\WindowsUpdates.csv"
EndPowershell:


*****************


Processes closed successfully.


========= Powershell: =========




========= End of Powershell: =========






The system needed a reboot.


==== End of Fixlog 02:44:35 ====
 
"Date","Operation","Status","Title"
"10/24/2018 9:44:28 AM","Installation","Succeeded","Definition Update for Windows Defender Antivirus - KB915597 (Definition 1.279.410.0)"
"10/24/2018 9:43:59 AM","Installation","Failed","Update for Windows 7 for x64-based Systems (KB2952664)"
"10/24/2018 9:43:58 AM","Installation","Failed","2018-09 Security Monthly Quality Rollup for Windows 7 for x64-based Systems (KB4457144)"
"10/23/2018 2:33:00 PM","Installation","Succeeded","Definition Update for Windows Defender Antivirus - KB915597 (Definition 1.279.208.0)"
"10/23/2018 2:31:13 PM","Installation","Failed","Update for Windows 7 for x64-based Systems (KB2952664)"
"10/23/2018 2:31:12 PM","Installation","Failed","2018-09 Security Monthly Quality Rollup for Windows 7 for x64-based Systems (KB4457144)"
"10/20/2018 5:34:07 AM","Installation","Failed","Update for Windows 7 for x64-based Systems (KB2952664)"
"10/20/2018 5:34:00 AM","Installation","Failed","2018-09 Security Monthly Quality Rollup for Windows 7 for x64-based Systems (KB4457144)"
"10/19/2018 8:52:02 AM","Installation","Failed","Update for Windows 7 for x64-based Systems (KB2952664)"
"10/19/2018 8:51:59 AM","Installation","Failed","2018-09 Security Monthly Quality Rollup for Windows 7 for x64-based Systems (KB4457144)"
"10/18/2018 3:05:48 PM","Installation","Failed","Update for Windows 7 for x64-based Systems (KB2952664)"
"10/18/2018 3:05:47 PM","Installation","Failed","2018-09 Security Monthly Quality Rollup for Windows 7 for x64-based Systems (KB4457144)"
"10/18/2018 2:27:41 AM","Installation","Succeeded","Definition Update for Windows Defender Antivirus - KB915597 (Definition 1.279.8.0)"
"10/17/2018 9:34:12 PM","Installation","Failed","2018-09 Preview of Monthly Quality Rollup for Windows 7 for x64-based Systems (KB4457139)"
"10/17/2018 9:30:37 PM","Installation","Failed","2018-09 Preview of Monthly Quality Rollup for Windows 7 for x64-based Systems (KB4457139)"
"10/17/2018 9:30:07 PM","Installation","Failed","Update for Windows 7 for x64-based Systems (KB2952664)"
"10/17/2018 9:30:04 PM","Installation","Failed","2018-09 Security Monthly Quality Rollup for Windows 7 for x64-based Systems (KB4457144)"
"10/17/2018 9:15:17 PM","Installation","Failed","Update for Windows 7 for x64-based Systems (KB2952664)"
"10/17/2018 9:15:16 PM","Installation","Failed","2018-09 Security Monthly Quality Rollup for Windows 7 for x64-based Systems (KB4457144)"
"10/17/2018 8:55:35 PM","Installation","Failed","Update for Windows 7 for x64-based Systems (KB2952664)"
"10/17/2018 8:55:34 PM","Installation","Failed","2018-09 Security Monthly Quality Rollup for Windows 7 for x64-based Systems (KB4457144)"
 
Thanks, we have some workable information from this report so we will go with that, for now.

Please do this.

===================================================

Farbar's Recovery Scan Tool Registry Search With Component Hive Loaded

--------------------
  • If necessary, download FRST for either 64 bit or 32 bit computers. If unsure, download both and only the correct one will run.
  • Hit the Windows Key + R at the same time
  • Type appwiz.cpl and hit Enter
  • On the left side click Turn Windows features on or off and allow that information to populate <<<Important, do not close this window until these steps are completed<<<
  • Right click on FRST and select Run as administrator
  • Type or copy and paste the following in the Search: box
Code:
KB4457144;KB4457139
  • Click the Search Registry button
  • When completed click OK and a Searchreg.txt document will open on your desktop
  • Copy and paste the contents of that document your reply
===================================================

Things I would like to see in your next reply. Please be sure to copy and paste any requested log information unless you are asked to attach it.

  • Searchreg.txt
 
Thanks, we have some workable information from this report so we will go with that, for now.

Please do this.

===================================================

Farbar's Recovery Scan Tool Registry Search With Component Hive Loaded

--------------------
  • If necessary, download FRST for either 64 bit or 32 bit computers. If unsure, download both and only the correct one will run.
  • Hit the Windows Key + R at the same time
  • Type appwiz.cpl and hit Enter
  • On the left side click Turn Windows features on or off and allow that information to populate <<<Important, do not close this window until these steps are completed<<<
  • Right click on FRST and select Run as administrator
  • Type or copy and paste the following in the Search: box
Code:
KB4457144;KB4457139
  • Click the Search Registry button
  • When completed click OK and a Searchreg.txt document will open on your desktop
  • Copy and paste the contents of that document your reply
===================================================

Things I would like to see in your next reply. Please be sure to copy and paste any requested log information unless you are asked to attach it.

  • Searchreg.txt
Hello,

After allowing the info to populate on the Turn windows features on and off window, was I supposed to close that afterwards? I let it open while I proceeded to the next step.

Here is the searchreg.txt:

Farbar Recovery Scan Tool (x64) Version: 24.10.2018
Ran by Ahmed Al-Jefairi (25-10-2018 11:20:33)
Running from E:\
Boot Mode: Normal


================== Search Registry: "KB4457144;KB4457139" ===========




===================== Search result for "KB4457144" ==========




===================== Search result for "KB4457139" ==========


====== End of Search ======
 
Greetings.

I greatly appreciate your patience while I worked through some seemingly contridictory information in your logs.

Yes, you did it correctly, the Windows Features window needed to remain open while you continued with the steps.

Please do this.

===================================================

Installing Update Using DISM

--------------

  • Right click on windows6.1-kb4457144-x64_5ca467d42deadc2b2f4010c4a26b4a6903790dd5.msu, select Save Link As..., and save the file onto your Desktop <<<Important<<<
  • If necessary, download FRST for either 64 bit or 32 bit computers and save it to your Desktop. If unsure, download both and only the correct one will run.
  • Right click on the FRST icon on your Desktop and select Run as administrator
  • Highlight the below information then hit the Ctrl + C keys at the same time
  • The information will be copied invisibly and will be "pasted" into FRST automatically when you click Fix as instructed below
Code:
Start::
CreateRestorePoint:
cmd: md C:\WUPD
cmd: cd C:\WUPD
cmd: copy "%userprofile%\Desktop\windows6.1-kb4457144-x64_5ca467d42deadc2b2f4010c4a26b4a6903790dd5.msu" C:\WUPD
cmd: expand windows6.1-kb4457144-x64_5ca467d42deadc2b2f4010c4a26b4a6903790dd5.msu -f:* C:\WUPD
cmd: DISM.exe /Online /Add-Package /PackagePath:C:\WUPD\windows6.1-kb4457144-x64.cab
Reboot:
End::
  • Click Fix
  • Please wait patiently as the process takes some time to complete
  • When prompted click OK to restart your computer
  • When completed he tool will create a log on the desktop called Fixlog.txt. Please copy and paste the contents of the file in your reply.
===================================================

Sfc /Scannow with CBS Log From an Elevated Command Prompt

--------------------

  • Click Start, type Command, right click on Command Prompt (or cmd) above and select Run as administrator
  • After the C:\Windows\system32 command prompt type sfc /scannow and hit Enter
  • Once you are back at the C:\Windows\system32 command prompt copy and paste the below then hit Enter
copy %windir%\logs\cbs\cbs.log %userprofile%\Desktop\cbs.txt

  • Please zip and attach the file to your reply
===================================================

Things I would like to see in your next reply. Please be sure to copy and paste any requested log information unless you are asked to attach it.

  • Fixlog
  • Attached zipped CBS file
 
Greetings.

I greatly appreciate your patience while I worked through some seemingly contridictory information in your logs.

Yes, you did it correctly, the Windows Features window needed to remain open while you continued with the steps.

Please do this.

===================================================

Installing Update Using DISM

--------------

  • Right click on windows6.1-kb4457144-x64_5ca467d42deadc2b2f4010c4a26b4a6903790dd5.msu, select Save Link As..., and save the file onto your Desktop <<<Important<<<
  • If necessary, download FRST for either 64 bit or 32 bit computers and save it to your Desktop. If unsure, download both and only the correct one will run.
  • Right click on the FRST icon on your Desktop and select Run as administrator
  • Highlight the below information then hit the Ctrl + C keys at the same time
  • The information will be copied invisibly and will be "pasted" into FRST automatically when you click Fix as instructed below
Code:
Start::
CreateRestorePoint:
cmd: md C:\WUPD
cmd: cd C:\WUPD
cmd: copy "%userprofile%\Desktop\windows6.1-kb4457144-x64_5ca467d42deadc2b2f4010c4a26b4a6903790dd5.msu" C:\WUPD
cmd: expand windows6.1-kb4457144-x64_5ca467d42deadc2b2f4010c4a26b4a6903790dd5.msu -f:* C:\WUPD
cmd: DISM.exe /Online /Add-Package /PackagePath:C:\WUPD\windows6.1-kb4457144-x64.cab
Reboot:
End::
  • Click Fix
  • Please wait patiently as the process takes some time to complete
  • When prompted click OK to restart your computer
  • When completed he tool will create a log on the desktop called Fixlog.txt. Please copy and paste the contents of the file in your reply.
===================================================

Sfc /Scannow with CBS Log From an Elevated Command Prompt

--------------------

  • Click Start, type Command, right click on Command Prompt (or cmd) above and select Run as administrator
  • After the C:\Windows\system32 command prompt type sfc /scannow and hit Enter
  • Once you are back at the C:\Windows\system32 command prompt copy and paste the below then hit Enter
copy %windir%\logs\cbs\cbs.log %userprofile%\Desktop\cbs.txt

  • Please zip and attach the file to your reply
===================================================

Things I would like to see in your next reply. Please be sure to copy and paste any requested log information unless you are asked to attach it.

  • Fixlog
  • Attached zipped CBS file
Thanks for the reply. So I am running into some trouble.

Copying this line "copy %windir%\logs\cbs\cbs.log %userprofile%\Desktop\cbs.txt" gives me "The syntax of the command is incorrect"

Please advice on how to proceed.

Also, here is the fixlog results:
Fix result of Farbar Recovery Scan Tool (x64) Version: 24.10.2018
Ran by Ahmed Al-Jefairi (27-10-2018 22:11:56) Run:4
Running from C:\Users\Ahmed Al-Jefairi\Desktop
Loaded Profiles: Ahmed Al-Jefairi (Available Profiles: Ahmed Al-Jefairi)
Boot Mode: Normal
==============================================


fixlist content:
*****************
CreateRestorePoint:
cmd: md C:\WUPD
cmd: cd C:\WUPD
cmd: copy "%userprofile%\Desktop\windows6.1-kb4457144-x64_5ca467d42deadc2b2f4010c4a26b4a6903790dd5.msu" C:\WUPD
cmd: expand windows6.1-kb4457144-x64_5ca467d42deadc2b2f4010c4a26b4a6903790dd5.msu -f:* C:\WUPD
cmd: DISM.exe /Online /Add-Package /PackagePath:C:\WUPD\windows6.1-kb4457144-x64.cab
Reboot:


*****************


Restore point was successfully created.


========= md C:\WUPD =========




========= End of CMD: =========




========= cd C:\WUPD =========




========= End of CMD: =========




========= copy "%userprofile%\Desktop\windows6.1-kb4457144-x64_5ca467d42deadc2b2f4010c4a26b4a6903790dd5.msu" C:\WUPD =========


1 file(s) copied.


========= End of CMD: =========




========= expand windows6.1-kb4457144-x64_5ca467d42deadc2b2f4010c4a26b4a6903790dd5.msu -f:* C:\WUPD =========


expand: invalid option -- f
Try `expand --help' for more information.


========= End of CMD: =========




========= DISM.exe /Online /Add-Package /PackagePath:C:\WUPD\windows6.1-kb4457144-x64.cab =========




Deployment Image Servicing and Management tool
Version: 6.1.7600.16385


Image Version: 6.1.7601.18489


An error occurred trying to open - C:\WUPD\windows6.1-kb4457144-x64.cab Error: 0x80070003


Error: 3


The system cannot find the path specified.


The DISM log file can be found at C:\Windows\Logs\DISM\dism.log


========= End of CMD: =========






The system needed a reboot.


==== End of Fixlog 22:12:15 ====
 
Greetings.

Sorry for the difficulties. We are going to try to gather some additional information.

Please do this.

===================================================

Farbar Recovery Scan Tool (FRST) Fix

--------------------
  • Right click on the FRST icon and select Run as administrator
  • Highlight the below information then hit the Ctrl + C keys at the same time
  • The information will be copied invisibly and will be "pasted" into FRST automatically when you click Fix as instructed below
Code:
Start::
zip: C:\Windows\INF\setupapi.dev.log
End::
  • Click Fix
  • When completed he tool will create a log on the desktop called Fixlog.txt. Copy and paste the report in your reply.
  • The tool will also create a zip file on your Desktop with today's date and time, example 10.12.2018_13.04.06.zip. Please attach the file to your reply.
===================================================

Things I would like to see in your next reply.

  • Fixlog
  • Attached Zip file
 
Hello,

Here is the fixlog, and the zip is attached:

Fix result of Farbar Recovery Scan Tool (x64) Version: 24.10.2018
Ran by Ahmed Al-Jefairi (28-10-2018 15:43:52) Run:5
Running from C:\Users\Ahmed Al-Jefairi\Desktop
Loaded Profiles: Ahmed Al-Jefairi (Available Profiles: Ahmed Al-Jefairi)
Boot Mode: Normal
==============================================


fixlist content:
*****************
zip: C:\Windows\INF\setupapi.dev.log


*****************


================== Zip: ===================
C:\Windows\INF\setupapi.dev.log -> copied successfully to C:\Users\Ahmed Al-Jefairi\Desktop\28.10.2018_15.43.52.zip
=========== Zip: End ===========


==== End of Fixlog 15:43:52 ====
 

Attachments

I noticed this in the zipped file:

[Device Install Log]
OS Version = 6.1.7601
Service Pack = 1.0
Suite = 0x0100
ProductType = 1
Architecture = amd64

My architecture is not amd64.. Am I misunderstanding this?
 
Greetings.

My architecture is not amd64.. Am I misunderstanding this?

Kind of, this is counter-intuitive. AMD was the first to introduce 64 bit architecture and not all "AMD" references indicate they are for an AMD processor. Though the explanation is more complex, it is similar to calling a Pepsi a "Coke."

Can you tell me if you still use Clockworkmod/Helium? If not, please do this.

===================================================

Uninstalling Programs Using Revo Uninstaller Free

--------------------

I recommend uninstalling the below listed program(s) from your computer.

  • Please download and install Revo Uninstaller Free
  • Right click Revo Uninstaller and select Run as administrator
  • From the list of programs double click on the listed program(s), or anything similar, to remove it (if it exists)
Code:
Helium
  • Click Yes to any warning screen that may appear
  • If presented with the program uninstall option click Uninstall
  • If asked to restart now click No
  • Under Scanning Modes select Advanced then select Scan
  • On the Found leftover Registry items window click Select All, Delete, then Yes
  • If prompted click on Next
  • On the Found leftover files and folders window click on Select all, Delete, Yes, OK on any warning screen, then Finish
  • Reboot your computer
  • If you uninstall Helium please complete the Sfc /Scannow instructions below

===================================================

Sfc /Scannow with CBS Log From an Elevated Command Prompt

--------------------

  • Click Start, type Command, right click on Command Prompt (or cmd) above and select Run as administrator
  • After the C:\Windows\system32 command prompt type sfc /scannow and hit Enter
  • Once you are back at the C:\Windows\system32 command prompt copy and paste the below then hit Enter
copy %windir%\logs\cbs\cbs.log %userprofile%\Desktop\cbs.txt

  • Please zip and attach the file to your reply
===================================================

Things I would like to see in your next reply. Please be sure to copy and paste any requested log information unless you are asked to attach it.

  • Results of Clockworkmod/Helium?
  • CBS.zip file, if applicable
 
Hello,

Thanks for the info about the 64bit architecture. I understand it now :)

Yes, I installed Helium back less than 2 months ago (Very early september. I bought a note 9, moving from an old note 9. The program did what I needed to do). I doubt it has anything to do with my problem as my problem is, like I mentioned, from years ago.

In which case, do I need to do any of the above?

If yes, I'm not sure if you didnt notice this in one of my previous replies, so I'll post it again (Because you asked me to do it again in the instructions above):
Copying this line "copy %windir%\logs\cbs\cbs.log %userprofile%\Desktop\cbs.txt" gives me "The syntax of the command is incorrect"
​Thanks again
 
Greetings,

I have not forgotten you. I hope to be able to post something soon.
 
Greetings.

I apologize for the syntax. I identified the problem after you last mentioned it but didn't update my canned speech. If is fixed now!

Part of the difficulty is we are at a bit of a disadvantage because the SoftwareDistribution folder was previously cleared. Currently, there is an identifed issue with the Helium program which may or may not be the culprit as it relates to Windows Update. Either way, it is an issue we should address.

The program did what I needed to do). I doubt it has anything to do with my problem as my problem is, like I mentioned, from years ago.
Does this mean the program is no longer essential and it can be uninstalled? If that is true then please go ahead and uninstall it. There is a new set of instructions for the Sfc /Scannow step.

===================================================

Sfc /Scannow with CBS Log From an Elevated Command Prompt

--------------------

  • Click Start, type Command, right click on Command Prompt (or cmd) above and select Run as administrator
  • After the C:\Windows\system32 command prompt type sfc /scannow and hit Enter
  • Once you are back at the C:\Windows\system32 command prompt copy and paste the below then hit Enter
copy "%windir%\logs\cbs\cbs.log" "%userprofile%\Desktop\cbs.txt"

  • Please zip and attach the file to your reply
===================================================

Things I would like to see in your next reply. Please be sure to copy and paste any requested log information unless you are asked to attach it.

  • Program uninstalled?
  • CBS.log, if appropriate
 
Hello again,

a bit of a disadvantage because the SoftwareDistribution folder was previously cleared. Currently, there is an identifed issue with the Helium program which may or may not be the culprit as it relates to Windows Update. Either way, it is an issue we should address.
The SoftwareDistribution folder was just renamed. I could always rename it back and delete the new one. Wont that work?


The program did what I needed to do). I doubt it has anything to do with my problem as my problem is, like I mentioned, from years ago.
Does this mean the program is no longer essential and it can be uninstalled? If that is true then please go ahead and uninstall it. There is a new set of instructions for the Sfc /Scannow step.
I would have liked to keep it, but sure, I went ahead to uninstall it using the program mentioned in the last post.
That said, I did not get the results you were expecting. By your instructions, you were expecting it to give leftover registry items, which I should go ahead and delete.
The result of the scan told me there were no leftover items and took me back to the uninstaller's main screen

===================================================

Sfc /Scannow with CBS Log From an Elevated Command Prompt

--------------------

  • Click Start, type Command, right click on Command Prompt (or cmd) above and select Run as administrator
  • After the C:\Windows\system32 command prompt type sfc /scannow and hit Enter
  • Once you are back at the C:\Windows\system32 command prompt copy and paste the below then hit Enter
copy "%windir%\logs\cbs\cbs.log" "%userprofile%\Desktop\cbs.txt"

  • Please zip and attach the file to your reply
===================================================

Things I would like to see in your next reply. Please be sure to copy and paste any requested log information unless you are asked to attach it.

  • Program uninstalled?
  • CBS.log, if appropriate
Scan finished with this msg:
Windows Resource Protection did not find any integrity violations.

Copy function worked now. cbs.txt zipped and attached.

Hope this helps. Thanks :)
 

Attachments

Thank you for the detailed information. I will be reviewing it today to determine our next steps.

I want to mention again I appreciate your patience as it is allowing me to be trained to better assist you and others, a little bit at your expense!

Gary
 
Thank you for the detailed information. I will be reviewing it today to determine our next steps.

I want to mention again I appreciate your patience as it is allowing me to be trained to better assist you and others, a little bit at your expense!

Gary
Happy to do so :)
 
Greetings.

Once we are able to overcome your Windows Update issue you are certainly free to install Helium again.

Please do this.

===================================================

Retrieving Components Hive Using SFCFix Script

--------------------

  • If necessary, download SFCFix.exe by niemiro and save it to your Desktop
  • Download View attachment 40029 and save it to your Desktop
  • Close any open programs or windows
  • Drag the SFCFix.txt file over the SFCFix.exe icon and release it to run the fix
  • Once processed a SFCFix.txt document will open on your Desktop, with a copy placed on your Desktop as well
  • Copy and paste the contents of the SFCFix.txt report in your reply
  • In addition, a Components.zip file will be placed on your desktop
  • Upload the Components.zip file to either SendSpace or the upload site of your choice and provide a link to the download in your reply
===================================================

Things I would like to see in your next reply. Please be sure to copy and paste any requested log information unless you are asked to attach it. :thumbsup2:

  • SFCFix.txt
  • Link to download location
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top