Grrrr.... I'm going to keep pushing - merely having the patch apply via DISM, and then not agreeing with WSUS that it's applied, is not acceptable.
We'll see how far I get. Kurt On Fri, Dec 15, 2017 at 5:25 AM, Michael B. Smith <mich...@smithcons.com> wrote: > I'm sorry to say that Microsoft support no longer does root cause analysis, > unless you pay for premier support. In fact, their opening email should say > that, where they define the success criteria for the case. It's very > important that you get that wording to your liking. > > -----Original Message----- > From: listsad...@lists.myitforum.com [mailto:listsad...@lists.myitforum.com] > On Behalf Of Kurt Buff > Sent: Thursday, December 14, 2017 10:17 PM > To: ntsysadm > Subject: [NTSysADM] Update on KB4053579 > > I am not satisfied with MSFTs response on this. > > Here's how it played out. > > I was able to abscond with an affected laptop, and the tech worked on it for > a while. > > He was eventually able to see that our AV (ESET) was holding onto the drive. > > I uninstalled ESET, rebooted, and he: > - Expanded the downloaded patch > - Used to DISM apply the patch, which seems to be successful. > > However, WSUS is still offering the update, and still requiring updates. The > update doesn't show in the list of updates through the Windows Update GUI. > > The update does show in the registry, and if I do either a "wmi qfe list" or > a powershell wmi query, but the InstalledBy and InstalledOn columns are > missing. > > MSFT would only work with me on one machine, which I can almost understand - > he stated that each machine could have a different cause for failure to > install. While that's technically true, I have to believe that this many (35 > out of just over 100) having this problem will likely have the same root > cause. Further, I could point to another machine right now that doesn't have > same configuration as the others (no AV), but I'm willing to bet the same > root cause. > > I'm pushing back, saying that until the client and WSUS agree that this > update is installed and no longer needed, the problem isn't really solved. > > Kurt > >
