Acknowledged printing bugs in KB 3177725, Win7 security patch, and KB 3176493, Win10 10586.545 update

Topic

New Reply

The “magic” Win7 Update speedup patch has a flaw. InfWorld Woody on Windows
[See the full post at: Acknowledged printing bugs in KB 3177725, Win7 security patch, and KB 3176493, Win10 10586.545 update]

Reply | Quote

Replies

Woody,

FYI….My very reliable Epson WF 2540 will not print even one page after having installed KB 3177725.

Reply | Quote

Also I don’t print multiple pages. When I print-it’s sorta double-sided so to save on paper. So would my pixma printer be safe from the “magic” speed up update’s flaw?

Anyway I was gonna download it tonight so I can download and install the patch by tomorrow at midnight.

Reply | Quote

What’s the rush?

Reply | Quote

That’s weird. Have you tried uninstalling the patch, to see if it’s the cause?

Reply | Quote

I don’t know….but what am I gonna do? If I download the update, Then my printer won’t work, if I don’t download the update, I can’t speed up windows update and download the patch.

I mean has there ever been such a thing as skipping a month patch and wait to download next month’s speed update and september patch?

Is there any other speed up update to help speed up windows update for the month that the flawy one stated?

Reply | Quote

Patch Tuesday was OK before I installed KB3177725, but I figured it wouldn’t hurt. Silly me. When I need the printer, I really need it, so ’25 is getting uninstalled. I hope MSE updates won’t be screwed.

Windows Update: the most compelling argument for Linux.

Reply | Quote

Naw, uninstalling 3177725 won’t hurt anything.

Reply | Quote

Most printers work most of the time. There’s just a specific situation where the printer won’t work.

Relax. Wait a week or two, and see if any other problems crop up.

Reply | Quote

Seems I’m lucky : just printed pages 1-4 out of a 60 pages document (asked/tested only 4 pages since the problem is reported starting with 3 pages). Printer is HP LaserJet 1018. KB3177725 is of course installed. Windows 7SP1 64-BIT.

Likely the interaction between the KB3177725 and other updates and/or the users configuration. A true mystery, once again.

Reply | Quote

“Windows Update: the most compelling argument for Linux.” together with Windows 10 itself, of course!

Reply | Quote

I was going to put my Joe Users back on Automatic now that GWX is over because, across the board, they cannot deal with manual updates. It was either that or no updates got done unless I made phone calls and/or house calls. But it looks like you’re d**ed if you do and d**ed if you don’t.

If you crowdsource your operating system instead of engineering it, maybe you should crowdsource your fixes as well (Har Har).

When is MS going to get it together? We went for YEARS without all this trouble until they started working Win10. Now they can’t even do that right.

Reply | Quote

Sigh~I guess I can wait until Saturday/Sunday night to install the update and then put the patch in and then uninstall the speed up to keep my printer safe-UNLESS THEY RELEASE A new speed up update to fix the windows update slowness.

Reply | Quote

FYI, there’s the optional July 2016 update roll-up KB3172605 which provides an updated WU client among other things. I’m not recommending it, merely advising of its existence.

Reply | Quote

The problem is reported to affect multi-page printing from the third document onwards, so if you’ve only printed a single set of 4 pages then you won’t have encountered the issue.

Reply | Quote

@Woody,

Uninstalled 3177725 and the Epson printed. Re-installed 7725, would not print. (All install uninstalls followed by reboots)

Went into the Epson printer settings, turned everything back to default, shut down the printer, rebooted the computer first then hard rebooted the printer after the computer returned to the desktop.

Back into Epson’s settings, turned on my custom print settings, and was able to print again.

Too many variables to determine what corrected the problem. We’ll see if the problem returns tomorrow.

When will MS stop causing problems? And if others can’t self correct this issue is MS going to release a hot fix?

Reply | Quote

Gad. I’m sure MS will fix the 3177725 problem that they’ve identified – but it seems to be different from your problem….

Reply | Quote

“from the third document onwards” … OK. I had in mind from the third page, not document.

Thanks for this precision. I seldom, very seldom print pages from more than one document so for the time being I won’t uninstall KB3177725.

Reply | Quote

Even if you print from more than one document, the bug doesn’t kick in unless you’re printing more than one document from a single command – something like the barcode printer.

Reply | Quote

Queued printing is it? That is I add pages from several documents and then only start the printing, and problem occurs in this scenario from the third document onwards. That’s a company’s office scenario more than that of home work, but if I’m correct (if I’ve understood correctly) then indeed for heavy printing it definitely is an issue. Anyway, concerned or not remains the fact this IS not normal.

Thanks, Woody and thanks again, Seff.

Reply | Quote

