[SOLVED] Server 2022 - Windows Update Failing KB5027225 - 0x800f081f

dism error: 2

cbs.log attached

Code:
SFCFix version 3.0.2.1 by niemiro.
Start time: 2023-08-21 08:27:32.594
Microsoft Windows Server 10 Build 20348 - amd64
Using .zip script file at C:\Users\OPDVGHTC\Desktop\SFCFix.zip [0]




PowerCopy::
Successfully took permissions for file or folder C:\Windows\WinSxS\Manifests

Successfully copied file C:\Users\OPDVGHTC\AppData\Local\niemiro\Archive\amd64_microsoft-windows-i..oyment-languagepack_31bf3856ad364e35_10.0.20348.1547_en-us_30756f7c6e208a61.manifest to C:\Windows\WinSxS\Manifests\amd64_microsoft-windows-i..oyment-languagepack_31bf3856ad364e35_10.0.20348.1547_en-us_30756f7c6e208a61.manifest.
Successfully copied file C:\Users\OPDVGHTC\AppData\Local\niemiro\Archive\amd64_microsoft-windows-i..oyment-languagepack_31bf3856ad364e35_10.0.20348.1607_en-us_30669e686e2c40f6.manifest to C:\Windows\WinSxS\Manifests\amd64_microsoft-windows-i..oyment-languagepack_31bf3856ad364e35_10.0.20348.1607_en-us_30669e686e2c40f6.manifest.
Successfully copied file C:\Users\OPDVGHTC\AppData\Local\niemiro\Archive\amd64_microsoft-windows-s..oyment-languagepack_31bf3856ad364e35_10.0.20348.1129_en-us_c4a70c5face5ae85.manifest to C:\Windows\WinSxS\Manifests\amd64_microsoft-windows-s..oyment-languagepack_31bf3856ad364e35_10.0.20348.1129_en-us_c4a70c5face5ae85.manifest.
Successfully copied file C:\Users\OPDVGHTC\AppData\Local\niemiro\Archive\amd64_microsoft-windows-s..oyment-languagepack_31bf3856ad364e35_10.0.20348.1547_en-us_5eaf43506870f1bf.manifest to C:\Windows\WinSxS\Manifests\amd64_microsoft-windows-s..oyment-languagepack_31bf3856ad364e35_10.0.20348.1547_en-us_5eaf43506870f1bf.manifest.
Successfully copied file C:\Users\OPDVGHTC\AppData\Local\niemiro\Archive\amd64_microsoft-windows-s..oyment-languagepack_31bf3856ad364e35_10.0.20348.1547_en-us_5ec3f7b5e66311f0.manifest to C:\Windows\WinSxS\Manifests\amd64_microsoft-windows-s..oyment-languagepack_31bf3856ad364e35_10.0.20348.1547_en-us_5ec3f7b5e66311f0.manifest.
Successfully copied file C:\Users\OPDVGHTC\AppData\Local\niemiro\Archive\amd64_microsoft-windows-s..oyment-languagepack_31bf3856ad364e35_10.0.20348.1607_en-us_c46f29bfad0fd44a.manifest to C:\Windows\WinSxS\Manifests\amd64_microsoft-windows-s..oyment-languagepack_31bf3856ad364e35_10.0.20348.1607_en-us_c46f29bfad0fd44a.manifest.
Successfully copied file C:\Users\OPDVGHTC\AppData\Local\niemiro\Archive\amd64_microsoft-windows-s..oyment-languagepack_31bf3856ad364e35_10.0.20348.1726_en-us_5e97b9ac6882dd52.manifest to C:\Windows\WinSxS\Manifests\amd64_microsoft-windows-s..oyment-languagepack_31bf3856ad364e35_10.0.20348.1726_en-us_5e97b9ac6882dd52.manifest.
Successfully copied file C:\Users\OPDVGHTC\AppData\Local\niemiro\Archive\amd64_microsoft-windows-s..oyment-languagepack_31bf3856ad364e35_10.0.20348.1726_en-us_5eac6e11e674fd83.manifest to C:\Windows\WinSxS\Manifests\amd64_microsoft-windows-s..oyment-languagepack_31bf3856ad364e35_10.0.20348.1726_en-us_5eac6e11e674fd83.manifest.
Successfully copied file C:\Users\OPDVGHTC\AppData\Local\niemiro\Archive\amd64_microsoft-windows-s..oyment-languagepack_31bf3856ad364e35_10.0.20348.1726_zh-tw_c22f15d5cb07b405.manifest to C:\Windows\WinSxS\Manifests\amd64_microsoft-windows-s..oyment-languagepack_31bf3856ad364e35_10.0.20348.1726_zh-tw_c22f15d5cb07b405.manifest.
Successfully copied file C:\Users\OPDVGHTC\AppData\Local\niemiro\Archive\amd64_microsoft-windows-s..oyment-languagepack_31bf3856ad364e35_10.0.20348.502_en-us_067abeb92783c69a.manifest to C:\Windows\WinSxS\Manifests\amd64_microsoft-windows-s..oyment-languagepack_31bf3856ad364e35_10.0.20348.502_en-us_067abeb92783c69a.manifest.
Successfully copied file C:\Users\OPDVGHTC\AppData\Local\niemiro\Archive\amd64_microsoft-windows-s..res-deployment04100_31bf3856ad364e35_10.0.20348.1070_en-us_e93b0abe8bf1c5c0.manifest to C:\Windows\WinSxS\Manifests\amd64_microsoft-windows-s..res-deployment04100_31bf3856ad364e35_10.0.20348.1070_en-us_e93b0abe8bf1c5c0.manifest.
Successfully copied file C:\Users\OPDVGHTC\AppData\Local\niemiro\Archive\amd64_microsoft-windows-s..res-deployment04100_31bf3856ad364e35_10.0.20348.1726_en-us_e8e9d1288c2fa46a.manifest to C:\Windows\WinSxS\Manifests\amd64_microsoft-windows-s..res-deployment04100_31bf3856ad364e35_10.0.20348.1726_en-us_e8e9d1288c2fa46a.manifest.
Successfully copied file C:\Users\OPDVGHTC\AppData\Local\niemiro\Archive\amd64_microsoft-windows-s..res-deployment08110_31bf3856ad364e35_10.0.20348.1070_en-us_eb0227c08accf133.manifest to C:\Windows\WinSxS\Manifests\amd64_microsoft-windows-s..res-deployment08110_31bf3856ad364e35_10.0.20348.1070_en-us_eb0227c08accf133.manifest.
Successfully copied file C:\Users\OPDVGHTC\AppData\Local\niemiro\Archive\amd64_microsoft-windows-s..res-deployment08110_31bf3856ad364e35_10.0.20348.1726_en-us_eab0ee2a8b0acfdd.manifest to C:\Windows\WinSxS\Manifests\amd64_microsoft-windows-s..res-deployment08110_31bf3856ad364e35_10.0.20348.1726_en-us_eab0ee2a8b0acfdd.manifest.
Successfully copied file C:\Users\OPDVGHTC\AppData\Local\niemiro\Archive\amd64_microsoft-windows-s..tures-deployment010_31bf3856ad364e35_10.0.20348.1726_zh-tw_e1e4dfaf76c5df00.manifest to C:\Windows\WinSxS\Manifests\amd64_microsoft-windows-s..tures-deployment010_31bf3856ad364e35_10.0.20348.1726_zh-tw_e1e4dfaf76c5df00.manifest.
Successfully copied file C:\Users\OPDVGHTC\AppData\Local\niemiro\Archive\amd64_microsoft-windows-s..tures-deployment020_31bf3856ad364e35_10.0.20348.1311_en-us_7efe706791ca23c5.manifest to C:\Windows\WinSxS\Manifests\amd64_microsoft-windows-s..tures-deployment020_31bf3856ad364e35_10.0.20348.1311_en-us_7efe706791ca23c5.manifest.
Successfully copied file C:\Users\OPDVGHTC\AppData\Local\niemiro\Archive\amd64_microsoft-windows-s..tures-deployment020_31bf3856ad364e35_10.0.20348.1726_en-us_7ed3bf1991ea2d05.manifest to C:\Windows\WinSxS\Manifests\amd64_microsoft-windows-s..tures-deployment020_31bf3856ad364e35_10.0.20348.1726_en-us_7ed3bf1991ea2d05.manifest.
Successfully copied file C:\Users\OPDVGHTC\AppData\Local\niemiro\Archive\amd64_microsoft-windows-s..tures-deployment040_31bf3856ad364e35_10.0.20348.1129_de-de_d70692aca249cf8b.manifest to C:\Windows\WinSxS\Manifests\amd64_microsoft-windows-s..tures-deployment040_31bf3856ad364e35_10.0.20348.1129_de-de_d70692aca249cf8b.manifest.
Successfully copied file C:\Users\OPDVGHTC\AppData\Local\niemiro\Archive\amd64_microsoft-windows-s..tures-deployment040_31bf3856ad364e35_10.0.20348.1607_de-de_d6ceb00ca273f550.manifest to C:\Windows\WinSxS\Manifests\amd64_microsoft-windows-s..tures-deployment040_31bf3856ad364e35_10.0.20348.1607_de-de_d6ceb00ca273f550.manifest.
Successfully copied file C:\Users\OPDVGHTC\AppData\Local\niemiro\Archive\amd64_microsoft-windows-s..tures-deployment040_31bf3856ad364e35_10.0.20348.1607_zh-tw_e3422dc975e4b797.manifest to C:\Windows\WinSxS\Manifests\amd64_microsoft-windows-s..tures-deployment040_31bf3856ad364e35_10.0.20348.1607_zh-tw_e3422dc975e4b797.manifest.

