Windows 10: Corrupt 'sfc /scannow' after Threshold 2 upgrade

Hi Everyone
I have a problem with 'sfc /scannow' run from Command prompt (Admin) in Windows version 1511 (OS Build 10586.11)
I have attached the 1st CBS Log I saved….(I have 2 other later logs saved)
I had been running Windows 10Pro 64bit upgrade on a 8.1Pro 64bit OS HP laptop. With 'no integrity found' for the past 3 weeks maintenance checks and no noticeable problems.
The installation of Windows 10 was about 3 weeks ago.
I was offered the latest upgrade to version 1511 10586 in WU…I have installed the upgrade twice.The first install I had problems with the install and had to contact MS as I was stuck at 0% upgrade "Do not turn off your computer" for over 2 hours. With MS help I was able to install the upgrade, After rebooting and logging in I checked the sfc folder and it was corrupt and 'unable to repair'. When MS support called back I told the 'supervisor' about the corruption of sfc and he said …"Is the computer working fine, if it is then do not worry" (After 2 hours of operation, who knows if the computer is working correctly after a reinstall?) I said to him I need to have an uncorrupted sfc file as a 'base line' to monitor my computer…just not interested…I hung up
Sfc /scannow , now (11/20/15) takes about 8 to 10 minutes to run and comes back with the"unable to repair" sentence. I have run it 4 times with the same result.
As I said, I have installed twice…after the help of MS on the first installation, I decided to reinstall an image I had captured the day before I upgraded…The result is the same corruption of the sfc file with the upgrade to v10586.11. There are no more updates to install according to MU
Reinstalling the captured image returns my computers' sfc to 'no integrity's found'
I have followed thread…

SFC some corrupt files can not be fixed

But I do not have Nvidia drivers and I am really out of my depth. I really do not know how to read the CBS log...except 'cannot repair'
Any help would be gratefully appreciated in layman terms… I have very old eyes…
Thanks

:)

 

sfc/scannow corrupt file

This is because the system has corrupt files and is partially able to repair some of them. Here is a snip from the log:

0000608e [SR] Repairing corrupted file \??\C:\WINDOWS\System32\IME\IMEJP\IMJPPRED.DLL from store

2017-12-02 16:54:25, Info CSI 00006090 [SR] Repairing corrupted file \??\C:\WINDOWS\System32\IME\IMETC\IMTCTIP.dll from store

2017-12-02 16:54:25, Info CSI 00006092 [SR] Repairing corrupted file \??\C:\WINDOWS\SysWOW64\IME\IMEJP\IMJPSET.EXE from store

2017-12-02 16:54:26, Info CSI 00006094 [SR] Repairing corrupted file \??\C:\WINDOWS\System32\IME\IMEKR\imkrapi.dll from store

2017-12-02 16:54:26, Info CSI 00006096 [SR] Repairing corrupted file \??\C:\WINDOWS\SysWOW64\IME\IMEJP\IMJPLMP.DLL from store

2017-12-02 16:54:26, Info CSI 00006098 [SR] Repairing corrupted file \??\C:\WINDOWS\System32\IME\IMEJP\imjpuexc.exe from store

2017-12-02 16:54:26, Info CSI 0000609a [SR] Repairing corrupted file \??\C:\WINDOWS\System32\IME\IMEJP\IMJPTIP.DLL from store

2017-12-02 16:54:26, Info CSI 0000609c [SR] Repairing corrupted file \??\C:\WINDOWS\SysWOW64\IME\IMEJP\APPLETS\IMJPSKF.DLL from store

2017-12-02 16:54:26, Info CSI 0000609e [SR] Repairing corrupted file \??\C:\WINDOWS\IME\IMEJP\DICTS\IMJPZP.DIC from store

2017-12-02 16:54:26, Info CSI 000060a0 [SR] Repairing corrupted file \??\C:\WINDOWS\System32\IME\IMEJP\imjputyc.dll from store

2017-12-02 16:54:26, Info CSI 000060a2 [SR] Repairing corrupted file \??\C:\WINDOWS\SysWOW64\IME\IMEKR\APPLETS\imkrcac.dll from store

2017-12-02 16:54:26, Info CSI 000060a4 [SR] Repairing corrupted file \??\C:\WINDOWS\System32\IME\IMEKR\DICTS\imkrhjd.dll from store

2017-12-02 16:54:26, Info CSI 000060a5 [SR] Could not reproject corrupted file...

I suggest doing a repair install, as some system files are missing:

http://www.yourwindowsguide.com/2016/06/how-to-...

http://www.tenforums.com/tutorials/16397-repair...

 

sfc/scannow corrupt file

https://1drv.ms/u/s!ApJz2K2MUntDhjqDF49EhWYTUO50