Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Sunday, December 1, 2019 12:55 AM
Hi,
I am one of the masses to have received the Workstation error/Windows file sharing not turning on, and after spending 3 evenings sifting through forums, I'm finally at a point where I can't find an answer. I've done everything from the SFC scans to disabling/enabling various networking services through CMD and Powershell, but I am now just stuck with this message from Event Viewer caused from trying to start the Workstation service:
"The Workstation service depends on the following service: msi. This service might not be installed."
I can't find anything online relating to this message, and none of the Windows recovery tools have picked this up to repair. Any ideas will be greatly appreciated, I'm not sure what else I can share that will be useful. I'm really trying to avoid a full Windows reset just to connect to a NAS drive.
Many thanks,
Jake
All replies (7)
Sunday, December 1, 2019 1:16 AM ✅Answered | 1 vote
1) Make a backup of or export this registry key:
|
2) Then open regedit.exe (Start -> Run)
3) Browse to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lanmanworkstation
3) Empty the value of “DependOnService”
4) Make sure the value of “Start” is set to 2
5) Reboot the PC
Repeat the same steps for Server service:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lanmanserver
S.Sengupta,Microsoft MVP Windows and Devices for IT, Windows Insider MVP
Monday, December 2, 2019 10:18 AM ✅Answered | 1 vote
Hello Jake,
Did you follow S.Sengupta's advice? What is the current state of the "DependOnService" setting for the service? Are all three of the services NSI, Bowser and MRxSmb20 running?
If all of the services that LanmanWorkstation actually depends on (NSI, Bowser and MRxSmb20) and all of the services (perhaps erroneously included) in the "DependOnService" setting are also running, then the service might start...
Gary
Sunday, December 1, 2019 1:15 PM
Thank you, I have done this and now the service start progress bar fails further along and I am now just getting the following error:
"The Workstation service terminated with the following error:
The system cannot find the file specified."
Sunday, December 1, 2019 5:29 PM | 1 vote
Hello Jake,
Did you copy and paste that message from the Event Viewer or explicitly type the text?
I ask, because on my system, the LanmanWorkstation service depends on Bowser/MRxSmb20/NSI. It might just be a coincidence that MSI and NSI differ by just one letter, but "msi" is not a service name that I can find. One often sees the extension ".msi" or the abbreviation MSI (Microsoft Installer in both cases) and there is a service with the name "msiserver" (Description: Windows Installer), but no service named plain "msi".
Gary
Monday, December 2, 2019 9:46 AM
Hi Gary,
That's where I've been thrown, I copied and pasted the text from event viewer, and looking online I can't find anything relating to this service either; just the MS Installer
Monday, December 2, 2019 6:20 PM
I am assuming NSI is the Network Store Interface? I came across this before and it is running fine, and I have followed guides to make sure the SMB services are running, including disabling and re-enabling SMB1 in Programmes and Features. I have just found a .bat to restore the Bowser settings to default, and Workstation is now giving a new errors:
The Workstation service terminated with the following error:
This security ID may not be assigned as the owner of this object.
The Computer Browser service depends on the Workstation service which failed to start because of the following error:
This security ID may not be assigned as the owner of this object.
Looking through the event viewer logs, this error started before running the .bat and after booting up the computer this evening.
Monday, December 2, 2019 6:25 PM
Okay, I found how to solve this, I just overwrite the Log In tab and re-applied the settings and it magically worked and file sharing had turned itself back on.
Thank you so much for your help!