Share via

Error 1075 dependency services do not exists

Anonymous
2018-06-04T20:06:36+00:00

FYI, the system in question is an Intel Core 2 Quad with 8 GB RAM and a 1TB HD.

The operating system is 64 bit Win 10 Pro, Version 1709,  OS Build 16299.461

Ever since a recent update, the Workstation service cannot be started and the above error message results when I attempt to start it.

Furthermore, when, from an Admin command prompt, I attempt NET VIEW (which worked just fine last week sometime) I get a 2194 error..

I have used SYSTEM RESTORE to "step back" to at least one previous restore point, have searched the web for at least two weeks, without finding a solution to this problem, and am at my wits end.

I can "see" all the computers and our NAS on my local network, and can see and connect to the networked printers, but absolutely cannot connect to any of the computers, nor our NAS, which I can "see" from this computer. One of the computers on our network cannot "see" this computer, but I can connect to it from that computer by inputting \NAMEOFBOX into QuickAccess from it and can access the files and directories I have shared on this one.

I can no longer run backups to our NAS from this computer since the system on this computer will no longer let me connect.

I have examined and, where necessary, updated network sharing parameters, have run SFC /SCANNOW (which DID find, and correct, a corrupted file or two), even tried netcfg -d (as suggested on one website) then rebooted and so far, nothing!

Has anyone here run into this within the last week or two, and if so, have you found a solution? I am going absolutely nuts!!! :-(

Windows for home | Windows 10 | Internet and connectivity

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

12 answers

Sort by: Most helpful
  1. Anonymous
    2018-06-05T16:09:43+00:00

    I am seeing, as far as I can tell, all the dependencies, and ALL are running and ALL are on "Automatic".

    FYI, I was an "IT Professional" for over 30 years at the University of Idaho, and this one has me completely snowed.

    At this point, I am thinking about completely reinstalling the OPSYS, but, as you know, that is a big job, and I really don't want to do that.

    I am not pleased. :-(

    And what really baffles me is that this problem popped up silently and suddenly. No warning of any kind. I turned the 'pooter off one night and went to bed, and when I got up the next morning and turned it on, it was there.

    I'm going to run SFC /SCANNOW again to see if anything pops up...

    I doubt if that will tell me much.

    BTW, I remember, vividly, when XP-Pro first came out: I forbid anyone I worked with to change to it for at least a year after that point since it was so buggy, but eventually MS got it stable. In my opinion, Win 10 is worse. I hope MS gets it lined out eventually...

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  2. Anonymous
    2018-06-05T04:19:49+00:00

    Sorry, I thought it was a simple fix. I'll admit I'm baffled.

    OK, lets go back to first principles. Restart the computer and see if the problem has been "fixed".

    Run the WINVER command. What Version and Build numbers do you have?

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2018-06-05T00:40:48+00:00

    ALL dependencies are not only already set to Automatic, but ALL are running.

    Any other ideas?

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2018-06-04T22:33:18+00:00

    Also, check for the corresponding error in the Event Log as that may give some clue what is failing.

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2018-06-04T21:14:21+00:00

    In the start menu search for services.msc

    right click on it

    select run as admin

    submit the admin password when prompted

    scroll to find the service (workstation happens to be at the bottom of the list)

    right click on it

    select properties

    click on the Dependencies tab

    in the top window it lists services that have to already be running for this one to start. there are 3. Go to those 3 and start them. For all 4 services (the 3 dependent ones and this one, in the General tab also make sure to set the "startup type" to "automatic" or "automatic delayed"

    Was this answer helpful?

    0 comments No comments