In this case, it is mostly due to the abnormal operation of the%temp%/low folder in protected mode (being mistakenly deleted, shifted, and so on).
[The following information for reference only, not interested students can skip, directly to the third part: small easy ideas. ]
It turns out that when IE is running in protected mode, it has low privileges that are not sufficient to read and write files to the normal Internet temporary folder, so it creates low, lower-privileged subfolders in the original Internet temporary folder and saves the appropriate resources in the lower, for example:
Temp:%userprofile%/appdata/local/temp/low
Cookies:%userprofile%/appdata/roaming/microsoft/windows/cookies/low
Historical record:%userprofile%/appdata/local/microsoft/windows/history/low
However, sometimes they point to new folders in other locations for disk space considerations, and IE protection mode has an exception because there is no permission to read and write files in the new folder. This is why the Web page can print correctly after you remove the protection mode.
Small easy to:
Small easy here for you to find two ways to solve.