7

Notifications for "Windows Updates causing BarTender errors"

Sign in and follow this post to receive an email notification when the article Windows Updates causing BarTender errors is updated with new information.

 

There is an issue printing from BarTender if Microsoft Windows Updates from August 9, 2016 are installed.  

12 August 2016, 12:09pm PST: Microsoft has confirmed this problem is due to a bug in their code. They are currently working on a hotfix for the issue. ETA for the hotfix is TBD. Updates will be posted as soon as they are available.

17 August 2016, 4:35pm PST: We made contact with Microsoft several times this week to check on the status of this issue. They are actively working on a fix for the bug, but are unable to provide an estimate as to when it will be available. Thank you for your patience so far; we will continue to do everything we can to expedite a resolution.

24 August 2016, 2:43pm PST: Currently, Microsoft has released an update that addresses the issue for Windows 8.1, Windows 7, Windows Server 2012 R2, Windows Server 2012, and Windows Server 2008 R2. An update for Windows 10 is still pending. We will update you again once it becomes available. You can find more information about this update in Microsoft's KB article here (3187022). The update can be obtained from Microsoft's site here.The fix had not been verified at this time.

29 August 2016, 2:25pm PST: Microsoft has released an update that addresses the issue for Windows 8.1, Windows 7, Windows Server 2012 R2, Windows Server 2012, and Windows Server 2008 R2. An update for Windows 10 is still pending; we will update this page as soon as it is available. You can find more information about the update in the Microsoft article KB3187022. The update can be obtained from the Microsoft Update Catalog.Note: This fix has been verified by the Seagull QA team.

31 August 2016, 9:21am PST: Microsoft has released an update that addresses the issue for Windows 10 version 1511. You can find more information about the update in the Microsoft article 3186988.  Microsoft is still working on an update for Windows 10 version 1607; we will update the page as soon as it is available. The update can be obtained from the Microsoft Update CatalogNote: This fix has not been verified by the Seagull QA team. They are currently in the process of testing and verifying this fix from Microsoft.

31 August 2016, 11:39am PST: Microsoft has released an update that addresses the issue for Windows 10 version 1607. You can find more information about the update in the Microsoft article 3176938.  The update can be obtained from the Microsoft Update CatalogNote: This fix has not been verified by the Seagull QA team. They are currently in the process of testing and verifying this fix from Microsoft.

Latest Update, 31 August 2016, 12:34am PST: Microsoft has informed us that the update for Windows 10 version 1607 is also available via Windows Update, and that updates for previous versions of Windows should be available on Windows Update in mid-September.

41 comments

Date Votes
0
Avatar
luke.thompson

Not affecting our terminals yet, but I have blocked the update on the ok machines for now. I followed to keep track off the situation.

0
Avatar
Lowry Pierce

On August 10th I installed KB3177725 on two Windows 7 PCs.   I have  not experienced the printer problem with my two HP Printers, yet.  Nevertheless, just to be safe, I uninstalled  KB3177725 on both PCs.    When a fix shows up, I will consider the recommended action by others.

0
Avatar
Bernard Manguette

Any news about this?

0
Avatar
Amos Phoenix

Any update on this yet? I have been uninstalling these updates but they keep pulling them back down.

4
Avatar
Kai Kohler

Latest Update, 17 August 2016, 4:35pm PST: We made contact with Microsoft several times this week to check on the status of this issue. They are actively working on a fix for the bug, but are unable to provide an estimate as to when it will be available. Thank you for your patience so far; we will continue to do everything we can to expedite a resolution.

0
Avatar
Mickey Rasmussen

I manually ran this script on all clients hrmpf. and have to do it again today.. 

If someone wats the script: 

if exist c:\windows\servicing\packages\package_for_KB3177725* (
echo Found updates that must be removed, please wait...
wusa /uninstall /kb:3177725 /quiet /norestart
takeown /F c:\windows\servicing\packages\*KB3177725*.*
icacls c:\windows\servicing\packages\*KB3177725*.*
del c:\windows\servicing\packages\*KB3177725*.*
ECHO an update is uninstalled
pause
) ELSE (
echo No updates need to be removed
)

