Angolo di WindowsWindows error 1075 can appear when the Workstation service fails to start correctly because of one of its dependencies.
The problem is therefore not necessarily with the network connection itself, but may be related to the internal configuration of the services Windows uses to manage SMB (Server Message Block) connections to NAS devices, servers, routers, and other shared resources.
When the Workstation service is not started, various problems can occur, including being unable to access mapped network drives.
What are the symptoms of error 1075?
One of the most common cases is when a network drive, for example Y:, suddenly becomes inaccessible.
Windows may display messages such as:
Microsoft Windows Network: The network is not present or not started
or:
The path is not accessible.
In some cases, the situation can be even more unusual: the network device is visible under This PC as a network location and its contents can be viewed, while the mapped drive still does not work.
This behavior can be an important clue.
The two access methods, in fact, do not necessarily use the same Windows components. A mapped drive that uses SMB depends on the Workstation service and its network redirector, while some network locations may use different mechanisms or protocols.
For this reason, being able to see the device on the network does not necessarily mean that the SMB component used by mapped drives is working correctly.
Check the Workstation service dependencies
The service involved in the problem is Workstation, identified internally by Windows as:
lanmanworkstationThis service is essential for client connections to servers and shared resources over SMB.
When error 1075 is returned, Windows is essentially indicating that one of the dependencies required by the service no longer exists or has been marked for deletion.
One possible cause is an inconsistent configuration left behind after changing or removing some Windows components, particularly those related to SMB 1.0.
To check which dependencies are configured for the Workstation service, open Command Prompt as an administrator and type:
sc qc lanmanworkstationIn the command output, look for the entry:
DEPENDENCIESThis section shows the services that Workstation depends on.
If mrxsmb10appears among the dependencies, the system may still be referencing the old SMB component 1.0, even though it has been removed or disabled.
This type of inconsistent configuration can cause error 1075.
How to fix Workstation dependencies
Once we have checked the configuration, we can realign the Workstation service dependencies using the command sc config.
Then open Terminal or Command Prompt as an administrator and run:
sc config lanmanworkstation depend= Bowser/MRxSmb20/NSIPay attention to one important detail: the command must include a space after depend=.
The command sets the service dependencies to use the components required for modern SMB networking:
- Bowser
- MRxSmb20
- NSI
This removes any obsolete reference to mrxsmb10.
At this point, we can try starting the service again:
net start lanmanworkstationIf the command completes successfully, the Workstation service should be operational again.
Check that the service is actually working
After carrying out the procedure, it is a good idea to check the service status with:
sc query lanmanworkstationThe output should show:
STATE : 4 RUNNINGThis indicates that the Workstation service is running correctly.
At this point, we can do a practical test by opening File Explorer and checking access to the network drive that was not working before.
If, for example, we had a drive Y: connected to a NAS or server, it should be accessible again as normal.
Restart Windows and check that the fix persists
The final step, which is often overlooked, is to restart the computer completely.
This lets us check that the change has not only resolved the problem temporarily and that Windows can start the Workstation service automatically after restarting.
After signing in to Windows, check again:
sc query lanmanworkstationand verify that the service is still:
RUNNINGAlso check that the network drives are available again.
In conclusion
Error 1075 associated with the Workstation service does not necessarily indicate a problem with the network or NAS.
In many cases, the problem may be caused by a service dependency that is still configured incorrectly, especially after changes to Windows SMB components.
The command:
sc qc lanmanworkstationlets you quickly check the current configuration, while:
sc config lanmanworkstation depend= Bowser/MRxSmb20/NSIallows you to realign the service dependencies.
Once restarted Workstation with:
net start lanmanworkstationyou can check the result and check the network drives again.
This procedure is therefore particularly useful when network resources seem reachable, but mapped SMB drives do not work and Windows returns error 1075.
