Bork Tuesday, Any Problems Yet?

Yes, it's not good. I feel exactly the same. My other computer runs Ubuntu. This was a deliberate decision to avoid Win 8/10.

" ... sometimes I wonder if Micro$oft is actively sabotaging users of their other versions of Windows, in order to basically force their hand in switching to 10."

I have a feeling that this is a deliberate but unstated policy, I really do.

 

After creating Macrium Reflect images, I dug into the monthly chore.
Check for updates took about 30-40 minutes on two different 7x64 machines.
I researched each update, compared what was being offered this month to the last several months, hid a couple that keep coming back (and one about DST in Chile), then installed 18 "important" updates, including all seven security updates.
Install went well, and both machines are running smoothly.
No bork... yet.

 

I just installed all 16 important updates (4 were Office), and everything has been fine since. If there is a problem, I just uninstall the offending update later. This month's updates seem fine.

 

+1. Installed all important except MSRT with no problem. Also had to hide GWX again.

 

Microsoft releases KB 3163207, retires KB 3157993, reissues Flash patch MS16-064
http://www.infoworld.com/article/30...reissues-flash-patch-ms16-064.html#tk.twt_ifw
---------------------------
https://www.wilderssecurity.com/thre...tifications-for-may-2016.385582/#post-2587942

.

 

Well, since I installed all the updates in Win 7. something weird has begun to happen randomly at login. When I reach the desktop, I get a popup notification that the System Event Notification Service can't load or some such message. I have no idea which update might have caused this, but it has happened several times now over the last few logins. My graphics has borked itself somehow too, but that's probably another issue. Prior to Bork Tuesday's updates, none of this was happening and everything was fine and dandy. So I suspect something is amiss with one of the updates. Sorry I can't be specific, but proceed with caution.. It may or may not affect others. It almost seems like MS is sabotaging 7. If this keeps up much longer, I will have to restort to my Win 10 images and go with 10, as much as I really dislike that idea.

 

Yeah .... what is that all about ?
I have yet to read of a single instance , ever , where MSRT has been needed or used by anybody !

..... almost worth starting a poll

 

I had to uninstall KB3153171. I noticed an exclamation mark on shutdown and it was this KB waiting install - with a cold boot. Do not know why. Nothing online that I can find. Each time I try to install it standalone after the cold boot, I keep getting BLSOD. Windows repair reverts windows update KB3153171- system did not configure properly. Try uninstalling this one - not saying it is the one that is causing you a problem but it might be.

Update: Have since found out that KB3153171 is only a problem on W7/32 systems. Also this KB does not play nice with EMET 5.5 (just as KB3146706 did not). One again EAF is the culprit.

 

Have you web searched the issue, "Windows could not connect to the System Event Notification Service"?
The issue can have different causes.
Edited:
I had the same issue on my (former) Windows Vista system, off and on, in the period May 2014 till April 2015. I was never able to pinpoint the cause of the issue. The issue bothered me for quite some time, till one day, the issue was gone.
Where I first wrote, "one day, after both a G Data Internet Security update and a HitmanPro.Alert update, the issue was gone," now I think it was differently:
I think it was after ditching EMET and the older HitmanPro.Alert version 2.5, and using the then new HitmanPro.Alert version 3.x, that the "Windows could not connect to the System Event Notification Service" issue was gone. So, I guess EMET, or HitmanPro.Alert version 2.5, or the combination of those two, or perhaps some incompatibility with some earlier Windows update, may have been the cause of the mentioned issue, on my then Vista system.
/end edit
I've also seen the issue mentioned in relation to Symantec Norton and Microsoft Forefront.
Doing a netsh winsock reset may probably fix the issue for the moment, but it may be back with another reboot.

 

for fun I ran MSRT from desktop. Quick scan 15 minutes. Full scan two hours. Here's list of items MSRT looks for.

Spoiler: MSRT items