After that a reboot is required, but windows will try to reinstall the Patch :/ 

Microsoft better pull that back, or send out a fix..

2
Avatar
Jared Baszler

Just a friendly reminder that there is a valid workaround for users running versions Bartender 10.1 or 16.  We've implemented this solution and it is working fine.  Granted, I had to change this setting on every PC that runs BarTender but that was a much easier task then trying to prevent Windows Updates from coming through. 

From this article: https://support.seagullscientific.com/hc/en-us/articles/225047808 

are these solutions:

2
Avatar
Malcolm Smart

Take a deep breath and relax Mickey. In my 35 years of working in IT, I can safely say that this comes with the territory and is just a small, albeit annoying, speed bump. May I suggest that the next time you run your excellent script to remove the updates, that you go ahead and disable automatic Windows updates too. Once the fix is release you can turn automatic updates back on. I've already done this on several of our PC's and so far all is well and I've only had to remove the offending code once.

Hang in there.

0
Avatar
Russell Johnson

This is a good reason to use a centralized patching system so admins can have control.  At least with Windows 7, one can "hide" the undesirable KB from Windows Update so it won't keep applying.  But Windows 10 is a cumulative update so that one would require changing Group Policy to configure how updates are applied and deferring all updates.  Requires Pro or Enterprise.

0
Avatar
Lowry Pierce

 

I turned off my Windows 7 automatic update function last August when I discovered Microsoft was trying to infest my PC with Windows 10 downloads without my permission, (otherwise known as Microsoft Malware).  Now I “hide” every optional update, and closely screen all recommended and important updates.  Often I hide those too because they appear to be unnecessary or dangerous.   Am I smarter than Microsoft?   No, but it is my PC and I will decide what to download and install, not Microsoft.   Yes, my screening takes lots of time and is a pain in the butt, but necessary.   In the past 12 months I have hidden 12 Microsoft updates, and I expect to hide more.

 

0
Avatar
Dennis Du

To Kai Kohler, 

   Pls advise latest status on this.any timeline share with us? Thx.

 

0
Avatar
Rob Simpson

We did "Uninstall an Update" for "Security Update for Microsoft Windows (KB3177725)" overnight and that resolved the issue entirely. Our patching is centrally managed by system administrators, so this is good enough for us regardless of how long it takes Microsoft to resolve the issue.

0
Avatar
stephan andersson

We also did this as a quick fix but in the long run we need to apply the security related patches.

0
Avatar
Lowry Pierce

I have installed, then un-installed, and hide KB3177725.   If I un-hide the KB and reinstall it, that is the fix?  How does that fix the printer problem?   Does not make sense to me?

0
Avatar
Rob Simpson


I would think you need to leave it (just the one KB3177725) uninstalled, like we did (per my comment above).

0
Avatar
Jasper Wen

Latest Update, 24 August 2016, 2:43pm PST: Currently, Microsoft has released an update that addresses the issue for Windows 8.1, Windows 7, Windows Server 2012 R2, Windows Server 2012, and Windows Server 2008 R2. An update for Windows 10 is still pending. We will update you again once it becomes available. You can find more information about this update in Microsoft's KB article here (3187022). The update can be obtained from Microsoft's site here.

Note: This fix hasn't been verified yet by our QA team. Our QA team is currently in the process of fully testing and verifying this fix from Microsoft.

0
Avatar
ht104

Don't understand, why this MS update does not affect every Bartender installation?

Have about 20 BT installations here on Win 7 Pro (all fully patched), but no one was affected by this issue...

0
Avatar
Scott Radandt

No one has yet mentioned having this problem on Windows Vista.  I have three Vista PC's running BarTender 10.1 and one has shown the error.  Using the workaround to modify the printer setting has resolved it for now.

0
Avatar
Lowry Pierce

OK, so I am waiting on Microsoft to release update KB3187022 which will fix the printer problem and includes the security patches.  Correct?   Therefore, KB3177725 will remain "hidden" and never will be needed.  Correct?

0
Avatar
ht104

Not correct.

KB3187022:

Update replacement information

This update doesn't replace a previously released update.

