Cannot access file metadata from Windows v1809


  1. Posts : 29
    Windows 10 Professional (x64) (build 16299)
       #1

    Cannot access file metadata from Windows v1809


    This is a bit of a head scratcher.

    I am migrating from one PC to the other, both using Windows 10, but different builds. My problem is that I cannot access some of the file metadata from Windows v1809 (the new computer).

    A complicated process that I run weekly relies on being able to access the Title of each of some 3000 PDF files. This Title changes when a genuinely new file is created. The actual file name does not. All 3000 are recreated every week by the source regardless of whether there is any change, so I cannot rely on creation date. I can then identify new and old files by comparing with last week.

    I access the Title by using the GetDetailsOf function, running within Excel VBA. The Title can also be viewed under the PDF information tab if you look at Properties within File Manager. It also pops into view if you hover over the file nameOn the new PC GetDetails returns a null string rather than the Title. Not much chance of detecting what is new when all files are called ".pdf"!

    After pursuing a few red herrings, I realised that it was unlikely to be my coding, as the PDF Information tab was not visible any more, nor did the Title reveal itself when hovering.The Title is visible using a modest bit of free software called PDFill PDF Tools, so the Title still exists. However, with 3000 files this has to be done programatically and the chance of being able to do that from VBA is almost certainly zero!

    The first PC is v1803 (build 17134.648) and uses Office 2010. The computer was upgraded from Windows 7, which went OK.

    The second PC uses v1809 (build 17763.379) and uses Office 365.

    So ... the Title info that I need is there but something has been done to Windows 10 that blocks access to it (unless somehow it is related to it being a new build rather than an upgrade, which seems unlikely). It cannot be Office 365 because File Manager no longer supports the two manual methods of seeing the Title either.

    Any ideas welcome!
      My Computer


  2. Posts : 43,212
    Win 10 Pro (22H2) (2nd PC is 22H2)
       #2

    Hi, if you install a free program called File metadata
    CodePlex Archive
    (rather interesting..)

    and choose to configure pdf files using its configuration utility (available from the start menu)
    then you gain the ability to view/edit various fields in Properties/Details sheet and in the Details view pane in file explorer.

    The title still isn't shown in the infotip, however.

    I have one PC with this configured, and that works, and another without it, where no title field etc is shown. Both 1809.
      My Computers


  3. Posts : 29
    Windows 10 Professional (x64) (build 16299)
    Thread Starter
       #3

    Thanks Dalchina.

    I'll try that tomorrow, though it will be a very pleasant surprise if I can operate it from within VBA!

    Is this a known issue with 1809? Unless there is a security issue with metadata being editable, I can't see why any sensible software company would deliberately remove this functionality.
      My Computer


  4. Posts : 43,212
    Win 10 Pro (22H2) (2nd PC is 22H2)
       #4

    I've not come across this anywhere before... perhaps few use title in this way. As you probably know 1809 had many many problems. Could be interesting to get the view of someone using Insider builds on this.

    Before:
    Cannot access file metadata from Windows v1809-untitled.png
    After:
    Cannot access file metadata from Windows v1809-untitled2.png
      My Computers


  5. Posts : 29
    Windows 10 Professional (x64) (build 16299)
    Thread Starter
       #5

    On a quick inspection, File Association Manager would enable me to add a Title but not to view the Title that already exists. I could be wrong...

    ... but to my surprise I find I can use good ol' unreliable Sendkeys to grab the Title and stick it in a cell, which of course I can then use as a variable if necessary. I know Sendkeys is frowned upon but it has never actually let me down in the past.

    I can post the code if required but basically it involves sending keystrokes to the free PDF handling program to tab to the right button, select the button, feed in the (variable) file name, copy the Title, then more tabbing to exit. Select a cell on my worksheet, paste the value and it's done.

    Looping through 3000 files is the next step but the logic should be pretty simple (he wrote with misplaced confidence).

    I really didn't expect this to work at all...
      My Computer


  6. Posts : 29
    Windows 10 Professional (x64) (build 16299)
    Thread Starter
       #6

    To update on this...

    While Sendkeys "works" up to a point, it depends very much on the right window being open at the right time, which in practice seems to mean putting in Application.Wait commands to keep things in sync. Even then I doubt it would be reliable cycling through 3000 iterations in a macro. I got it up to about 300 before a crash but that took best part of an hour, so even if it did work a procedure which was taking 30 seconds accessing the attributes through Windows would take hours using Sendkeys. So I am going to have to look for another solution.

    Can anyone confirm that v1809 (or at least my build) does not have the functionality to access extended file metadata and that there is no "magic switch" somewhere in Settings which would bring the capability back?

    It would also be "interesting" to know whether it was done intentionally or by accident and if a future upgrade might bring it back.
      My Computer


  7. Posts : 43,212
    Win 10 Pro (22H2) (2nd PC is 22H2)
       #7

    I'm pretty sure the utility is the only hope there is of improving this: from their site and the link I quoted:
    In Windows XP, Explorer could see and edit metadata (for example comments or tags) for any type of file. In Vista and later, this has been possible only for certain types of file, such as Office documents, JPEGs and MP3s.

    It is pretty clear that Microsoft originally intended to ship a broader capability. What this package does is wire together pieces that were built into Windows in readiness, but never joined up: it connects Explorer's ability to see and edit metadata with NTFS's support for storing property data in an annex to any file, and so allowing metadata to be added to files of any type. And because Windows Search uses the same property system hooks as Explorer, you can also search using this metadata, both in Explorer and from the Start Menu (or Search charm). That all this takes just a 19K DLL (64-bit, release build) and some registry settings tells you how close Microsoft got.

    One reason why Microsoft never shipped the complete solution is that all works well when the file is moved around between NTFS drives, but the metadata is lost when a file is, say, emailed, or moved to a FAT file system. Also, if your files are still being edited, then you need to check that associated metadata is preserved on save. Some file editors, rather than update the file in place, save updates using a write-new-file, delete-original-file, rename-new-to-original strategy that loses any metadata held in the annex to the original file.
    You do need to be aware of these limitations, but think of being able to add metadata to txt files, pdfs, anything, editable directly in Explorer! And because XP used the same storage mechanism for the general case (see XP, Vista and File Metadata for the full story), this package will also read some metadata written under XP, hidden by a Windows upgrade, and invisible ever since . Also, to help with unfriendly editors and non-NTFS transfers, the installation optionally sets up an Explorer context menu that lets you right click on a file to export its metadata to a separate XML file, and import it again to reapply it to the original file (or indeed to a different file). If you want to back up all your metadata, then there is also a command line utility for bulk metadata export and import that works with the same XML file format.
      My Computers


  8. Posts : 29
    Windows 10 Professional (x64) (build 16299)
    Thread Starter
       #8

    Solved - access to extended PDF metadata


    Solution!

    On another forum, I was (slowly!) persuaded that this wasn't about Windows as such but that some utility must have been giving me the capacity to access additional PDF metadata. I installed the File Metadata management program to which you had pointed me on the old PC as well and - glory be - it showed a handler for PDFs, describing it as "PDF-XChange PDF Property Handler."

    This came from a program PDF-XChange Viewer which I had trialled for quite different reasons but never used in anger. Without my realising it, it had added functionality which I was then able to exploit using VBA. This Viewer is free and still available (though development work is now concentrated on PDF-XChange Editor. I installed it on the new PC - and there were the extra metadata, visible as before via File Explorer and also available to VBA!

    I still think this should be bog standard Windows functionality for a common file type, particularly as the Title will often document archived files better than the file name. In this example, there was individuality in the Titles field which was missing from the file name, because successive editions were given the same file name in order to catch a standard link. I think that is quite common where you have almost a "time series" of documents.

    One moral is NOT to dejunk your PC too vigorously, or I would have lost the facility without having a clue how to reinstate it. Another is not to assume the cause of a symptom! Eventually I started looking down the right end of the telescope. And in the end the File Metadata program, although it was not the answer itself (as it gave no access to existing Title data) it identified the utility which was. So thanks very much for your help.
      My Computer


  9. Posts : 43,212
    Win 10 Pro (22H2) (2nd PC is 22H2)
       #9

    Interesting that there's metadata - and then there's metadata. Glad you solved it.

    Considering the OS, as you know pdf (e.g.) is not a native filetype. And as you know, authors are free to define their own file types and programs are free to add them. (e.g. docx, xlsx ....)

    The OS is conventionally a framework - the bare structure- that provides a layer of abstraction: programs use it to provide higher levels of functionality.

    For example, Windows search requires support for content indexing from ifilters. Again, you need a pdf ifilter to search pdf content, and similarly for othe file types. In general, I rather think confusion has arisen about what to expect from an OS because so many utlities and programs are provided with Windows.
      My Computers


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 08:21.
Find Us




Windows 10 Forums