Bartender 10.0 SR2 VBScript error after August 2025 Windows Update
Posted by Parking_Elephant3190@reddit | sysadmin | View on Reddit | 10 comments
We use Bartender 10.0 SR2 from Seagull Scientific to print our labels and since the 2025-08 cumulative update for Windows 11 24H2 we have been having issues with print station and labels that use VBscript. When we try to print a label we get the below error message:
One or more objects requires the use of Visual Basic scripting. You currently have installed a version of Visual Basic scripting earlier than version 2.0. BarTender requires Visual Basic scripting 2.0 or greater. Please run the BarTender setup program to install the correct verison of Visual Basic scripting.
Upon investigation the issue appears to be related to Microsoft updating the vbscript version from 5.812.10240.16384 to 10.0.26100.4768. I believe that Bartender is only looking at the first digit in the version and seeing 1 instead of 10 and therefore 1 is less than 2 and VBScript 2.0 or higher is required.
Does anyone know how Bartender validates the VBScript version and if there is a way to either get it to look at the first 2 digits or spoof it by getting it to look somewhere else where I can enter a random number higher than 2?
We are currently in the process of updating our MRP software from AX 2009 to D365 so cannot update Bartender until that process is finished first.
Any assistance would be much appreciated.
Virtual_Pirate7521@reddit
Did you find a fix for this, as we are having the same issue...
Parking_Elephant3190@reddit (OP)
Not so far, have rolled back the update on a couple of devices that it is business critical for labels to be printed. We are currently speaking with Seagull to update to the latest version of Bartender
Virtual_Pirate7521@reddit
Did you find a work around or fix for this?
SysAdminDennyBob@reddit
Classic IT inflection point where the decision has already been made for you externally but the company just keeps on keeping on.
VBScript is dead, the warnings were issued, time was given. And your company is just not following through.
It's time to spend money and move to a modern supported solution. Anything else and you are just backing yourself into a corner more and more until it eventually traps you and causes downtime. Be the voice of reason in the next meeting.
nohairday@reddit
Wasn't VBscript due to be disabled in windows now or soon?
I'm sure I saw something that it would be removed from the operating system by default.
Even if not yet, using VBS in 2025 is... suboptimal.
RedShift9@reddit
File a support request with Seagull?
Parking_Elephant3190@reddit (OP)
Unfortunately we don't have support with Seagull at the moment and the version we are currently using is EOL support wise
RedShift9@reddit
Can you avoid using VB script in your templates?
Parking_Elephant3190@reddit (OP)
Our testsets where information for the labels are pulled from have their programs written in vbscript so have to use it
RedShift9@reddit
Ok but do you have VB script in use inside your templates?