Windows Update (August 2016) causing BarTender errors Follow
There is an issue printing from all BarTender versions if Microsoft Windows Updates from August 9, 2016 are installed.
2 September 2016, 12:16pm PST: Microsoft has released updates that resolve this issue for all affected operating systems and all updates have been tested by Seagull Scientific. Please see the “Recommended Solution” section on this page for more details.
If you would like to be notified when this page is updated please "Follow" the Community post Notifications for "Windows Update causing BarTender errors."
Windows Updates that cause printing problems
Microsoft has acknowledged this problem in the Known Issues section of the articles below:
"After you apply this security update and you print multiple documents in succession, the first two documents may print successfully. However, the third and subsequent documents may not print."
Applies to: All BarTender versions
BarTender will print 2-3 jobs successfully and then throw one or more of the following BarTender or Windows errors. The error message you receive may vary based on your unique environment.
BarTender cannot use printer '<printer name>' to design, print or export a document due to a printer setup problem.
BarTender cannot use printer '<printer name>' to design, print, or export a template due to a printer setup problem.
A Windows error code was returned: <data>
Error message: <data>
The I/O operation has been aborted because of either a thread exit or an application request.
The specified datatype is invalid.
The data area passed to a system call is too small.
Microsoft has released updates that resolve this issue on all affected operating systems. Please download and install the update specific to your operating system. All of these solutions have been tested by Seagull Scientific.
Windows 10 version 1607
Installing KB3176938 resolves this issue. Install the update using Windows Update or download it from the Microsoft Update Catalog (site requires Internet Explorer 6.0 or later; other browsers are not supported).
Windows 10 version 1511
Installing KB3186988 resolves this issue. Microsoft has informed us that this update will not be available through Windows Update until mid-September. You can download and install it from the Microsoft Update Catalog (site requires Internet Explorer 6.0 or later; other browsers are not supported).
Windows 7, Windows 8.1, Windows Vista, Server 2008, Server 2012, Server 2012 R2
Installing KB3185911 resolves this issue. Microsoft has informed us that this update will not be available through Windows Update until mid-September. You can download and install it from the Microsoft Update Catalog (site requires Internet Explorer 6.0 or later; other browsers are not supported).
Note: Please check the pre-requisites section here before installing this update.
Modify BarTender setting for each printer
Applies to: BarTender 2016, v10.1
When "Use new device context for each print job" is enabled, BarTender can print without issue with the Windows Updates installed. This setting may impact performance in high volume printing. Visit Use new device context for each print job for instructions.
Remove the update from the affected system
Applies to: Windows 10, Windows 8.1, Windows 7, Windows Server 2012 R2, Windows Server 2012, and Windows Server 2008 R2
The issue appears to be directly related to specific Windows Updates from August 9, 2016. Uninstalling the appropriate update should allow BarTender to return to normal functionality. Visit How to find and remove a Windows Update for instructions.
Please assess your security needs carefully before deciding whether to uninstall or delay installing these Windows security updates.
|Windows Version||Windows Update to remove|
|Windows 10||Security Update for Microsoft Windows (KB3176493)|
|Windows 8.1, 7, Server 2012 R2, Server 2012, Server 2008 R2||Security Update for Microsoft Windows (KB3177725)|
Continuously restart BarTender
Applies to: All versions of BarTender
Restarting BarTender will allow 2-3 print jobs to work before it needs to be restarted again.