Successfully restored ownership for C:\Windows\WinSxS\Manifests
Successfully restored permissions on C:\Windows\WinSxS\Manifests
PowerCopy:: directive completed successfully.




Successfully processed all directives.
SFCFix version 3.0.2.1 by niemiro has completed.
Currently storing 66 datablocks.
Finish time: 2023-08-21 08:27:58.393
Script hash: sEsKV+TuVZoOBmNym58HYnbB9/eaOsF2NLrj0b70DxE=
----------------------EOF-----------------------
 

Attachments

Only one entry being flagged this time, not entirely sure why, so ...

Can you please post me the latest version of your Components Hive ...

  • Navigate to C:\Windows\System32\Config and locate the COMPONENTS file.
  • Please copy this file to your desktop.
  • Note: If you receive an error that this file is in-use, simply reboot your computer and try again.
  • Right-click on this file on your desktop and select Send To...Compressed (zipped) folder. This will create a file named COMPONENTS.ZIP on your desktop.
  • The file will likely be too large to upload here, if so please upload to a file sharing service.
  • Examples of services to upload to are WeTransfer and TransferKit and SendFileOnline

Please post me the link to the file
 
Warning: this fix is specific to the user in this thread, and no one else should follow these instructions.

  • Download COMPONENTS.ZIP and save to your Desktop.
  • Right-click on it and select Extract all....
    • Make sure the Show extracted files when complete is checked and click Extract.
    • You should now have the COMPONENTS file that we will be using to replace your current one.

