News, tips, advice, support for Windows, Office, PCs & more. Tech help. No bull. We're community supported by donations from our Plus Members, and proud of it
Home icon Home icon Home icon Email icon RSS icon
  • TonyC

    Forum Replies Created

    Viewing 15 posts - 46 through 60 (of 74 total)
    • Author
      Posts
    • in reply to: Tests of KB4099950 #189706
      TonyC
      AskWoody Lounger

      @abbodi86
      I’ve only just caught up with this thread and it has been revealing. QUESTION: Is the desired end result of installing KB4099950 and KB4088875/KB4088878 (i) that pci.sys is updated from 6.1.7601.17514 to 6.1.7601.24056 and (ii) that no SlotPersistentInfo key exists in the Registry? If so, then I had not previously known about condition (ii).

      Using regedit, I have just searched my registry for SlotPersistentInfo keys and found that none exist. If the sole objective of your .vbs script is to delete all SlotPersistentInfo keys, then I presume now that I don’t need to run it. Yes?

      The background to all this, elaborated in another thread, is that, on the 8 April 2018, I installed KB4099950 (from the catalog) followed by a reboot before I installed KB4088878 (from the catalog). The suggestion was that the reboot might have recreated the SlotPersistentInfo keys after KB4099950 had deleted them. Well, that doesn’t appear to have been the case unless the subsequent installation of KB4088878 somehow deleted any that had been recreated.

      in reply to: A protocol question about KB 4099950 #189560
      TonyC
      AskWoody Lounger

      … This created a temporary condition within the system; whereby a successful update to the driver could be performed by the next operation, as long as that was done before the next bootstrapping function of the system. The ‘boot’ function will recreate the ‘unfixed’ condition and result in this driver failing to update yet again. …

      Well, as I have mentioned before in this thread, I installed KB4099950 and then rebooted before I installed KB4088878 (the March 2018 security only update). Afterwards, PCIClearStaleCache.txt reports that pci.sys was at 6.1.7601.17514 but, looking at the properties of pci.sys, it is now at 6.1.7601.24056. So, it appears that, even though I rebooted after installing KB4099950, KB4088878 still successfully updated pci.sys. Can you account for that? (I still haven’t installed any of the April 2018 updates.)

      in reply to: A protocol question about KB 4099950 #188879
      TonyC
      AskWoody Lounger

      @woody
      Sorry, a few days late on this. My interpretation of anonymous’s post #187691 is that he/she was asking about the March security only update (anonymous is in Group B). But your query on Reddit asked about the March monthly rollup instead.

      1 user thanked author for this post.
      in reply to: A protocol question about KB 4099950 #188871
      TonyC
      AskWoody Lounger

      @SueW
      Yesterday (29 April 2018), I received a follow-up reply email for your post #188624 in this thread. It was a reply to my post #188617. The email contained a link to your post but, when I clicked it, the post was not found. I’ve searched for the post by other means but I cannot find it. Did you decide to delete it?

      in reply to: A protocol question about KB 4099950 #188846
      TonyC
      AskWoody Lounger

      @ch100
      Thank you.

      Well, I haven’t noticed any side effects, but I haven’t gone digging around in Device Manager or wherever I should be looking. I certainly have an physical Ethernet network interface card in my system which connects via an Ethernet cable to my router/hub, but I don’t know whether its settings have been changed. And my system does not have a static IP address; I use DHCP.

      I shall contemplate your remarks on the other matter.

      in reply to: A protocol question about KB 4099950 #188839
      TonyC
      AskWoody Lounger

      And do we know what might be the consequences if those registry keys were present when I installed KB4088878?

      in reply to: A protocol question about KB 4099950 #188617
      TonyC
      AskWoody Lounger

      (Win7 x64 Group B)
      I thought I was in the clear on this but now you’ve got me worried again. Unless I am told otherwise, I prefer to reboot after applying each update. It’s in my nature to consolidate as I go along.

      On the 8 April 2018, @MS-DEFCON 3, I installed KB4099950 (downloaded from the Catalog) and then rebooted. True, KB4099950 didn’t tell me to reboot after it had completed but, for the reason given above and because nobody was telling me not to reboot at the time, I did reboot. The contents of my PCIClearStaleCache.txt are:

      Path = C:\Windows\system32\drivers\pci.sys
      pci.sys file version is 6.1.7601.17514
      Pci.sys indicates KB2550978 or later KBs *NOT* installed
      Deleting the PCI SlotPersistentInfo registry keys…
      Deleted PCI SlotPersistentInfo registry keys successfully

      I then installed KB4088878 (the March security only update) and KB4099467 (to prevent a BSOD) before rebooting again. KB4088878 left my pci.sys file at the 6.1.7601.24056 level. I have not yet applied any of the April updates.

      Could someone please tell me what are now the negative consequences on my system after having rebooted directly after installing KB4099950 instead of waiting until I had installed KB4088878?

      As far as I am aware, my system is working well.

      in reply to: A protocol question about KB 4099950 #188582
      TonyC
      AskWoody Lounger

      @MrBrian, thank you. But that still begs the question, if the .msu contains the .exe, why did the second release of KB4099950 on the 17 April 2018 provide the .exe explicitly along with the .msu? On the face of it, this looks like duplication.

      1 user thanked author for this post.
      in reply to: A protocol question about KB 4099950 #188575
      TonyC
      AskWoody Lounger

      @ch100
      Concerning @abbodi86 never advising people in so-called Group B, it was actually Woody’s article of the 27 April 2018 that pointed Group B people to @abbodi86‘s post. I quote, “For those of you who are spitting in the patching god’s face and manually installing Security Only patches (the “Group B” approach), I wish you well and point you to @abbodi86’s instructions.”.

      Your recent comments in this thread and the use of phrases such as “so-called Group B”, in conjunction with Woody’s comment quoted above, are all beginning to sound a little hostile towards the Group B approach. Is this going to be a continuing trend?

      1 user thanked author for this post.
      TonyC
      AskWoody Lounger

      I also agree with SueW. I’m in exactly the same situation. On the 8 April 2018, I installed the first release of KB4099950 (downloaded from the Catalog) before installing KB4088878, the March security only update. By all appearances, everything has worked as it should.

      PCIClearStaleCache.txt tells me that the PCI SlotPersistentInfo registry keys have been deleted. And KB4088878 left pci.sys at the 6.1.7601.24056 level. So I am planning to leave everything as it is before installing the April updates.

      2 users thanked author for this post.
      in reply to: A protocol question about KB 4099950 #188338
      TonyC
      AskWoody Lounger

      @Elly
      I don’t think that answers the question. I’m in Group B and I installed the first release of KB4099950 (from the Catalog) BEFORE installing KB4088878 (the March security only update), which also “bumps” pci.sys to 6.1.7601.24056.

      When KB4099950 was installed, my pci.sys was at 6.1.7601.17514 but, after installation, PCIClearStaleCache.txt tells me that the PCI SlotPersistentInfo registry keys had been deleted. So, if there was no associated pciclearstalecache.exe with the first release of KB4099950, what deleted the PCI SlotPersistentInfo registry keys?

      1 user thanked author for this post.
      in reply to: A protocol question about KB 4099950 #188306
      TonyC
      AskWoody Lounger

      … The first release of 4099950 was not recognized to have an exe if deployed via WSUS or WU. It was then re-released and since then is available via WSUS or WU. I haven’t heard of this update recently missing from WU. …

      (Win7 x64 Group B) What I don’t understand is this. I downloaded the first release of KB4099950 from the Catalog on the 8 April 2018. The download comprised a single .msu file. So, from all external appearances, that release of KB4099950, deployed from the Catalog, did not have an associated .exe either. And yet it still appears to have worked on my system (according to the contents of PCIClearStaleCache.txt) when I installed it before the March security only update.

      The second release, which I downloaded for inspection on the 25 April 2018, comprised both a .msu file and pciclearstalecache.exe. How is it that the first release of KB4099950 worked without a .exe (apparently) while the second release requires an explicit .exe?

      (As far as I have been able to gather from various posts on the subject of KB4099950, the two .msu files are identical. They are certainly the same size.)

      2 users thanked author for this post.
      in reply to: A protocol question about KB 4099950 #187876
      TonyC
      AskWoody Lounger

      So, are you saying that, in my case, the KB4099950 that I downloaded from the Catalog and installed on the 8 April 2018 actually performed correctly? … and therefore I don’t need to do anything else?

      And thank you for informing me that it was the March security only update that installed the later version of pci.sys. Having read elsewhere that KB4099950 did not do it, I was beginning to wonder what did.

      1 user thanked author for this post.
      in reply to: A protocol question about KB 4099950 #187871
      TonyC
      AskWoody Lounger

      … I will also add that I don’t care at all about a functioning Windows Update – as long as it doesn’t download or install anything without my permission. I’m perfectly happy to do all my updating from the Microsoft Update Catalog. …

      As someone in Group B, I do care about how well Windows Update functions. Each month, after installing the security only update and the IE11 cumulative update from the Catalog, I am supposed to switch to Windows Update for the remainder of my updates.

      1 user thanked author for this post.
      in reply to: A protocol question about KB 4099950 #187862
      TonyC
      AskWoody Lounger

      After installing the previous version of KB4099950, along with the March security only update + others, on the 8 April 2018 @MS-DEFCON 3, my pci.sys is 6.1.7601.24056. (KB4099950 was downloaded from the Catalog.) Does that mean that I don’t need to do anything despite Microsoft’s advice to uninstall the previous version of KB4099950 and install the new version?

      I’ve just taken a look at PCIClearStaleCache.txt in C:\Windows\Logs and its contents are:

      Path = C:\Windows\system32\drivers\pci.sys
      pci.sys file version is 6.1.7601.17514
      Pci.sys indicates KB2550978 or later KBs *NOT* installed
      Deleting the PCI SlotPersistentInfo registry keys…
      Deleted PCI SlotPersistentInfo registry keys successfully

      Well, as stated above, my pc.sys is at the 6.1.7601.24056 level, NOT 6.1.7601.17514, so the information in this file is wrong. Does this mean that I should follow Microsoft’s advice after all?

      1 user thanked author for this post.
    Viewing 15 posts - 46 through 60 (of 74 total)