Replacing it with a do-nothing version might unblock Offset setup but would bad in other ways. The FontCache service is an important system component. The SCM should log an error if a service fails to start, and that should at least give us an error code if not much more. If there’s nothing in the FontCache event log, check the System event log (Windows Logs / System) for an event logged by the Service Control Manager.If the service still failed to start, see if there’s anything in the FontCache event log.Check the status for FontCache (not FontCache3.0.0.0, which is something different).Check the status of the FontCache service via Task Manager:Start task manager (e.g., by right-clicking the task bar).We excluded Access from the install as most users don't need it and the ones that do needed to update their DB's before we deployed. Enable the DirectWrite-FontCache/Tracing log Install MS Access when the Office 365 suite is already installed We recently rolled out Office 365 2016 suite (C2R) using the Office Deployment Tool and SCCM."It’s possible that after the first failure to start, subsequent attempts would fail for an unrelated reason, in which case we’d need to reboot to determine the true cause. Apparently the FontCache3.0.0.0 service is something different.
0 kommentar(er)
