OK, found it! I may have typo'd the path name but I had a screen shot of the actual error so I got there anyway.

BUT my version is 2.1.8.2751

Regarding this update, my IT manager is recalling that this problem existed on the previous ledger update so I guess this problem may have been around for a while...