Can't print from the web if you run Internet Explorer 11 as another user
The Internet Explorer 11 desktop application is retired and out of support as of June 15, 2022 for certain versions of Windows 10.
You can still access older, legacy sites that require Internet Explorer with Internet Explorer mode in Microsoft Edge. Learn how.
The Internet Explorer 11 desktop application will progressively redirect to the faster, more secure Microsoft Edge browser, and will ultimately be disabled via Windows Update. Disable IE today.
This article provides a workaround to solve the issue that you cannot print from Internet Explorer 11 by using another user account.
Original product version: Internet Explorer 11
Original KB number: 3136268
Consider the following scenario:
- You sign in to a 64-bit version of Windows through user account A.
- You run Internet Explorer 11 through user account B (by using the Run as a different user option).
- You browse to any webpage by using this Internet Explorer instance.
- You try to print the webpage contents.
In this scenario, the document doesn't print. No error is displayed.
This issue occurs because Internet Explorer 11 uses newer APIs to retrieve more detailed printer information. These new APIs require that the caller application run as the session user for 32-bit applications.
To work around this issue, determine whether you really have to run Internet Explorer 11 as another user. If not, remove this dependency.
If you make sure that the iexplore.exe process that's responsible for the printing procedure is a 64-bit process, printing should work correctly. You can do this by configuring Internet Explorer 11 to use a single process (
TabProcGrowth=0), but this will reduce security and increase the chance of application compatibility issues.
Alternatively, you could enable Enhanced Protected Mode (EPM) and force all processes to be 64-bit, but this applies to only websites that belong to security zones where Protected Mode is enabled (typically only the Internet zone). And this may also cause application compatibility issues.
Because of the problems that they may trigger, neither of the workarounds in this section are recommended. Therefore, removing the dependency is the best option.