[German]Recently, Microsoft acknowledged problems with devices that use the eSCL scan protocol under Windows 11 24H2. This also affects USB scanners that simply cannot be found if they use the eSCL scan protocol. Microsoft claims to have fixed this error. Furthermore, device manufacturer updates should be tested in the event of scanner problems.
Problems with eSCL support fixed
Microsoft acknowledged a problem with scanners that support the eSCL scan protocol on November 22, 2024. The Windows 11 24H2 Health Status page contains the support articleUSB devices that support eSCL scan protocol may not be discoverable, which provides details.
This issue has since been resolved by Windows updates released on December 10, 2024 (KB5048667) and later. If this update is installed, scanners that are connected via USB and support the eSCL scan protocol should also be found.
The upgrade block set for this problem (ID 54762729) has now been lifted by Microsoft. If necessary, restarting the device may help if the upgrade to Windows 11 24H2 is not offered.
Other scanner problems fixed?
In the article Windows 11 24H2: Problems with USB scanners that use eSCL, I mentioned the problem that owners of various scanners cannot use their Canon scanners with Windows 11 24H2.
Blog reader MOM20xx had posted a comment in the discussion area and reported problems with his scanner. His Canon i-SENSYS MF633Cdw Laser worked perfectly for printing and as a scanner under Windows 10 22H2 and Windows 11 23H2. With Windows 11 24H2 only printing works. The scanner driver is installed, but a scan attempt ends in an error message. There were also messages in US forums, which I have outlined in the post above.
In this German comment a blog reader confirmed, that his Canon scanner works again using Microsoft driver ant he lawlessly with Microsoft's own drivers and the Windows scanner app from the MS Store. In the event of scanner problems, we recommend checking for driver and software updates from the device manufacturer and testing them.
In Microsoft Answers Forum is this thread discussing a conflict between Windows 11 and the Canon MF Scan Utility. It seem, that somebody found a workaround (re-installing the driver, as described within the tread).
Similar articles:
Windows 11 24H released (Oktober 1, 2024)
Windows 11 24H2: Numerous show-stoppers and known bugs
Windows 11 24H2: Serious issues after upgrade
Windows: DirectAccess discontinued; Always On VPN recommended
Attention: Windows 11 24H2 changed default settings for standby
Windows 11 24H2: Administrative templates (.admx)
Windows 11 24H2: Activation lost?
Windows 11 24H2: SMB read/write transfer rate extremely slow?
Windows 11 24H2: Issues with VPN connections, Direct Access …
Windows 11 24H2: Recall can't be uninstalled; and "poor mans recall" found
Windows 11 24H2: Microsoft confirms wrong display in disk cleanup
Windows 11 24H2: Apps no longer respond when using the camera
Windows 11 24H2: Installation fails on some ASUS devices
Windows 11 24H2: SSD firmware updates fixes crashes
Windows 11 24H2: Explorer bug opens menu "upwards" – Workaround
YOU ARE WRONG. The fix issued by Microsoft is FAKE NEWS. It does not work. Microsoft is full of baloney. I have a close to top of line recent model Brother MFC-L3870CDW and spoke with escalated support. They have thousands of customers on a list waiting for Brother to email them when a fix is found and Microsoft has not been helpful to Brother with vague answers like sometime in 2025 disrupting big and small business and individuals from multiple manufacturers. Microsoft does not make the working 23H2 available for download, so new Windows installs and new computers are stuck unable to un-install and revert back unless they caught the update immediately and could reverse it which you cannot do on new computers. Microsoft is getting more abusive and arrogant and not taking responsibility for their actions. They created a spelling/grammar feature in Office365 that has no OFF switch. You can no longer override or turn off spell/ grammar checker in Word or Outlook and it makes lots of mistakes. They just do what they want and do not listen or prioritize customer feedback. Their developer team should all be terminated.