Upgrade 5.2.26 r128414 (Qt5.6.2) to 5.2.28 r130011 (Qt5.6.2) causes scanner malfunction

[iwannaknow]

Today I performed an upgrade 5.2.26 r128414 (Qt5.6.2) to 5.2.28 r130011 (Qt5.6.2) for the VirtualBox program on a Windows 10 Home edition x64 with all the latest updates.
After the upgrade I started a virtual machine with Windows XP sp3, to use the scanner Epson Perfection 1250.
Previous to the upgrade, when I log into the virtual machine, I hear the scanner device being detected by the OS.
So when I go find the scanner and click the 'sample' button, the scanner button start immediately to flash and a short time later the scanner presented the requested sample.
However, after the upgrade this procedure no longer seem to work as the scanner button does not flash anymore, but after some time the buttonlight goes off and nothing else happens.
At first there's system error window on the host machine (Windows 10) telling me that something tried to write to the memory, but that couldn't be read followed by an immediate shutdown of the virtual machine, some sort of BSOD so to speak.
So I first I rebooted the virtual machine in safe mode and performed 'check disc' to check system settings, just in case.
I then closed the VirtualBox program and also rebooted the host system and performed the sfc command, just in case.
After the reboot I retried to load the virtual machine again and when requiring the same sample ... the same thing happens again, only this time a window within XP opens telling me:
'When the device is busy, you have to wait until the job is done and try again' yet the scanner button does not light up anymore until the virtual machine shut down and then the scanner light come up again.

So I undo the upgrade to the previous version and the scanner functions as it did before, when I press the 'sample' button, scanner button flashes and shortly after that the requested sample is shown.
That tells me that something goes wrong while upgrading.
So what's the problem here, anyone same sort of issues?

[andyp73]

So what's the problem here, anyone same sort of issues?

It is unlikely anyone else has an Epson Perfection 1250 running inside a Windows XP SP3 guest so I doubt anyone else has seen your exact set of circumstances.

How is the scanner connected to the host?

Can you provide the VBox.log file for the guest from a session where you have the issue with the scanner. Zip it and attach it here.

-Andy.

[Commodore]

There's definitely something wrong because I have similar issues with my oldie goldie scanner on a WinXP guest. Except that it started way before - at least a few months ago. I can sometimes "randomly force" it to work (unplugging USB, plugging again, changing USB port, unplugging USB port, resetting the guest etc. etc.), but that's no science.

[socratis]

One easy way to tell is to simply start downgrading to previous versions, until you get it to fail between two consecutive releases. I would suggest the bisection method, it saves you time by halving the versions between Working and Failing...

5.2.0   <-- Test 1 WORKS
5.2.2
5.2.4
5.2.6
5.2.8
5.2.10
5.2.12
5.2.14      <-- Test 3 WORKS
5.2.16
5.2.18
5.2.20
5.2.22          <-- Test 4 WORKS
5.2.24
5.2.26                  <-- Test 5 ???
5.2.28  <-- Test 2 FAILS

The closer you get to the failing between versions 5.2.x and 5.2.(x+2) the better chances you have of your issue taken seriously...

[iwannaknow]

So what's the problem here, anyone same sort of issues?

It is unlikely anyone else has an Epson Perfection 1250 running inside a Windows XP SP3 guest so I doubt anyone else has seen your exact set of circumstances.

How is the scanner connected to the host?

Can you provide the VBox.log file for the guest from a session where you have the issue with the scanner. Zip it and attach it here.

-Andy.

Hi Andy, VB can and will be used for these kind of things, right ... and nothing has been altered in between, in my systemconfiguration anyways.
So for many years it already worked flawlessly without any problem.
The device has been connected onto a Windows 10 Home edition with a twain driver, which recognised the device but remain unusable within Windows 10.
After Windows XP has been installed virtually in VB, I installed also the extensionspack and at the VM I only needed to add the USB device.
Then I booted the Virtual Windows XP, installed needed drivers for the new found hardware and configured the device, that's all.
I'm quite sure something has been changed within new version of VB that causes this scanner no longer to be reachable/usable within the VM.
I'll add 4 attachments into the zip, the first of which, will be the last log using the older version of VB when all seem to work flawlessly and the following 3 logs are using the newer VB version causing all the trouble. Interesting here's the scanner that will be recognised in both versions. Yet in the latest version, the error occurs when I issue a preview, then the scanner device stopped responding and get stuck, followed by an unexpected crash of the VM. So restoring the previous (older) version with the restore point before installing the newer version, made the changes undone so I can use the old scanner as it was before.

VBoxSVC.log.zip

(8.87 KiB) Downloaded 11 times

[Commodore]

Still an issue for me, but slightly different. In the meantime I downgraded to 5.1.12 r112440 (which was the last fully functional version for me). The scanner is detected and connected; however.. when I start the scanning process, the head/belt starts moving in the opposite direction (basically a dangerous thing, as it's already "parked" there in one corner, so I have to unplug quickly to avoid damaging the device).

It happened before with newer versions of VirtualBox too. Later on I "gradually" downgraded - with clean/total uninstalls inbetween.

Any way to salvage this once glorious WinXP guest?

[scottgus1]

Commodore, a new topic would be better than glomming onto an old post, even if the issue is the same. Much better if the issue is "slightly different". Forum rules request, Do not hijack other threads, create your own. Choose your title carefully.