|
|
Post by Sepiana on Nov 3, 2020 11:06:13 GMT
and which portion of the filename highlighted blue ? up to the first dot or all the way to the last dot ? The whole file name got highlighted in blue. However, I was not interested in renaming the file (using no ".", or two or more "."). My earlier troubleshooting had already shown this was not the cause for the blank thumbnail. My goal was to change the file extension. The error message I got when I tried to open the file in Elements -- "Could not complete your request because it is not the right kind of document" -- was a dead giveaway. Elements was confused, not by the file name but by the file extension. Once I changed the file extension, a preview thumbnail was generated and the file opened in Elements. |
|
|
|
Post by tourerjim on Nov 18, 2020 15:22:45 GMT
Thank you all for your help and advise, however it was just nice of Sepiana to solve the blank file mystery and future 'Save As' will be, save_as_001 etc.
|
|
|
|
Post by Sepiana on Nov 19, 2020 1:23:18 GMT
Thank you all for your help and advise, however it was just nice of Sepiana to solve the blank file mystery and future 'Save As' will be, save_as_001 etc. Jim, you are very kind! I should thank you for bringing up this problem; it was a learning experience. Living and learning!  As this thread is a bit long and convoluted, here is a recap. Hopefully it will help those who may encounter this problem. PROBLEM:- Thumbnails were displayed blank in Windows Explorer; previews were not being generated. - Elements couldn’t open the files; this error message would pop up -- "Could not complete your request because it is not the right kind of document."- The file names included additional "." (periods). TROUBLESHOOTING:- Opened the problem files in Paint, saved them as JPEG picture. Note: Retained the additional "." in the file names. RESULTS:- The thumbnails are no longer blank; previews are being generated. - Elements will open the files; no error message. CONCLUSION:- Elements was not the culprit. - The inclusion of "." in the file names didn't cause the problem. |
|
