Premiere Pro 26.5 – Program Monitor guides exist but are completely invisible after updating to 26.5.1
Issue:
Program Monitor guides are present in my Premiere Pro project but are completely invisible. Premiere recognizes that the guides exist, but does not display them.
Premiere Pro version:
26.5 (Windows)
Operating system:
Windows 10 22H2
What happened:
I had a Premiere 26.x project with visible Program Monitor guides. After updating Premiere to 26.5.1, the guides disappeared from the Program Monitor.
I rolled Premiere back to 26.5, but the guides remained invisible.
Troubleshooting performed:
- Confirmed View → Show Guides is enabled.
- Confirmed View → Show Rulers is enabled.
- Confirmed the existing guides are still present under Guide Templates / Manage Guides.
- "Clear Guides" is available, confirming Premiere recognizes that guides exist.
- Created a brand-new project. Guides display normally in the new project.
- Created a new guide in the affected project. The new guide is also invisible.
- Reset Premiere application preferences. The guides briefly appeared immediately after the reset, then disappeared again.
- Imported the affected sequence into a new project. The guides remained invisible.
- Created a new sequence and transferred the edit. The guides were still invisible.
- Exported the existing guide template and re-imported it. The guides remained invisible.
- The problem therefore appears to be specific to how Premiere is rendering guides for this project/sequence rather than the guides having been deleted.
Expected result:
Existing and newly created Program Monitor guides should be visible when Show Guides is enabled.
Actual result:
Premiere recognizes that the guides exist, but they are not rendered/visible in the Program Monitor.
Important comparison:
Guides work normally in a completely new Premiere project.
When it started:
The problem first appeared after updating from the previous Premiere 26.x version to Premiere 26.5.1.
Additional information:
I do NOT want to update to a newer Premiere version as a workaround. The issue needs to be investigated in Premiere 26.5/26.x.
