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
  • ashfan212

    Forum Replies Created

    Viewing 15 posts - 1 through 15 (of 47 total)
    • Author
      Posts
    • in reply to: August 2019 Security patches: It’s a biiiiiiiiig month #1907346

      ashfan212
      AskWoody Lounger

      Windows 7 x64 Home Premium Group A, McAfee AV

      I installed the SHA-2 update KB4474419 back in March. It appears that the August update to KB4474419 only applies to IA64 and not X64 based systems. Therefore, I am assuming that I will not need to reinstall this update.

      What is unclear is whether I will even be offered this update. I would imagine that WU would only offer KB4474419 as an “exclusive” update. Therefore, if I am not offered the update, should I use the technique of hiding all of the other updates to see if KB4474419 appears as an “exclusive” update? Or is it preferable not to attempt to reinstall the update (even if replacing the March update version with the August update version does no harm) as the August update only applies to IA64 based systems according to the documentation?

      • This reply was modified 1 week, 2 days ago by  ashfan212.
      • This reply was modified 1 week, 2 days ago by  ashfan212.
    • in reply to: July 2019 Patch Tuesday has arrived #1873702

      ashfan212
      AskWoody Lounger

      Windows 7 x64 Home Premium Group A.

      All of this month’s updates installed successfully followed by a successful reboot. However, I experienced severe issues the first time that I started my computer after the successful reboot and shutdown. I am hoping that someone may be able to offer guidance.

      On this next startup, I received a SYSTEM EVENT NOTIFICATION SERVICE error. Visually, the taskbar graphics no longer appeared in their usual aero theme. Out of desperation, I ran the command NETSH WINSOCK RESET from an elevated command prompt. I had difficulties rebooting my computer after successfully running that command as EXPLORER.EXE would not terminate neither on its own nor when I clicked on the button to force the termination of that process. After a hard shutdown and going through the same process a couple of times, I was able to reboot my computer and, as far as I can tell, the SENS message/error disappeared and my taskbar graphics reverted back to normal.

      I have no idea if my running the NETSH WINSOCK RESET command resolved the problem or whether the errors went away fortuitously after executing a few reboots. I also don’t know if what I experienced was related to the Event Viewer issues that this month’s rollup was designed to fix. For the record, I experienced no issues with the June rollup nor did I install the subsequent preview rollup. I never use the Event Viewer and therefore never had experienced any issues pertaining to Custom Views.

      If anyone understands what causes these SENS errors in the first place and can suggest a better way to avoid/resolve such issues in the future, I would be most appreciative.

      1 user thanked author for this post.
    • in reply to: Office non-security patches for July 2019 are out #1867248

      ashfan212
      AskWoody Lounger

      Does anyone know how to determine whether the Office 2010 Filter Pack SP2 has been previously installed? This would be a necessary prerequisite in order to install this month’s update KB3114879.

      It is also unclear to me whether WU would only offer the update provided that the Office 2010 Filter Pack SP2 has been previously installed.


    • ashfan212
      AskWoody Lounger

      Windows 7 x64 Home Premium Group A.

      KB4499164 and .Net  monthly rollups installed successfully. I just wanted to clarify that it is no longer necessary to manually disable the two Remote Desktop services given the successful installation of the monthly rollup.

      I also do not understand why the pci-clear-cache executable was removed from the monthly rollup starting with last month. I assume that Microsoft removed it for valid reasons, and that I probably don’t need to understand the rationale given that I am in Group A. Was it removed by Microsoft because the NIC error that occurred around March, 2018 had been resolved recently?

      1 user thanked author for this post.
    • in reply to: Details emerging on the March 2019 Patch Tuesday trove #343440

      ashfan212
      AskWoody Lounger

      Windows 7 x64 Home Premium Group A

      I encountered a weird experience which may or may not be related to the installation of the March updates. I installed the updates successfully on March 12th. I first hid the 4 offered, checked as important updates (Monthly Rollup, SHA-2, MSRT, Office 2010 Security) ensuring that the SSU update installed first (successfully). Then I unhid the 4 offered checked updates and installed them successfully. My system rebooted successfully. I double-checked WU to confirm that all 5 March updates installed successfully. So far, so good.

      However, the 2nd time that I started my computer after having installed the March updates I received a “SYSTEM EVENT NOTIFICATION SERVICE” error. I DID NOT lose internet connectivity. My display also appeared as if I had booted my computer in safe mode. Upon researching this error, one possible solution was to open an elevated command prompt and execute the command NETSH WINSOCK RESET. Upon rebooting my computer the system event error was resolved and my display returned back to normal. I also noticed a HUGE improvement in the performance of my computer in that the time to boot my computer took about 1 minute as compared with about 5 minutes (before having run the NETSH command). Once again, there was no disruption of internet connectivity. All looked resolved so I shut down my computer. However, the next time I booted the computer my battery status indicated: ” 0% available, battery charging”. I KNOW that my battery was 100% charged prior to running the NETSH WINSOCK RESET command. My adapter was working and the Dell Battery Meter indicated that the battery was functioning normally. The only resolution I could think of was to remove the battery and reinsert it to see if the battery would begin to charge. To my surprise, when I next booted my computer, the battery meter indicated that it was charging. I am currently in the process of determining if the battery will charge to 100% capacity upon turning off the computer (the manual estimates 4 hours for the battery to charge completely).

      My question to the experts would be: 1) was the SYSTEM EVENT NOTIFICATION SERVICE error likely related to the installation of this month’s updates or mere happenstance; 2) was running the NETSH WINSOCK RESET command the appropriate means to resolving the error or did I incur risks by executing that command; 3) should I have run NETSH INT IP RESET instead or in addition to the NETSH WINSOCK RESET command; and 4) was running the NETSH command the likely cause of the battery drainage.

      I apologize if my post is inappropriate for this topic. I have posted it only because of the possibility that it was a side effect caused by the installation of the March updates. While I have done my best to resolve the issues, I would be grateful to better understand the implications of running the NETSH command and the reason why I encountered the SYSTEM EVENT NOTIFICATION SERVICE error.

       

       

    • in reply to: March 2019 Patch Tuesday patches #340801

      ashfan212
      AskWoody Lounger

      According to the MS support pages, neither the SHA-2 update KB4474419 nor the new SSU update KB4490628 has any prerequisites. Therefore, installing KB4474419 followed by KB4490628 followed by the March updates appears to be the intended order.

      Windows 7 x64 Home Premium, Group A

      1 user thanked author for this post.
    • in reply to: March 2019 Patch Tuesday patches #340723

      ashfan212
      AskWoody Lounger

      Windows 7 x64 Home Premium, Group A

      Does anyone know whether the new SSU update KB4490628 needs to be installed exclusively? Or if WU offers it along with the March rollup KB4489878 that Windows will “know” to install the SSU update prior to the rollup? I am recalling that when the previous SSU update KB3177467 was offered that it was marked as exclusive, meaning that all other offered updates had to be hidden in order for WU to offer KB3177467.

    • in reply to: February 2019 non-Security Office Updates are available #322540

      ashfan212
      AskWoody Lounger

      The silence appears to bode well for the success of this month’s non-security Office 2010 patches. Still holding off, of course, but it appears that January’s Office 2010 issues might have been resolved.

      1 user thanked author for this post.
    • in reply to: KB4461614 kills Office 2010 same as KB4461522 #316975

      ashfan212
      AskWoody Lounger

      Office 2010 32-bit running on Windows 7 Home Premium x64

      I am sorry to hear that these patches are causing problems. For some reason, my computer appears unaffected even though I installed both since-retracted November, 2018 non-security Office 2010 patches without subsequently uninstalling them.

      I did NOT install the 4 retracted Office 2010 patches dated January 2nd. However, I did install KB4461614 on January 10th along with January’s monthly rollup. I believe that KB4461614 initially appeared unchecked but I checked it manually and installed it because it was indicated as a security update.

      When the problem with KB4461614 was noted on January 15th, I tested Word, Excel and Outlook and was able to open them successfully. I do not have Access on my computer.

      On January 25th, I was offered KB4462157 as a checked update and installed it successfully. I then tested my Office 2010 applications and have thankfully not received any errors. I am assuming that the GetDateFormatEx error would appear on startup of Excel, Word or Outlook if my decision to install KB4461522 and KB4461614 were affecting my computer.

      I am curious as to why my computer is not experiencing the reported error. I couldn’t tell from the thread discussion whether the errors caused by the installation of KB4461522 and/or KB4461614 were universal or limited in scope.

      I am just trying to learn so as to be better prepared going forward. If it is unknown why some were affected while others such as myself were spared then so be it. This is obviously disconcerting and it appears that I have been very lucky (so far).

    • in reply to: August 2019 Security patches: It’s a biiiiiiiiig month #1907551

      ashfan212
      AskWoody Lounger

      Hi PKCano,

      I had meant to say that KB4474419 is listed as a prerequisite to installing the August rollup KB4512506. That fact along with its required reboot caused me to inquire whether I should install KB4474419 separately prior to the installation of the August rollup. Anyway, that’s what I did and it seems to have worked. Thanks!

      1 user thanked author for this post.
    • in reply to: August 2019 Security patches: It’s a biiiiiiiiig month #1907389

      ashfan212
      AskWoody Lounger

      Very encouraging! I am also being offered KB4474419 as checked and important notwithstanding that I had installed the update in March.

      Perhaps your update procedure was successful because you had also previously installed KB4474419 prior to the August update.

    • in reply to: August 2019 Security patches: It’s a biiiiiiiiig month #1907375

      ashfan212
      AskWoody Lounger

      Hi PKCano,

      I am not doubting your claim that KB4474419 is NOT exclusive; however, the documentation for KB4474419 indicates that installation of this update requires a reboot. Wouldn’t that mean that one should install this update by itself and then reboot before attempting to install any other offered updates? I would imagine that installing KB4474419 along with the August monthly rollup concurrently would cause the rollup installation to fail, even when KB4474419 is installed first by WU before attempting the installation of the August monthly rollup.

      Perhaps this explains why the user Geekdom reported that the installation of the August monthly rollup KB4512506 failed to install on its first attempt, as that user indicated that KB4474419 was included in the set of updates that were received from WU.

      As an aside, is there a convenient way to check whether an update is marked as exclusive?

      • This reply was modified 1 week, 2 days ago by  ashfan212.
    • in reply to: Office non-security patches for July 2019 are out #1867354

      ashfan212
      AskWoody Lounger

      Hi PKCano,

      Your link to the catalog entry indicates that KB2878281 is the prerequisite update. It would be nice if Microsoft posted that information in its support page for this update as well. The best that I could research was that the Filter Pack SP2 first came out in 2013 under KB2687447. Obviously, there have been other updates since that introduction.

    • in reply to: March 2019 Patch Tuesday patches #340807

      ashfan212
      AskWoody Lounger

      If I am understanding you correctly, you are advising to install the SSU update by itself rather than in conjunction with the other March updates. I assume that you do not disagree with installing the SHA-2 update KB4474419 prior to the new SSU update KB4490628.

    • in reply to: March 2019 Patch Tuesday patches #340730

      ashfan212
      AskWoody Lounger

      Thank you for the reply. Any idea whether WU will initially only offer KB4490628? Or will the SSU update be offered concurrently with the March rollup, MSRT, Office updates, the .Net rollup, etc.? If the SSU update is offered concurrently with other updates, is it sufficient to uncheck all updates except the SSU update or will I need to physically hide all other concurrently offered updates, install the SSU update, and then physically unhide the hidden updates?

    Viewing 15 posts - 1 through 15 (of 47 total)