Hi, tocguy
Thanks for reaching out to Microsoft Q&A forum.
Sorry for this frustrating experience that you're having. Both errors you’re showing point to a Click-to-Run (App-V based) Office install that’s either partially broken or being forced to run while its required service is disabled, so Office can’t repair itself and the installer can’t complete.
You can try these recommendations to solve this issue:
1) Re-enable the Click-to-Run service (this is required for any C2R-based Office to start, repair, or uninstall cleanly)
- Press Win + R, type services.msc, press Enter.
- Find Microsoft Office Click-to-Run service (often shown as ClickToRunSvc).
- Open Properties and set Startup type to Manual or Automatic (not Disabled), then click Start if it’s stopped.
- Try launching an Office app again. If it opens, immediately go to Step 2 below to repair the missing DLL properly.
Why this matters: error 30068-4 (1058) is exactly what Office throws when that service is disabled.
2) Repair Office to restore the missing App-V subsystem DLL (AppVIsvSubsystems32.dll)
Do this after the service is no longer Disabled:
- Control Panel > Programs and Features > select Microsoft Office > Change.
- Run Quick Repair first. If it still fails, run Online Repair next.
That specific DLL error is a known Office symptom, and Microsoft’s recommended fix is Repair (then reinstall if Repair can’t fix it).
3) If your goal is specifically “CD / MSI Office” (and you don’t want C2R Office at all), remove C2R cleanly first, then install MSI
If you truly have an MSI-based installer, it should not need Click-to-Run, but your screenshots indicate your machine is currently trying to run Click-to-Run Office components. The clean path is:
Use Microsoft’s Office uninstall troubleshooter to remove the existing Office completely (this is the official method Microsoft points to when installs/repairs are stuck).
Reboot, then run your CD setup again.
Important: do not re-disable the Click-to-Run service until you’ve fully removed any Click-to-Run Office. Disabling it mid-stream is what causes the “service is disabled” loop and blocks repair/uninstall.
4) If the service keeps flipping back to Disabled
That usually means something outside Office is enforcing it (policy, “debloat” tools, aggressive antivirus hardening, or service-tweakers). Temporarily undo that change long enough to complete Repair or Uninstall, then lock it down again after the C2R Office is gone.
Hope this can help you. Don't hesitate to get back if you need more help.
If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment."
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.