VMware Windows updates not showing up

BatchPatch Forums Home Forums BatchPatch Support Forum VMware Windows updates not showing up

  • This topic has 5 replies, 2 voices, and was last updated 5 years ago by doug.
Viewing 6 posts - 1 through 6 (of 6 total)
  • Author
    Posts
  • #12134
    NotABot
    Participant

    After doing the usual select the VM’s from the list, right click, Windows updates, check for available updates, and finally proceed to download and install updates, I noticed that even after going through the process, I go into the Windows Updates on the VM, there is still a list of VMware updates showing up in the “Updates are available”. Is there a trick to have BP apply those as well?

    Thanks

    #12136
    doug
    Moderator

    This link explains all of the possible reasons you could be seeing this:

    batchpatch-and-the-windows-update-control-panel-report-a-different-number-of-available-updates

    #12137
    NotABot
    Participant

    Ahh, I had to enable the driver updates checkbox and now they are showing up.

    Thanks!

    #12138
    doug
    Moderator

    Glad that worked. However, it’s also worth noting that the Windows Update Agent has a lot of trouble installing the driver updates that it advertises. We generally do not recommend installing drivers through Windows Update (or through BatchPatch which utilizes the Windows Update Agent). They will frequently fail to install.

    #12139
    NotABot
    Participant

    Yeah, I see that now.

    Error 1611: 59. Failure

    A restart of the VM seems to clear things up and the driver updates are no longer listed. Updating the VMware drivers from within Windows Update on other candidates seems to work ok. I suppose I’ll need to be a bit more careful now when looking at the listed updates. If I see drivers, I’ll need to do it the old fashion way.

    Thanks

    #12140
    doug
    Moderator

    I’m not sure that the error you posted has anything to do with drivers failing to install in the way that I was suggesting. Error 59 is a network error. So if you were updating VMWare drivers remotely then it certainly makes sense that the VM would lose connectivity while those drivers were being updated. That’s a separate thing from what I was suggesting about drivers not installing successfully via Windows Update.

    ERROR_UNEXP_NET_ERR
    59 (0x3B)
    An unexpected network error occurred.

    Yeah also it seems that in the newer OSes Microsoft doesn’t even present the driver updates anymore in the normal Windows Update control panel. At least so far as we have seen it appears to be the case that they now hide these from the user, so I guess they recognize that the driver installations through Windows Update aren’t a great method for installation.

Viewing 6 posts - 1 through 6 (of 6 total)
  • You must be logged in to reply to this topic.