@sphere:

What I'm most interested in is a local directory and photo organizer. I'm curious if the face recognition still works in isolation from Google?
...As an aside, it looks like there is a Picasa import for lightroom utility
http://picasa-lightroom.com/

-sphere (April 23, 2019, 10:00 PM)

Regarding Lightroom: Thanks re the Lightroom utility. Looks potentially rather useful

Regarding face recognition: In Picasa, face recognition seems to have always been independently carried out by the desktop app and thus not requiring any online Cloud-based/Google functionality, unless you wanted to link people's names/faces with their email address (the database for which would be in your online Gmail account). I therefore find it curious and somewhat telling that the Google marketing push - effectively shutting down Picasa and only partially replacing it with a new offering (Google Photos) - was to force the user into a seemingly unnecessary (i.e., not a user requirement or benefit) and sole reliance on Cloud functionality, thereby apparently creating/ensuring an increasingly more captive audience and owning unfettered access to an increasingly large amount of users' data (i.e., including the image databases).

Some people (not me, you understand) might say that Google - like Facebook - is decidedly NOT your "friend", but merely a very successful marketing data miner and and corporate psychopath that - rather like the US NSA - considers the user's right to privacy to be an annoying nuisance to be variously trampled upon or evaded at all costs, but I couldn't possibly comment.

@mouser: Nope, the gotcha is still there after boot-up has completed with R:\Temp running OK.
As soon as CHS is restarted after setting the CHS Tweaks to Force to system Temp directory, the error:
   Error DBG103: DBISAM Engine Error # 11013 Access denied to table or backup file '124120'
 - pops up and and CHS is without any settings.
Whilst CHS is still thus active, I go into CHS to change the Tweaks, and this error pops up again:
   Error DBG103: DBISAM Engine Error # 11013 Access denied to table or backup file '124120'

I then set CHS Tweaks back to Let database engine decide and then terminate CHS and restart it. CHS then seems to start up just fine, with all settings correct as previously.
This seems to be consistently repeatable.

However, CHS is definitely "allergic" to the ImDisk RAMdisk under this current version of Win10-64 Home, whereas it was perfectly OK using that RAMdisk under Win10-64 Pro.
I presume that the likely cause could be some vestigial Registry entry in this Home version which remains even after fast startup has been disabled. I shall try to research that as I'd like to know.
It might be worth identifying exactly what CHS looks at when the user sets CHS Tweaks to Force to system Temp directory, as a good starting-point, because that's when the error is triggered - e.g., whether it checks the Registry for anything at that point.

As far as any other apps being similarly afflicted by this mysterious error, so far there's still been no sign. Pretty much everything that has to use system Temp will need to be happily using that ImDisk RAMdisk. Apart from CHS, everything else seems stable with it, so far.    :o

@Ath + @Shades: Thanks for trying to help.

The files (in the CHS database) in question are definitely unticked in the Read-only attribute. I have double-checked this, as I initially thought that would probably be the problem, even going so far as to enforce them to be unticked again. It made no difference though.

The files are in a directory on the C:\  drive, which is where they have always been since I started using CHS. The drive location has never been a problem before, anyway, so I don't see how/why it could be a problem now. It doesn't seem to be a problem, at any rate.