Hey Indra, sorry to see this! Is this coming up again and again, or did it only happen once? Did any of the steps shared in this thread work for you? We can take a closer look at it.
Yes, 2025, its still happening, you guys have had this issue as part of premier pro since i think 2022 was the first time I saw it, and yes, the steps here work but its a real hassle to have to do this every single time it happens, I often work on big projects that take about a month to complete and this has affected me on EVERY SINGLE ONE, why is this still happening? Having to rename a file in order to fix a bug thats persisted within the software for 3 years is rediculous and has to be fixed
Same here, cleaned my cache and worked. Recently got to my current company and there were cache files from years ago. Clear your cache and it is likely to work properly.
Inspired by one of the answers below, I simply renamed my project and it worked for me! Since 4.6k people looked for this thread, I supposed I'd share this simple trick.
I fixed this by creating a new project and then importing the project the search stopped working in.
I'm startring to realize that everytime Premiere has a new update, I should stop opening old projects and instead import them into a new project created with lastest version of Premiere.
Peter makes a good point. Also, it saves some possible anguish to delete the cache before using the new update. Or anytime some wonky behavior starts happening. (Hold down Shift as you start PP from it's normal icon, and respond to the dialog.)
Sorry for the poor experience. I have moved this thread to the Discussions sections for troubleshooting purposes. Since you only see this issue with a specific project, please try these steps and let us know if they help.
1. Launch Premiere Pro (do not open any projects), go to Window > Workspaces > uncheck "Import Workspaces from Projects.
2. Create a new project, go to Window > Workspaces, and choose one of the default Workspaces (other than the one you're currently using in case you're not using a custom Workspace).
3. Import your problematic project to the new project.