Why does it take up to 5 minutes to open PDF-eXPLODE for a couple of our Users in our Network?

ISSUE:

I reinstalled the license you released for me yesterday.   Post installation and configuration, when the user opens either the desktop shortcut or PDF-eXPLODE.exe from the install folder,  it takes close to 5 minutes before it displays.  

See the log lines below.

-------------------------------------------------------------------------------------------------------------------

3/10/2026 9:56:47 AM: Version 4.1.28.07.Nov 2022 Program Start - ******

3/10/2026 10:01:07 AM: PDFeXPLODE LOGs Folder path - C:\PDF-eXPLODE\LOGS\adam
3/10/2026 10:01:07 AM: PDF-eXPLODE INI file path: C:\PDF-eXPLODE\INIs\adam\PDFeXplode.ini
3/10/2026 10:01:07 AM: Temp Folder is : C:\PDF-eXPLODE\TEMP\adam\

3/10/2026 10:02:28 AM: Version 4.1.28.07.42307.Nov 2022 Program End - ******

------------------------------------------------------------------------------------------------------------------- 

ANSWER:

 It appears to me that the User may have a corrupt user profile which is a notorious "silent killer" for start-up performance, and it fits the timestamps shown in the log. 

• The First Hang (4 minutes, 20 seconds): 

9:56:47 AM: Program Start 

10:01:07 AM: Logs/INI path identified 

Analysis: This is the most significant delay. Between the moment the .exe is double-clicked and the moment it successfully identifies its own configuration files, over 4 minutes pass. This is almost certain that the program PDF-eXPLODE which reads the Registry on start-up to determine various environment variable values, start-up install folder and list of installed printers  on the target PC/server via the registry. It is possible that the Antivirus/EDR (Endpoint Detection and Response) scanning could be causing the delay, but the main culprit in most cases I encountered, has been a corruption of the Start-up User profile

• The Second Hang (1 minute, 21 seconds): 

10:01:07 AM: Paths identified

10:02:28 AM: Program End (User likely closed it or it timed out)

Analysis: Once the paths are known from the registry, it still takes 81 seconds to finish loading (or in this case, closing). If the user clicked  'Close' on the app intentionally immediately after 10:02:28 AM,  then this suggests that the app closed 1 minute 21 seconds after requesting a close. This usually points to an additional issue of Printer communication. The software is likely struggling to "handshake" with the PDF-eXPLODE printer driver or a default system printer that is offline/unreachable.

Why does PDF-eXPLODE take so long to display, yet others don't?

Unlike a lot of other programs, at the start up, PDF-eXPLODE needs to query the registry to find its license, the install folder , environment variables and printer settings. This leads us to believe one of 2 issues exists here:

1. If the pdfexplode.ini found in [install_folder_path]\INIS\%User%\ folder is corrupt, it may cause issues when opening PDF-eXPLODE to read the contents of the file and then to assign them to various global variables in memory   OR 
2. The User's profile (C:\Users\%User%\ folder, sub-folders and login script may be corrupted. This is a far more serious issue with starting and using PDF-eXPLODE.

When a Windows profile is damaged, the OS struggles to resolve basic environmental variables and registry hives (like HKEY_CURRENT_USER). At start up, PDF-eXPLODE queries the Window's registry key {HKEY_LOCAL_MACHINE} in addition to other keys previously mentioned. In the log, at the 9:56:47 AM mark, a corrupt profile would cause Windows to hang while it repeatedly retrying those registry calls.

Here is how you can confirm if it’s the profile:

• Registry Latency: PDF-eXPLODE queries the registry to find its installation path and the PDF-eXPLODE printer. If the user's registry hive is bloated or corrupt, every "Read" command takes ages.
• Folder Redirection: If their "Documents" or "AppData" folders are redirected to a network drive, and the profile is flaky, the app will hang while the OS tries to resolve those paths.
• The  Subfolders: I noticed the log uses ...\LOGS\adam. If "Adam" is the Windows username, and his profile is corrupted, the app will struggle to get permission to even see those folders, even if they are local.

How to Test this:

Can you get a different user or  any non-admin person to perform these two quick tests to narrow it down: 

1. Have a different user log into that same computer and launch PDF-eXPLODE. I assume when you installed PDF-eXPLODE, you selected ‘for use with all Users’

• If it opens instantly,  then "Adam" profile is definitely corrupt.
• If it's still slow: It’s a system-wide issue (Antivirus or Printer Driver).

Note:

• We do NOT believe this is an Anti-Virus scanning issue. It would help by creating an Exclusion or Exception (normally available under Advanced Settings) for the Install folder - (if default used) --> C:\PDF-EXPLODE (folder) and the App EXE C:\PDF-EXPLODE\PDF-EXPLODE.EXE (file) so that it would benefit Print or Exploding processing or both
• Do not attempt to uninstall and reinstall PDF-eXPLODE. It will serve no purpose.

 Recommendation for the User

If the "Different User" test proves the profile is the issue, the most effective solution seems to be (based on 10 Client sites acreoss US, UK, Australia and Europe was  to rebuild the Windows user (Adam) profile.  This involves recreating  C:\USERS\ADAM\ Folder with contents and the login script. This will regenerate the NTUSER.DAT db for this user. However your IT department may want to investigate and fix these first: 

1. Registry Permissions:  Grant the User FULL CONTROL over the following registry keys: 

      

   

   HKEY_CURRENT_USER\Software\VB and VBA Program Settings\PDF-eXPLODE ---> (application)

   HKEY_CURRENT_USER\Software\VB and VBA Program Settings\PDFeXPLODE  ---> (printer)

2. NTFS Folder Permissions:  Ensure the User has FULL CONTROL permissions over the [install_folder] and sub-folders (C:\PDF-EXPLODE\)

If  the above 2 suggestions don't make a difference in the start-up of PDF-eXPLODE.EXE, then rebuild the User Profile thereby regenerating a new NTUSER.DAT db for this User.