DOS/Alureon
DOS/Bancos
DOS/Caphaw
DOS/Poison
DOS/Ramnit
DOS/Sinowal
Java/Bancos
Java/Banload
Java/Lecpetex
MSIL/Bafruz
MSIL/Bancos
MSIL/Banker
MSIL/Banload
MSIL/Bepush
MSIL/Bladabindi
MSIL/BrobanDel
MSIL/Dofoil
MSIL/Drixed
MSIL/Fareit
MSIL/Fynloski
MSIL/Gamarue
MSIL/Hupigon
MSIL/IRCbot
MSIL/Jenxcus
MSIL/Kilim
MSIL/Kovter
MSIL/Samas
MSIL/Sdbot
MSIL/Simda
MSIL/Spacekito
MSIL/Upatre
MSIL/Vobfus
MSIL/Zbot
PowerShell/Drixed
PowerShell/Fareit
PowerShell/Plugx
W97M/Gamarue
W97M/Jenxcus
W97M/Vawtrak
W97M/Zbot
Win32/Afcore
Win32/Alinaos
Win32/Allaple
Win32/Alureon
Win32/Antinny
Win32/Babonock
Win32/Bafruz
Win32/Bagle
Win32/Bagopos
Win32/Bagz
Win32/Bamital
Win32/Bancos
Win32/Banker
Win32/Banload
Win32/Bedep
Win32/Bepush
Win32/Berbew
Win32/Bladabindi
Win32/Blakamba
Win32/Bocinex
Win32/Brambul
Win32/Bredolab
Win32/BrobanDel
Win32/Brontok
Win32/Bubnix
Win32/Caphaw
Win32/Carberp
Win32/Ceekat
Win32/Chir
Win32/Claretore
Win32/Cleaman
Win32/CompromisedCert
Win32/Conficker
Win32/Conhook
Win32/CplLnk
Win32/Cridex
Win32/Critroni
Win32/Crowti
Win32/Cutwail
Win32/Cycbot
Win32/Deminnix
Win32/Derusbi
Win32/Dexter
Win32/Diplugem
Win32/Dishigy
Win32/Dofoil
Win32/Dorkbot
Win32/Drixed
Win32/Dumaru
Win32/Dursg
Win32/Dyzap
Win32/Emotet
Win32/Enterak
Win32/Escad
Win32/EyeStye
Win32/FakeCog
Win32/FakeDef
Win32/Fakeinit
Win32/FakePAV
Win32/FakeRean
Win32/FakeScanti
Win32/FakeSecSen
Win32/FakeSpypro
Win32/FakeSysdef
Win32/FakeVimes
Win32/FakeXPA
Win32/Fareit
Win32/Filcout
Win32/Foidan
Win32/Folstart
Win32/Fotomoto
Win32/Frethog
Win32/Funner
Win32/FURootkit
Win32/Fynloski
Win32/Gael
Win32/Gamarue
Win32/Ganelp
Win32/Gaobot
Win32/Gatak
Win32/Hackdef
Win32/Hamweq
Win32/Harnig
Win32/Haxdoor
Win32/Helompy
Win32/Hikiti
Win32/Hiloti
Win32/Hioles
Win32/Hupigon
Win32/IeEnablerCby
Win32/InternetAntivirus
Win32/IRCbot
Win32/Jeefo
Win32/Jenxcus
Win32/Jinupd
Win32/Joanap
Win32/Kasidet
Win32/Kelihos
Win32/Kexqoud
Win32/Kilim
Win32/Koobface
Win32/Korgo
Win32/Kovter
Win32/Kuluoz
Win32/Ldpinch
Win32/Lecpetex
Win32/Lefgroo
Win32/Lethic
Win32/Locky
Win32/Lolyda
Win32/Lovgate
Win32/Magania
Win32/Matcash
Win32/Matsnu
Win32/Mdmbot
Win32/Medfos
Win32/Miuref
Win32/Mydoom
Win32/Mytob
Win32/Mywife
Win32/Napolar
Win32/Necurs
Win32/Netsky
Win32/Nitol
Win32/Nuqel
Win32/Nuwar
Win32/Oderoor
Win32/Oficla
Win32/Onescan
Win32/Optixpro
Win32/Parite
Win32/Phdet
Win32/Phorpiex
Win32/Pirpi
Win32/Plugx
Win32/Pluzoks
Win32/Poison
Win32/Pramro
Win32/PrivacyCenter
Win32/Purstiu
Win32/Pushbot
Win32/Qakbot
Win32/Ramdo
Win32/Ramnit
Win32/Rbot
Win32/Redyms
Win32/Renocide
Win32/Renos
Win32/Reveton
Win32/Rimecud
Win32/RJump
Win32/Rorpian
Win32/Rotbrow
Win32/Rustock
Win32/Sality
Win32/Sasser
Win32/Sdbot
Win32/Sefnit
Win32/Sensode
Win32/Shiotob
Win32/Simda
Win32/Sinowal
Win32/Sirefef
Win32/Slenfbot
Win32/Spacekito
Win32/Spybot
Win32/Stration
Win32/Stuxnet
Win32/Taterf
Win32/Teerac
Win32/Tescrypt
Win32/Tibs
Win32/Tofsee
Win32/Tracur
Win32/Tupym
Win32/Unruy
Win32/Unskal
Win32/Upatre
Win32/Valla
Win32/Vawtrak
Win32/Vesenlosow
Win32/Vicenor
Win32/Virtumonde
Win32/Virut
Win32/Vobfus
Win32/Vonteera
Win32/Vundo
Win32/Waledac
Win32/Wecykler
Win32/Weelsof
Win32/Winnti
Win32/Winsec
Win32/Winwebsec
Win32/Wukill
Win32/Wysotot
Win32/Yeltminky
Win32/Zbot
Win32/Zemot
Win32/Zlob
Win32/Zonebac
Win32/Zuten
Win64/Alureon
Win64/Bedep
Win64/Carberp
Win64/Claretore
Win64/Cridex
Win64/Derusbi
Win64/Drixed
Win64/Dyzap
Win64/Emotet
Win64/Escad
Win64/EyeStye
Win64/FakeSysdef
Win64/Fynloski
Win64/Hikiti
Win64/Jenxcus
Win64/Kilim
Win64/Koobface
Win64/Necurs
Win64/Phdet
Win64/Plugx
Win64/Ramnit
Win64/Reveton
Win64/Rotbrow
Win64/Sefnit
Win64/Simda
Win64/Sinowal
Win64/Sirefef
Win64/Vawtrak
Win64/Weelsof
Win64/Winnti
Win64/Zbot
WinNT/Alureon
WinNT/Bagle
WinNT/Bancos
WinNT/Bubnix
WinNT/Caphaw
WinNT/Conficker
WinNT/Cridex
WinNT/Cutwail
WinNT/Derusbi
WinNT/F4IRootkit
WinNT/FURootkit
WinNT/Haxdoor
WinNT/Hikiti
WinNT/IRCbot
WinNT/Koobface
WinNT/Ldpinch
WinNT/Necurs
WinNT/Nuwar
WinNT/Phdet
WinNT/Pirpi
WinNT/Ramnit
WinNT/Rustock
WinNT/Sality
WinNT/Simda
WinNT/Sinowal
WinNT/Sirefef
WinNT/Stuxnet
WinNT/Tibs
WinNT/Tofsee
WinNT/Winnti
WinNT/Zuten

 

