DIM wants to download and install all my content again after 4.11 install

So I launched DIM today and it told me I had an update to DIM available. My version was 64 bit and ending in 006. It installed and relaunched by itself and now it's 027 So I see some product updates in the list and lots of products installed.
I let DIM get the updates, which included DAZ 4.11, but apparently not the extra resources. I close DIM, launch 4.11 to see if there was a quick readme about new features. I close DAZ and go back to DIM. It does not list anything installed now and lots of files ready to download, and apparently some already downloaded and ready to be installed. But 0 products installed.
So I go back to DAZ 4.11 and try to load an actor and I see all my content in the Smart Content pane.
How do I get DIM to remember all the content that is currently installed?
Comments
SO DIM forgot where I was putting the install manifests and didn't know what to do. I tracked them down and pointed DIM at the right directory and the list of installed content is back.
I had a similar issue with Connect. Many of my previously installed products showed in Smart Content with the ! thumbnail and behaved as though they were not installed. I had to uninstall them, then reinstall and it fixed the issue. But, I spent about 3 hours going through my entire library fixing missing files after installing 4.11
Did you wait between closing/launching? One particularly sneaky gotcha is that both DIM and DAZ|Studio need access to the content database. The awkward bit is that some of the database updates don't finish until after the program has closed; this generally takes no more than a minute or three. If you look at the Task Manager, the Processes tab will show several instances of the program "postgres", this is the database controller running in the background. After the updating is completed, these instances will close.
But, and it's a big one, if you re-open DIM or D|S before the background tasks are finished, the database can hiccup in many weird and wonderful ways, including failing to launch at all. If you're jumping back and forth between DIM and D|S, always make sure the background stuff is finished in between times.