I use XpdfReader 4.0.4 on 2 corporate-imaged Windows 11 machines at work. Approximately 2025-05-15 to 16, XpdfReader's file open dialogue box on one of them started to take several dozen seconds to appear after pressing Ctrl+O. This is working off of the local drive rather than a network drive. I don't see that problem with 2 non-work machines that I use. I don't see a report of this problem on any Linux/Unix forums, so I suspect that it might be Cygwin's interaction with the Windows file system.
In case is caused by conflicting Cygwin packages (e.g., perhaps X-11 packages), I uninstalled Cygwin on the affected machine and re-installed Cygwin with the same packages as the unaffected machine. The problem persists.
The drive mappings are the same for both machines as are the Xresources that start up X-11. The bash and xpdf startup scripts are the same, so the conditions under which xpdf is launched should be the same, including environment variables.
What are some ways to track down the cause of this, from the perspective of a user who is familiar with Bash at a user level, but not familiar with underlying Unix systems (and often times, baffled by the X-windows documentation)?
The work machines are quite locked down, so even with temporary administrative privileges, the registry cannot be edited. Apps cannot be installed willy nilly.
Afternote: The affected machine has Windows 11 Enterprise 10.0.22631 Build 22631 while unaffected machine as Windows 11 Enterprise 10.0.26100 Build 26100. If it is due to a difference in Windows, then the change happened between those two builds.