same here while bringing (few at a time) Important updates current (from March) on seldom use Vista box.....

 

To all that replied to my earlier post, I guess I've reached the point where I'm giving up on 7. Seems that when this kind of stuff starts happening, there's no way to really track it down, and I'm not up to putting in that kind of effort. Just too much trouble to keep running 7. So I just loaded my Win 10 image and I'll go with that for now. I don't like 10 that much, but it seems to work pretty well on my machine, none of these kinds of issues at all. If I can't stand 10, then there is always Linux, which I'm familiar with also. Thanks for the replies everyone...

 

When you do a web search, you see that the "Windows could not connect to the System Event Notification Service" issue is definitely not a new thing, definitely not limited to Windows 7, and definitely not limited to Microsoft's 2015/2016 shenanigans.
I really hope you'll never be bothered by the "Windows could not connect to the System Event Notification Service" issue on Windows 10, but I don't think there's any guarantee to that.
Good luck!

 

Yeah, I did Google search for it a bit, but obviously it's been happening to all kinds of people thru several years time, so the bottom line is, I have no way of figuring out what the problem is. Interesting thing though, prior to this last batch of 16 udpdates, this issue had never occurred or happened to me ever. So I have to suspect that something in one of the updates changed something and that there is some connection there. I'm pretty sure if I restored my previous image from last month and ran it with updates turned off, that I'd not be having that issue at all. So draw your own conclusions, right?

