Bartender 10.0 SR2 VBScript error after August 2025 Windows Update
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:
Upon investigation the issue appears to be related to Microsoft updating the vbscript.dll 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?
Any assistance would be much appreciated.
-
BarTender 10.0 is not compatible, nor has it been fully tested, with Windows 11 (it was released 13 years ago!) and so I doubt there is a way round this without updating BarTender.
-2 -
We are having the same problem on Win 11 with message about Visual Basic. We have returned to Windows 10 because of this. Does anyone know of a fix?
0 -
Hi,
Same problem with version 10.1.
What we see though is that everything still functions well. It's just boring to have this pop-up at startup and each time we print.Patching old version is probably not your plan. Could we just make Bartender stop checking the VBscript version?
0 -
We also have a user that ran into this issue on Windows 11 running BT10.1. He reported that everything still seems to work while design label templates, he was just annoyed by the popup. We advised him to disable the error message for now unless he encounters issues with VB.
This can be disabled by going to:
- Administer > Application Message Setup
- Search for the error “3901”
- Select the search result.
- Uncheck “Dialog (Interactive Use Only)” and click “OK”
2 -
Thank you so much for the fix. We have tried this and it works. The error message 3901 no longer shows. Works great.
Thanks again.
1 -
Regarding disabling message in “Administer” - this works on Regular BarTender - but not on “Automation” version.
Question: Do you know the steps to disable the message on the “Automation” version 10.1 ?
0 -
On Automation 10.1, I have disabled the error 3901 but then the 3903 appeared, so I did the same with it and it works now. Don't forget, when disabling the 3903, to change the default response to “continue”.
Regards.
0 -
That will be using a different instance of BarTender running using Local System Credentials that is running when Commander is active. Try stopping the detection in Commander as that should hopefully stop all the BarTender instances and when you restart the detection in Commander that may mean the BT instance now picks up the changes with the messages.
0 -
we are also using 10.1 Automation but also using commander to automatically print labels from a bartender file using a .csv, I have disabled the error messages above and clicked the continue box but while I can manually print using the bartender file if I try to print through the commander folder the labels do not even make it to the printer,
I have tried restarted the PC, the service and running bartender as a local user which I logged onto separately to check if the error messages were still disabled, the same printers are also installed on the local account.
any ideas?
0 -
Did you try stopping Commander first, as mentioned above, and all make sure all the BarTender instances are closed too?
0 -
both commander and bartender were closed, PC was restarted too
wondering if bartender is using different settings than the version of bartender where I the error message is not disabled, bit of a weird one
0 -
It has been a long time since I last played with Commander but I think it will be the local system account or similar that is running it. If you open Commander and click on the link in there to open BarTender I wonder if that opens the one the actual “user” is using
0
Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.
Kommentare
12 Kommentare