Error 1075 means the service depends on another service that Windows can no longer find, usually because that dependency was uninstalled, renamed, or marked for deletion while something still pointed at it.
sc query followed by the dependency name in an admin Command Prompt. If it reports that the service does not exist, the dependency entry is stale.sc config with the service name and depend= followed by a space and nothing after it, which clears the dependency list. If the service needs other dependencies, list them instead, separated by slashes, like depend= RpcSs/Winmgmt.sc config command needs a space after each equals sign, like depend= , and no space before it. Without the space, the command fails with error 87.
If the service still reports 1075 after clearing the stale dependency, the program itself may be partly uninstalled. Remove it fully, restart, and install it again from the vendor's official installer.
Why does a service depend on something that does not exist? Usually because the dependency was uninstalled or removed by another program, or a service was deleted while it was still listed as a dependency. The reference stays behind even though the service is gone.
Is it safe to clear a service's dependencies? Clearing the list with sc config and an empty depend= only removes the dependency references, not the service itself. Reinstalling the program afterward rebuilds the correct list.