W11 24H2 eSCL "BUG" causing havoc

In Windows 11 23H2, the Canon Color imageCLASS MF654Cdw printer and scanner (just an example) with using the MF Scan Utility Ver.1.21.0.2 works fine, no errors or problems. Basically, about all eSCL based devices, which are multi-functional devices (scan/copy/fax) connected to our computers and networks, affecting all brands (HP, Canon, Brother, etc.).

After Windows 11 23H2 updates to Windows 11 24H2, the Canon Color imageCLASS MF654Cdw printer does not always print without error and the scanner using the MF Scan Utility Ver.1.21.0.2 always shows an error. No matter what, this MF utility will not work with the scanner:


The Canon Color imageCLASS MF654Cdw has been configured these ways and all have the same error when scanning only in Windows 11 24H2:
* Ethernet connection - cable connected to the printer to the router, static IP 192.168.1.10, scanning shows the above error.
* Wireless connection - static IP 192.168.1.10, scanning shows the above error.
* USB connection - printer prints very SLOW, but it prints, and scanning shows the above error.

I have found some users stating that in Windows 11 24H2, that their eSCL device still scans and many others do not scan at all. The majority of eSCL scanners in Windows 11 24H2 do NOT work at all.

Microsoft shows this a bug in Windows 11 24H2:

Windows 11, version 24H2 known issues and notifications
USB devices that support eSCL scan protocol may not be discoverable

I also found this particular discussion in Canon Community Discussions and Help forum about other users experiencing the same problem:

Canon Community Discussions and Help:
Canon MF655cdw Scan Utility not working on Win11 24H2

I am trying to figure out why some devices (HP, Brother, Canon, etc.) scanners do work for a period of time or continually work in Windows 11 24H2 while others do not. Microsoft and Canon are currently pointing fingers at each other, so I do not see any upcoming fixes for this problem.

In this article, I did not see Microsoft noting "Network-connected scanners" and just USB scanners, as this article provides more details (at least so far that I found):

Microsoft Blocks Windows 11 24H2 Update for USB Devices: eSCL Issues Explained

What Devices Are Affected?
This eSCL bug isn’t just ruining the party for niche devices. We’re talking about the workhorses of many offices and home setups:
* USB-connected multifunction printers (the kind that can scan, copy, and fax)
* Standalone scanners supporting the eSCL protocol
* Network-connected scanners

Here is the information on the eSCL specification:

Mopria eSCL Specification and/or Mopria eSCL Specifications

Also in the news (about everywhere):

Microsoft blocks Windows 11 24H2 on some PCs with USB scanners (Date: November 25, 2024)

Supposedly these Microsoft blocks takes a while to take affect and as I have experienced, these blocks do not block anything.

The only solution that I know that works, is to return back to Windows 11 23H2 and have your system backed up. That way you can restore it back to 23H2, or once, if ever, Microsoft fixes this bug in 24H2.

my brother MLC L3710CW was playing up with 24H2 printing and scanning.
it wouldn't come out of sleep mode unless it was switched off and then back on.

i found that using the Windows driver but with brother iPrint & Scan software installed solved the problem.
please note. thats just the iPrint & Scan software no drivers from brother.

unsure if Cannon have something similar but that was the work around i found worked with this laser printer.

not sure if that is of any help, best of luck, Steve ..

XxXxX said:

my brother MLC L3710CW was playing up with 24H2 printing and scanning.
it wouldn't come out of sleep mode unless it was switched off and then back on.

i found that using the Windows driver but with brother iPrint & Scan software installed solved the problem.
please note. thats just the iPrint & Scan software no drivers from brother.

unsure if Cannon have something similar but that was the work around i found worked with this laser printer.

not sure if that is of any help, best of luck, Steve ..

Click to expand...

I found the Windows Scan app in the Microsoft Store works with the Canon scanner, but has very limited features than I am used to in the Canon MF Scan Utility.

I tried a variety of troubleshooting options on the Canon MF printer/scanner and never got the scanner to work in 24H2. Power on/off; reapply firmware, reset printer setttings, etc. without success.

