Missy Morrison
asked on
Server 2003 after Wanna Cry patch KB4012598
Can get services to start due to dependencies - workstation. Browser works, just no network resources or RPC. Workstation service is stopped. Netlogon service is stopped - all throw relative errors when clicking on start.
Workstation error: Could not start the workstation service on Local computer. ERROR:1075 The dependency services does not exist or has been marked for deletion. Have exhausted reg edits suggestions - no results - about to resort to 'last known good.'
Thanks in advance
MM
Workstation error: Could not start the workstation service on Local computer. ERROR:1075 The dependency services does not exist or has been marked for deletion. Have exhausted reg edits suggestions - no results - about to resort to 'last known good.'
Thanks in advance
MM
Have you rebooted since applying the patch? That's a requirement.
i would also look at uninstalling the update; something in your environment might have caused the network stack to break
might also considering restoring from backup (you do have one, right?)
might also considering restoring from backup (you do have one, right?)
ASKER
@Adam Brown, yes a reboot was necessary and performed. No changes are realized without a reboot.
@Seth Simmons, have uninstalled the patch. and yes to the 'gotcha' question about backups. I have one.
Microsoft posted a 'hotfix' for this problem, others have experienced this issue, but there are few different variables. The 'hotifx' available from Microsoft is for x64. Have you guys seen one for x86?
Thanks for your suggestions.
@Seth Simmons, have uninstalled the patch. and yes to the 'gotcha' question about backups. I have one.
Microsoft posted a 'hotfix' for this problem, others have experienced this issue, but there are few different variables. The 'hotifx' available from Microsoft is for x64. Have you guys seen one for x86?
Thanks for your suggestions.
There is a x86 version of the patch too
Windows6.0-KB4012598-x86.m su
http://download.windowsupdate.com/c/csa/csa/secu/2017/02/windowsserver2003-kb4012598-x86-custom-enu_f617caf6e7ee6f43abe4b386cb1d26b3318693cf.exe
SHA1
13E9B3D77BA5599764C296075A 796C16A85C 745C
SHA256
FC7F28A72C117C2A8ECE591653 2048C8BF33 79C8638634 8C24319EAC 2C6B23C8
Windows6.0-KB4012598-x86.m
http://download.windowsupdate.com/c/csa/csa/secu/2017/02/windowsserver2003-kb4012598-x86-custom-enu_f617caf6e7ee6f43abe4b386cb1d26b3318693cf.exe
SHA1
13E9B3D77BA5599764C296075A
SHA256
FC7F28A72C117C2A8ECE591653
ASKER
@Dmitri Farafontov I was able to obtain the initial patch for x86 as you noted above. However, it did break RPC, Netlogon and Workstation. The 'hotfix' that came after that to fix these issues is only for x64. At least that is all I have found.
Do you have the KB article for it?
ASKER
Yes
I would reimage and start over
ASKER
I am being prompted by email to accept a solution or close the request. Unfortunately, there is not yet a solution to accept that has not been done before requesting help. I am not reimaging. Looking to reboot to a 'last known good'.
Additionally, Microsoft has been sloppy in sending the 'hotfix' for x86. If anyone notices, the available hotfix titled to be applicable for x86, download, it is for x64. No Go. Thanks Microsoft.
But I did get spammed by EE during this process. EE Support was ready to respond and did. Thanks for that.
Thanks contributors from EE. Your participation is appreciated. Must close this submission unresolved.
Good day to all,
Missy Morrison
Additionally, Microsoft has been sloppy in sending the 'hotfix' for x86. If anyone notices, the available hotfix titled to be applicable for x86, download, it is for x64. No Go. Thanks Microsoft.
But I did get spammed by EE during this process. EE Support was ready to respond and did. Thanks for that.
Thanks contributors from EE. Your participation is appreciated. Must close this submission unresolved.
Good day to all,
Missy Morrison
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Opening this up to Microsoft and asking them if they can release a patch is probably best course of action now.