Edge version 149 unable to do print preview and print due to URLAllowList and URLBlockList

pong kien ping 10 Reputation points
2026-06-11T00:41:11.8066667+00:00

Hi Microsoft Edge Support Team,

After updating Microsoft Edge to version 149, we are unable to open Print Preview and perform printing. During further investigation, we found that adding the following entry into the URLAllowList resolves the issue:

chrome-untrusted://print

Could you please confirm whether this behavior is expected in Edge version 149? Previously, we tested the same scenario on Edge version 148 and did not encounter this issue.

Please refer to the attached screenshot for more details.

Picture 1: Current URLBlockList setting

User's image

Picture 2: URLAllowList setting that does not work. Notice the print preview cannot load up

User's image

Picture 3: After adding "chrome-untrusted://print", able to work

User's image

Microsoft Edge | Other | Windows 11
0 comments No comments

2 answers

Sort by: Most helpful
  1. Jeronimo Fuerte 45,045 Reputation points Independent Advisor
    2026-06-11T02:44:21.95+00:00

    Hi! With URLBlocklist = *, Edge is configured to block all URL patterns unless they are explicitly allowed. URLAllowlist is intended to create exceptions to restrictive blocklists, and the allow list takes precedence over the block list.

    However, I would not say that this is a specific Edge 149 print preview bug or intentional change, because Microsoft has not released a note that specifically says “Print Preview changed in Edge 149.”

    But it does appear to be an expected side effect of using URLBlocklist = * with Edge internal pages, although the difference between Edge 148 and 149 may be due to an internal implementation change in the print preview page.

    Was this answer helpful?

    1 person found this answer helpful.

  2. Eric Lawrence 16 Reputation points Microsoft Employee
    2026-08-26T16:29:00.7466667+00:00

    Blocking Edge’s internal protocols, including edge:, about, chrome-untrusted, etc will interfere with the proper functioning of the browser and should be avoided, as noted in the documentation: https://learn.microsoft.com/en-us/deployedge/microsoft-edge-policies/urlblocklist

    Trying to exempt specific URLs from these protocols is not a scalable or reliable approach. At a minimum, there should be URLAllowlist entries for the entire protocol (e.g. chrome-untrusted:*) but generally URLBlocklist’ing “*” is inherently going to require constant maintenance because the browser can use new URLs as a part of its internal operation at any time.

    Was this answer helpful?

    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.