New
#21
I understand that KB3004394 has been "pulled" by Microsoft. I haven't had any issues after new Update Patch was installed on my Wins 7-64 OS. All seems to be working just right at the moment. I assume that Microsoft will be issuing a FIX to correct this. I'll just have to continue to use my machine and see what happens if anything. Does anyone know about Microsoft releasing a FIX??? Hope to hear from you guys soon.....
Last edited by melen001; 11 Dec 2014 at 09:09. Reason: wrong OS
I was getting WGA problems with popups saying that my version of Windows wasn't authentic. (My Snipping Tool had stopped working too). I deleted the KB3004394 update and I have just checked my operating system and it is now being recognised as authentic, and the snipper works too. Thanks folks.
I just uninstalled it be on safe side. Can't see any difference either way but the update wasn't offered again as advised by others
Best always to uninstall a troublesome update if you can, rather than do a system restore which can leave a messy partial installation if you're unlucky.
I just went through my Windows Updates and i see that this KB3004394 was not installed on my machine. I usually get my Microsoft Updates Tuesday during the afternoon but this last Tuesday I checked for updates very early in the morning on my own and downloaded them. Maybe that's why it's not on my machine. Don't know why, just curious. Does anybody know???
I was also having problems with popups saying that my version of Windows wasn't authentic, following my Tuesday update. Chatted with a tech from M$, who, after streaming in, reset my authentication, and said it was fixed.... Rebooted, and immediately got another authentication popup... This morning, frustrated (naturally), I started researching, and found numerous similar complaints, all pointing to KB3004394... While reading through, and deciding on doing some abstract repairs, I noticed that I had received an Important Update notice from M$, KB3024777, to correct a flawed update... Imagine that !!!... Ran the update, ran MGADiag, and behold!!!... Problem fixed... And, BTW, M$ recommends NOT removing KB3004394 by "hand", as it could cause "unforeseen" problems. Best of luck to all.
Thanks Jim. That's good to know.
Yesterday someone was chasing that 4777 and could not find it on his updates although he saw it was on his system.