You should install first KB3177725. If you have printing problems after this installation you should apply KB3187022.

0
Avatar
Rob Simpson

>> Don't understand, why this MS update does not affect every Bartender installation?

It only affected 2 of our 8 printers that we know of. Since it's related to printer drivers, it may depend on the printer. We had the issue with just one of five Printronix T5204 printers and a ZDesigner ZM400.  No specific reports of trouble with Intermec PM43, Zebra 90XiIII Plus and 4 other Printronix T5204 printers, but it's possible the business processes on some of those don't require the app to print more than one label at a time.

0
Avatar
Ed Terry

Temporary work around without uninstalling KB3177725 from Windows Server for those using the Commander Service to monitor BarTender print jobs:

We use the Commander Service to monitor shipping label printing within Epicor ERP.  I gave our traffic clerk permission to modify the Commander Service service, then created a CMD (batch) file on the desktop to stop, pause, then restart the service.  It is run whenever a label fails to print.

Grant permission:

Download SubInACL.msi from Microsoft (an old resource kit application from 2000) and install it on the server running the Commander Service.

https://www.microsoft.com/en-us/download/details.aspx?id=23510

The command below assigns Query, Start, Stop and Enumerate permissions to the user.  Replace YOURDOMAIN and USERNAME as appropriate.

In a Command Prompt window, move to the installed location of subinacl.exe and type:
subinacl/service "Commander Service" /grant=YOURDOMAIN\USERNAME=stoe

Open Notepad and create a batch file (I called mine Labels.cmd):
Again, replace SERVERNAME as appropriate.

@echo off
sc \\SERVERNAME stop "Commander Service"
timeout 10
sc \\SERVERNAME start "Commander Service"

As I mentioned, whenever a label fails to print, the traffic clerk double clicks on Labels.cmd on the desktop to restart the Commander Service on our Epicor server, then reprints the shipping label.

0
Avatar
Kai Kohler

Latest Update, 29 August 2016, 2:25pm PST: Microsoft has released an update that addresses the issue for Windows 8.1, Windows 7, Windows Server 2012 R2, Windows Server 2012, and Windows Server 2008 R2. An update for Windows 10 is still pending; we will update this page as soon as it is available. You can find more information about the update in the Microsoft article KB3187022. The update can be obtained from the Microsoft Update Catalog.

Note: This fix has been verified by the Seagull QA team.

0
Avatar
Francisco Javier Mellado

Hello, I uninstall KB3177725 Microsoft update to fix the problem, if i install KB3187022 it´s necessary install KB3177725 before??

Thanks.

0
Avatar
Lowry Pierce

To:  Francisco Javier Mellado:  

Your question is very good.   I do not know the answer.   I uninstalled KB3177725 too.   I am afraid to reinstall it.   I can not find  KB3187022 or download it.    I will wait until KB3187022 shows up in my daily update screen.   I will not reinstall KB3177725 until I have guarantees it is safe.

0
Avatar
Ed Terry

Based on what Microsoft has posted at https://support.microsoft.com/en-us/kb/3187022, you can go to the Microsoft Update Catalog to get the update KB3187022 at http://catalog.update.microsoft.com/v7/site/Search.aspx?q=KB3187022.

Choose your version (Title), click the "add" button, then the "view basket" button and finally the "download" button (on the following window). Follow the instructions to choose a download location.

Note: Microsoft does not allow access to the update catalog from any web browser other than Internet Explorer, version 6 or greater.

I do not know if KB3177725 needs to be reinstalled before running KB3187022.  If someone from Seagull Scientific could respond to Francisco's question we could get on with this fix.

1
Avatar
Kai Kohler

Francisico, Lowry, and Ed,

Thank you for your posts and questions.  Our QA department has verified the fix.  KB3187022 does not replace any previous updates, so you should install KB3177725 before installing KB3187022 (Note this fix is not for Windows 10.  We are still waiting on a fix from Microsoft for that operating system):

  1. Install KB3177725
  2. Print 3-4 print jobs from BarTender to confirm you suffer from the issue
  3. Install KB3187022

 

Please sign in to leave a comment.