Search for a folder similar to this:

C:\Users\Bob\AppData\Roaming\StageManager.BD092818F67280F4B42B04877600 987F0111B594.1\Local Store

Of course the user name and those numbers will likely be different.

Delete it. You’ll lose any local folios but that should hopefully get you up and running again.

I have hidden files viewable on my system. If a search doesn’t show this you may have to do that on yours.

Bob

You can also relink a folio to an InDesign document using the relink function in the folio builder panel.

I'll echo what Neil says with a little more hammer. You don't want to build any sort of workfow that relies on direct manipulation of the folio files on your drive. The file format changes almost every release, the file format for each release is tied to a viewer version of an app built for consuming those folios. If you try and mess with the files, you will break the ability for your app to read those files or the distribution service to deliver those files.  Maybe not immediately, but eventually.

The DPS team has a lot of experience watching the acrobat team write enormous amounts of code into acrobat reader in an attempt to read and render "bad" pdf files. PDF has had a well publicized file format for years and yet many applications still can't write valid pdf. The world of digital publishing is changing too rapidly at this time to allow any 3rd party manipulation of folios, instead we've tried providing a single source of folio generation (the digital publishing plug in) and a variety of ways to drive that plug in via UI, scripting and other SDK's.

create the folio in the cloud, package up the InDesign files, move them to a new computer, relink the cloud based folio to the path of the InDesign file on the different machine.

If you are using local (offline) folios...it's simpler to just recreate the folio after you move the Indesign files to a different computer. Local folios take very little time to create. If you do it often, create a sidecar.xml file to help automate the process.