When I installed the Canon MF654Cdw driver, both Printer and Scanner options are selected for installation. I may unselect the Scanner option to see if the Canon MF Scan Utility will work. When I did this before (long time ago), the scanner was not recognized at all. I'll try it at this point.

Re the eSCL issue Microsoft have been recommending:

Important: We recommend that you do not attempt to manually update to version 24H2 using the Windows 11 Installation Assistant or the media creation tool until this issue has been resolved.

Click to expand...

Marcus Vinicus said:

Re the eSCL issue Microsoft have been recommending:

USB devices that support eSCL scan protocol may not be discoverable

USB standalone scanners are primarily affected, and compatibility hold has been applied to safeguard update experience.

learn.microsoft.com

Click to expand...

Quote:
Important: We recommend that you do not attempt to manually update to version 24H2 using the Windows 11 Installation Assistant or the media creation tool until this issue has been resolved.

Windows 11 24H2 has been automatically installing on my systems (post).

Nipdawg said:

Quote:
Important: We recommend that you do not attempt to manually update to version 24H2 using the Windows 11 Installation Assistant or the media creation tool until this issue has been resolved.

Windows 11 24H2 has been automatically installing on my systems (post).

Click to expand...

That is a bit odd. There is supposed to be a 'safeguard hold' on computers using eSCL devices getting an update to 24H2, meaning the update shouldn't be offered via Windows Update.

Marcus Vinicus said:

That is a bit odd. There is supposed to be a 'safeguard hold' on computers using eSCL devices getting an update to 24H2, meaning the update shouldn't be offered via Windows Update.

Click to expand...

I thought so too, but I lost trust in what Microsoft's states any more. I have other posts on here about this issue. These Microsoft's Safeguard Holds are basically false assurances.

My opinion based on experience is that WU is not fool proof and reliable anymore. It used to install GPU drivers on my system unannounced. Not a good idea when my card is a high end one that needs careful tweaking of settings.

Nipdawg said:

I found the Windows Scan app in the Microsoft Store works with the Canon scanner, but has very limited features than I am used to in the Canon MF Scan Utility.

I tried a variety of troubleshooting options on the Canon MF printer/scanner and never got the scanner to work in 24H2. Power on/off; reapply firmware, reset printer setttings, etc. without success.

When I installed the Canon MF654Cdw driver, both Printer and Scanner options are selected for installation. I may unselect the Scanner option to see if the Canon MF Scan Utility will work. When I did this before (long time ago), the scanner was not recognized at all. I'll try it at this point.

Click to expand...

This did not work as I get the same problem. 24H2 has broken eSCL very good. 23H2 is the only solution.

We have been offered 24H2 but we have a Canon Pixma TS6351a printer/scanner. I'm wondering how MS decides on compatibility holds on potential eSCL issues and if this hold ( or in our case not,) is reliable? The printer connects to PC using a USB cable only when printing and then disconnected. Is the hold based on installed Canon software/device manager etc? I can't seem to find out if the Canon uses the eSCL protocol. Maybe best to wait until MS fixes this.

Mitch said:

We have been offered 24H2 but we have a Canon Pixma TS6351a printer/scanner. I'm wondering how MS decides on compatibility holds on potential eSCL issues and if this hold ( or in our case not,) is reliable? The printer connects to PC using a USB cable only when printing and then disconnected. Is the hold based on installed Canon software/device manager etc? I can't seem to find out if the Canon uses the eSCL protocol. Maybe best to wait until MS fixes this.

Click to expand...

I wondered myself if Microsoft's safeguard holds are based on active or configured devices. I could not find any documentation on Microsoft's web site determine how the determine safeguards.

Since all my Windows 11 computers had the safeguard ID 54762729 in the registry, not sure when this safeguard ID entered the registry and when Microsoft scanned the system or checked it before installing 24H2:

