Replies

I have seen conflicting information as to whether the registry key belongs under HKEY_CURRENT_USER or HKEY_LOCAL_MACHINE. Can someone please clarify.

Also, the registry path cited above is appearing as truncated. I would assume that the intended registry path ends with …CurrentVersion\EOSNotify but I am not sure.

Windows 7 x64 Home Premium Group A

I also was able to install the monthly rollup KB4525235 yesterday. At that time I was offered the MSRT update KB890830 which failed to install. Accordingly, I had hid the MSRT update.

Today, however, when WU checked for updates, I noticed that the hidden MSRT update was removed. Therefore, it appears that Microsoft has pulled the MSRT update and I would imagine that it will be offered again once Microsoft has fixed it.

1 user thanked author for this post.

Pierre77

Windows 7 x64 Home Premium Group A

KB4524157 is described as a monthly rollup. Therefore, all of its enhancements will be contained (presumably) in next Tuesday’s scheduled October monthly rollup.

Accordingly, I cannot conceive why today’s monthly rollup can be deemed “important” and mandatory when its replacement will be available in 5 days.

I assume that the consensus advice would be to ignore this rollup update.

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.

rockandroller

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.

[ashfan212]

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 3 years, 7 months ago by ashfan212.

[ashfan212]

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 3 years, 7 months ago by ashfan212.
• This reply was modified 3 years, 7 months ago by ashfan212.

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.

jburk07

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.

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.

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.

jburk07

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.

 

 

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.

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.

dlsdjh

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?