<p>Once again Windows update messed up some of our Windows 2008 Servers. After the successful installation of Windows update and a server restart, we could not ping the server.</p>
<p><img class="alignnone size-full wp-image-550" src="https://www.wincert.net/wp-content/uploads/2015/01/windows-server.jpg" alt="Windows Server,printer,hp,hp deskjet,kms,backup,notification area,update,wsus,illegaltag,printer port,scheduled task,root hints,installation file missing,spoolsv.exe,installer error,iis6,home server,print drivers, print spooler,windows update,metro apps,auto-login,standalone installer,iis6,ie11 compatibility view; cannot access template; group policy; .NET Framework 3.5; Licenses are not available for this Remote Desktop Session" width="720" height="340" /></p>
<p>After checking the server on the VMware console I could see that some services like Netlogon and Workstation along with their dependencies could not start.</p>
<p><img class="alignnone wp-image-3441 size-full" title="Windows could not start the Netlogon service" src="https://www.wincert.net/wp-content/uploads/2019/12/netwlogon-error.jpg" alt="" width="410" height="150" /></p>
<p>When I have checked the logs I could see that the root cause of this issue is related to the Browser Support Driver service which failed to start.</p>
<p>Now, I had to compare the bowser.sys file with the same file on the working server. The bowser.sys file can be found in the following location:<br />
<strong>C:\Windows\System32\drivers</strong></p>
<p><img class="alignnone wp-image-3443 size-full" title="Windows could not start the Netlogon service" src="https://www.wincert.net/wp-content/uploads/2019/12/bowser-file.jpg" alt="" width="579" height="31" /> <img class="alignnone wp-image-3442 size-full" title="Windows could not start the Netlogon service" src="https://www.wincert.net/wp-content/uploads/2019/12/bowser-file-2.jpg" alt="" width="609" height="26" /></p>
<p>As you can see, these files had different modified dates. This could have been caused by the failed update.</p>
<p>In order to solve this problem, just copy and overwrite the bowser.sys file from the working server and restart. After the server is restarted all of the Automatic services should be started normally.</p>