Next ...

  • Navigate to C:\Windows\System32\config
  • Right-click on the current COMPONENTS file and select Rename.
    • Rename it to COMPONENTS.old
    • Note .... If you get an error that the file is in use, reboot your computer and then try again.
  • Take the file from the Components folder on your desktop and paste it into C:\Windows\System32\config

Next ...

  • Click Search button and type Command Prompt
  • From the results, right click on the Command Prompt icon, and select Run as administrator
  • A Command Window will open.
  • Copy paste the command below into it, then press Enter
  • Dism /Online /Cleanup-Image /RestoreHealth
  • Once DISM has finished running ...
    • Please attach your ... C:\Windows\Logs\CBS\cbs.log ... to your next reply.
  • If the file is too large, upload it to a file sharing service, and post me the link.
  • Examples of services to upload to are WeTransfer and TransferKit and SendFileOnline
 

Attachments

At this point I think we need to take a realistic look at things. We're pretty much getting nowhere, and patching one set of errors just reveals a new (but similar) set of errors. There's no real indication of just how much corruption we need to patch, and there does not appear to be a root cause for the corruption, just an endless set of the following type of errors ....

Code:
2023-08-22 08:38:46, Info                  CSI    00000007 Warning: Unable to repair manifest for component ([l:102 ml:140]'wow64_microsoft-windows-c..r-name-ui.resources_31bf3856ad364e35_10.0.20348.1070_en-us_6c5323f103bd0b98') from backups directory with disposition (2). A backup file may not exist or may be corrupt. Falling back to WU.
2023-08-22 08:38:46, Info                  CSI    00000008 Warning: Unable to repair manifest for component ([l:102 ml:140]'amd64_microsoft-windows-c..r-name-ui.resources_31bf3856ad364e35_10.0.20348.1070_en-us_61fe799ecf5c499d') from backups directory with disposition (2). A backup file may not exist or may be corrupt. Falling back to WU.
2023-08-22 08:38:48, Info                  CSI    00000009 Warning: Unable to repair manifest for component ([l:102 ml:140]'amd64_microsoft-windows-t..tivexcore.resources_31bf3856ad364e35_10.0.20348.1070_en-us_1c5dd719b89839b6') from backups directory with disposition (2). A backup file may not exist or may be corrupt. Falling back to WU.
2023-08-22 08:38:48, Info                  CSI    0000000a Warning: Unable to repair manifest for component ([l:102 ml:140]'amd64_microsoft-windows-t..cesclient.resources_31bf3856ad364e35_10.0.20348.1547_en-us_1d002acda0643776') from backups directory with disposition (2). A backup file may not exist or may be corrupt. Falling back to WU.
2023-08-22 08:38:48, Info                  CSI    0000000b Warning: Unable to repair manifest for component ([l:98 ml:140]'amd64_microsoft-windows-kernel32.resources_31bf3856ad364e35_10.0.20348.1070_en-us_e5b6e986575e5fc7') from backups directory with disposition (2). A backup file may not exist or may be corrupt. Falling back to WU.
2023-08-22 08:38:48, Info                  CSI    0000000c Warning: Unable to repair manifest for component ([l:101 ml:140]'amd64_microsoft-windows-e..e-library.resources_31bf3856ad364e35_10.0.20348.587_en-us_fad799f99dbd087d') from backups directory with disposition (2). A backup file may not exist or may be corrupt. Falling back to WU.
2023-08-22 08:38:48, Info                  CSI    0000000d Warning: Unable to repair manifest for component ([l:95 ml:140]'amd64_microsoft-windows-mprmsg.resources_31bf3856ad364e35_10.0.20348.617_en-us_6d9965ef57b6b17f') from backups directory with disposition (2). A backup file may not exist or may be corrupt. Falling back to WU.
2023-08-22 08:38:48, Info                  CSI    0000000e Warning: Unable to repair manifest for component ([l:97 ml:140]'amd64_microsoft-windows-netjoin.resources_31bf3856ad364e35_10.0.20348.1129_en-us_20000b7c03d8f79d') from backups directory with disposition (2). A backup file may not exist or may be corrupt. Falling back to WU.
2023-08-22 08:38:48, Info                  CSI    0000000f Warning: Unable to repair manifest for component ([l:101 ml:140]'amd64_microsoft-windows-s..rver-apis.resources_31bf3856ad364e35_10.0.20348.946_en-us_47e7c7782d0c4add') from backups directory with disposition (2). A backup file may not exist or may be corrupt. Falling back to WU.
2023-08-22 08:38:48, Info                  CSI    00000010 Warning: Unable to repair manifest for component ([l:101 ml:140]'amd64_microsoft-windows-t..visioning.resources_31bf3856ad364e35_10.0.20348.681_en-us_ee1e1db0a4d61970') from backups directory with disposition (2). A backup file may not exist or may be corrupt. Falling back to WU.
2023-08-22 08:38:48, Info                  CSI    00000011 Warning: Unable to repair manifest for component ([l:102 ml:140]'amd64_microsoft-windows-x..nrollment.resources_31bf3856ad364e35_10.0.20348.1070_en-us_f622c85af3c5bf66') from backups directory with disposition (2). A backup file may not exist or may be corrupt. Falling back to WU.
2023-08-22 08:38:48, Info                  CSI    00000012 Warning: Unable to repair manifest for component ([l:101 ml:140]'amd64_microsoft-windows-b..os-loader.resources_31bf3856ad364e35_10.0.20348.707_en-us_5f5d1add6df06bb5') from backups directory with disposition (2). A backup file may not exist or may be corrupt. Falling back to WU.
2023-08-22 08:38:48, Info                  CSI    00000013 Warning: Unable to repair manifest for component ([l:101 ml:140]'amd64_microsoft-windows-b..t-windows.resources_31bf3856ad364e35_10.0.20348.707_en-us_0541598bba15df98') from backups directory with disposition (2). A backup file may not exist or may be corrupt. Falling back to WU.
2023-08-22 08:38:48, Info                  CSI    00000014 Warning: Unable to repair manifest for component ([l:102 ml:140]'amd64_microsoft-windows-i..rityzones.resources_31bf3856ad364e35_11.0.20348.1547_en-us_5a9d3ba93d33d97a') from backups directory with disposition (2). A backup file may not exist or may be corrupt. Falling back to WU.
2023-08-22 08:38:48, Info                  CSI    00000015 Warning: Unable to repair manifest for component ([l:102 ml:140]'amd64_microsoft-windows-f..lientcore.resources_31bf3856ad364e35_10.0.20348.1070_en-us_88703db9cfab4f1c') from backups directory with disposition (2). A backup file may not exist or may be corrupt. Falling back to WU.
2023-08-22 08:38:48, Info                  CSI    00000016 Warning: Unable to repair manifest for component ([l:97 ml:140]'amd64_microsoft-windows-com-base.resources_31bf3856ad364e35_10.0.20348.261_en-us_a0fd3234c7cb5151') from backups directory with disposition (2). A backup file may not exist or may be corrupt. Falling back to WU.
2023-08-22 08:38:48, Info                  CSI    00000017 Warning: Unable to repair manifest for component ([l:102 ml:140]'amd64_microsoft-windows-pktmon-setup.resources_31bf3856ad364e35_10.0.20348.1194_en-us_94ecc3fc4582d08b') from backups directory with disposition (2). A backup file may not exist or may be corrupt. Falling back to WU.
2023-08-22 08:38:48, Info                  CSI    00000018 Warning: Unable to repair manifest for component ([l:101 ml:140]'amd64_microsoft-windows-s..ls-nltest.resources_31bf3856ad364e35_10.0.20348.469_en-us_faa1d81fa8194bb1') from backups directory with disposition (2). A backup file may not exist or may be corrupt. Falling back to WU.
2023-08-22 08:38:48, Info                  CSI    00000019 Warning: Unable to repair manifest for component ([l:92 ml:140]'amd64_networking-mpssvc-svc.resources_31bf3856ad364e35_10.0.20348.380_en-us_6fcf8c0c18abfa6d') from backups directory with disposition (2). A backup file may not exist or may be corrupt. Falling back to WU.
2023-08-22 08:38:48, Info                  CSI    0000001a Warning: Unable to repair manifest for component ([l:100 ml:140]'amd64_microsoft-windows-cryptui-dll.resources_31bf3856ad364e35_10.0.20348.803_en-us_ec228fcc28497607') from backups directory with disposition (2). A backup file may not exist or may be corrupt. Falling back to WU.
2023-08-22 08:38:48, Info                  CSI    0000001b Warning: Unable to repair manifest for component ([l:101 ml:140]'amd64_microsoft-windows-d..ne-netdom.resources_31bf3856ad364e35_10.0.20348.469_en-us_9c042e55b94b672a') from backups directory with disposition (2). A backup file may not exist or may be corrupt. Falling back to WU.
2023-08-22 08:38:48, Info                  CSI    0000001c Warning: Unable to repair manifest for component ([l:96 ml:140]'amd64_microsoft-windows-com-ole.resources_31bf3856ad364e35_10.0.20348.261_en-us_ccd40c40ad1a758e') from backups directory with disposition (2). A backup file may not exist or may be corrupt. Falling back to WU.
2023-08-22 08:38:48, Info                  CSI    0000001d Warning: Unable to repair payload file ([l:28]'AppXDeploymentServer.dll.mui') for component ([l:101 ml:140]'amd64_microsoft-windows-a..nt-server.resources_31bf3856ad364e35_10.0.20348.143_en-us_6a05157b5549d99c') from backups directory with disposition (2). A backup file may not exist or may be corrupt. Falling back to WU.
2023-08-22 08:38:48, Info                  CSI    0000001e Warning: Unable to repair payload file ([l:14]'srpapi.dll.mui') for component ([l:98 ml:140]'amd64_microsoft-windows-appidcore.resources_31bf3856ad364e35_10.0.20348.202_en-us_42181860d296ee66') from backups directory with disposition (2). A backup file may not exist or may be corrupt. Falling back to WU.
2023-08-22 08:38:48, Info                  CSI    0000001f Warning: Unable to repair payload file ([l:13]'AcRes.dll.mui') for component ([l:101 ml:140]'amd64_microsoft-windows-a..necoreuap.resources_31bf3856ad364e35_10.0.20348.112_en-us_19e831645673184d') from backups directory with disposition (2). A backup file may not exist or may be corrupt. Falling back to WU.
2023-08-22 08:38:48, Info                  CSI    00000020 Warning: Unable to repair manifest for component ([l:98 ml:140]'amd64_microsoft-windows-kernel32.resources_31bf3856ad364e35_10.0.20348.1668_en-us_e57453745790bb1e') from backups directory with disposition (2). A backup file may not exist or may be corrupt. Falling back to WU.
2023-08-22 08:38:48, Info                  CSI    00000021 Warning: Unable to repair manifest for component ([l:95 ml:140]'amd64_networking-mpssvc-admin.resources_31bf3856ad364e35_10.0.20348.1726_en-us_e93b07eec9215c7d') from backups directory with disposition (2). A backup file may not exist or may be corrupt. Falling back to WU.
2023-08-22 08:38:48, Info                  CSI    00000022 Warning: Unable to repair manifest for component ([l:102 ml:140]'amd64_microsoft-windows-t..visioning.resources_31bf3856ad364e35_10.0.20348.1726_en-us_ae012c4d4cfafeb1') from backups directory with disposition (2). A backup file may not exist or may be corrupt. Falling back to WU.
2023-08-22 08:38:48, Info                  CSI    00000023 Warning: Unable to repair manifest for component ([l:99 ml:140]'amd64_microsoft-windows-rpc-local.resources_31bf3856ad364e35_10.0.20348.1607_en-us_440f439fefdcc0de') from backups directory with disposition (2). A backup file may not exist or may be corrupt. Falling back to WU.
2023-08-22 08:38:48, Info                  CSI    00000024 Warning: Unable to repair manifest for component ([l:102 ml:140]'amd64_microsoft-windows-s..ineclient.resources_31bf3856ad364e35_10.0.20348.1607_en-us_f50e51060f6b8cc9') from backups directory with disposition (2). A backup file may not exist or may be corrupt. Falling back to WU.
2023-08-22 08:38:48, Info                  CSI    00000025 Warning: Unable to repair manifest for component ([l:102 ml:140]'amd64_microsoft-windows-s..ls-nltest.resources_31bf3856ad364e35_10.0.20348.1726_en-us_ba6748605055986a') from backups directory with disposition (2). A backup file may not exist or may be corrupt. Falling back to WU.
2023-08-22 08:38:48, Info                  CSI    00000026 Warning: Unable to repair manifest for component ([l:93 ml:140]'amd64_networking-mpssvc-svc.resources_31bf3856ad364e35_10.0.20348.1726_en-us_2fb3a0a4c0cff07a') from backups directory with disposition (2). A backup file may not exist or may be corrupt. Falling back to WU.

