sfc /scannow WILL NOT function

(1) It looks to me you've got a good MSIExec.exe. Yours is for 1809, but it's got a date 2 months newer even than mine which is 1909. Something is nutty with Autoruns, looks like, regarding Timestamps. One of them on a file I've got looks pretty old too (1982).

(2) Regarding Fontbase, you did enough to remove that useless entry. It went to a file that no longer existed. If the image path had led to an empty folder (or one that looked pretty much it belonged only to Fontbase), it would have been tidy to delete that folder. Actually, right-clicking Fontbase in Autoruns & selecting "Jump to image" likely would have said whether the folder still existed by opening it or not. But doing a search in File Explorer probably was risky. I'm glad it found nothing that could be deleted.

(3) Right-click "C:\PROGRA~3\INTERE~1\INTERE~2.DLL" in Autoruns, & select "Jump to image". What happens? If it says the folder doesn't exist, just delete the entry. Otherwise, let's see what's in the folder.

(4) That's a pity that SFC still will not run in Windows. But /Checkhealth is the least informative option for DISM. Do this one...

DISM  /Online  /Cleanup-Image  /ScanHealth

If it says "repairable", then do a "/RestoreHealth" which actually makes the repairs. And try SFC afterward. I hope it will run.

(5) OMG, read this to see what sedlauncher.exe is...

https://www.askvg.com/what-are-sedsvc-exe-sedlauncher-exe-files-and-rempl-folder-in-windows-10/

What are Sedsvc.exe, Sedlauncher.exe Files and REMPL Folder in Windows 10?

I've read elsewhere, KB4023057 comes in when your version of Windows is two versions too old. That's what yours is, now that 2004 is about to be released. (I guess 1903 isn't counted). So KB4023057 is trying to give you 1909.

Not sure what to suggest. Must hit the sack.

1a) I followed the fontbase path but there was no files, I deleted the entry and ran a find search in file explorer. It found some folders that wouldn't delete because they can't be found.

1b)------------

1c) I don't have the "Resubmit to Virus Total" just "Check Virus Total" like you say 1809 vs 1909 but when I clicked it, it came back with The operation times out. One drive keeps asking me to let it clear up stuff it says it's stored on one cloud or drive well one of the them but not sure if I totally trust it to be careful with it.

1d)\Microsoft\Windows\rempl\shell            File not found: C:\Program Files\rempl\sedlauncher.exe      

After I get to the rempl folder there is a sub-folder called logs and is full of LauncherRemediations, Remeidations, and ServiceRemediations going back a couple years but i don't see any shell folder.

I go this off the Winsows Club

1] What is REMPL folder?

If you are not aware, there are certain files and folders that are used by Windows 10 Updates to make sure that any updates rolled out by Microsoft as future or feature updates are installed on your PCs without any issues. REMPL folder happens to be one such folder.

The folder can be seen under C:\Program Files\rempl and contains files like – remsh.exe, Sedlauncher.exe, Sedsvc.exe, disktoast.exe, rempl.exe and others. The Remsh.exe executable typically is a special Windows Update that includes reliability improvements to Windows Update Service components in older versions of Windows 10.

It exists on only a few Windows 10 systems. The folder includes an automated troubleshooting tool that’s deployed only on those PCs which report issues updating to the most recent version of Windows 10. When this occurs, this special package is automatically downloaded by Windows 10, and it tries to determine the reasons for the failure and then attempts to remediate them.

It is not a malware or virus, but a part of a reliability update pushed out by Microsoft. Also, it can be viewed as an automated troubleshooting tool, deployed to determine and report the reason(s) for the failure (downloading updates) and then attempt to remediate them.

• I don't know what C:\PROGRA~3\INTERE~1\INTERE~2.DLL            File not found: C:\PROGRA~3\INTERE~1\INTERE~2.DLL.exe       File explorer didn't find it. I couldn't find what it was on google either.

1e) sfc run as administrator = Windows Resource Protection could not start the repair service.

DSIM = C:\WINDOWS\system32>DISM /Online /Cleanup-Image /CheckHealth

Deployment Image Servicing and Management tool

Version: 10.0.17763.1

Image Version: 10.0.17763.557

No component store corruption detected.

The operation completed successfully.

(1) Regarding that Autoruns report...

(a) Fontbase  apparently didn't uninstall elegantly. It left behind its Startup entry & even left it checked. You should right-click it, & select "Delete" which removes the entry from the Registry (& from Autoruns). I might also follow that image path to its ultimate destination folder (the ellipsis indicate there's more - point to it or expand the column). If you can determine that ultimate folder belonged entirely to Fontbase, then delete it too for neatness sake.

(b) My entry named "OneDrive" wasn't flagged by any antivirus, but I don't suppose yours is infected. Mine is in a different location than yours, but I'm 1909. Also, it might be the SysWOW64 folder (where yours is) gets involved in legit circumstances you have invoked (but I didn't)...

(c)My "Onedrive Standalone Updater" is named a bit differently & is in a different location than yours. Maybe that's an 1809/1909 difference -- I don't know. But when you see "the operation timed out" in the Virus Total column, right-click it, & select "Resubmit to Virus Total". It may take a minute/so, but should return with a result.

(d) "Microsoft\Windows\re..." & "C:\Progra~3\Inter..." are like Fontbase (above). Right-click those two, & select "Copy". Then paste them here so I may see the full entry names & the full paths. Can you explain what they are/were? Does the ultimate folder in the path have anything in it &/or does it look entirely like something you've uninstalled? Treat them like I said for Fontbase, if they meet that criteria.

(e) My MSIServer entry got no positive, but yours looks OK on that. However, yours has a date of 10/18/1973. It is ancient compared to mine of 2/14/2020...

That one is the Windows Installer service -- could be why Windows Update is bad for you. I can't believe SFC didn't repair that one. I know you did the offline SFC. Are you able to do one in Windows now? If so -- check the date on "C:\Windows\System32\MSIExec.exe" afterwards. I can't believe 1809 should have one as old as yours.

Edit: Now I'm not sure what that Timestamp is -- it doesn't say in the Help pages. Right-click MSIServer in Autoruns, & select Properties. What does yours show at the Details tab...?...

Still, try a DISM & SFC to see whether it fixes anything. Your Timestamp is suspicious.