Microsoft Slaps Windows 11 Update Hold on Hardware Connected To eSCL Devices (theregister.com) 10
Microsoft has confirmed that Windows 11 24H2 has issues with USB-connected devices that support the Scanner Communication Language (eSCL) protocol. From a report: A compatibility hold has been applied to the hardware. The hold means that hardware connected to a USB device supporting the eSCL protocol will not be offered an upgrade to Windows 11 24H2. Microsoft said: "This issue primarily affects USB-connected multifunction devices or standalone scanners that support scan functionality and the eSCL protocol."
According to Microsoft, the issue lies in device discovery. Install Windows 11 24H2, wait for it to discover USB-connected peripherals, and... nothing. Or as Microsoft put it: "You might observe that your device does not discover the USB-connected peripheral and the device discovery does not complete." The company added: "This issue is caused due to the device not switching out of eSCL mode to USB mode, which allows the scanner drivers to be matched."
According to Microsoft, the issue lies in device discovery. Install Windows 11 24H2, wait for it to discover USB-connected peripherals, and... nothing. Or as Microsoft put it: "You might observe that your device does not discover the USB-connected peripheral and the device discovery does not complete." The company added: "This issue is caused due to the device not switching out of eSCL mode to USB mode, which allows the scanner drivers to be matched."
Pro Tip (Score:4, Interesting)
If it would block updates to Windows 11, it might be worth buying an eSCL device and leaving it attached. Could we just get a dongle?
Re: (Score:2)
They will fix it eventually, so the only good way is to disable TPM in BIOS.
If your BIOS won't allow that, you should have got a better motherboard. I suggest ASRock (I used to do Giga-Byte, but the most expensive board I ever got from them died shortly out of warranty and that left me with a distaste for 'em)
Re: (Score:2)
I have never run into a board that does not allow you to disable the TPM. I also had it disabled on my teaching laptop, but I recently needed bitlocker there and without a TPM active that turns into a real hassle, probably intentionally.
Re: (Score:2)
I haven't either, but I haven't messed with too many PCs since it became a thing. My clones will do it, but I wonder about corporate PCs like Dells or whatever. I'm used to those often not having BIOS options that everything else has.
Re: (Score:2)
Oh, _those_ systems. Yes, they might be a problem.
Crapware.... (Score:2)
Well. We all know this even is many are in denial.
I love/hate scanners (Score:2)
I love scanners. They make my record keeping so much easier when I can just pass any paper I get through it for filing in my NAS.
I hate scanners. The only reason I have a Windows VM on my Linux PC is because I can't get that damned thing to work under Linux at all. I even tried to buy a new (used) scanner and the Linux experience with it just sucks.
Re: (Score:3)
I have had the opposite experience. I've owned two different scanners that were sold cheap (one at a flea market and one at a yard sale) because a new version of Windows didn't support them, both worked on Linux (one Canon, one Epson. Only the latter required that I install a driver separately.)
Now I have a Brother laser MFC and not only does it have a Linux driver which works, but it also supports standards-based scanning and printing over the network.
Re: (Score:2)
Have a look at VueScan. It's not free but it works on my Linux systems. https://www.hamrick.com/ [hamrick.com]
Wait a minute (Score:2)
Does this mean that if my Windows is updated and then I connect a (certain) scanner to it, it won't work? As far as I can tell from the article, yes, it does mean exactly that.
It's very irresponsible of Microsoft to push this update to ANY computer, whether connected to one of these scanners or not.
But this is Microsoft we're talking about, so it was to be expected.