May I make a suggestion to all of you regarding black Tuesday updates. DON’T APPLY ANY OF THEM UNTIL WOODY GIVE YOU THE WORD THATS ITS OK TO DO SO.
If you listen to Woody you will be much better off and have a lot less trouble.

Reply | Quote

+1

Reply | Quote

No, it’s actually more complex than that. But nevermind. If you don’t print labels, you probably won’t be affected.

Reply | Quote

So once you uninstall 3177725, your printer will be normal to print multiple pages and stuff?

Reply | Quote

Your printer will always be capable of printing multiple pages, whether you have the patch installed or not. The bug is for a very specific printer setup.

Reply | Quote

Ooohhhh~Well I’m gonna uninstall the 3177725 just in case after I download and install the month patch. 🙂

Reply | Quote

What I don’t understand is louis’ comment (#1) when he writes that his printer would not print even one page after having installed KB 3177725, which is far from labels as labels are far from what seems to appear from the original article.

I don’t quite understand. Does KB3177725 induce printing issues on a very tight area of circumstances or on such a scale that louis’ comment above would confirm?

In other words what must be joined in order to test, reproduce KB3177725 printing issues? If the answer is not clear then the alarm isn’t either.

Reply | Quote

(Erie Chanting)

Listen to Wood-deee… Listen to Wood-deee… Dooo as Wood-deee sez…. ouuuu… ouuuu…

Show us the light oh wise one…. Ouuuu… awwwww

(Chains rattle SFX out)

😉

Reply | Quote

Is it sad that reading this site and passing on stuff to my friend in IT for the library system we work for is becoming normal? Thanks for the warning – considering all of the stuff we print every day (including barcode labels for items and receipts), our IT guys would definitely need to test that aspect of the latest updates. They might not have thought about that before, since the patch notes originally wouldn’t lead you to check that.

Reply | Quote

Why do you say 3177725 fixed the update slow down when it was actually the June rollup that did: KB3161647

Reply | Quote

For those who already had installed the July updates, 3177725 was necessary to speed things up. But if you hadn’t installed the July updates, the July “magic” patch did the trick.

Reply | Quote

I think it is about kernel-mode (legacy) print drivers which were supposed to be discontinued many years ago, probably starting with Vista and Windows 2008 Server. User mode print drivers are supposed to be used instead. It may be a patch like the one for Group Policies few months ago where Microsoft just restores the functionality as it was supposed to be there from the beginning and which is documented.

Reply | Quote

Anyway I’ll uninstall the speedup update on thursday after I check to ensure things runned smoothly (I kinda do a check updates thing and keep track of how long it takes like a few minutes or such.) Besides after I install patch-I switch my windows update off and turn it on come next patch day.

Besides I might be testing out how to print a few poems out and I don’t want the update to mess with my printer setup.

So I will uninstall 3177725 on thursday after I install patch at midnight wednesday.

Also I only use my printer sometimes-but I wanna ensure that I have no bug messing with its setup.

Reply | Quote

+1

Reply | Quote

And THEN they want us to trust a single rollup update every month, when a single bug in one of the components causes such a kerfuffle? FFS…

Reply | Quote

Well, it is indeed a bit more complex. But unfortunately not just limited to labels…

I can reliably reproduce the problem with both Office 2010 and Office 2013 through trivial automation.

(Note: I didn’t test 2016)

Reply | Quote

@Sam @Woody: If you are fortunate to even have the “ability” to “install” any of the updates you are lucky.

I agree about NOT installing any of the updates (other than the only one I need KB3177725), however not being able to even get “all” of the updates (and that after 2 hours of running the “search for updates) is very disturbing.

I didn’t get the replacement update for KB6186108 which is KB3172605 (I think). It was hidden, and never installed.

I’ve wondered if this could possibly help, however apparently it carries a lot of baggage, and apparently still breaks Blue Tooth (WHICH I DO NOT HAVE).

I may also try to do the maneuver of trying the directions to get the KB3177725 installed once again as a “stand alone”. I may have made an error the first time I tried this. I know I need to “do something” just to get the ALL of the updates listed (only have 4 presently). One of them is KB3177725, however haven’t been able to get it to install and download. This is the only one of those listed by “Daili” that I don’t already have.

This has been the worst month of all for me.
Any and all suggestions are welcome. Thank you once again, Woody, for all of your help. 🙂

Reply | Quote

The Bluetooth driver has been fixed. See EP’s post

https://www.askwoody.com/2016/win7-scan-speedup-patch-kb-3161608-breaks-intel-bluetooth/#comment-95542

Reply | Quote

@Woody: Since the update: KB3172605 has been hidden (since June), and I do not have Blue Tooth, I am thinking that I could restore this “hidden update” and try to install it in that manner. To my knowledge I don’t have anything else that could be affected by this update.

I did get the updates from June installed without using that one however.

At least it’s a “hope” since I’ve never had a problem with installing any previously hidden updates. I hope that I’m not overlooking anything.

Thank you once again for posting this here. I’m hoping to be able to get something done with this problem because I’m spending almost all of my time trying to find a resolution. I do not intend to DL & install ANYTHING OTHER than one or both of the two updates I’ve referred to in my post.

The KB3177725 I have listed however could not get it DL & installed from the list. I’m not concerned about printer problems.

I will do my best. Is there anything else I should be aware of? I do appreciate your help – – – it is invaluable. 🙂

Reply | Quote

I think you’re going to find that both will be made obsolete in October – but we’ll see.

Reply | Quote

@Woody: I already have the 5 updates listed in the referenced “August 9th” InfoWorld (and have had for quite some time). All June and July updates were DL & installed. August is the one I’ve been having problems with.

Are these 5 updates enough to work with or are we “waiting” for the “speed up patch” for August? Please clarify as I’m confused about this.

I hope this thread is the correct one to post this information on (?).

Thank you and all of the others who provided information for this InfoWorld August 9th article.

Reply | Quote

I’m waiting for the dust to settle.

With big changes coming in October, I still haven’t figured out the best approach for August…

Reply | Quote

Walker, I don’t understand why you have so many issues. Just install everything that comes up to August 2016. Trust me, for your situation all patches are secure, the issues which are still outstanding do not apply to your setup. Unhide all patches that you may have hidden in the past and install them.
Leave your computer on 24/7 on Automatic Updates, do not hide anything and just install everything. I mean it, updates for Silverlight, Flash (only if you are on Windows 8 or 8.1 as they come on Windows Update), Adobe Reader, Internet Explorer, everything. You will end up with a stable, reliable and above all supported Windows system.
When you finish updating and nothing else comes on Windows Update, run Disk Cleanup and select all boxes. After that, restart your system.
Run again Windows Update until nothing comes up anymore and switch to Never check for updates.
Next, wait for Woody’s instructions for September and following months.
This is my last reply to you for the time being, I think we exhausted all possibilities and if you decide to do differently, please do your own research.

Reply | Quote

@ch100 @Woody:

ch100: There is information which you do not possess about the problems I’ve been having. It IS NOT about “checking” WHICH updates to install.

I am fully patched through July. When I attempted to search for updates for August is when I encountered the problem of the “never-ending” search for updates. After several hours 4 updates appeared. However these would not DL and install. I only tried the KB3177725 and 1 definition update, and those were not successful.

I subscribe to ALWAYS WAITING for the “all clear” from Woody before installing any new
monthly updates unless I know it is the “magic Patch”. My attempt to get the KB3177725 update DL & installed was unsuccessful, however now there is the “latest information” which I intend to utilize as set forth.

That summarizes the situation succinctly.

Reply | Quote

Yep. This is a good time to sit back and chill. Nothing important happening.

Reply | Quote

Walker, then you have operating system issues or software behaving badly. Too much third-party security software most of the times is worse for functionality than none.
No fix or “magic” patch for Windows Update can resolve that and this cannot be resolved over the internet in few generic posts.

Reply | Quote

Isn’t the same for troubleshooting if a bug affects one individual update or a bundle?
It is still one update only for you and for anyone else.

Reply | Quote

the KB3177725 is affecting a lot of printers the Toshiba and the IBM printers. uninstalling this update does solve the issue for me.

Reply | Quote

Actually, the problem isn’t with specific printers or print drivers. It’s the way Microsoft changed the way certain commands get executed. The solution, as you note, is to uninstall the KB.

Reply | Quote

New update is released for Win32k.sys to fix the issue
https://support.microsoft.com/en-us/kb/3187022

currently only distributed through MU catalog
it replaces KB3177725

Reply | Quote

Very interesting. I wonder how they’ll apply this to Win10 machines? Another cumulative update, perhaps… ???

Reply | Quote

it wasn’t a question actually it was a fact without going into much details about the problem. as you may know it is a security update so you guessed…

Reply | Quote

Daft question maybe but i dont know where to put it.
The speed up patches seem to only work for the month they are issued. On that idea can they then be uninstalled when the next one comes out or should they just be left alone. W7 home
Thank You

Reply | Quote

They could be uninstalled, but I wouldn’t go to the extra effort at this point.

The whole world is changing in October. Let’s see what happens.

Reply | Quote

The KB3177725 print problems don’t seem to affect Vista/Server 2008 R0/R1 SP2 users, ch100.

Reply | Quote

I was wondering about that, and hit a report of a problem on the Seagull Scientific community support site https://support.seagullscientific.com/hc/en-us/community/posts/216590067

Of course, Microsoft hasn’t told us anything….

Reply | Quote

@EP Then is was just the wrong assumption…

Reply | Quote