reg query "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\TargetVersionUpgradeExperienceIndicators\GE24H2" /v GatedBlockId

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\TargetVersionUpgradeExperienceIndicators\GE24H2
GatedBlockId REG_MULTI_SZ 54762729

Basically, any eSCL scanning device will not work until this problem has been corrected. I would image this impacts millions of scanners as eSCL is widely used in about all scanners.

I connected our printer/scanner to our PC using a USB cable and turned the printer on. I checked for Windows Updates and still showed 24H2 as available. Windows is obviously not interrogating the entire system when deciding on compat hold or our device is not affected. Don't know what to believe. I assume that MS will modify 24H2 to fix the issue and not throw it back on to the users to deal with?

On WindowsLatest.com highlight shows:

For Windows 11, KB5048667 update resolves issues with USB scanning, printing, and network devices like modems, which previously led to a safeguard hold on the 24H2 feature update.

Click to expand...

When I read this article, Windows 11 KB5048667 24H2 big update, direct download .msu, I do not see any mention of "... resolves issues with USB scanning, printing, and network devices..." in Windows 11 24H2.

Just wondering if this information is right or wrong for this update.

Thanks.

Nipdawg said:

On WindowsLatest.com highlight shows:

When I read this article, Windows 11 KB5048667 24H2 big update, direct download .msu, I do not see any mention of "... resolves issues with USB scanning, printing, and network devices..." in Windows 11 24H2.

Just wondering if this information is right or wrong for this update.

Thanks.

Click to expand...

Oh.. Just found my answer here:

KB5048667: Microsoft removing Windows 11 24H2 USB-related 54762729 update block soon

With the latter, the tech giant is going to remove an upgrade block for Windows 11 version 24H2 feature update "in the coming days." The block was put in place under safeguard hold ID 54762729 to prevent issues with USB scanning, printing and network devices like modems. For those who may not have followed, Microsoft had stated that switching from USB to eSCL mode was broken.

Click to expand...

Nipdawg said:

Oh.. Just found my answer here:

KB5048667: Microsoft removing Windows 11 24H2 USB-related 54762729 update block soon

Click to expand...

Oh goody, I'll soon be offered 24H2...I'm trembling with sheer and utter joy...

colinp said:

Oh goody, I'll soon be offered 24H2...I'm trembling with sheer and utter joy...

Click to expand...

I'm hoping this still blocks or prevents 24H2 from installing on my main system.

Interesting find. On another system with Windows 11 23H2 that has/had the GatedBlockId 54762729, I had to restart Windows and noticed an update applied when there were not updates available. When I checked the registry, the GatedBlockId now shows "None". I checked the other two registry entries that I updated to prevent 24H2 from installing, and they are now reset. I expected only the GatedBlockId to show None and the rest of the changes would remain. What to see what happens next.

I posted on my GatedBlockId 54762729 yesterday (AFAICT, I don't have any eSCL devices, the closest thing being an old Brother laser printer that uses WSD):


Today, it's gone, replaced by GatedBlockId 55382406, which Google search has never heard of.

barreleye said:

I posted on my GatedBlockId 54762729 yesterday (AFAICT, I don't have any eSCL devices, the closest thing being an old Brother laser printer that uses WSD):

Cant upgrade from 23H2 to 24H2

Alternatively, please open command prompt and then enter the following: reg query HKEY_CLASSES_ROOT >> %userprofile%\Desktop\Classes.txt Please attach Classes.txt to your next post. I did clean install of 24H2. Thanks.

www.elevenforum.com

Today, it's gone, replaced by GatedBlockId 55382406, which Google search has never heard of.

Click to expand...

I just checked the GatedBlockId and its still set to None. Actually on that computer, Windows 11 24H2 update is sitting in Windows Update.

Looking on my list of 24H2 problems, the December update fixes the eSCL bug. That was the last reason I was preventing 24H2 from installing, but I am very hesitant to let 24H2 install yet.

I wonder what the GatedBlockId 55382406 means.

@Nipdawg

This page might get you started with this. It is the only link CoPilot came up with.