KB3097877 re-issued?

Layback Bear said:

I removed and hid KB3097877 Yesterday and got a new re-issue again today.
Just hid it again.
KB3097877 was screwing up my Realtek Audio on two computers.

It would be nice to know for sure if the new version still messes up Realtek Audio... but only if you have an image that you can restore to.

StuartMcArthur said:

Hello all,

Found this error late yesterday on some of our 60 or so field devices, scattered all over the country. Today we managed to use Kaseya to run a couple of scripts and force the machine to log in as the administrator account, once it was logged in we could connect remotely, remove the update, disable automatic updates (these tablets are on the verge of being phased out anyway) and then change the registry keys we had changed in the scripts back to their defaults. All in all, close to a best case scenario considering where we were yesterday.

Nice job getting them operational.

Are you going to risk installing the new version?

[QUOTE=UsernameIssues;3176100]

StuartMcArthur said:

Are you going to risk installing the new version?

Not a chance, on the other side of my desk is the new version of the tablet, tested and ready to be ordered. Not worth the (potential) trouble.

UsernameIssues said:

jalind said:

I have seen nothing that would lead me to believe that there's two versions of this update.

The version in the screenshots in my OP show an update that was published on 12 Nov.

Maybe the publish date can change without the KB changing... but it sure looks like a new offering. Those that hid the update will be offered it again if the update has indeed changed.


CBS.log indicates the install on the 10th and the 11th was:
KB3097877~31bf3856ad364e35~amd64~~6.1.1.1

CBS.log indicates the install on the 12th was:
KB3097877~31bf3856ad364e35~amd64~~6.1.1.2

Makes me wonder if I missed 6.1.1.0.


...or maybe those log entries don't mean what I think they mean.

Yes . . . it was updated to a new version . . . but getting that to install on five machines here was a real chore. I found the reference to it buried in MS's docs on the update. You would think they would headline it instead of hiding it. For whatever reason v1 installed yesterday and it persisted as the version that would be installed on all the machines even after uninstalling it and trying a reinstall. The process I finally used to get the revised version to install:

1. Downloaded the standalone KB install and installed it instead of using Windows Update . . . after ensuring the KB had been uninstalled. All the stuff still broke and looking at file version numbers showed a mix of original files (prior to update) and v1 versions. I was left wondering if the standalone was still v1 (downloaded it this morning), but wasn't going to spend the time ripping into the msu file to investigate. It is (or was as of this morning) still v1, or in the process v1 was still present on the machines and that was used in lieu of the standalone file as the msu first looks for installed updates.

2. Without uninstalling v1 (or whatever it was) I went into Windows Update and discovered the KB listed there as a critical update waiting for installation. Directed Windows Update to download and install it to see what would happen. That apparently pulled down v2 and installed it over the top of v1. Everything magically worked again afterward.

This turned into a time consuming chore on five machines. Those with many more to support have my sympathy for the effort they will expend having to recover from this debacle. Too bad MS can't be billed for the manhours of time they consumed with this . . . the cost of that would convince them not to release stuff that obviously hasn't been adequately tested.

You could send MS a bill for your labor...
...then MS could start charging you for every update