![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(147.20000000000002, 88%, 24%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAM%3C/text%3E%3C/svg%3E)
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(275.2, 16%, 36%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EV%3C/text%3E%3C/svg%3E)
Hello Andre Manoel Duarte,
I'm writing to check if switching to the LPR Protocol (Option 2) successfully allowed you to bypass the authentication loop.
Since the 24H2 update enforces strict SMB Signing and RPC Encryption that breaks legacy "Guest" sharing, the LPR method is the definitive workaround because it communicates directly over TCP/IP (Port 515) and ignores the Windows User Authentication stack entirely.
If that method failed, please verify that the LPD Print Service is installed and running on the Host machine, and that the Windows Firewall on the Host is not blocking "LPD Service" (Inbound TCP 515).
If the issue has been successfully resolved, please consider accepting the answer as it helps other people sharing the same question benefit too. Thank you!
VP