Jump to content

Recommended Posts

Posted

Are any updates safe to apply?

I guess that’s down to your own interpretation of safe!

 

We had a Business Critical incident yesterday after two updates KB4093108 and KB4093118 were applied to Win 7 Pro machines.

 

Two out of 3 machines stopped printing overnight from a bespoke access database that generates Invoices.

 

After a few hours of head scratching by using using Procmon we identified that the only working PC was connecting to the databases UNC path with the SMB1 short netbios name \\server-file\database\mydata.mdb

The ones with the latest update were connecting with SMB2/3 using the FQDN path, \\server-file.mydomain.local\mydata.mdb

 

The database itself was fine allowing input, searching, indexing etc but printing which outputs to a Word document resulted in a VB error.

 

Users drives are mapped using GP’s and the working PC had not yet applied the WUS updates, it was pending a restart so we knew it was update related.

 

We ended up working around the issue by remapping the UNC path by legacy login scripts to the shortened NETBIOS server name instead of the FQDN thus forcing SMB1 (The server is 2012 and will still accept SMB1 if negotiated)

 

The latest updates appear to have no impact on any other systems of which there are 30+ it only hit these three PC’s that need to use the legacy Access Database.

 

So, as always the MS security roll ups can have some very strange side effects especially on older VB based apps that you may have over looked, so as always be prepared to have to go the extra mile before blaming the updates for a problem as in my case I have been expecting this for years... the developer by now would be in his 80’s and I suspect the only support would be via Ouija Board!

 

We are now going to have to move these databases into a dedicated share on a 2012 server as everything else will shortly be moving onto 2016 where SMB1 is no longer supported whilst the business owner expedites an alternative Invoicing solution.

 

I’ve come to expect issues with every update, especially where client systems and applications are concerned anything more than a couple of years old is vulnerable and anything not Microsoft relies on a 3rd party to provide its own updates to match.

 

Expect the unexpected.

  • Thanks 1
Posted

Hi

KB4093123 and KB4088883 installs but after rebooting the system you are damaged. Enters the screen of the option to repair. You have to roll back these updates in safe mode because the system is dead. That's how our beloved Microsoft makes fun of us ...

 

best regards

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...