I posted mostly as a head up to others in case anyone else saw this issue after updating.

I'm moving to Win 10 for now. It does seem to run very well on my machine, with zero issues to date. To each his own, as they say....

 

Good luck running Win 10. I don't know if it's any good, if I like it or not. I don't like being micromanaged into something (Win 10). I haven't updated in the last 3 months with M$. I'll wait a few months after the cut off date for the Free Win 10, watch the forum to see if anything is happening to Win 7 / 8 users. If all is well and M$ stops the push for Win 10 I'll do a reformat of Win 7 to get all the Win 10 crap updates off the computer.

 

Yeah, I don't like 10 much, but I have to admit that it runs well here. I've been using it off and on since it's release, just loading images of 7 or 10 or linux as desired. I wanted to stick with 7, but if this kind of thing is going to be happening, then at some point, it just becomes too much trouble for me. Then there is always Linux too, so there are options.

Also, regarding my earlier post above, I'm not saying that MS is deliberately sabotaging 7, but it's also possible that their quality control is just so lax and bad these days, that they are simply putting out garbage updates and nobody cares. That's no good either. So deliberate or not, the end result is still the same. Not good.

 

Ok, after a day of Win 10, I decided to bite the bullet, and restore my previous Win 7 image from a few days before this month's Bork Tuesday updates, and booted up, all is fine and well. I immediately turned Win Updates OFF. That's where I'm going to leave it I think... just forget the updates. Unless there is some way I can be sure one of them won't bork something here. Seems like a lot of people are doing this. I don't like the idea too much, but I gotta be practical. Turning updates off seems to actually be the safest way to go nowadays. Anyway, going to go with that for now. No sign of the mysterious System Event Notification Service problem. I'm not surprised. Before this month's updates, I had never seen that issue ever. So, for now, all is well.

 

Thanks for that bjm_

Interesting to see that it still searches for Stuxnet ....
.... I'll sleep better knowing that my ultra-centrifuges are safe from tampering

 

How sweet of Windows to take good care of my best interests/wishes by broadcasting via a Win 7 update (?) message on my box that Windows will forcibly update my system to Win 10 unless I cancel the "reservation"... (Tomorrow)

 

@Lagavulin16 It's good that it let you know, rather than automatically upgrading with no notice.

 

Yes indeed. Never mind the tatoo. Let's start with a kiss.

 

Wow that didn't take long to go back to Win 7.

 

Haha, yeah, it happens every time. 10 runs fairly well, but somehow I just don't feel like I can trust it. I use it for a day, and during that time, I see TONS of disk i/o and processing going on that doesn't seem to have anything to do with what I'm doing on the machine. It had already checked for updates, so it wasn't that. It wasn't defragging the disk, because that stops when I start using the machine. It was doing a whole lot of something, but what, I have no idea. I don't feel comfortable with 10. Maybe that's being a bit paranoid, lol, but somehow I don't think so. Every time I use 10, I always come away with the feeling that there is way too much going on behind the scenes. So..... back to 7. With updates turned off, it'll be smooth sailing now.

 

Same here.

 

It was probably that Windows Defender that everyone thinks is so light. I determined one time with Process Explorer that it was background scanning files with no UI indication it was doing so.