.... so I don't think we can keep creating "custom" fixes for your problem, and expect a result in any realistic time frame, and that the best solution to it is to perform a repair install / inplace upgrade.

  • Mount the Windows Server ISO and run Setup.exe. You can use the Microsoft Evaluation Centre to download the ISO files.
  • Use the option Download updates, drivers, and optional features (recommended) and click Next.
  • Note: If you don't want to update during the in-place upgrade, press Change how setup downloads updates and select Not right now - !!! Not recommended !!!
  • Depending on your Windows Server version and license, you may see a screen prompting you to enter the licensing key.
  • In the next screen, select the image of the installed Windows Server edition and click Next.
  • Then accept the EULA. To perform a in-place upgrade, you need to check keep personal files and apps. Then click Next.
  • After clicking Next, an upgrade process will start checking for updates, when this is ready click install to start the in-place upgrade.
 
I understand. Thank you for your assistance during this period.
I will research how to reinstall the system.

Thank you again for everything you’ve done(y)

 
You're welcome, sorry we couldn't find a more convenient solution.

I'll leave this topic open, so that if you have any problems with the repair install then you can get back in touch.
 
After using the Windows Server ISO file for a repair installation, Windows Update is now functioning completely normally.

Thank you again.
 
You're welcome.

Glad you were able to resolve things with the repair install. Thanks for letting me know. (y)

I'll mark this topic as solved then.
 

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

Back
Top