That was a marked improvement. It still failed DISM, but this is the first time it has event started the scanning process. Here is the output of the DISM tool.
Microsoft Windows [Version 6.2.9200]
(c) 2012 Microsoft Corporation. All rights reserved.
C:\Windows\System32>Dism /Online /Cleanup-Image /RestoreHealth
Deployment Image Servicing and Management tool
Version: 6.2.9200.16384
Image Version: 6.2.9200.16384
[==========================100.0%==========================]
Error: 582
An illegal character was encountered. For a multi-byte character set this includ
es a lead byte without a succeeding trail byte. For the Unicode character set th
is includes the characters 0xFFFF and 0xFFFE.
The DISM log file can be found at C:\Windows\Logs\DISM\dism.log
C:\Windows\System32>
C:\Windows\System32>
and here are the CBS logs.
https://providencecomputers-my.shar...hHuBoaFdjajYwBVOi5VO02GaOczh646EOmxg?e=AGlkwP
Thanks for your time!. Sleep well!